Warning method, device, system and equipment for task collection and dispatch and storage medium

Abstract

The invention provides a collection and dispatch task early warning method, device, system and equipment and a storage medium, and relates to the technical field of intelligent logistics. The method comprises the following steps: acquiring real-time information of a waybill, wherein the real-time information of the waybill comprises expected performance time; carrying out collection and dispatch operation link identification on the real-time information of the waybill, and generating a link to be evaluated of the waybill; according to the link to be evaluated and a pre-stored historical practical operation link time length, calculating a total time length of the task to be dispatched; obtaining a journey duration corresponding to the waybill; calculating overtime early warning time according to the total time length, the journey time length and the expected performance time of the asking and dispatching task; and generating a timeout early warning message according to the timeout early warning time, and sending the timeout early warning message to the user client. According to the method and the device, the timeout early warning message can be finely pushed, clearer collection and dispatching operation guidance is provided for front-line couriers, and the processing efficiency of collection and dispatching tasks is improved.

Description

Background Art

[0002] At present, placing orders through online platforms has become the main way for customers to place orders and send parcels. After customers place orders through official websites, WeChat and other online channels, the dispatch system assigns the orders to couriers for collection, and the couriers accept, transfer or return the orders.

[0003] In the related art, a timeout warning is usually sent to the courier, and a time point for the warning is obtained by the difference between the expected fulfillment time of the user and the timeout warning time. However, the above warning method is too rough, and it is easy to cause the collection timeout or even serious timeout without knowing it, and the warning effect is poor.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present disclosure provides a collection and dispatch task warning, device, system, equipment and storage medium, which at least to a certain extent overcome the problems in the related technology of easy collection and dispatch timeout or even serious timeout without knowing it and poor warning effect.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of the present disclosure, a method for warning of a collection and dispatch task is provided, comprising: obtaining real-time information of a waybill, the real-time information of the waybill including an expected fulfillment time; identifying the collection and dispatch operation links of the real-time information of the waybill, and generating a link to be evaluated of the waybill; calculating the total duration of the collection and dispatch task based on the link to be evaluated and the pre-stored historical practical operation link duration; obtaining the journey duration corresponding to the waybill; calculating the timeout warning time based on the total duration of the collection and dispatch task, the journey duration and the expected fulfillment time; generating a timeout warning message based on the timeout warning time, and sending the timeout warning message to a user client.

[0008] In one embodiment of the present disclosure, when multiple waybills are obtained, sending the timeout warning message to the user client includes: determining the priority of each waybill and giving priority to pushing the timeout warning message with a high priority.

[0009] In one embodiment of the present disclosure, after sending the timeout warning message to the user client, the method further includes: if the processing completion information sent by the user client is not received within a preset time, generating a new timeout warning message and sending the new timeout warning message to the user client.

[0010] In one embodiment of the present disclosure, the total duration of the pick-up and dispatch task is calculated based on the link to be evaluated and the pre-stored historical practical link duration, including: sending the link to be evaluated to a data processing subsystem, so that the data processing subsystem predicts the duration of the link to be evaluated based on the historical pick-up and dispatch task duration; receiving the duration of the link to be evaluated returned by the data processing subsystem; and obtaining the total duration of the pick-up and dispatch task based on the duration of the link to be evaluated.

[0011] In one embodiment of the present disclosure, the duration of the historical practical operation link is calculated by the tracking data of the pickup and dispatch practical operation link reported by the user client and stored in the data processing subsystem, wherein one pickup and dispatch practical operation link corresponds to one historical duration value.

[0012] In one embodiment of the present disclosure, obtaining the journey duration corresponding to the waybill includes: sending the current location information of the user client and the destination address data of the pick-up and delivery task to the positioning subsystem, so that the positioning subsystem calculates the journey duration based on the current location information of the user client, the destination address data of the pick-up and delivery task and the historical operation trajectory of the user client; and obtaining the journey duration sent by the positioning subsystem.

[0013] According to another aspect of the present disclosure, a device for warning of a pickup and dispatch task is also provided, including: a first acquisition module, used to acquire real-time information of a waybill, wherein the real-time information of the waybill includes an expected fulfillment time; a link identification module, used to identify the pickup and dispatch operation link of the real-time information of the waybill, and generate a link to be evaluated of the waybill; a first calculation module, used to calculate the total duration of the pickup and dispatch task based on the link to be evaluated and the pre-stored historical practical operation link duration; a second acquisition module, used to acquire the journey duration corresponding to the waybill; a second calculation module, used to calculate the timeout warning time based on the total duration of the pickup and dispatch task, the journey duration and the expected fulfillment time; a timeout warning module, used to generate a timeout warning message based on the timeout warning time, and send the timeout warning message to a user client.

[0014] According to another aspect of the present disclosure, a collection and dispatch task warning system is also provided, the system comprising a collection and dispatch background subsystem, a waybill subsystem, a data processing subsystem, a positioning subsystem and a user client, wherein the waybill subsystem is used to store real-time information of the waybill; the collection and dispatch background subsystem is used to obtain real-time information of the waybill, the real-time information of the waybill includes expected fulfillment time; the collection and dispatch operation link is identified based on the real-time information of the waybill, and the link to be evaluated of the waybill is generated; the data processing subsystem is used to store the duration of historical practical operation links; the positioning subsystem is used to determine the expected fulfillment time based on the user's request; The real-time location of the user client and the destination location of the waybill are used to determine the journey duration corresponding to the waybill; the collection and dispatch backend subsystem is also used to calculate the total duration of the collection and dispatch task according to the to-be-evaluated links and the pre-stored historical practical link durations; obtain the journey duration corresponding to the waybill; calculate the timeout warning time according to the total duration of the collection and dispatch task, the journey duration and the expected fulfillment time; generate a timeout warning message according to the timeout warning time, and send the timeout warning message to the user client; the user client is used to receive the timeout warning message so that the user can process the waybill.

