Task solicitation task early warning method, device, system, equipment and storage medium

Abstract

The present disclosure provides a kind of task prewarning method, device, system, equipment and storage medium of soliciting, related to wisdom logistics technical field.The method includes obtaining the real-time information of waybill, the real-time information of waybill includes expected performance time;The real-time information of waybill is identified, and the pending evaluation link of waybill is generated;According to the pending evaluation link and the pre-stored historical actual operation link length, the total length of soliciting task is calculated;The route length corresponding to waybill is obtained;According to the total length of soliciting task, route length and expected performance time, the overtime warning time is calculated;According to overtime warning time, overtime warning message is generated, and overtime warning message is sent to user client.The present disclosure can finely push overtime warning message, provide more explicit soliciting operation guidance for front-line expressman, and improve the processing efficiency of soliciting task.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of intelligent logistics, and in particular, to a pick-up task early warning method, a pick-up task early warning device, a pick-up task early warning system, an electronic device, and a computer readable storage medium. BACKGROUND

[0002] At present, customers placing orders through a network platform has become the main way for customers to place orders and send out items. After customers place orders through a network channel such as an official website or WeChat, a dispatch system allocates the orders to a courier for pick-up, and the courier processes the orders by taking the orders, transferring the orders, or returning the orders.

[0003] In related technologies, a pick-up task overtime early warning reminder is usually pushed to a courier, and a start early warning reminder time point is obtained through a difference between a user expected performance time point and an overtime early warning time. However, the above early warning method is too rough, and problems such as not knowing that pick-up is overtime or even serious overtime and poor early warning effect are likely to occur.

[0004] It should be noted that the information disclosed in the above background section is only used to strengthen the understanding of the background of the present disclosure, and therefore can include information that does not constitute prior art known to those of ordinary skill in the art. SUMMARY

[0005] The present disclosure provides a pick-up task early warning, device, system, equipment, and storage medium, which at least to some extent, overcomes the problem of not knowing that pick-up is overtime or even serious overtime and poor early warning effect in related technologies.

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

[0007] According to one aspect of the present disclosure, a pick-up task early warning method is provided, comprising: obtaining real-time information of a shipping order, the real-time information of the shipping order including an expected performance time; identifying a pick-up operation link of the real-time information of the shipping order to generate a to-be-evaluated link of the shipping order; calculating a total time length of a pick-up task according to the to-be-evaluated link and a pre-stored historical actual operation link time length; obtaining a route time length corresponding to the shipping order; calculating an overtime early warning time according to the total time length of the pick-up task, the route time length, and the expected performance time; generating an overtime early warning message according to the overtime early warning time, and sending the overtime early warning message to a user client.

[0008] In one embodiment of the present disclosure, when a plurality of shipping orders are obtained, the sending of the overtime early warning message to the user client comprises: determining priorities of the respective shipping orders, and preferentially pushing an overtime early warning message of a high priority.

[0009] In one embodiment of this disclosure, after sending the timeout warning message to the user client, the method further includes: if no processing completion information is received from the user client 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 this disclosure, calculating the total duration of the pickup and dispatch task based on the stage to be evaluated and the pre-stored historical operation stages includes: sending the stage to be evaluated to a data processing subsystem so that the data processing subsystem can predict the duration of the stage to be evaluated based on the historical pickup and dispatch task durations; receiving the duration of the stage to be evaluated returned by the data processing subsystem; and obtaining the total duration of the pickup and dispatch task based on the duration of the stage to be evaluated.

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

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

[0013] According to another aspect of this disclosure, a pickup and delivery task early warning device is also provided, comprising: a first acquisition module, configured to acquire real-time information of a waybill, the real-time information of which includes an expected fulfillment time; a link identification module, configured to identify pickup and delivery operation links in the real-time information of the waybill and generate links to be evaluated for the waybill; a first calculation module, configured to calculate the total duration of the pickup and delivery task based on the links to be evaluated and the duration of pre-stored historical operation links; a second acquisition module, configured to acquire the travel time corresponding to the waybill; a second calculation module, configured to calculate a timeout warning time based on the total duration of the pickup and delivery task, the travel time, and the expected fulfillment time; and a timeout warning module, configured 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, there is also provided a task assignment early warning system, comprising a task assignment background subsystem, a waybill subsystem, a data processing subsystem, a positioning subsystem and a user client, wherein the waybill subsystem is configured to store real-time information of a waybill; the task assignment background subsystem is configured to obtain the real-time information of the waybill, the real-time information of the waybill comprising an expected performance time; perform task assignment link identification on the real-time information of the waybill to generate a to-be-evaluated link of the waybill; the data processing subsystem is configured to store historical actual operation link time lengths; the positioning subsystem is configured to determine a route time length corresponding to the waybill according to a real-time location of the user client and a destination location of the waybill; the task assignment background subsystem is further configured to calculate a total time length of a task assignment according to the to-be-evaluated link and the pre-stored historical actual operation link time lengths; obtain the route time length corresponding to the waybill; calculate an overtime early warning time according to the total time length of the task assignment, the route time length and the expected performance time; generate an overtime early warning message according to the overtime early warning time and send the overtime early warning message to the user client; and the user client is configured to receive the overtime early warning message to enable a user to handle the waybill.