[0015] According to another aspect of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the above-mentioned method for early warning of dispatching tasks by executing the executable instructions.

[0016] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned method for early warning of the task of soliciting and dispatching is implemented.

[0017] According to another aspect of the present disclosure, a computer program product is provided, which includes a computer program or computer instructions, and the computer program or the computer instructions are loaded and executed by a processor to enable a computer to implement the above-mentioned task warning method.

[0018] In the disclosed embodiment, real-time information of the waybill is obtained, and the real-time information of the waybill includes the expected fulfillment time; the collection and delivery operation link is identified for the real-time information of the waybill, and the to-be-evaluated link of the waybill is generated; the total duration of the collection and delivery operation is calculated based on the to-be-evaluated link and the pre-stored historical practical operation link duration; the journey duration corresponding to the waybill is obtained; the timeout warning time is calculated based on the total duration of the collection and delivery task, the journey duration and the expected fulfillment time; based on the timeout warning time, a timeout warning message is generated, and the timeout warning message is sent to the user client, so that the timeout warning message can be pushed in a refined manner, and more clear guidance on the collection and delivery operation can be provided to the front-line couriers, thereby improving the processing efficiency of the collection and delivery tasks.

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

[0020] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0021] Figure 1 The following is an architecture diagram of a warning system for task dispatching provided by an embodiment of the present disclosure;

[0022] Figure 2 A flow chart of a method for early warning of a task dispatching provided by an embodiment of the present disclosure is shown;

[0023] Figure 3 A flowchart of another method for early warning of a task dispatching provided by an embodiment of the present disclosure is shown;

[0024] Figure 4 A flow chart of another method for early warning of a task dispatching provided by an embodiment of the present disclosure is shown;

[0025] Figure 5 A flow chart showing a method for obtaining the total duration of a pickup and dispatch operation provided by an embodiment of the present disclosure is shown;

[0026] Figure 6 A flow chart of a method for obtaining journey duration provided by an embodiment of the present disclosure is shown;

[0027] Figure 7 A specific example flow chart of a task warning method provided by an embodiment of the present disclosure is shown.

[0028] Figure 8 A schematic diagram showing the structure of a warning device for a task dispatching provided by an embodiment of the present disclosure is shown;

[0029] Fig. 9 A structural block diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0030] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0031] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0032] Figure 1 An exemplary system architecture 100 is shown to which the method for early warning of a task to be dispatched or the device for early warning of a task to be dispatched according to an embodiment of the present disclosure may be applied.

[0033] like Figure 1 As shown, the system architecture 100 may include a user terminal 110 , a network 120 and a server 130 .

[0034] The network 120 is used to provide a medium for a communication link between the user terminal 110 and the server 130, and may be a wired network or a wireless network. The network 120 may include various connection types, such as wired or wireless communication links or optical fiber cables.

[0035] A user may use the user terminal 110 to interact with the server 130 via the network 120 to receive or send messages.

[0036] The user terminal 110 may be any electronic device having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, a display screen, and a desktop computer.

[0037] Various communication client applications may be installed on the user terminal 110, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. The waybill submitted by the first user and the real-time information of the waybill may be obtained through the communication client application. The courier or other personnel may use the user client to receive timeout warning messages sent by the collection and delivery backend subsystem.

[0038] It should be noted that the client of the application installed on the user terminal 110 is the same, or the client of the same type of application based on different operating systems. Based on the different terminal platforms, the specific form of the client of the application can also be different, for example, the application client can be a mobile client, a PC client, etc.

[0039] The server 130 may be a server that provides various services, such as a backend management server that provides support for shopping websites browsed by the user using the user terminal 110. The backend management server may analyze and process received waybill requests, etc., and obtain processing results (such as timeout warning messages, etc.) and feed them back to the client of the user terminal used by the courier.

[0040] Optionally, server 130 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0041] It should be noted that the task warning method provided in the embodiment of the present disclosure is generally executed by a server, and accordingly, the task warning device is generally arranged in the server.

[0042] Those skilled in the art will know that Figure 1 The number of user terminals, networks and servers in the embodiment is only for illustration, and any number of user terminals, networks and servers may be provided according to actual needs. The embodiments of the present disclosure are not limited to this.

[0043] In related technologies, couriers can configure the timeout warning threshold on the application APP installed on the user terminal according to their needs. For example, the warning starts 30 minutes before the end time of the waybill fulfillment, and then the system polls the orders that are about to time out at an interval of 5 minutes, and pops up a window to remind the courier one by one for all orders that are about to time out without distinction. However, the above warning method cannot be too rough, lacks an estimated calculation of the actual operation time of collection and delivery, and cannot be more refined. In the case of a large number of timeout warning tasks, the courier cannot know the timeout tasks that need to be handled first, which affects the customer's experience of receiving and sending parcels and reduces the courier's collection and delivery time efficiency.