[0015] According to another aspect of the present disclosure, there is provided an electronic device, comprising a processor and a memory configured to store executable instructions of the processor, wherein the processor is configured to perform the above-mentioned task assignment early warning method via execution of the executable instructions.

[0016] According to another aspect of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the above-mentioned task assignment early warning method.

[0017] According to yet another aspect of the present disclosure, there is provided a computer program product, comprising a computer program or computer instructions, the computer program or the computer instructions being loaded and executed by a processor to enable a computer to implement the above-mentioned task assignment early warning method.

[0018] In the embodiments of the present disclosure, the real-time information of the waybill is obtained, the real-time information of the waybill comprising an expected performance time; the real-time information of the waybill is subjected to task assignment link identification to generate a to-be-evaluated link of the waybill; a total time length of a task assignment is calculated according to the to-be-evaluated link and pre-stored historical actual operation link time lengths; a route time length corresponding to the waybill is obtained; an overtime early warning time is calculated according to the total time length of the task assignment, the route time length and the expected performance time; an overtime early warning message is generated according to the overtime early warning time and sent to the user client, so that the overtime early warning message can be pushed in a refined manner and more explicit task assignment guidance can be provided to frontline express delivery personnel, thereby improving the handling efficiency of the task assignment.

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

[0020] The accompanying drawings, which are incorporated in and form a part of the specification, illustrate one or more embodiments of the present disclosure and, together with the description, further serve to explain the principles of the disclosure. It is to be understood that other drawings can be obtained from these drawings by virtue of the drawings merely being some embodiments of the present disclosure, and other drawings can be obtained by those of ordinary skill in the art without any creative effort, based on these drawings.

[0021] Figure 1 A schematic diagram of a task pre-warning system is shown according to an embodiment of the present disclosure;

[0022] Figure 2 A flowchart of a task pre-warning method is shown according to an embodiment of the present disclosure;

[0023] Figure 3 A flowchart of another task pre-warning method is shown according to an embodiment of the present disclosure;

[0024] Figure 4 A flowchart of still another task pre-warning method is shown according to an embodiment of the present disclosure;

[0025] Figure 5 A flowchart of a method for obtaining total duration of a task pre-warning link is shown according to an embodiment of the present disclosure;

[0026] Figure 6 A flowchart of a method for obtaining distance duration is shown according to an embodiment of the present disclosure;

[0027] Figure 7 A flowchart of a specific example of a task pre-warning method is shown according to an embodiment of the present disclosure.

[0028] Figure 8 A schematic diagram of a task pre-warning device is shown according to an embodiment of the present disclosure;

[0029] Figure 9 A block diagram of an electronic device is shown according to an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0031] Further, the accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this specification. The drawings are not necessarily to scale of the various elements, and can be simplified for the sake of illustration. Identical reference numbers in the figures denote identical or similar elements, and common description thereof will not be repeated. Some of the blocks in the drawings can be functional building blocks, and can not necessarily correspond to a physical or logical entity. These functional building blocks can be implemented in software, or in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0032] Figure 1 An exemplary system architecture 100 is shown, to which the task pickup pre-warning method and the task pickup pre-warning device according to embodiments of the present disclosure can be applied.

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

[0034] The network 120 is a medium for providing a communication link between the user terminal 110 and the server 130, and can be a wired network or a wireless network. The network 120 can include various connection types, such as wired, wireless communication links or fiber optic cables, etc.

[0035] The user can use the user terminal 110 to interact with the server 130 through the network 120 to receive or send messages.

[0036] The user terminal 110 can be various electronic devices with a display screen and supporting web browsing, including but not limited to smartphones, tablets, display screens, desktop computers, etc.

[0037] Various communication client applications can 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. Through the communication client application, the first user can submit the shipping order and obtain real-time information of the shipping order. The courier or other personnel can use the user client to receive the overtime pre-warning message sent by the pickup background subsystem, etc.

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

[0039] ​The server 130 can be a server providing various services, for example, a background management server providing support for a shopping website browsed by a user using the user terminal 110. The background management server can analyze and process the received delivery order request, etc., to obtain a processing result (for example, a timeout warning message, etc.) and feed back to the client of the user terminal used by the courier.

[0040] Optionally, the server 130 can be a stand-alone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms.

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

[0042] Those skilled in the art can know that, Figure 1 The number of user terminals, networks and servers in the above embodiment is only illustrative, and any number of user terminals, networks and servers can be provided according to actual needs. The embodiments of the present disclosure do not limit this.

[0043] In the related art, the courier can configure a timeout warning threshold on the application program APP installed on the user terminal according to the needs, for example, starting to warn 30 minutes before the delivery order fulfillment end time, and then polling the orders about to timeout every 5 minutes, and for all orders about to timeout, the system pops up a window to remind the courier one by one without discrimination. However, the above warning method is too rough, lacks the estimation of the time of the actual operation of the task, and cannot be more finely warned. In the case of a large amount of timeout warning tasks, the courier cannot know the timeout tasks that need to be processed in priority, which affects the experience of customers receiving and sending mail, and reduces the time efficiency of the courier picking up tasks.

[0044] Based on this, the present disclosure provides a pickup and delivery task early warning method, which obtains real-time information of waybills, including expected fulfillment time; identifies pickup and delivery operation links based on the real-time information of waybills, generating links to be evaluated for the waybills; calculates the total pickup and delivery operation time based on the links to be evaluated and the pre-stored historical operation time; obtains the travel time corresponding to the waybill; calculates the overtime warning time based on the total pickup and delivery task time, travel time, and expected fulfillment time; generates an overtime warning message based on the overtime warning time, and sends the overtime warning message to the user client, thereby enabling refined push of overtime warning messages, providing clearer pickup and delivery operation guidance for front-line couriers, and improving the processing efficiency of pickup and delivery tasks.

[0045] It should be noted that, unless otherwise specified, the embodiments of the present invention and the technical features thereof can be combined with each other.

[0046] The following detailed description of this exemplary implementation method is provided in conjunction with the accompanying drawings and embodiments.

[0047] First, this disclosure provides a method for early warning of pickup and dispatch tasks, which can be executed by any system with computing power. The pickup and dispatch task early warning method provided in this disclosure can be executed by a server, for example, by a pickup and dispatch backend subsystem configured on the server.

[0048] Figure 2 This diagram illustrates a flowchart of a pickup and dispatch task early warning method provided in an embodiment of the present disclosure, such as... Figure 2 As shown in the embodiments of this disclosure, the pickup and dispatch task early warning method includes the following steps:

[0049] S202. Obtain real-time information of the waybill, including the expected fulfillment time.

[0050] In S202, a waybill may include at least the customer information who placed the order, the destination address, the expected fulfillment time, and information related to the pickup or delivery waybill. The expected fulfillment time is the expected pickup time or delivery time specified by the user when placing the order. The destination address information is the location information of the customer who placed the order. Information related to the pickup or delivery waybill may include any actions the customer submits regarding the package, such as opening the package for inspection or packing, as requested by the customer when placing the order.

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

[0052] S204. Identify the pickup and delivery operation stages of the waybill based on its real-time information and generate the evaluation stages of the waybill.

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

[0054] For pickup waybills, the necessary practical steps to identify include one or more of the following:

[0055] Does this pickup and delivery note require weighing?

[0056] Does the pickup order require opening the box for inspection, taking photos, and uploading them?

[0057] Does the pickup order require on-site real-name authentication by the user?

[0058] Does this pickup and delivery order require packaging of consumables?

[0059] Does this pickup and delivery order require any other special manual processing?

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

[0061] Does the delivery note need to be photographed and uploaded?

[0062] Does the delivery note indicate that the customer requested on-site opening and inspection of the goods?

[0063] Does the delivery note require the user's on-site signature for receipt?

[0064] Does this delivery order require any special manual processing?

[0065] It should be noted that the identification of pickup and dispatch operation links may include links that have not yet been evaluated, or may include links that have been evaluated multiple times; this disclosure does not make any specific limitations.

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

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

[0068] For example, the duration of historical operational steps can be calculated based on the historical pickup and delivery data reported by the current courier over a period of time. For instance, the average duration of each historical operational step can be calculated based on the data reported by the current courier in the past month, and used as the historical operational step duration for the corresponding step.

[0069] Exemplarily, the historical operation link time length can be obtained by weighted summation according to the historical operation link time length of the current courier and the historical mean value of the enterprise.

[0070] S208, obtaining a route time length corresponding to the waybill.

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

[0072] S210, calculating a timeout warning time according to the total time length of the pickup task, the route time length and the expected performance time.

[0073] In an embodiment, the timeout warning time can be calculated as the difference between the expected performance time and the current time, the total time length of the to-be-evaluated link and the route time length.

[0074] For example, a customer places an order to send a parcel at 9:00 am, expecting that the courier can arrive at the door to pick up within an hour, i.e., the expected performance time T1 is 10:00, and if the current time T0 is 9:10, the system estimates that the total time length of the to-be-evaluated link T2 is 5 minutes, and the route time length 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 length required for the courier to handle the above waybill. During the implementation of the pickup task, it can not be guaranteed that the handling of each waybill can be performed in the minimum time length due to factors such as road conditions and courier state. Therefore, the timeout warning time can be based on the minimum time length and added with a preset compensation value. The preset compensation value can be determined according to actual conditions, for example, the preset compensation value can be configured as 5 minutes, 10 minutes, etc., and the present disclosure is not limited in this regard.

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

[0077] S212, generating a timeout warning message according to the timeout warning time, and sending the timeout warning message to the user client.

[0078] The above timeout warning message is used to remind the courier to handle the above waybill in a timely manner. The timeout warning message can include the waybill number, the destination address of the waybill and other information.