[0044] Based on this, an embodiment of the present disclosure provides a method for warning of a collection and delivery task, which obtains real-time information of a waybill, and the real-time information of the waybill includes the expected fulfillment time; the collection and delivery operation links are identified based on the real-time information of the waybill, and the link to be evaluated is generated for the waybill; the total duration of the collection and delivery operation is calculated based on the link to be evaluated and the pre-stored historical practical operation link duration; the journey duration corresponding to the waybill is obtained; the timeout warning time is calculated based on the total duration of the collection and delivery task, the journey duration and the expected fulfillment time; a timeout warning message is generated based on the timeout warning time, and the timeout warning message is sent to the user client, so that the timeout warning message can be pushed in a refined manner, and more clear guidance on collection and delivery operations can be provided to front-line couriers, thereby improving the processing efficiency of collection and delivery tasks.

[0045] It should be pointed out that the embodiments of the present invention and the technical features therein may be combined with each other without conflict.

[0046] The present exemplary implementation is described in detail below with reference to the accompanying drawings and embodiments.

[0047] First, a method for early warning of a pick-up and dispatch task is provided in an embodiment of the present disclosure, and the method can be executed by any system with computing and processing capabilities. The method for early warning of a pick-up and dispatch task provided in an embodiment of the present disclosure can be executed by a server, for example, by a pick-up and dispatch backend subsystem configured on the server.

[0048] Figure 2 A flowchart of a task warning method provided in an embodiment of the present disclosure is shown. Figure 2 As shown, the task early warning method provided in the embodiment of the present disclosure includes the following steps:

[0049] S202: Acquire real-time information of the waybill, where the real-time information of the waybill includes the expected fulfillment time.

[0050] In S202, the waybill may include at least the customer information of the ordering party, the destination address information, the expected fulfillment time, and the relevant information of the collection waybill or the delivery waybill. The expected fulfillment time is the expected collection time or the express delivery time of the item filled in by the user when placing the order. The destination address information is the location information of the customer who placed the order. The relevant information of the collection waybill or the delivery waybill may include the relevant operations that the customer submits when placing the order, such as unpacking inspection, packaging, etc.

[0051] In one embodiment, after a customer places an order through an application installed on a customer terminal, the real-time information of the waybill is stored in a waybill subsystem, and the waybill subsystem can uniformly process and manage different waybills in real time.

[0052] S204: Identify the collection and dispatch operation links of the waybill based on the real-time information of the waybill, and generate the link to be evaluated of the waybill.

[0053] The real-time information of the waybill is used to identify the collection and delivery operation links. On the one hand, the identification result may include the waybill type, which can be divided into collection waybill and delivery waybill; on the other hand, the identification result also includes the necessary practical operation links contained in the waybill.

[0054] For the collection of waybills, the necessary practical steps that need to be identified include one or more of the following:

[0055] Whether the collection waybill needs to be weighed;

[0056] Whether the collection waybill needs to be unpacked for inspection, photographed and uploaded;

[0057] Whether the collection waybill requires on-site real-name authentication by the user;

[0058] Whether the collection waybill needs to be packaged for consumables;

[0059] Whether the collection waybill requires any other special manual processing.

[0060] For delivery of waybills, the necessary practical steps to be identified include one or more of the following:

[0061] Whether the delivery waybill needs to be photographed and uploaded;

[0062] Whether the delivery waybill requires on-site unpacking and inspection of the goods by the customer;

[0063] Whether the delivery waybill requires the user to sign on site for receipt;

[0064] Whether the delivery waybill requires any other special manual processing.

[0065] It should be noted that the identification of the links in the pickup and dispatch operation may include links that have not been obtained and are to be evaluated, or may include multiple links that are to be evaluated, and this disclosure does not make any specific limitation.

[0066] S206. Calculate the total duration of the pickup and dispatch operation based on the duration of the link to be evaluated and the pre-stored historical practical operation links.

[0067] It should be noted that the duration of the historical practical operation is calculated from the tracking data of the pickup and dispatch practical operation reported by the user client and stored in the data processing subsystem, where one pickup and dispatch practical operation corresponds to one historical duration value.

[0068] Exemplarily, the duration of historical practical operations can be calculated based on the historical collection and delivery practical operation data reported by the current courier over a period of time. For example, the average duration of each historical practical operation link can be calculated based on the collection and delivery practical operation data reported by the current courier in the past month as the historical practical operation duration of the corresponding link.

[0069] Exemplarily, the historical practical operation duration of the current courier may be weighted and summed with the historical average of the enterprise to obtain the historical practical operation duration.

[0070] S208: Obtain the journey time corresponding to the waybill.

[0071] The journey time is the time between the current courier's location and the destination address of the waybill, and the journey time can be estimated by the positioning subsystem. The positioning subsystem can be a geographic information system (GIS) map system, etc.

[0072] S210. Calculate the overtime warning time based on the total duration of the pick-up and delivery task, the journey duration and the expected fulfillment time.

[0073] In one embodiment, the timeout warning time can be calculated by the difference between the expected fulfillment time and the current time, the total duration of the link to be evaluated, and the journey duration.

[0074] For example, a customer places an order at 9:00 a.m. and expects the courier to pick up the package within an hour, that is, the expected fulfillment time T1 is 10:00. If the current time T0 is 9:10, the system estimates that the total duration T2 of the link to be evaluated is 5 minutes, and the journey time T3 is 20 minutes, then the timeout warning time Ta = (T1-T0)-T2-T3=50min-5min-20min=25min.

[0075] It should be noted that the timeout warning time calculated above is the minimum time required for the courier to process the above waybill. During the implementation of the collection and delivery task, it may be impossible to guarantee that the processing of each waybill can be carried out within the minimum time due to factors such as road conditions and courier status. Therefore, the timeout warning time can be superimposed with a preset compensation value on the basis of the minimum time. The preset compensation value can be determined according to the actual situation. For example, the preset compensation value is configured to 5 minutes, 10 minutes, etc., which is not specifically limited in the present disclosure.