[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 delivery time and the timeout warning time. When the above sending time arrives, the pickup background subsystem sends the timeout warning message to the user client.

[0080] In the embodiment of the present disclosure, real-time information of the waybill is obtained, the real-time information of the waybill including the expected delivery time; the real-time information of the waybill is subjected to pickup operation link identification to generate a to-be-evaluated link of the waybill; the total duration of the pickup operation is calculated according to the to-be-evaluated link and the pre-stored historical actual operation link duration; the route duration corresponding to the waybill is obtained; the timeout warning time is calculated according to the total duration of the pickup task, the route duration and the expected delivery time; the timeout warning message is generated according to 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 detail, and more specific pickup operation guidance can be provided for the frontline express delivery personnel, and the processing efficiency of the pickup task is improved.

[0081] Figure 3 Another flowchart of a pickup task warning method provided by the embodiment of the present disclosure is shown. Figure 2 On the basis of the embodiment, S212 is further refined, and the case where there are multiple waybills in the user client and at least two waybills are about to timeout is limited. As shown in Figure 3 The pickup task warning method provided by the embodiment of the present disclosure includes S202-S210 and S312, and specifically, the method includes:

[0082] S312, when multiple waybills are obtained, the priority of each waybill is determined, and the timeout warning message of high priority is preferentially pushed.

[0083] It should be noted that the specific implementation modes of S202-S210 in the embodiment are the same as those of S202-S210 in the foregoing embodiments, and will not be described herein.

[0084] The priority of the waybill can be determined according to the type of the waybill, and the waybill with a high timeout warning risk level of strict delivery time limit requirement, such as a fresh food order, a customer forced delivery time limit order, etc., can be configured as a high-priority waybill, and the order without the above information can be configured as a low-priority order.

[0085] For example, the identified high-priority order can be marked to facilitate the determination of the priority of the order.

[0086] In one embodiment, when the at least two imminent-time-out waybills are both high-priority waybills, the time-out warning message can display the number of high-priority waybills on the user client, and can also display the relevant information of the at least two imminent-time-out waybills one by one on the user client, and a forced pop-up window reminds the courier to immediately handle the order, and only after the priority completion of the handling of such order, the courier can perform other pick-up tasks.

[0087] In the embodiments of the present disclosure, by identifying the priority of the waybill and preferentially pushing the time-out warning message of the high-priority waybill, the time-out warning message is further refined to push, and the courier is provided with more explicit guidance for the pick-up task, and the processing efficiency of the pick-up task is improved.

[0088] Figure 4 A flow chart of another pick-up task warning method provided by the embodiments of the present disclosure is shown. Figure 2 Or Figure 3 On the basis of the embodiments, S214 is added after S212 to limit whether the courier handles the time-out warning message. As shown in Figure 4 The pick-up task warning method provided by the embodiments of the present disclosure includes S202-S214, and specifically, the method includes:

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

[0090] It should be noted that the specific implementation of S202-S210 of the present embodiment is the same as that of S202-S210 of the foregoing embodiments, which will not be described here.

[0091] The preset time in S214 can be pre-configured in the pick-up background subsystem, and the preset time can be set according to actual conditions, for example, the preset time is 5 min, that is, the processing completion information sent by the user client is not received every 5 min, and the new time-out warning message is sent once.

[0092] The processing completion information sent by the user client can be determined according to actual conditions, for example, it can be a preset string, number, character, etc.

[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 handling of the imminent-time-out waybill, and the pick-up background subsystem does not need to continue to track, at this time, the pick-up background subsystem can delete the relevant information of the waybill, or modify the waybill as completed.

[0094] It should be noted that the present embodiment can also be used Figure 3After step S312, for at least two orders that are about to time out, continue to track them based on order priority.

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

[0096] Figure 5 This diagram illustrates a method for obtaining the total time of a pickup and delivery operation according to an embodiment of this disclosure. Figure 5 As shown, in one embodiment, S206 above calculates the total duration of the pickup and dispatch operation based on the stage to be evaluated and the pre-stored historical operation durations, including:

[0097] S502. Send the process to be evaluated to the data processing subsystem so that the data processing subsystem can predict the duration of the process to be evaluated based on the historical task assignment duration.

[0098] S504, the duration of receiving the evaluation stage returned by the data processing subsystem;

[0099] S506. Based on the duration of the stages to be evaluated, the total duration of the pickup and delivery operation is obtained.

[0100] In one embodiment, the user client sends the embedded data of each step in the current courier's historical pickup and delivery operation to the data processing system. The data processing system processes the embedded data, calculates the duration of each step, and stores it as the duration of historical pickup and delivery tasks.

[0101] The pickup and delivery backend subsystem calls the data processing subsystem interface and inputs the list of stages to be estimated. The data processing subsystem can analyze the list of stages to be estimated and the current courier's historical pickup and delivery operation data to predict and calculate the time data list of each stage to be evaluated for the current waybill. The time data list is then output to the pickup and delivery backend subsystem to obtain the total pickup and delivery operation time.

[0102] It should be noted that the total time for pickup and delivery operations is the sum of the times for each stage to be evaluated.

[0103] In the embodiments disclosed herein, the duration of each step is calculated using the embedded data generated from the current courier's historical pickup and delivery operations, which serves as the historical pickup and delivery task duration. On the one hand, this can effectively characterize the current average performance level of the courier and achieve accurate early warning; on the other hand, it can also use the relevant data of multiple couriers on the platform as a benchmark to issue early warnings. By storing and processing different types of data independently, the system's processing efficiency can be improved.

[0104] Figure 6 A flowchart illustrating the method for obtaining travel time provided in an embodiment of this disclosure is shown. Figure 6 As shown, in one embodiment, the above-mentioned S208 process of obtaining the travel time corresponding to the waybill includes:

[0105] S602. Send 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 can calculate the travel time based on the current location information of the user client, the destination address data of the pickup and dispatch task and the historical operation trajectory of the user client.

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

[0107] In one embodiment, the pickup and delivery backend subsystem calls the interface of the positioning subsystem (such as a GIS map system) to input the real-time location information of the current courier and the destination address data of the task to be picked up and delivered. The positioning subsystem calculates the destination location information based on the destination address of the task to be picked up and delivered, and calculates the travel time by combining the current courier's historical work trajectory and current real-time location information, and outputs the path time to the pickup and delivery backend subsystem.

[0108] In the real-time method disclosed herein, the pickup and delivery backend subsystem and the positioning subsystem interact to comprehensively consider factors such as the current courier's historical work trajectory, real-time location information, and destination location information to accurately calculate the journey time, thereby improving the accuracy of the overdue warning time.

[0109] To deepen the understanding of the implementation process of this disclosure, the following will be combined with... Figure 7 Please provide a detailed explanation.

[0110] like Figure 7 As shown, the pickup and delivery task early warning system in this example includes a pickup and delivery 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 early warning method provided in this example mainly includes three core steps: S701 pickup and dispatch operation identification step, S702 pickup and dispatch operation time estimation step, and S703 accurate push timeout warning step.

[0112] See Figure 7For the S701 task assignment operation link identification step, the main task is that the task assignment background subsystem obtains real-time information of the waybill by calling a waybill subsystem interface, and identifies necessary task assignment operation links of the express courier in actual processing of the task assignment by analyzing necessary information in the interface data, to finally generate a to-be-estimated link list, wherein the to-be-estimated link list can include order number, user expected performance time, destination address data, to-be-estimated link identifier and the like, and the to-be-estimated link identifier can be represented by at least one of a word, data and a symbol to uniquely represent the corresponding operation link.

[0113] In the S701 task assignment operation link identification step, it mainly includes a pick-up waybill scenario and a delivery waybill scenario.

[0114] For the pick-up waybill scenario, the task assignment background subsystem obtains whole-process tracking data by calling an order subsystem interface, and if it is identified that the waybill is currently at a pick-up node, it identifies necessary actual operation links of the express courier in pick-up of the express, and the necessary actual operation links include one or more of the following:

[0115] whether the pick-up waybill needs to be weighed;

[0116] whether the pick-up waybill needs to be unpacked, viewed and photographed and uploaded;

[0117] whether the pick-up waybill needs user on-site real-name authentication;

[0118] whether the pick-up waybill needs to be packed with consumables;

[0119] whether the pick-up waybill needs other special manual processing.

[0120] It should be noted that whether the pick-up waybill needs user on-site real-name authentication is for the case that the user does not perform real-name authentication when ordering.

[0121] The task assignment background subsystem generates a to-be-estimated link list according to the identified necessary actual operation links, or to-be-estimated links, for subsequent calculation of time lengths of the to-be-estimated links.

[0122] For the delivery waybill scenario, the task assignment background subsystem obtains whole-process tracking data of the waybill by calling a waybill subsystem interface, and if it is identified that the waybill is currently at a delivery node, it identifies necessary actual operation links of the express courier in delivery of the express, wherein the necessary actual 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 needs to be unpacked and viewed by the customer;

[0125] whether the delivery waybill needs user on-site signature and receipt;

[0126] Is the delivery waybill required for other special manual processing?

[0127] The pickup and delivery background subsystem generates a list of to-be-estimated steps based on the identified necessary operational steps, and the subsequent calculation of the time length of each to-be-estimated step has been completed.

[0128] It should be noted that for the pickup and delivery waybill scenario and the delivery waybill scenario, the to-be-estimated step list includes but is not limited to weighing, opening the box, verifying and photographing, on-site real-name authentication, package packaging, user opening and verifying the goods, user signature, photographing, signing and returning, etc.

[0129] After completing the S701 pickup and delivery operation step identification step, enter the S702 pickup and delivery operation time estimation step, and the main task of the S702 pickup and delivery operation time estimation step is for the pickup and delivery background subsystem and the data processing subsystem to calculate the total time length of each to-be-estimated step, or the total time length of the pickup and delivery operation.

[0130] The specific implementation process of the S702 pickup and delivery operation time estimation step includes:

[0131] The data processing subsystem receives the pickup and delivery operational step data reported by the user client (such as the courier workstation APP), calculates the time length of each step based on the received pickup and delivery operational step data, and stores the time length of each step in the data processing subsystem.

[0132] The pickup and delivery background subsystem calls the data processing subsystem interface, inputs the to-be-estimated time length step list data generated in step 1, and based on the data list and the courier's historical pickup and delivery operation data analysis, the data processing subsystem predicts and calculates the time length data list of each pickup and delivery step of the current waybill, and outputs the data list to the pickup and delivery background subsystem.

[0133] The pickup and delivery background subsystem summarizes and calculates the estimated total time length of the pickup and delivery operation.

[0134] Through the S702 pickup and delivery operation time estimation step processing, the calculated pickup and delivery operation estimated total time length data is synchronized to the S703 accurate push timeout warning step processing.

[0135] After the S701 pickup and delivery operation step identification step and the S702 pickup and delivery operation time estimation step processing, enter the S703 accurate push timeout warning step accurate push timeout warning processing, and the processing flow of this step is as follows:

[0136] According to the type of the waybill, identify orders with high risk levels of timeout warning due to strict performance time requirements, such as fresh food orders, customer-mandated performance time orders, etc.

[0137] The call positioning subsystem interface is called by the calling background subsystem, and the current real-time location information of the courier and the destination address data of the to-be-called task are input.

[0138] The calling background subsystem calculates the overtime warning time of the to-be-called task according to the total estimated calling operation time, the route time and the user expected performance time obtained through the waybill subsystem.

[0139] The calling background subsystem pushes the overtime warning message to the user client according to the accurate overtime warning time calculated through the above process and the order warning risk level, and preferentially pushes the orders with high warning levels. For orders that need to be performed immediately, the courier is prompted to process immediately through a pop-up window. Only when the calling operation of such orders is completed preferentially, the new overtime warning order prompt message is pushed again according to the accurate overtime warning logic.

[0140] After the user client receives the overtime warning message, the message is displayed prominently on the front end to prompt the courier to change the waybill that will be overdue and to process immediately to avoid calling delay and user complaints.

[0141] Through the above process, the accurate pushing of the overtime warning message of the to-be-called task is completed.

[0142] The present disclosure analyzes the real-time information of the to-be-called waybill by combining the waybill subsystem, the user client, the calling background subsystem, the data processing subsystem and the positioning subsystem, identifies the calling operation link type of the waybill, calculates the time of each calling operation link (such as weight determination, real-name authentication, opening box and taking photos, consumable packaging processing, delivery photograph uploading, user signature, etc.) based on the historical point data of each calling operation link of the user client through the data processing subsystem, calculates an accurate overtime warning time difference by combining the user expected performance time, the route time calculated by the positioning subsystem and the estimated total calling operation time through the calling background subsystem, and then accurately pushes the overtime warning message to the user client to remind the courier to process the calling task in time. The present disclosure realizes the fine overtime warning of the calling task of express delivery by estimating the calling operation time, and accurately reminds the courier to process the calling task that will be overdue in time, reduces the calling overtime rate, improves the user's experience of receiving and sending mail and the courier's experience of calling, and reduces the probability of the courier's overtime performance of the calling task.

[0143] Based on the same inventive concept, the embodiment of the present disclosure also provides a task pre-warning device, as follows. Since the principle of solving problems of the device embodiment is similar to the above-mentioned method embodiment, the implementation of the device embodiment can be referred to the implementation of the above-mentioned method embodiment, and the repeated parts will not be described here.

[0144] Figure 8 A schematic diagram of a task pre-warning device provided by an embodiment of the present disclosure is shown. As shown in the figure, Figure 8 The task pre-warning device of the present embodiment comprises 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 pre-warning module 860.

[0145] The first acquisition module 810 is configured to acquire real-time information of a shipping order, wherein the real-time information of the shipping order comprises an expected fulfillment time.

[0146] The link identification module 820 is configured to identify a pre-assessment link of the shipping order based on the real-time information of the shipping order.

[0147] The first calculation module 830 is configured to calculate a total duration of the task based on the pre-assessment link and a pre-stored historical actual operation link duration.

[0148] The second acquisition module 840 is configured to acquire a route duration corresponding to the shipping order.

[0149] The second calculation module 850 is configured to calculate a timeout pre-warning time based on the total duration of the task, the route duration, and the expected fulfillment time.

[0150] The timeout pre-warning module 860 is configured to generate a timeout pre-warning message based on the timeout pre-warning time, and send the timeout pre-warning message to a user client.

[0151] In one embodiment, when a plurality of shipping orders are acquired, the timeout pre-warning module 860 is further configured to determine a priority of each shipping order, and preferentially push a timeout pre-warning message of a high priority.

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

[0153] In one embodiment, the first calculation module 830 is configured to send the pre-assessment link to a data processing subsystem, so that the data processing subsystem predicts a duration of the pre-assessment link based on a historical task duration, receives a duration of the pre-assessment link returned by the data processing subsystem, and obtains the total duration of the task based on the duration of the pre-assessment link.

[0154] It should be noted that the duration of the historical practical operation is calculated from the data points of the pickup and dispatch practical operation reported by the user client and stored in the data processing subsystem. 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 pickup and dispatch task to the positioning subsystem, so that the positioning subsystem can calculate the travel time based on the current location information of the user client, the destination address data of the pickup and dispatch task and the historical operation trajectory of the user client; and acquire the travel time sent by the positioning subsystem.

[0156] In this embodiment, real-time information of the waybill is obtained, including the expected fulfillment time; the real-time information of the waybill is used to identify the pickup and delivery operation stages, generating stages to be evaluated; the total pickup and delivery operation time is calculated based on the stages to be evaluated and the pre-stored historical operation stages; the travel time corresponding to the waybill is obtained; the overtime warning time is calculated based on the total pickup and delivery task time, travel time, and expected fulfillment time; and an overtime warning message is generated based on the overtime warning time and sent to the user client. This allows for more refined push of overtime warning messages, providing clearer guidance for frontline couriers in pickup and delivery operations and improving the processing efficiency of pickup and delivery tasks.

[0157] According to another aspect of this disclosure, a pickup and delivery task early warning system is also provided, including a pickup and delivery backend subsystem 720, a waybill subsystem 730, a data processing subsystem 740, a positioning subsystem 750, and a user client 710. The waybill subsystem 730 is used to store real-time information of waybills; the pickup and delivery backend subsystem 720 is used to acquire real-time information of waybills, including expected fulfillment time; identify pickup and delivery operation stages based on the real-time information of waybills, and generate stages to be evaluated for the waybill; the data processing subsystem 740 is used to store the duration of historical operational stages; and the positioning subsystem 750... The location subsystem 750 is used to determine the travel time corresponding to the waybill based on the real-time location of the user client and the destination location of the waybill; the pickup and delivery backend subsystem 720 is also used to calculate the total pickup and delivery operation time based on the time of the link to be evaluated and the pre-stored historical operation link; obtain the travel time corresponding to the waybill; calculate the timeout warning time based on the total pickup and delivery task time, travel time and 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] Those skilled in the art can understand that each aspect of the present application can be implemented as a system, a method or a program product. Therefore, each aspect of the present application can be specifically implemented as a complete hardware embodiment, a complete software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software aspects, which can be collectively referred to as "circuitry", "module" or "system" here.

[0159] The electronic device 900 according to this embodiment of the present application will be described below with reference to Figure 9 Figure 9 The electronic device 900 shown is merely an example and should not limit the function and scope of use of the embodiments of the present application.

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

[0161] The storage unit stores program code that can be executed by the processing unit 910, so that the processing unit 910 performs the steps described in the "Exemplary Method" section above according to various exemplary embodiments of the present application. For example, the processing unit 910 can perform the steps of obtaining real-time information of a shipping order, the real-time information of the shipping order including an expected fulfillment time, as shown in Figure 2

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

[0163] The storage unit 920 can further include a program / utility 9204 having a set of 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 thereof can include implementation of a network environment.

[0164] ​​Bus 930 can be one or more of several types of bus structures including a memory bus or memory controller, a peripheral bus, a graphics bus, a processor or local bus using any of a variety of bus architectures.

[0165] Electronic device 900 can also communicate with one or more external devices 940 such as a keyboard or pointing device, a Bluetooth device, etc.; other devices associated with electronic device 900; and / or one or more devices that enable user interaction with electronic device 900 (e.g., Figure 9 As shown, network adapter 960 communicates with the other Figure 9 It should be appreciated that the software modules described herein can be stored in persistent stores of the electronic device 900. For example, the software modules can be stored in the RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, as well as any combination thereof. Note that the software modules can also be transmitted or received as a computer data signal in a carrier wave or any other form of electromagnetic or optical communication signal on a communication medium. Given the

[0166] From the description given above, those skilled in the art will readily perceive that the example embodiments described herein can be practiced by using software coded instructions. Thus, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, USB flash disk, or mobile hard disk, etc.) or a network on the Internet, and includes a number of instructions for causing a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.

[0167] In the example embodiments of the present disclosure, a computer readable storage medium is also provided, which can be a readable signal medium or a readable storage medium. In the example embodiments of the present disclosure, a computer program product is also provided, which includes a computer program or computer instructions loaded and executed by a processor to enable a computer to implement the steps of the methods disclosed in the above embodiments.

[0168] More specific examples of the computer-readable storage medium in the present disclosure can include but are not limited to an electrical connection having one or more wires, a portable computer diskette, 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 disc 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 can include a data signal carrying the readable program code in a baseband or in a carrier wave. Such a propagated data signal can take a wide variety of forms, including but not limited to electro-magnetic, optical, or any suitable combination thereof. A computer readable medium can also be any medium that can be read by a computer or a device that can be used to store or transport the program in a functional manner, rather than the medium that the program is presented on.

[0170] Optionally, program code embodied on a computer readable storage medium can be transmitted by any data transmission techniques, including but not limited to radio frequency, wireless, cable, wire, optical fiber cable, or any suitable combination thereof.

[0171] In an implementation, the program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, and the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on a user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's device and partly on a remote computing device or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider (ISP).

[0172] It should be noted that, although several modules or units for a device to perform actions are mentioned in the above detailed description, the division into the modules or units is not mandatory. In fact, according to an embodiment of the present disclosure, features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, features and functions of one module or unit described above can be further divided into a plurality of modules or units.

[0173] Moreover, although individual steps of the methods in the present disclosure are described in a particular order in the drawings, this is not required or implied, nor is it necessary to perform all of the steps shown to achieve the desired result. Additionally or alternatively, certain steps can be omitted, combined into a single step, performed in a different order, broken down into multiple steps, and / or the like.

[0174] Those skilled in the art will readily understand that the example embodiments described herein can be implemented by software and / or by hardware coupled with software, as described above. Thus, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash disk, a mobile hard disk, or the like) or on a network, and includes a number of instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the methods according to the embodiments of the present disclosure.