[0076] Continuing with the above example, if the preset compensation value is configured as 5 minutes, the timeout warning time is 30 minutes.

[0077] S212: Generate a timeout warning message according to the timeout warning time, and send the timeout warning message to the user client.

[0078] The above-mentioned timeout warning message is used to remind the courier to process the above-mentioned waybill in time. The timeout warning message may include other information such as the waybill number, the destination address of the waybill, etc.

[0079] It should be noted that when the timeout warning time is calculated, the sending time of the timeout warning message can be determined according to the expected fulfillment time and the timeout warning time. When the above sending time arrives, the collection and dispatch backend subsystem sends a timeout warning message to the user client.

[0080] In the disclosed embodiment, real-time information of the waybill is obtained, and the real-time information of the waybill includes the expected fulfillment time; the collection and delivery operation link is identified for the real-time information of the waybill, and the to-be-evaluated link of the waybill is generated; the total duration of the collection and delivery operation is calculated based on the to-be-evaluated link and the pre-stored historical practical operation link duration; the journey duration corresponding to the waybill is obtained; the timeout warning time is calculated based on the total duration of the collection and delivery task, the journey duration and the expected fulfillment time; based on the timeout warning time, a timeout warning message is generated, and the timeout warning message is sent to the user client, so that the timeout warning message can be pushed in a refined manner, and more clear guidance on the collection and delivery operation can be provided to the front-line couriers, thereby improving the processing efficiency of the collection and delivery tasks.

[0081] Figure 3 Another method for early warning of a task dispatching provided by an embodiment of the present disclosure is shown in the flowchart. Figure 2 Based on the embodiment, S212 is further refined to define the situation when the user client has multiple waybills and at least two waybills are about to time out. Figure 3 As shown, the method for early warning of the task of taking over and dispatching provided by the embodiment of the present disclosure includes S202 to S210 and S312. Specifically, the method includes:

[0082] S312: When multiple waybills are obtained, the priority of each waybill is determined, and high-priority timeout warning messages are pushed first.

[0083] It should be noted that the specific implementation method of S202 to S210 in this embodiment is the same as the implementation method of S202 to S210 in the aforementioned embodiment, and will not be repeated here.

[0084] The priority of waybills can be determined based on the waybill type. Waybills with strict fulfillment time requirements and high risk of overtime warning can be identified. For example, fresh food orders and orders where customers have mandatory fulfillment time requirements. The above types of orders can be configured as high-priority waybills, and orders that are not marked with the above information can be configured as low-priority orders.

[0085] Exemplarily, the identified high-priority orders may be marked to facilitate determining the priority of the orders.

[0086] In one embodiment, when at least two waybills that are about to time out are both high-priority waybills, the timeout warning message can display the number of high-priority waybills on the user client, or it can display the relevant information of at least two waybills that are about to time out on the user client one by one, forcing a pop-up window to remind the courier to process it immediately. Only after processing such orders and completing the collection and delivery operations in priority can other collection and delivery tasks be performed.

[0087] In the embodiments of the present disclosure, by identifying the priority of the waybill and giving priority to pushing high-priority timeout warning messages, the push of timeout warning messages is further refined, providing couriers with clearer guidance on collection and delivery operations, thereby improving the processing efficiency of collection and delivery tasks.

[0088] Figure 4 A flowchart of another method for early warning of a task dispatching provided by an embodiment of the present disclosure is shown. Figure 2 or Figure 3 On the basis of the embodiment, after S212, S214 is added to limit the situation of whether the courier handles the timeout warning message. Figure 4 As shown, the method for early warning of the task of taking over and dispatching provided by the embodiment of the present disclosure includes S202 to S214. Specifically, the method includes:

[0089] S214: If the processing completion information sent by the user client is not received within the preset time, a new timeout warning message is generated and sent to the user client.

[0090] It should be noted that the specific implementation of S202 to S210 of this embodiment is the same as the specific implementation of S202 to S210 of the aforementioned embodiment, and will not be repeated here.

[0091] The preset time in the above S214 can be pre-configured in the collection and dispatch backend subsystem. The preset time can be set according to actual conditions. For example, the preset time is 5 minutes, that is, if the processing completion information sent by the user client is not received every 5 minutes, a new timeout warning message will be resent.

[0092] The processing completion information sent by the user client may be determined according to the actual situation, for example, it may be a preset character string, number, text or other information.

[0093] In one embodiment, if the processing completion information sent by the user client is received within the preset time, it indicates that the courier has completed the processing of the waybill that is about to time out, and the collection and delivery backend subsystem does not need to continue tracking. At this time, the collection and delivery backend subsystem can delete the relevant information of the waybill, or modify the waybill to be completed.

[0094] It should be noted that this embodiment can also be used for Figure 3After step S312, at least two orders that are about to time out are continuously tracked based on order priorities.

[0095] In an embodiment of the present disclosure, by receiving the processing completion information sent by the user client in real time, if the processing completion information is received, there is no need to continue tracking the order and re-identify the timeout risk order; if the processing completion information is not received, the above order will continue to be tracked, and a new timeout warning message will be sent every preset time, thereby providing couriers with more refined collection and delivery task management.

[0096] Figure 5 The flowchart of the method for obtaining the total duration of the pickup and dispatch operation provided by the embodiment of the present disclosure is shown. Figure 5 As shown, in one embodiment, the above S206 calculates the total duration of the dispatching operation according to the to-be-evaluated link and the pre-stored historical practical link duration, including:

[0097] S502, sending the link to be evaluated to the data processing subsystem, so that the data processing subsystem predicts the duration of the link to be evaluated based on the historical duration of the task;

[0098] S504, receiving the duration of the link to be evaluated returned by the data processing subsystem;

[0099] S506. According to the duration of the link to be evaluated, the total duration of the collection and dispatch operation is obtained.

[0100] In one embodiment, the user client sends the buried data of each link in the current courier's historical collection and delivery operation process to the data processing system. The data processing system processes the above buried data, calculates the duration of each link, and stores it as the historical collection and delivery task duration.

[0101] The collection and delivery backend subsystem calls the data processing subsystem interface to pass in the list data of the links to be estimated. The data processing subsystem can analyze the time data list of each link to be evaluated in the current waybill based on the list data of the links to be estimated and the current courier's historical collection and delivery operation data, and predict and calculate the time data list of each link to be evaluated. The time data list can be output to the collection and delivery backend subsystem to obtain the total time of the collection and delivery operation.

[0102] It should be noted that the total duration of the pick-up and dispatch operation is the sum of the durations of each link to be evaluated.

[0103] In the embodiments of the present disclosure, the duration of each link is calculated through the buried data generated by the current courier's historical collection and delivery operations. This is used as the historical collection and delivery task duration. On the one hand, it can effectively characterize the current courier's average practical operation level and achieve accurate early warning. On the other hand, early warning can also be carried out based on the relevant data of multiple couriers on the platform as a benchmark. Independent storage and processing of different types of data can improve the processing efficiency of the system.

[0104] Figure 6 FIG. 2 shows a flow chart of a method for obtaining a journey duration provided by an embodiment of the present disclosure. Figure 6 As shown, in one embodiment, the above S208 obtains the journey time corresponding to the waybill, including:

[0105] S602, sending the current location information of the user client and the destination address data of the pickup and dispatch task to the positioning subsystem, so that the positioning subsystem calculates the journey duration according to the current location information of the user client, the destination address data of the pickup and dispatch task and the historical operation track of the user client;

[0106] S604: Obtain the journey time sent by the positioning subsystem.

[0107] In one embodiment, the collection and delivery backend subsystem calls the positioning subsystem (such as a GIS map system) interface to pass in the current courier's real-time location information and the destination address data of the task to be collected and delivered. The positioning subsystem calculates the destination location information based on the destination address of the task to be collected and delivered, and calculates the journey duration based on the current courier's historical work trajectory and current real-time location information, and outputs the path duration to the collection and delivery backend subsystem.

[0108] In the real-time method disclosed in the present invention, the collection and delivery backend subsystem interacts with the positioning subsystem, comprehensively considering factors such as the current courier's historical work trajectory, real-time location information, and destination location information, and accurately calculates the journey duration, thereby improving the accuracy of the timeout warning time.

[0109] In order to deepen the understanding of the implementation process of the present disclosure, the following Figure 7 Provide detailed explanation.

[0110] like Figure 7 As shown, the pickup and dispatch task warning system of this example includes a pickup and dispatch backend subsystem 720 , a waybill subsystem 730 , a data processing subsystem 740 , a positioning subsystem 750 and a user client 710 .

[0111] The pickup and dispatch task warning method provided in this example mainly includes three core steps, namely S701 pickup and dispatch operation link identification step, S702 pickup and dispatch operation time estimation step and S703 accurate push timeout warning step.

[0112] See also Figure 7For the S701 collection and delivery operation link identification step, the main task is for the collection and delivery backend subsystem to obtain the real-time information of the waybill by calling the waybill subsystem interface, and to identify the necessary collection and delivery operation links when the courier actually handles the collection and delivery task by parsing the necessary information in the interface data, and finally generate a list of links to be estimated, where the list of links to be estimated can include order number, user expected fulfillment time, destination address data, identification of the link to be estimated and other information. The identification of the link to be estimated can be represented by at least one of text, data, symbols, etc. to uniquely represent the corresponding operation link.

[0113] The S701 collection and delivery operation identification step mainly includes the scene of collecting waybills and the scene of delivering waybills.

[0114] For the collection of waybills scenario, the collection and dispatch backend subsystem obtains the full tracking data by calling the order subsystem interface. If it is identified that the waybill is currently at the collection node, it will identify the necessary practical links for the courier when collecting the express delivery. The necessary practical links include one or more of the following:

[0115] Whether the collection waybill needs to be weighed;

[0116] Whether the collection waybill needs to be unpacked for inspection, photographed and uploaded;

[0117] Whether the collection waybill requires on-site real-name authentication by the user;

[0118] Whether the collection waybill needs to be packaged for consumables;

[0119] Whether the collection waybill requires any other special manual processing.

[0120] It should be noted that whether the collection waybill requires the user to perform real-name authentication on site is for the situation where the user did not perform real-name authentication when placing an order.

[0121] The backend subsystem of the recruitment and dispatch generates a list of links to be estimated based on the identified necessary practical links, or links to be estimated, in preparation for the subsequent calculation of the duration of each link to be estimated.

[0122] For the delivery of waybills, the collection and delivery backend subsystem obtains the full tracking data of the waybills by calling the waybills subsystem interface. If it is identified that the waybills are currently at the delivery node, the necessary practical operation links of the courier during express delivery are identified. The necessary practical operation links include at least one of the following:

[0123] Whether the delivery waybill needs to be photographed and uploaded;

[0124] Whether the delivery waybill requires on-site unpacking and inspection of the goods by the customer;

[0125] Whether the delivery waybill requires the user to sign on site for receipt;

[0126] Whether the delivery waybill requires any other special manual processing.

[0127] The backend subsystem for recruitment and dispatch generates a list of links to be estimated based on the necessary practical links identified, and subsequently calculates the duration of each link to be estimated.

[0128] It should be noted that for the scenarios of collecting waybills and delivering waybills, the list of links to be estimated includes but is not limited to weighing, unpacking and inspecting and taking photos, on-site real-name authentication, package packing, user unpacking and inspecting the goods, user signature, taking photos, signing and returning the waybill, etc.

[0129] After completing the S701 pick-up and dispatch operation link identification step, enter the S702 pick-up and dispatch operation time estimation step. The main task of the S702 pick-up and dispatch operation time estimation step is for the pick-up and dispatch backend subsystem and the data processing subsystem to calculate the total duration of each link to be estimated, or the total duration of the pick-up and dispatch operation.

[0130] The specific implementation process of the S702 pick-up and dispatch operation time estimation step includes:

[0131] The data processing subsystem receives the point-in-time data of each link of the collection and delivery operation reported by the user client (such as the courier workstation APP), calculates the duration of each link based on the received point-in-time data of each link of the collection and delivery operation, and stores the duration of each link in the data processing subsystem.

[0132] The collection and delivery backend subsystem calls the data processing subsystem interface and passes in the list of time links to be estimated generated by step 1. Based on the data list and the courier's historical collection and delivery operation data analysis, the data processing subsystem predicts and calculates the time data list of each collection and delivery link of the current waybill, and outputs the data list to the collection and delivery backend subsystem.

[0133] The collection and dispatch backend subsystem summarizes and calculates the total estimated duration of the collection and dispatch operations.

[0134] Through the S702 pick-up and dispatch operation time estimation step processing, the calculated estimated total duration data of the pick-up and dispatch operation is synchronized to the S703 accurate push timeout warning step processing.

[0135] After the S701 pick-up and dispatch operation link identification step and the S702 pick-up and dispatch operation time estimation step are processed, the S703 accurate push timeout warning step is entered. The processing flow of this step is as follows:

[0136] Based on the waybill type, identify orders with high risk of overtime warnings that have strict fulfillment time requirements, such as fresh food orders and orders where customers have mandatory fulfillment time requirements.

[0137] The collection and delivery backend subsystem calls the positioning subsystem interface and inputs the courier's current real-time location information and the destination address data of the collection and delivery task. The positioning subsystem calculates the location information based on the destination address of the collection and delivery task, and combines the courier's historical operation trajectory and real-time location information to calculate the estimated journey time and output it to the collection and delivery backend subsystem;

[0138] The collection and dispatch backend subsystem calculates the overtime warning time of the collection and dispatch task by combining the estimated total collection and dispatch operation time and the journey time obtained in the collection and dispatch operation time estimation step S702 and the user's expected fulfillment time obtained through the waybill subsystem;

[0139] The collection and delivery backend subsystem calculates the precise timeout warning time through the above process and pushes timeout warning messages to the user client in combination with the order warning risk level. It gives priority to orders with high warning levels. For orders that need to be fulfilled immediately, a forced pop-up window will be displayed to remind the courier to handle them immediately. Only when such orders are collected and delivered first, new timeout warning order prompt messages will be pushed again according to the precise timeout warning logic.

[0140] After the user client receives the timeout warning message, it will be prominently displayed on the front end, reminding the courier that the waybill change is about to time out. Please speed up the process immediately to avoid delays in collection and delivery and user complaints.

[0141] Through the above process, the accurate push of the timeout warning message for the pickup and dispatch task order is completed.

[0142] The present invention combines the waybill subsystem, the user client, the collection and dispatch backend subsystem, the data processing subsystem and the positioning subsystem to parse the real-time information of the waybill to be collected and dispatched, identify the type of the collection and dispatch practical operation link of the waybill, and calculate the duration of each collection and dispatch practical operation link (for example: weighing, real-name authentication, unpacking and inspection, photo taking, consumables packaging, successful delivery photo uploading, user signature, etc.) based on the historical buried point data of each collection and dispatch practical operation link of the user client in combination with the data processing subsystem. The collection and dispatch backend subsystem calculates the time required for the delivery by combining the user's expected fulfillment time and the positioning subsystem. The calculated journey time and the estimated total actual collection and delivery time are used to calculate an accurate time difference for the timeout warning, and then the timeout warning message is accurately pushed to the user client to remind the courier to handle the collection and delivery task in time. The present invention realizes refined express collection and delivery task timeout warning through the estimated collection and delivery operation time, and accurately reminds the courier in combination with the priority of the collection and delivery task waybill that is about to time out, prompting him to immediately handle the collection and delivery task that is about to time out, thereby reducing the collection and delivery timeout rate, improving the user's collection and delivery experience and the courier's collection and delivery experience, and reducing the probability of courier's timeout in performing collection and delivery tasks.

[0143] Based on the same inventive concept, the disclosed embodiment also provides a task warning device, such as the following embodiment. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0144] Figure 8 FIG. 1 is a schematic diagram of a task warning device provided by an embodiment of the present disclosure. Figure 8 As shown, the task dispatching warning device of this embodiment includes a first acquisition module 810, a link identification module 820, a first calculation module 830, a second acquisition module 840, a second calculation module 850 and a timeout warning module 860.