[0175] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure following the general principles thereof and including such departures from the present disclosure that come within known use or custom in the art to which the present disclosure pertains. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the present disclosure are indicated by the appended claims.

Claims

1. A method for prewarning a task, characterized in that, include: Obtain real-time information of the waybill, including the expected fulfillment time; The real-time information of the waybill is used to identify the pickup and delivery operation stages, and to generate the stages to be evaluated for the waybill. The total duration of the pickup and dispatch task is calculated based on the duration of the stages to be evaluated and the pre-stored historical operation stages. Obtain the travel time corresponding to the waybill; Calculate the overtime warning time based on the total duration of the pickup and dispatch task, the travel time, and the expected delivery time; Based on the timeout warning time, a timeout warning message is generated and sent to the user client; The step of calculating the total duration of the pickup and dispatch task based on the stage to be evaluated and the pre-stored historical operation stage durations includes: sending the stage to be evaluated to the data processing subsystem so that the data processing subsystem can predict the duration of the stage to be evaluated based on the historical operation stage durations, wherein one pickup and dispatch operation stage corresponds to one historical operation stage duration; receiving the duration of the stage to be evaluated returned by the data processing subsystem; and obtaining the total duration of the pickup and dispatch task based on the duration of the stage to be evaluated.

2. The method of claim 1, wherein, When multiple waybills are received, sending the timeout warning message to the user client includes: Determine the priority of each waybill and push timeout warning messages to high-priority waybills first. 3.The method 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 is not received from the user client within a preset time, a new timeout warning message is generated and sent to the user client.