[0145] The first acquisition module 810 is used to acquire the real-time information of the waybill, and the real-time information of the waybill includes the expected fulfillment time;

[0146] The link identification module 820 is used to identify the collection and dispatch operation links based on the real-time information of the waybill and generate the links to be evaluated of the waybill;

[0147] The first calculation module 830 is used to calculate the total duration of the dispatching operation according to the to-be-evaluated link and the pre-stored historical practical operation link duration;

[0148] The second acquisition module 840 is used to obtain the journey time corresponding to the waybill;

[0149] The second calculation module 850 is used to calculate the overtime warning time according to the total duration of the pickup and dispatch task, the journey duration and the expected fulfillment time;

[0150] The timeout warning module 860 is used to generate a timeout warning message according to the timeout warning time, and send the timeout warning message to the user client.

[0151] In one embodiment, when multiple waybills are obtained, the timeout warning module 860 is also used to determine the priority of each waybill and give priority to pushing high-priority timeout warning messages.

[0152] In one embodiment, the timeout warning module 860 is also used to generate a new timeout warning message and send the new timeout warning message to the user client if the processing completion information sent by the user client is not received within a preset time after sending the timeout warning message to the user client.

[0153] In one embodiment, the first calculation module 830 is used to send the link to be evaluated to the data processing subsystem, so that the data processing subsystem predicts the duration of the link to be evaluated based on the historical duration of the pick-up and dispatch tasks; receives the duration of the link to be evaluated returned by the data processing subsystem; and obtains the total duration of the pick-up and dispatch operation based on the duration of the link to be evaluated.

[0154] It should be noted that the duration of the historical practical operation is calculated from the tracking data of the pickup and dispatch practical operation reported by the user client and stored in the data processing subsystem, where one pickup and dispatch practical operation corresponds to one historical duration value.

[0155] In one embodiment, the second acquisition module 840 is used to send the current location information of the user client and the destination address data of the pick-up and dispatch task to the positioning subsystem, so that the positioning subsystem calculates the journey duration based on the current location information of the user client, the destination address data of the pick-up and dispatch task and the historical operation trajectory of the user client; and obtains the journey duration sent by the positioning subsystem.

[0156] In the disclosed embodiment, real-time information of the waybill is obtained, and the real-time information of the waybill includes the expected fulfillment time; the collection and delivery operation link is identified for the real-time information of the waybill, and the to-be-evaluated link of the waybill is generated; the total duration of the collection and delivery operation is calculated based on the to-be-evaluated link and the pre-stored historical practical operation link duration; the journey duration corresponding to the waybill is obtained; the timeout warning time is calculated based on the total duration of the collection and delivery task, the journey duration and the expected fulfillment time; based on the timeout warning time, a timeout warning message is generated, and the timeout warning message is sent to the user client, so that the timeout warning message can be pushed in a refined manner, and more clear guidance on the collection and delivery operation can be provided to the front-line couriers, thereby improving the processing efficiency of the collection and delivery tasks.

[0157] According to another aspect of the present disclosure, a collection and dispatch task warning system is also provided, including a collection and dispatch background subsystem 720, a waybill subsystem 730, a data processing subsystem 740, a positioning subsystem 750 and a user client 710, wherein the waybill subsystem 730 is used to store real-time information of the waybill; the collection and dispatch background subsystem 720 is used to obtain real-time information of the waybill, and the real-time information of the waybill is used to identify the collection and dispatch operation link of the waybill and generate the link to be evaluated of the waybill; the data processing subsystem 740 is used to store the duration of the historical practical operation link; the positioning subsystem 750 is used to store the real-time information of the waybill ... The location subsystem 750 is used to determine the journey duration corresponding to the waybill based on the real-time location of the user client and the destination location of the waybill; the collection and dispatch backend subsystem 720 is also used to calculate the total duration of the collection and dispatch operation based on the link to be evaluated and the pre-stored historical practical link duration; obtain the journey duration corresponding to the waybill; calculate the timeout warning time based on the total duration of the collection and dispatch task, the journey duration and the expected fulfillment time; generate a timeout warning message based on the timeout warning time, and send the timeout warning message to the user client; the user client 710 is used to receive the timeout warning message so that the user can process the waybill.

[0158] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as a system, method or program product. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as a "circuit", "module" or "system".

[0159] Refer to the following Fig. 9 An electronic device 900 according to this embodiment of the present invention will be described. Fig. 9 The electronic device 900 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.

[0160] like Fig. 9 As shown, the electronic device 900 is in the form of a general computing device. The components of the electronic device 900 may include but are not limited to: at least one processing unit 910, at least one storage unit 920, and a bus 930 connecting different system components (including the storage unit 920 and the processing unit 910).

[0161] The storage unit stores program codes, which can be executed by the processing unit 910, so that the processing unit 910 performs the steps of various exemplary embodiments of the present invention described in the above “Exemplary Method” section of this specification. For example, the processing unit 910 can perform the following steps: Figure 2 As shown in , the real-time information of the waybill is obtained, and the real-time information of the waybill includes the expected fulfillment time; the real-time information of the waybill is used to identify the collection and dispatch operation links, and generate the to-be-evaluated links of the waybill; the total duration of the collection and dispatch operation is calculated based on the to-be-evaluated links and the pre-stored historical practical operation link durations; the journey duration corresponding to the waybill is obtained; the timeout warning time is calculated based on the total duration of the collection and dispatch task, the journey duration and the expected fulfillment time; based on the timeout warning time, a timeout warning message is generated, and the timeout warning message is sent to the user client.