4. The method of claim 1, wherein the alerting of the task is performed by a server. The duration of the historical operation process is calculated from the data points of the pickup and dispatch operation process reported by the user client and stored in the data processing subsystem.

5. The method of claim 1, wherein the alerting of the task is performed by a server. The process of obtaining the journey time corresponding to the waybill includes: The current location information of the user client and the destination address data of the pickup and dispatch task are sent to the positioning subsystem so that the positioning subsystem can calculate the travel time based on the current location information of the user client, the destination address data of the pickup and dispatch task and the historical operation trajectory of the user client. Obtain the travel time sent by the positioning subsystem.

6. A task alerting device, comprising: include: The first acquisition module is used to acquire real-time information of the waybill, including the expected fulfillment time. The process identification module is used to identify the pickup and delivery process in the real-time information of the waybill and generate the process to be evaluated in the waybill. The first calculation module is used to calculate the total duration of the pickup and dispatch task based on the evaluation stage and the pre-stored historical operation stage durations. The second acquisition module is used to acquire the travel time corresponding to the waybill; The second calculation module is used to calculate the overtime warning time based on the total duration of the pickup and dispatch task, the travel time, and the expected fulfillment time. The timeout warning module is used to generate a timeout warning message based on the timeout warning time and send the timeout warning message to the user client; The first calculation module is further configured to send the to-be-evaluated link to a data processing subsystem, so that the data processing subsystem predicts the time length of the to-be-evaluated link according to historical actual operation link time lengths, wherein one pickup operation link corresponds to one historical actual operation link time length; receive the time length of the to-be-evaluated link returned by the data processing subsystem; and obtain the total time length of the pickup task according to the time length of the to-be-evaluated link.