[0162] The storage unit 920 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 9201 and / or a cache storage unit 9202 , and may further include a read-only storage unit (ROM) 9203 .

[0163] The storage unit 920 may also include a program / utility 9204 having a set (at least one) of program modules 9205, such program modules 9205 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 the implementation of a network environment.

[0164] Bus 930 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0165] The electronic device 900 may also communicate with one or more external devices 940 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the system, and / or any device that enables the electronic device 900 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 950. Furthermore, the system 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) via a network adapter 960. Fig. 9 As shown, the network adapter 960 communicates with other modules of the electronic device 900 via the bus 930. It should be understood that although Fig. 9 Not shown, other hardware and / or software modules may be used in conjunction with electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0166] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0167] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. In an exemplary embodiment of the present disclosure, a computer program product is also provided, which includes a computer program or a computer instruction, and the computer program or the computer instruction is loaded and executed by a processor to enable the computer to implement the steps of the method disclosed in the above embodiment.

[0168] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, 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), 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 foregoing.

[0169] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. 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. A readable signal medium may also be any readable medium other than a 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.

[0170] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0171] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0172] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0173] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0174] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0175] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A method for early warning of a task, characterized in that: include: Obtaining real-time information of the waybill, wherein the real-time information of the waybill includes an expected fulfillment time; Identify the collection and dispatch operation links of the waybill based on the real-time information of the waybill, and generate the link to be evaluated of the waybill; Calculate the total duration of the pickup and dispatch task based on the to-be-evaluated phase and the pre-stored historical practical phase duration; Obtain the journey time corresponding to the waybill; Calculate the overtime warning time based on the total duration of the pickup and delivery task, the journey duration and the expected fulfillment time; A timeout warning message is generated according to the timeout warning time, and the timeout warning message is sent to the user client.

2. The early warning method for the task of dispatching according to claim 1 is characterized in that: When multiple waybills are obtained, the sending of the timeout warning message to the user client includes: Determine the priority of each waybill and give priority to pushing high-priority timeout warning messages.

3. The early warning method for the task of dispatching according to claim 1 or 2, characterized in that: After sending the timeout warning message to the user client, the method further includes: If the processing completion information sent by the user client is not received within the preset time, a new timeout warning message is generated and sent to the user client.

4. The early warning method for the task of dispatching according to claim 1 is characterized in that: The total duration of the task is calculated based on the to-be-evaluated phase and the pre-stored historical practical phase duration, including: Sending the link to be evaluated to the data processing subsystem, so that the data processing subsystem predicts the duration of the link to be evaluated based on the duration of the historical dispatch tasks; Receive the duration of the link to be evaluated returned by the data processing subsystem; According to the duration of the link to be evaluated, the total duration of the task is obtained.

5. The early warning method for the task of dispatching according to claim 1 is characterized in that: The duration of the historical practical operation link is calculated based on the buried data of the pickup and dispatch practical operation link reported by the user client, and stored in the data processing subsystem, wherein one pickup and dispatch practical operation link corresponds to one historical duration value.

6. The early warning method for the task of soliciting and dispatching according to claim 1 is characterized in that: The obtaining of the journey time corresponding to the waybill includes: Sending the current location information of the user client and the destination address data of the pickup and dispatch task to the positioning subsystem, so that the positioning subsystem calculates the journey duration according to the current location information of the user client, the destination address data of the pickup and dispatch task and the historical operation track of the user client; Obtain the journey duration sent by the positioning subsystem.

7. A warning device for a task of dispatching, characterized in that: include: A first acquisition module is used to acquire real-time information of the waybill, wherein the real-time information of the waybill includes an expected fulfillment time; A link identification module, used to identify the collection and dispatch operation links of the real-time information of the waybill and generate the link to be evaluated of the waybill; A first calculation module is used to calculate the total duration of the task according to the link to be evaluated and the pre-stored historical practical operation link duration; The second acquisition module is used to obtain the journey time corresponding to the waybill; A second calculation module is used to calculate the overtime warning time according to the total duration of the pickup and dispatch task, the journey duration and the expected fulfillment time; The timeout warning module is used to generate a timeout warning message according to the timeout warning time and send the timeout warning message to the user client.

8. A warning system for dispatching tasks, characterized in that: The system includes a collection and dispatch backend subsystem, a waybill subsystem, a data processing subsystem, a positioning subsystem and a user client, wherein: The waybill subsystem is used to store the real-time information of the waybill; The collection and dispatch backend subsystem is used to obtain real-time information of the waybill, including the expected fulfillment time; identify the collection and dispatch operation link of the real-time information of the waybill, and generate the link to be evaluated of the waybill; The data processing subsystem is used to store the duration of historical practical operation sessions; The positioning subsystem is used to determine the journey duration corresponding to the waybill according to the real-time location of the user client and the destination location of the waybill; The collection and dispatch backend subsystem is further used to calculate the total duration of the collection and dispatch task according to the to-be-evaluated link and the pre-stored historical practical operation link duration; obtain the journey duration corresponding to the waybill; calculate the timeout warning time according to the total duration of the collection and dispatch task, the journey duration and the expected fulfillment time; generate a timeout warning message according to the timeout warning time, and send the timeout warning message to the user client; The user client is used to receive the timeout warning message so that the user can process the waybill.

9. An electronic device, characterized in that: include: processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the task warning method as described in any one of claims 1-6 by executing the executable instructions.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by the processor, the method for early warning of the dispatching task as described in any one of claims 1 to 6 is implemented.

Images