7. A task alerting system, comprising: The system comprises a pickup background subsystem, a waybill subsystem, a data processing subsystem, a positioning subsystem and a user client, wherein The waybill subsystem is configured to store real-time information of a waybill. The pickup background subsystem is configured to acquire real-time information of a waybill, wherein the real-time information of the waybill comprises an expected fulfillment time; perform pickup task link identification on the real-time information of the waybill, generate a to-be-evaluated link of the waybill, and send the to-be-evaluated link to the data processing subsystem. The data processing subsystem is configured to store historical actual operation link time lengths, receive the to-be-evaluated link, predict the time length of the to-be-evaluated link according to the historical actual operation link time lengths, wherein one pickup operation link corresponds to one historical actual operation link time length, and return the time length of the to-be-evaluated link to the pickup background subsystem. The positioning subsystem is configured to determine a route time length corresponding to a waybill according to a real-time position of the user client and a destination position of the waybill. The pickup background subsystem is further configured to calculate a total time length of a pickup task according to the to-be-evaluated link and the pre-stored historical actual operation link time lengths; acquire the route time length corresponding to the waybill; calculate an overtime warning time according to the total time length of the pickup task, the route time length and the expected fulfillment time; generate an overtime warning message according to the overtime warning time, and send the overtime warning message to the user client. The user client is configured to receive the overtime warning message, so that the user processes the waybill. The pickup background subsystem is further configured to receive the time length of the to-be-evaluated link returned by the data processing subsystem, and obtain the total time length of the pickup task according to the time length of the to-be-evaluated link.

8. An electronic device, comprising: comprise: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the pickup task warning method according to any one of claims 1-5 by executing the executable instructions.

9. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the pickup task warning method according to any one of claims 1-5.

Images