Delivery task scheduling method, device, and electronic equipment

Abstract

The present application discloses a method for dispatching delivery tasks, which belongs to the field of computer technology and helps to improve the timeliness of delivery task execution of a delivery platform. The method includes: the delivery platform receives a delivery task generated according to an order to be delivered, and obtains the delivery configuration data of the store associated with the delivery task, the delivery configuration data including: the store-bound delivery person identification and / or the circle-based delivery person identification, and the delivery task overflow condition; when the delivery task matches the delivery task overflow condition, obtain the full network delivery person identification stored in the delivery platform; and according to the category order of the store-based delivery person identification, the circle-based delivery person identification, and the full network delivery person identification, judge in turn whether the delivery person associated with each delivery person identification meets the conditions for executing the delivery task, and when it is judged that the delivery person associated with a delivery person identification meets the conditions for executing the delivery task, send the delivery task to the delivery task receiving terminal bound to a delivery person identification in the category of delivery person identification.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a delivery task scheduling method, device, electronic device, and computer-readable storage medium. Background Art

[0002] In the field of short-distance logistics and distribution, in order to meet the needs of some stores with higher requirements for delivery service quality and delivery timeliness, they will be equipped with dedicated delivery personnel, and the delivery tasks of these stores will be performed by the assigned dedicated delivery personnel first. When there are many delivery tasks and the dedicated delivery personnel cannot complete them on time, in order to ensure delivery timeliness, the delivery platform will usually dispatch the delivery tasks to full-time delivery personnel registered on the delivery platform. Since the full-time delivery personnel registered on the delivery platform accept the delivery task scheduling of the entire delivery platform, each full-time delivery personnel is responsible for multiple delivery tasks. In order to ensure the same delivery timeliness of the dedicated delivery personnel, it will often affect the timeliness of other delivery tasks.

[0003] It can be seen that improving the overall delivery timeliness of delivery tasks in the delivery platform is a problem that needs to be solved. Summary of the Invention

[0004] The embodiment of the present application provides a delivery task scheduling method, which helps to improve the timeliness of the execution of delivery tasks.

[0005] To solve the above problems, in a first aspect, an embodiment of the present application provides a delivery task scheduling method, comprising:

[0006] The delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs;

[0007] The delivery platform matches the identifier with pre-stored store configuration data to obtain the store's delivery configuration data, wherein the delivery configuration data includes: the store's resident delivery person identifier and / or circle-based delivery person identifier, and a delivery task overflow condition; the circle-based delivery person identifier is the delivery person identifier bound to the store set to which the store belongs;

[0008] Matching and judging the preset attribute information of the delivery task with the delivery task overflow condition;

[0009] In response to the delivery task matching the delivery task overflow condition, obtaining the network-wide delivery personnel identification stored in the delivery platform;

[0010] Establishing a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store and the obtained network-wide delivery person identification;

[0011] The delivery platform judges in order of the categories of store-based deliveryman identification, circle-based deliveryman identification, and network-wide deliveryman identification, based on the delivery task information stored in the delivery platform in association with each deliveryman identification in the deliveryman identification set, whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task; and when it is judged that the deliveryman associated with a deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a deliveryman identification in this category.

[0012] In a second aspect, an embodiment of the present application provides a delivery task scheduling device, comprising:

[0013] A delivery task receiving module is used for the delivery platform to receive delivery tasks generated based on orders to be delivered, wherein the delivery tasks carry the identifier of the store to which the orders to be delivered belong;

[0014] a store configuration data acquisition module, configured for the delivery platform to match the identifier with pre-stored store configuration data to obtain the delivery configuration data for the store, wherein the delivery configuration data includes: the identifier of the resident delivery person bound to the store and / or the identifier of the resident delivery person in the circle, and a delivery task overflow condition; the identifier of the resident delivery person in the circle is the identifier of the delivery person bound to the store set to which the store belongs;

[0015] A delivery task overflow judgment module, configured to match the preset attribute information of the delivery task with the delivery task overflow condition;

[0016] a network-wide delivery person identification acquisition module, configured to acquire network-wide delivery person identifications stored in the delivery platform in response to the delivery task matching the delivery task overflow condition;

[0017] A first delivery person identification set establishing module, configured to establish a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store and the obtained network-wide delivery person identification;

[0018] The first delivery task scheduling module is used for the delivery platform to judge in sequence whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task according to the category order of the store delivery personnel identification, the circle delivery personnel identification, and the whole network delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set; and when it is judged that the delivery personnel associated with the delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this category.

[0019] In a third aspect, an embodiment of the present application provides a delivery task scheduling method, including:

[0020] The delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs;

[0021] The delivery platform matches the identifier with pre-stored store configuration data to obtain the store's delivery configuration data; wherein the delivery configuration data includes: the store's resident delivery person identifier and the circle's resident delivery person identifier; the circle's resident delivery person identifier is the delivery person identifier bound to the store group to which the store belongs;

[0022] Determining, by a first preset delivery task scheduling engine, whether the in-store delivery person associated with the in-store delivery person identifier meets the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the in-store delivery person identifier;

[0023] In response to the fact that none of the resident delivery personnel associated with the resident delivery personnel identifier satisfies the conditions for executing the delivery task, determining, by a second preset delivery task scheduling engine, whether the resident delivery personnel associated with the resident delivery personnel identifier satisfies the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the resident delivery personnel identifier;

[0024] In response to the store-based delivery person associated with the resident delivery person identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identification.

[0025] In a fourth aspect, an embodiment of the present application provides a delivery task scheduling device, comprising:

[0026] A delivery task receiving module is used for the delivery platform to receive delivery tasks generated based on orders to be delivered, wherein the delivery tasks carry the identifier of the store to which the orders to be delivered belong;

[0027] A store configuration data acquisition module is used for the delivery platform to match the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store; wherein the delivery configuration data includes: the in-store delivery person identifier and the circle delivery person identifier bound to the store; the circle delivery person identifier is the delivery person identifier bound to the store group to which the store belongs;

[0028] a first scheduling judgment module, configured to determine, through a first preset delivery task scheduling engine, whether the in-store delivery person associated with the in-store delivery person identifier meets the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the in-store delivery person identifier;

[0029] a second scheduling judgment module for, in response to the fact that none of the resident delivery personnel associated with the resident delivery personnel identifiers meet the conditions for executing the delivery task, judging, through a second preset delivery task scheduling engine and based on the in-progress delivery task information stored in the delivery platform in association with the resident delivery personnel identifiers, whether the resident delivery personnel associated with the resident delivery personnel identifiers meet the conditions for executing the delivery task;

[0030] The first task scheduling module is configured to send the delivery task to a delivery task receiving terminal bound to the resident delivery person identification in response to the resident store delivery person associated with the resident delivery person identification meeting the conditions for executing the delivery task.

[0031] In a fifth aspect, an embodiment of the present application further discloses an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the delivery task scheduling method described in the embodiment of the present application is implemented.

[0032] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the delivery task scheduling method disclosed in the embodiment of the present application are performed.

[0033] The delivery task scheduling method disclosed in the embodiment of the present application receives a delivery task generated according to an order to be delivered through a delivery platform, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs; the delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the in-store delivery person identifier and / or the in-circle delivery person identifier bound to the store, and the delivery task overflow condition; the in-circle delivery person identifier is the delivery person identifier bound to the set of stores to which the store belongs; the preset attribute information of the delivery task is matched and judged with the delivery task overflow condition; in response to the delivery task matching the delivery task overflow condition, the network-wide delivery person identifier stored in the delivery platform is obtained; based on A deliveryman identification set is established based on the in-store deliveryman identification and / or in-circle deliveryman identification bound to the store and the obtained network-wide deliveryman identification; the delivery platform follows the category order of the in-store deliveryman identification, the in-circle deliveryman identification, and the network-wide deliveryman identification, and based on the delivery task information stored in the delivery platform associated with each deliveryman identification in the deliveryman identification set, determines in turn whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task; and when it is determined that the deliveryman associated with a deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a deliveryman identification in this category, which can improve the timeliness of delivery task execution of the delivery platform.

[0034] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0036] Figure 1 This is a flow chart of the delivery task scheduling method of Example 1 of the present application;

[0037] Figure 2 This is a flow chart of the delivery task scheduling method of Example 2 of the present application;

[0038] Figure 3 This is a schematic diagram of the relationship between delivery personnel with different identity attributes and store locations in Example 2 of this application;

[0039] Figure 4 This is one of the flow charts of the delivery task scheduling method of Example 3 of the present application;

[0040] Figure 5 This is the second flow chart of the delivery task scheduling method of Example 3 of the present application;

[0041] Figure 6 This is one of the structural diagrams of the delivery task scheduling device according to the fourth embodiment of the present application;

[0042] Figure 7 This is the second structural diagram of the delivery task scheduling device of the fourth embodiment of the present application;

[0043] Figure 8 This is one of the structural diagrams of the delivery task scheduling device of Example 5 of the present application;

[0044] Figure 9 This is the second structural diagram of the delivery task scheduling device of the fifth embodiment of the present application;

[0045] Figure 10 A block diagram schematically shows an electronic device for executing the method according to the present application; and

[0046] Figure 11The figure schematically shows a storage unit for storing or carrying a program code for implementing the method according to the present application. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0048] Example 1

[0049] The embodiment of the present application discloses a method for dispatching a delivery task, such as Figure 1 As shown, the method includes: steps 110 to 160.

[0050] In step 110 , the delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries an identifier of the store to which the order to be delivered belongs.

[0051] When the order system generates a new order, it generates a delivery task based on the store to which the order belongs, the delivery time, the delivery destination, and other data, and sends it to the delivery platform. The delivery task carries information such as the store ID, delivery time, and delivery destination of the order to be delivered.

[0052] Step 120: The delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store.

[0053] Among them, the delivery configuration data includes: the in-store delivery staff identification and / or the circle delivery staff identification bound to the store, and the delivery task overflow condition; the circle delivery staff identification is the delivery staff identification bound to the store set to which the store belongs, and the store configuration data also includes: store set information, that is, the binding data between the store and the store set to which it belongs.

[0054] The distribution platform pre-stores store configuration data, which may include: store identification, store-based delivery staff identification stored in conjunction with the store identification, the store collection to which the store belongs, the store's delivery task overflow conditions, and other data.

[0055] After receiving a delivery task, the delivery platform executes the delivery task scheduling based on the data carried by the delivery task. First, the delivery platform matches the store identifier of the delivery order carried in the delivery task with the store identifier in the pre-stored store configuration data to obtain the store configuration data associated with the delivery task.

[0056] The distribution platform described in the embodiments of the present application can be a network platform that provides ordering, shopping services, and order delivery services. The stores stationed on the distribution platform configure the products sold, delivery areas, time periods, delivery personnel and other information through the website page of the distribution platform or the application client (such as the merchant side client). The distribution platform stores the configuration information of each stationed store. For example, the distribution platform stores the store identification and the store configuration information as store configuration data. The store configuration data includes at least: store identification (such as one or more of the store name, identity identification, and store address), store delivery personnel information (for example, including: the number of store delivery personnel, one or more of the store delivery personnel identification), and circle information (such as the store set that shares the circle delivery personnel with the store, the number of the circle delivery personnel bound to the store set, and one or more of the circle delivery personnel identification). In some embodiments of the present application, the store configuration data may also include: delivery area, delivery task overflow conditions, wherein the delivery task overflow conditions further include: delivery task overflow quantity threshold, overflow time period and other information.

[0057] Among them, the in-store deliveryman is a deliveryman who performs the delivery task of a fixed store (i.e., the delivery starting address); the in-circle deliveryman is a deliveryman who performs the delivery task of multiple fixed stores in a specified geographical area, that is, the deliveryman who performs the delivery task of each store in a certain store set; the full-network deliveryman is a deliveryman who can perform the delivery task of any store stationed in the delivery platform. In some embodiments of the present application, the full-network deliveryman is not bound to any store, and the full-network deliveryman further includes: full-time deliverymen and full-network part-time deliverymen. Among them, the full-time deliverymen of the full network are delivery task executors of full-time deliverymen registered as full-time deliverymen on the delivery platform, who only accept the dispatch of the delivery platform and perform the delivery tasks of the delivery platform. The part-time deliverymen of the full network are delivery task executors of part-time deliverymen registered as delivery platforms, and part-time deliverymen of the full network can also undertake delivery tasks outside the delivery platform.

[0058] In some embodiments of the present application, the number of resident delivery personnel and the resident delivery personnel identifications bound to each store can be determined based on the historical delivery data of the store, and a store set consisting of specified stores in a specified geographical area can be determined, and the number of resident delivery personnel and the resident delivery personnel identifications shared by all stores in the store set can be further determined, and the store information (such as the store identification and / or the starting delivery address) can be bound and stored with at least the resident delivery personnel identification and the store set, and the resident delivery personnel information shared by all stores in the store set to obtain store configuration data.

[0059] After the delivery platform receives a delivery task for an order from a specific store (for example, after receiving a takeout order from a user via a client at a specific store), the delivery platform will determine at least the ID of the resident delivery person associated with the store based on the pre-stored store configuration data for the store. If the pre-stored store configuration data for the store includes binding data between the store and a store set, the platform will further obtain the ID of the resident delivery person associated with the store set based on the information of the store set associated with the store. The obtained ID of the resident delivery person is used to identify the resident delivery person associated with the store.

[0060] Step 130: Match and determine the preset attribute information of the delivery task with the delivery task overflow condition.

[0061] After determining the in-store delivery staff identification and circle delivery staff identification bound to the store, this application also needs to determine whether the delivery task can overflow to the entire network capacity if the in-store capacity and circle capacity cannot meet the demand.

[0062] In some embodiments of the present application, the delivery task overflow condition in the store configuration data includes one or more of the following information: a delivery task overflow area, a delivery task overflow time period, and a delivery task overflow quantity threshold. Accordingly, the step of matching and judging the preset attribute information of the delivery task with the delivery task overflow condition includes: determining the matching result between the corresponding attribute information of the store's delivery task and the delivery task overflow condition based on one or more of the following comparison results: comparing the destination of the delivery task with the delivery task overflow area; comparing the number of overflowed delivery tasks of the store to which the delivery order that generated the delivery task belongs with the delivery task overflow quantity threshold; and comparing the delivery time of the delivery task with the delivery task overflow time period.

[0063] For example, after obtaining the store configuration data based on the store identification, if the delivery task overflow conditions in the store configuration data include three pieces of information: the delivery task overflow area, the delivery task overflow time period, and the delivery task overflow quantity threshold, then the delivery platform needs to compare the relevant attribute information of the delivery task with the above three pieces of information respectively, and determine whether the delivery task matches the delivery task overflow conditions based on the comparison results. If the delivery task overflow conditions in the store configuration data include: the delivery task overflow area and the delivery task overflow time period, then the delivery platform needs to compare the destination of the delivery task with the delivery task overflow area, and compare the delivery time of the delivery task with the delivery task overflow time period, and then determine that the delivery task matches the delivery task overflow conditions based on the comparison results of the delivery task destination and delivery time with the delivery task overflow conditions.

[0064] In some embodiments of the present application, the delivery personnel registered on the delivery platform include delivery personnel with one or more of the following identity attributes: in-store delivery personnel, in-circle delivery personnel, and network-wide delivery personnel. The scheduling priority of delivery personnel with different identity attributes is from high to low: in-store delivery personnel, in-circle delivery personnel, and network-wide delivery personnel.

[0065] For example, each store first configures the delivery task overflow area and delivery task overflow time period on the delivery platform, which allows the delivery task to be dispatched to the delivery personnel of the entire network, and stores the delivery task overflow area and delivery task overflow time period as the delivery task overflow condition. When executing the delivery task scheduling, the delivery platform determines whether the delivery task can be dispatched to the delivery personnel of the entire network based on the delivery task overflow conditions in the above-mentioned store configuration data stored in advance. If so, the resident delivery personnel identification and resident delivery personnel identification configured in the store configuration data of the store to which the delivery task belongs will be added to the delivery personnel identification set corresponding to the delivery task. After that, the delivery personnel identification of the entire network whose delivery range matches the delivery address of the delivery task will be determined based on the delivery range of each delivery personnel of the entire network, and added to the delivery personnel identification set.

[0066] For another example, first, based on the delivery task overflow area set by the store to which the delivery task belongs, determine whether the delivery start address and delivery destination of the delivery task belong to the delivery task overflow area; if so, further determine whether the delivery time of the delivery task matches the delivery task overflow time period set by the store to which the delivery task belongs; if so, then determine whether the number of delivery tasks that have been dispatched to the resident delivery personnel and the full-network delivery personnel has reached the delivery task overflow number threshold. If not, then determine the full-network delivery personnel ID whose delivery range matches the delivery address of the delivery task based on the delivery range of each full-network delivery personnel, add it to the delivery personnel ID set, and determine the resident delivery personnel ID and the resident delivery personnel ID of the store based on the store configuration data of the store to which the delivery task belongs, and add them to the delivery personnel ID set. If any of the above conditions is not met, the delivery task will not be dispatched to the full-network delivery personnel, that is, the full-network delivery personnel ID will not be included in the delivery personnel ID set.

[0067] In other embodiments of the present application, other business logics may be used to determine candidate delivery personnel based on the store configuration data of the store to which the delivery task belongs, and these will not be listed one by one in this application document.

[0068] Step 140: In response to the delivery task matching the delivery task overflow condition, obtain the network-wide delivery personnel identification stored in the delivery platform.

[0069] When it is determined that the delivery task can overflow to the entire network's transportation capacity based on the preset attribute information of the delivery task and the delivery task overflow conditions of the store, the delivery platform will obtain the network-wide delivery personnel identification stored in the delivery personnel database as the identification of some of the dispatchable delivery personnel.

[0070] In some embodiments of the present application, in response to the delivery task matching the delivery task overflow condition, obtaining the network-wide delivery personnel identification stored in the delivery platform includes: the delivery platform obtains the network-wide delivery personnel identification that matches the delivery area with the destination and starting delivery address of the delivery task based on the pre-stored correspondence between the network-wide delivery personnel identification and the delivery area. For example, the delivery platform pre-stores the correspondence between the network-wide delivery personnel identification and the delivery area. After the delivery platform receives the delivery task, it first matches the starting delivery address and destination of the to-be-delivered order that generates the delivery task with the delivery area in the pre-stored correspondence between the network-wide delivery personnel identification and the delivery area on the delivery platform, and determines that the delivery area includes the network-wide delivery personnel identification that matches the starting delivery address and destination of the to-be-delivered order.

[0071] Step 150: Establish a deliveryman identification set based on the store-based deliveryman identification and / or the circle-based deliveryman identification bound to the store and the obtained network-wide deliveryman identification.

[0072] Afterwards, a delivery driver identification set is established based on the store-based delivery driver identification, the circle-based delivery driver identification, and the obtained network-wide delivery driver identification. The delivery driver identification set includes three types of delivery driver identifications: store-based delivery driver identification, circle-based delivery driver identification, and network-wide delivery driver identification. Each type of delivery driver identification identifies a type of delivery driver. For example, each store-based delivery driver identification identifies a store-based delivery driver, each circle-based delivery driver identification identifies a circle-based delivery driver, and each network-wide delivery driver identification identifies a network-wide delivery driver.

[0073] Step 160: the delivery platform determines in order whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task according to the order of the categories of the in-store delivery personnel identification, the in-circle delivery personnel identification, and the network-wide delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set; and when it is determined that the delivery personnel associated with the delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this category.

[0074] After determining the set of delivery driver identifiers that can be used to schedule the delivery task, the delivery platform inputs the determined set of delivery driver identifiers and the relevant information of the delivery task into a preset delivery task scheduling engine, which then performs hierarchical scheduling of the delivery task. As previously mentioned, the scheduling priority of delivery drivers with different identity attributes is, from high to low, as follows: in-store delivery drivers, in-circuit delivery drivers, and full-network delivery drivers. Full-network delivery drivers can further include full-time delivery drivers and part-time delivery drivers. When scheduling overflow delivery tasks, full-time delivery drivers have a higher scheduling priority than part-time delivery drivers.

[0075] In some embodiments of the present application, the delivery platform judges whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task in accordance with the order of categories of the resident delivery personnel identification, the resident delivery personnel identification, and the whole network delivery personnel identification, according to the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set, and when it is judged that the delivery personnel associated with a delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this type of delivery personnel identification, including: the delivery platform judges whether the delivery personnel associated with the resident delivery personnel identification meets the conditions for executing the delivery task according to the delivery task information stored in the delivery platform in association with each resident delivery personnel identification in the delivery personnel identification set through a preset delivery task scheduling engine; in response to the delivery personnel associated with the resident delivery personnel identification meeting the conditions for executing the delivery task, the delivery task is sent to the resident delivery personnel identification in the store through the preset delivery task scheduling engine. otherwise, the preset delivery task scheduling engine determines whether the delivery person associated with the resident delivery person ID meets the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform and associated with each resident delivery person ID in the delivery person ID set. In response to the delivery person associated with the resident delivery person ID meeting the conditions for executing the delivery task, the preset delivery task scheduling engine sends the delivery task to a delivery task receiving terminal bound to the resident delivery person ID. Otherwise, the preset delivery task scheduling engine determines whether the delivery person associated with the global delivery person ID meets the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform and associated with each global delivery person ID in the delivery person ID set. In response to the delivery person associated with the global delivery person ID meeting the conditions for executing the delivery task, the preset delivery task scheduling engine sends the delivery task to a delivery task receiving terminal bound to the global delivery person ID. The conditions for executing the delivery task include: satisfying the delivery business constraints and the delivery time being less than or equal to the preset duration. The information on the delivery tasks stored in association with the delivery person identification includes one or more of the following information: the number of unfinished delivery tasks associated with the delivery person identification and the required delivery time.

[0076] For example, the delivery platform estimates the delivery time and delivery path of the delivery task to be performed by the in-store delivery personnel associated with each in-store delivery personnel identification in the delivery personnel identification set through a preset delivery task scheduling engine, and determines whether there is an in-store delivery personnel who meets the delivery business constraints and whose delivery time does not exceed the delivery time. If so, the delivery task is assigned to the in-store delivery personnel with the shortest delivery time and the best delivery path. Among them, the delivery business constraints include: the maximum number of delivery tasks that a delivery personnel can carry, the assessment time, the delivery distance for which orders are given priority to in-store delivery personnel, and one or more other conditions. In some embodiments of the present application, the existing technology can be used to determine the delivery time and delivery path length of each delivery personnel, which will not be repeated in this embodiment.

[0077] If no in-store delivery driver exists that meets the delivery business constraints and can complete the delivery task without a timeout, the delivery platform will further use the preset delivery task scheduling engine to estimate the delivery time and delivery route for the delivery driver associated with each in-circle delivery driver ID in the delivery driver ID set. The platform will then determine whether any in-circle delivery driver exists that meets the preset business constraints and can complete the delivery task without a timeout. If so, the delivery platform will assign the delivery task to the in-circle delivery driver with the shortest delivery time and optimal delivery route.

[0078] If no resident delivery driver exists who can complete the delivery task within the specified timeframe, the delivery platform will further determine, through a pre-set delivery task scheduling engine, whether any resident delivery driver associated with the network-wide delivery driver identifiers in the delivery driver identifier set can complete the delivery task within the specified timeframe. If a resident delivery driver exists who can complete the delivery task within the specified timeframe, the delivery platform will assign the delivery task to the resident delivery driver with the shortest delivery time and optimal delivery route.

[0079] In the prior art, when scheduling delivery tasks, if there is no in-store delivery person who can complete a certain delivery task without timeout, the delivery task will directly overflow to the delivery personnel of the entire network, and the preset delivery task scheduling engine will perform task scheduling among the delivery personnel of the entire network. The delivery task scheduling process in the prior art will have a certain impact on the delivery efficiency of the delivery personnel of the entire network. Taking takeout orders as an example, for some stores with unstable meal delivery times, if the delivery orders overflowed to the delivery personnel of the entire network are delayed, it will extend the delivery time of other delivery orders carried by the delivery personnel of the entire network, and even cause other delivery orders to timeout. In the delivery task scheduling process disclosed in the embodiment of the present application, by setting up in-circle delivery personnel, and overflowing the orders that the in-store delivery personnel cannot deliver on time to the in-circle delivery personnel first, the impact on the delivery efficiency of the delivery personnel of the entire network can be effectively reduced. At the same time, since the in-circle delivery personnel are the delivery personnel shared by the store with overflow orders and other stores in the designated geographical area, the activity area of ​​the in-circle delivery personnel is near the store, and they can undertake delivery tasks within a certain geographical range, so the delivery efficiency is higher. From the above analysis, it can be seen that by setting up resident delivery personnel and improving the scheduling strategy of delivery tasks, the overall delivery efficiency of the delivery platform can be improved.

[0080] In some embodiments of the present application, after the step of determining whether the delivery person associated with the full-network delivery person identification meets the conditions for executing the delivery task, the step further includes: in response to the delivery person associated with the full-network delivery person identification not meeting the conditions for executing the delivery task, sending the delivery task to a delivery task receiving terminal bound to the resident delivery person identification through the preset delivery task scheduling engine or outputting a scheduling failure. For example, when there is no delivery person in the full-network corresponding to the full-network delivery person identification in the delivery person identification set who can complete the delivery task without a timeout, a resident delivery person with the shortest delivery time and the best delivery path is selected from the resident delivery persons associated with the resident delivery person identification in the delivery person identification set to assign the delivery task, or the delivery platform outputs a delivery task scheduling failure.

[0081] In some embodiments of the present application, the network-wide delivery personnel include: network-wide full-time delivery personnel and network-wide part-time delivery personnel, and correspondingly, the network-wide delivery personnel identification includes: network-wide full-time delivery personnel identification and network-wide part-time delivery personnel identification, and the step of judging whether the delivery personnel associated with the network-wide delivery personnel identification meets the conditions for executing the delivery task through the preset delivery task scheduling engine according to the delivery task information stored in the delivery platform in association with each network-wide delivery personnel identification in the delivery personnel identification set, includes: judging whether the network-wide full-time delivery personnel associated with the network-wide delivery personnel identification meets the conditions for executing the delivery task through the preset delivery task scheduling engine according to the delivery task information stored in the delivery platform in association with each network-wide delivery personnel identification in the delivery personnel identification set Whether the deliveryman associated with the deliveryman ID meets the conditions for executing the delivery task; in response to the deliveryman associated with the full-time deliveryman ID of the entire network meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the full-time deliveryman ID of the entire network through the preset delivery task scheduling engine; in response to the deliveryman associated with the full-time deliveryman ID of the entire network not meeting the conditions for executing the delivery task, the preset delivery task scheduling engine is used to determine whether the deliveryman associated with the part-time deliveryman ID of the entire network meets the conditions for executing the delivery task based on the delivery task information stored in the delivery platform in association with each part-time deliveryman ID of the entire network in the deliveryman ID set.

[0082] In some embodiments of the present application, the full-network delivery personnel may only include full-time delivery personnel registered in the delivery platform. Usually, in order to improve delivery efficiency, the full-time delivery personnel are usually provided with a delivery area. In other embodiments of the present application, the full-network delivery personnel include full-time delivery personnel (i.e., full-time delivery personnel of the whole network) and part-time delivery personnel (i.e., part-time delivery personnel of the whole network) registered in the delivery platform. When performing delivery task scheduling, the delivery platform first estimates the delivery time and delivery path of the full-time delivery personnel of the whole network associated with each full-time delivery personnel identifier of the whole network in the delivery personnel identifier set through a preset delivery task scheduling engine, and determines whether there is a full-time delivery personnel of the whole network whose estimated delivery time is less than the assessment time of the delivery task (i.e., not overtime). If so, the delivery task is dispatched to the full-time delivery personnel of the whole network with the shortest delivery time and the best delivery path. If the estimated delivery time for each full-time delivery driver on the entire network to perform the delivery task is greater than the assessment time for the delivery task (i.e., there are no delivery situations that do not exceed the time limit), the delivery platform will then use the preset delivery task scheduling engine to estimate the delivery time and delivery route for the part-time delivery driver on the entire network associated with each part-time delivery driver ID in the delivery driver ID set. Next, the delivery platform will determine whether there is a situation where the estimated delivery time of a part-time delivery driver on the entire network is less than the assessment time for the delivery task (i.e., there is no time limit). If so, the delivery task will be assigned to the part-time delivery driver on the entire network with the shortest delivery time and the best delivery route.

[0083] In some embodiments of the present application, after matching and judging the preset attribute information of the delivery task with the delivery task overflow condition, it also includes: in response to the delivery task not matching the delivery task overflow condition, establishing a deliveryman identification set based on the in-store deliveryman identification and / or in-circle deliveryman identification bound to the store; the delivery platform judges in order of the category order of the in-store deliveryman identification and the in-circle deliveryman identification, based on the delivery task information stored in the delivery platform associated with each deliveryman identification in the deliveryman identification set, whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task, and when it is judged that the deliveryman associated with the deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to the deliveryman identification in this type of deliveryman identification.

[0084] In some embodiments of the present application, when a delivery task does not meet the delivery task overflow conditions configured for a store, for example, the overflow delivery tasks of the store have reached a preset threshold, the delivery task will not be dispatched to delivery personnel across the entire network, but will be dispatched among the in-store delivery personnel and the in-circle delivery personnel.

[0085] For example, the delivery platform first uses a preset delivery task scheduling engine to determine whether there is a resident deliveryman among the store's resident deliverymen who can complete the delivery task without timeout. If so, the delivery platform will dispatch the delivery task to the resident deliveryman with the shortest delivery time and the best delivery path. If not, the delivery platform will further determine whether there is a resident deliveryman in the circle who can complete the delivery task without timeout. If so, the delivery platform will dispatch the delivery task to the resident deliveryman with the shortest delivery time and the best delivery path. Otherwise, the delivery platform outputs a scheduling failure.

[0086] In an embodiment of the present application, when judging whether the deliveryman associated with the deliveryman ID meets the conditions for executing the delivery task based on the delivery task information stored in association with the deliveryman ID, the shortest path time required for the deliveryman associated with the deliveryman ID to execute the delivery task can be estimated based on the number of unfinished delivery tasks, the time of the unfinished delivery tasks and the delivery destination stored in association with the deliveryman ID. If the time required for the shortest path is less than the delivery time specified for the delivery task, it is determined that the deliveryman associated with the deliveryman ID meets the conditions for executing the delivery task; otherwise, it is determined that the deliveryman associated with the deliveryman ID does not meet the conditions for executing the delivery task.

[0087] In an embodiment of the present application, the delivery platform executes the above steps through a scheduling server to implement a delivery task scheduling method; stores store configuration data through a store database; and registers delivery personnel and stores delivery personnel information and delivery task information associated with delivery personnel identification through a delivery personnel management system.

[0088] The delivery task scheduling method disclosed in the embodiment of the present application receives a delivery task generated according to an order to be delivered through a delivery platform, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs; the delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the in-store delivery person identifier and / or the in-circle delivery person identifier bound to the store, and the delivery task overflow condition; the in-circle delivery person identifier is the delivery person identifier bound to the set of stores to which the store belongs; the preset attribute information of the delivery task is matched and judged with the delivery task overflow condition; in response to the delivery task matching the delivery task overflow condition, the network-wide delivery person identifier stored in the delivery platform is obtained; based on A deliveryman identification set is established based on the in-store deliveryman identification and / or in-circle deliveryman identification bound to the store and the obtained network-wide deliveryman identification; the delivery platform follows the category order of the in-store deliveryman identification, the in-circle deliveryman identification, and the network-wide deliveryman identification, and based on the delivery task information stored in the delivery platform associated with each deliveryman identification in the deliveryman identification set, determines in turn whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task; and when it is determined that the deliveryman associated with a deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a deliveryman identification in this category, which can improve the timeliness of delivery task execution of the delivery platform.

[0089] The delivery task scheduling method provided in the embodiment of the present application determines the delivery personnel shared with multiple stores in a specified geographical area (i.e., resident delivery personnel) based on the geographical location information of the delivery tasks, and optimizes the delivery task scheduling process of the delivery platform. During the delivery task scheduling process, delivery tasks that the resident delivery personnel cannot execute on time are first overflowed to the corresponding resident delivery personnel, making full use of the geographical location advantages of the resident delivery personnel in the delivery area, which helps to improve the timeliness of delivery task execution. At the same time, it helps to reduce the impact of overflow delivery tasks on the delivery timeliness of delivery personnel across the entire network.

[0090] Example 2

[0091] The embodiment of the present application discloses a method for dispatching a delivery task, such as Figure 2 As shown, it includes: steps 210 to 2120.

[0092] In step 210 , the distribution platform determines a store set based on the distances between the stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set.

[0093] In some embodiments of the present application, the delivery platform matches the identifier with pre-stored store configuration data, and before the step of obtaining the delivery configuration data of the store, it includes: the delivery platform determines a store set based on the distance between the stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set, wherein the stores included in the store set can share delivery personnel; determines the in-store delivery personnel identifier configured for each of the stores based on the delivery task history data of each store in the store set, and determines the in-circle delivery personnel identifier configured for the store set; binds and stores each of the stores with the in-store delivery personnel identifier configured for the store, and binds and stores the store set with the in-circle delivery personnel identifier configured for the store set to obtain binding data.

[0094] In some embodiments of the present application, in order to improve the overall delivery efficiency of the delivery platform, the delivery starting addresses (i.e., stores) of the delivery tasks are clustered based on geographical location, store circles (i.e., store collections) are formed, and shared delivery personnel are configured for the store collections to improve the utilization of delivery resources and the processing efficiency of delivery tasks.

[0095] In some embodiments of the present application, the delivery platform determines a store set based on the distance between stores and the store portrait data of the stores, including: the delivery platform divides the stores in the specified geographical area into at least one candidate store set based on the distance between the geographical locations; for each of the candidate store sets, determines one or more of the following shared delivery personnel indicator scores for the corresponding candidate store set based on the store portrait data of each store in the candidate store set: a meal delivery difficulty score, a peak-valley complementarity score of the distribution of the number of delivery orders, and a delivery range overlap score; the shared delivery personnel indicator scores are weighted and summed according to preset weights to obtain the circle score of each of the candidate store sets; and the candidate store set is selected based on the circle score as the store set within the specified geographical area.

[0096] In some embodiments of the present application, the meal delivery difficulty score is negatively correlated with one or more of the average meal preparation time, average meal pickup time, and average delivery time of each store in the corresponding candidate store set; the delivery order quantity distribution peak-valley complementarity score is positively correlated with the ratio of the average order volume on weekdays to the average order volume on weekends, and the ratio of the off-peak order volume to the peak order volume of each store in the corresponding candidate store set; the delivery range overlap score is positively correlated with the ratio of the specified distance order volume to the total order volume of each store in the corresponding candidate store set within a preset time period. Among them, the weight of each shared deliveryman indicator score is determined based on experimental data. In some embodiments of the present application, the weight of the order volume distribution score during off-peak and peak periods is the largest.

[0097] For example, first, the stores of the same category in a certain business district are divided into multiple candidate store sets according to the condition that the distance between any two stores is no more than 5 kilometers; then, the circle retention score of each candidate store set is calculated respectively based on the store portrait data of the stores in each candidate store set; finally, the candidate store set with the highest circle retention score is determined as the store set corresponding to the business district, or the candidate store sets whose circle retention scores meet the preset conditions are determined as the store sets corresponding to the business district.

[0098] In some embodiments of the present application, the meal delivery difficulty score is used to indicate the overall meal delivery difficulty of the stores in the candidate store set, and the meal delivery difficulty score is negatively correlated with the overall meal delivery difficulty. For example, the weighted sum of the inverse of the average meal preparation time, the inverse of the average meal pickup time, and the inverse of the average delivery time of all stores in the candidate store set can be used as the meal delivery difficulty score of the candidate store set. The weights of the inverse of the average meal preparation time, the inverse of the average meal pickup time, and the inverse of the average delivery time can be equal or other values ​​set according to specific business needs.

[0099] In some embodiments of the present application, the delivery order quantity distribution peak-valley complementarity score is used to indicate the degree of peak-valley complementarity of the delivery order quantity distribution of the stores in the candidate store set, and the delivery order quantity distribution peak-valley complementarity score is positively correlated with the degree of peak-valley complementarity of the delivery order quantity distribution. For example, the ratio of the off-peak order volume to the peak order volume can be used as the delivery order quantity distribution peak-valley complementarity score of the candidate store set. Wherein, the off-peak order volume is calculated based on the sum of the number of delivery tasks of all stores in the candidate store set during off-peak hours, and the peak order volume is calculated based on the sum of the number of delivery tasks of all stores in the candidate store set during peak hours. For example, for the candidate store set consisting of stores A and B, the ratio (a1+b1) of the sum of the off-peak delivery task number a1 of store A and the off-peak delivery task number b1 of store B to the sum of the peak delivery task number a2 of store A and the peak delivery task number b2 of store B can be used as the delivery order quantity distribution peak-valley complementarity score of the candidate store set.

[0100] Alternatively, the weighted sum of the ratio of the average order volume on weekdays to the average order volume on weekends, and the ratio of the order volume during off-peak hours to the order volume during peak hours of all stores in the candidate store set can also be used as the score of the peak-valley complementarity of the distribution of the number of delivery orders of the candidate store set. The average order volume on weekdays is calculated based on the average number of delivery tasks on weekdays for all stores in the candidate store set, and the average order volume on weekends is calculated based on the average number of delivery tasks on weekends for all stores in the candidate store set. For example, for the candidate store set consisting of stores A and B, first, based on the sum a1+b1 of the number of off-peak delivery tasks a1 of store A and the number of off-peak delivery tasks b1 of store B, and the sum a2+b2 of the number of peak-hour delivery tasks a2 of store A and the number of peak-hour delivery tasks b2 of store B, determine the ratio X of the off-peak hour order volume to the peak-hour order volume, X=(a1+b1) / (a2+b2); and, based on the average number of delivery tasks a3 of store A on weekdays and the average number of delivery tasks a4 of store B on weekdays, determine the ratio X of the off-peak hour order volume to the peak-hour order volume. The sum of the average number of delivery tasks b3, a3+b3, the average weekend delivery tasks a4 for store A, and the average weekend delivery tasks b4 for store B, is used to determine the ratio Y of the average weekday order volume to the average weekend order volume: Y = (a3+b3) / (a4+b4). Next, the weighted sum of the ratio of the average weekday order volume to the average weekend order volume and the ratio Y of the off-peak order volume to the peak order volume is calculated using the formula αX+βY to obtain the peak-valley complementarity score for the delivery order quantity distribution of the candidate store set. α and β are the weights of the ratio of the average weekday order volume to the average weekend order volume and the ratio of the off-peak order volume to the peak order volume, respectively.

[0101] In some embodiments of the present application, the delivery range overlap score is used to indicate the degree of overlap of the delivery ranges of the stores in the candidate store set, and the delivery range overlap score is positively correlated with the degree of overlap of the delivery ranges. For example, the delivery range of each delivery task can be first determined based on the historical delivery tasks of each store in the candidate store set, such as determining that the delivery range of each historical delivery task within a preset time period (such as the past month) is 1 km, 2 km, 3 km or greater than 3 km; then, the ratio of the number of delivery tasks with a delivery range greater than or equal to 3 kilometers to the total number of delivery tasks is used as the delivery range overlap score. Since each store in the candidate store set is a store within a specified geographical area, the maximum distance between stores is subject to certain restrictions (such as the maximum distance between stores is less than or equal to 5 kilometers). Then, within this maximum distance limit, the proportion of long-distance delivery tasks of each store is relatively large, and it can be considered that the delivery range overlap of each store is relatively high. That is, the larger the delivery range overlap score, the higher the delivery range overlap of each store.

[0102] The above calculations show that for stores A, B, and C, if store A has more off-peak orders and fewer peak-hour orders, store B has fewer off-peak orders and more peak-hour orders, and store C has more off-peak orders and fewer peak-hour orders, then store set 1, consisting of stores A and B, will have a higher peak-valley complementarity score for the distribution of delivery orders than store set 2, consisting of stores A and C. This precisely reflects the higher peak-valley complementarity between the distribution of delivery orders for stores A and B. This means that the peak and valley periods of the distribution of delivery tasks within the store set are precisely staggered, enabling time-sharing of transportation capacity and fully utilizing shared transportation resources while ensuring the timely execution of delivery tasks. The above calculations also show that the shorter the average serving time, average pickup time, and average delivery time of the stores that make up the set, the easier it is to serve and deliver, and the higher the store set's retention score. In other words, stores with shorter serving time, pickup time, and delivery time are more suitable for forming a store set.

[0103] In some embodiments of the present application, through the above method, stores with low difficulty in delivering meals, high degree of complementarity in the peak and valley distribution of delivery order quantities, and high overlap in delivery ranges are combined into a store set corresponding to the business district, and hierarchical scheduling is performed on the delivery tasks of the stores in the store set to fully improve the delivery efficiency of the delivery platform.

[0104] Step 220: Determine the in-store delivery staff identification configured for each store and the in-circle delivery staff identification configured for the store set based on the delivery task history data of each store in the store set.

[0105] In some embodiments of the present application, the determining of the in-store delivery staff identification configured for each store according to the historical data of delivery tasks of each store in the store set, and the determining of the in-circle delivery staff identification configured for the store set, include: determining the number of in-store delivery staff configured for each store according to the historical mean of delivery tasks of each store in the store set and the time period distribution curve of the number of delivery tasks; determining the number of in-circle delivery staff configured for the store set according to the difference obtained by subtracting the number of delivery tasks undertaken by the in-store delivery staff from the number of delivery tasks for all stores in the store set within a preset time period, and the average number of delivery tasks undertaken by each in-circle delivery staff; determining the in-store delivery staff identification configured for each store according to the number of in-store delivery staff configured for the store, and determining the in-circle delivery staff identification configured for the store set according to the number of in-store delivery staff configured for the store.

[0106] After determining one or more store sets within a specified geographical area, for each store set, the number of on-site delivery personnel for each store in the store set and the number of delivery personnel shared by all stores in the store set (i.e., on-site delivery personnel) are further determined. In some embodiments of the present application, for a certain store in the store set, the average of the number of delivery tasks for the store in the past week is obtained, and the number of delivery tasks Q undertaken by the on-site delivery personnel is determined according to a preset ratio (e.g., 70%) of the number of delivery tasks undertaken by the on-site delivery personnel; then, the estimated per capita order volume q of each on-site delivery personnel is obtained; finally, the number of delivery tasks Q undertaken by the on-site delivery personnel is divided by the estimated per capita order volume q of the on-site delivery personnel, and the resulting quotient is used as the number of on-site delivery personnel for the store.

[0107] The preset ratio of delivery tasks undertaken by in-store delivery personnel is determined based on the time-period distribution curve of the store's delivery task volume. For example, if the time-period distribution curve of a store's delivery task volume is relatively flat, meaning that the store's delivery task volume does not fluctuate much across different time periods, the preset ratio of delivery tasks undertaken by in-store delivery personnel can be set to 80%-90%, allowing more delivery tasks to be performed by in-store delivery personnel. If the time-period distribution curve of a store's delivery task volume is very steep, meaning that the store's delivery task volume fluctuates significantly across different time periods, the ratio can be appropriately lowered, such as to 70%, allowing in-store delivery personnel to perform more delivery tasks.

[0108] After determining the number of on-site delivery personnel for each store in a store set, the total number of delivery tasks that the on-site delivery personnel for all stores in the store set can be determined within a specified time period. The difference between the number of delivery tasks for all stores in the store set within a preset time period and the total number of delivery tasks undertaken by the on-site delivery personnel is used as the number of delivery tasks that the on-site delivery personnel need to undertake. Next, the number of delivery tasks that the on-site delivery personnel need to undertake is divided by the average number of delivery tasks that each on-site delivery personnel can undertake, and the resulting quotient is used to determine the number of on-site delivery personnel assigned to the store set.

[0109] Afterwards, the delivery platform obtains the IDs of a corresponding number of delivery personnel based on the matching degree between the stored delivery personnel registration information (such as delivery range) and the delivery start address of the store's delivery order. These IDs are used as the IDs of the on-site delivery personnel assigned to the store. Based on the matching degree between the stored delivery personnel registration information (such as delivery range) and the geographical area determined by the store collection, the delivery platform obtains the IDs of a corresponding number of delivery personnel based on the matching degree between the stored delivery personnel registration information (such as delivery range) and the geographical area determined by the store collection. These IDs are used as the IDs of the on-site delivery personnel assigned to the store collection.

[0110] Step 230 , binding and storing each of the stores with the identification of the resident deliveryman configured for the store, and binding and storing the store set with the identification of the resident deliveryman configured for the store set, to obtain binding data.

[0111] Next, the delivery platform binds and stores the identifications of the corresponding number of in-store delivery personnel determined to the store information. Simultaneously, the identifications of the corresponding number of in-circle delivery personnel (e.g., including one or more of the in-circle delivery personnel identification, name, account number, and contact information) are bound and stored with the store collection. In some embodiments of the present application, the information bound and stored with the in-circle store information also includes: the in-store delivery personnel's name, contact information, and delivery task receiving terminal; and the information bound and stored with the store collection may also include: the in-circle delivery personnel's name, contact information, and delivery task receiving terminal.

[0112] The geographical distribution relationship between the store locations (i.e., the delivery start address) in the store set and the geographical locations of the store delivery staff and the geographical locations of the circle delivery staff can be obtained by Figure 3 That is, the delivery staff 11, 12 and 13 bound to store 1 pick up food from the store and then deliver it to other locations. When they are not performing delivery tasks, the delivery staff 11, 12 and 13 are distributed in or near store 1. The delivery staff 21 and 22 bound to store 2 are distributed in or near store 2 when they are not performing delivery tasks. Figure 3 The delivery personnel bound to the store group consisting of store 1, store 2 and store 3 are distributed in the geographical area formed by store 1, store 2 and store 3 when they are not performing delivery tasks, so as to facilitate the rapid acceptance of delivery tasks. When this application is implemented, the delivery platform also registers delivery personnel from the entire network, such as Figure 3 The full-network delivery personnel are 1, 2, and 3. Full-network delivery personnel can undertake delivery tasks that in-store delivery personnel and circle delivery personnel cannot undertake. Full-network delivery personnel are not bound to store collections or stores. When there is no delivery task, the position of the full-network delivery personnel is not fixed.

[0113] Therefore, when binding the resident delivery personnel for the store collection, you can select the delivery personnel for binding based on the geographic location information of the delivery personnel registered in the delivery platform.

[0114] In step 240 , the delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries an identifier of the store to which the order to be delivered belongs.

[0115] The delivery platform receives a delivery task generated according to the order to be delivered. The specific implementation method of the delivery task carrying the identifier of the store to which the order to be delivered belongs is shown in Example 1 and will not be repeated in this embodiment.

[0116] In step 250 , the delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store.

[0117] Among them, the delivery configuration data includes: the in-store delivery staff identification and / or the circle delivery staff identification bound to the store, and the delivery task overflow condition; the circle delivery staff identification is the delivery staff identification bound to the store set to which the store belongs.

[0118] The distribution platform matches the identifier with pre-stored store configuration data. The specific implementation method for obtaining the distribution configuration data of the store is shown in Example 1 and will not be repeated in this embodiment.

[0119] Step 260 , determining whether the delivery task matches the delivery task overflow condition. If the delivery task matches the delivery task overflow condition, executing step 270 ; otherwise, jumping to executing step 2110 .

[0120] For a specific implementation method of matching the preset attribute information of the delivery task with the delivery task overflow condition and determining whether the delivery task matches the delivery task overflow condition, please refer to Example 1 and will not be repeated in this embodiment.

[0121] Step 270: In response to the delivery task matching the delivery task overflow condition, obtain the network-wide delivery personnel identification stored in the delivery platform.

[0122] The specific implementation method of matching and judging the preset attribute information of the delivery task with the delivery task overflow condition is shown in Example 1, which will not be repeated in this embodiment.

[0123] Step 280: Create a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store and the obtained network-wide delivery person identification.

[0124] For the specific implementation method of establishing a deliveryman identification set based on the store-based deliveryman identification and / or the circle-based deliveryman identification bound to the store and the obtained network-wide deliveryman identification, please refer to Example 1 and will not be repeated in this example.

[0125] In step 290, the delivery platform determines in order whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task according to the order of the categories of the store delivery personnel identification, the circle delivery personnel identification, and the whole network delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set. When it is determined that the delivery personnel associated with the delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this category.

[0126] The delivery platform judges whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task in the order of the categories of the store delivery personnel identification, the circle delivery personnel identification, and the whole network delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set. When it is judged that the delivery personnel associated with the delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this type of delivery personnel identification. For the specific implementation method, please refer to Example 1, which will not be repeated in this example.

[0127] At this point, the hierarchical scheduling of the current delivery task is completed.

[0128] Step 2110: In response to the delivery task not matching the delivery task overflow condition, a delivery person identification set is established based on the in-store delivery person identification and / or the in-circle delivery person identification bound to the store.

[0129] In response to the delivery task not matching the delivery task overflow condition, a specific implementation method of establishing a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store is described in Example 1 and will not be repeated in this example.

[0130] In step 2120, the delivery platform determines in order according to the category order of the store-based deliveryman identification and the circle-based deliveryman identification, whether the deliverymen associated with each deliveryman identification in the deliveryman identification set meet the conditions for executing the delivery task, and when it is determined that the deliverymen associated with the deliveryman identification meet the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to the deliveryman identification in this category.

[0131] The delivery platform judges in order of the categories of the store-based deliveryman identification and the circle-based deliveryman identification, and based on the delivery task information stored in the delivery platform in association with each deliveryman identification in the deliveryman identification set, whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task. When it is judged that the deliveryman associated with the deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to the deliveryman identification in this type of deliveryman identification. For the specific implementation method, please refer to Example 1, which will not be repeated in this example.

[0132] At this point, the hierarchical scheduling of the current delivery task is completed.

[0133] The delivery task scheduling method disclosed in the embodiment of the present application determines a store set according to the distance between stores and the store portrait data of the stores through the delivery platform, and binds and stores the store set with the stores included in the store set; determines the store-based delivery staff identification configured for each store according to the delivery task history data of each store in the store set, and determines the circle-based delivery staff identification configured for the store set; binds and stores each store with the store-based delivery staff identification configured for the store, and binds and stores the store set with the circle-based delivery staff identification configured for the store set to obtain binding data. During the delivery task scheduling process, the delivery platform receives a delivery task generated according to an order to be delivered, and the delivery task carries the identification of the store to which the order to be delivered belongs; the delivery platform matches the identification with the pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the store-based delivery staff identification and / or circle-based delivery staff identification bound to the store, and the delivery task overflow Condition; the resident deliveryman identifier is the deliveryman identifier bound to the store set to which the store belongs; the preset attribute information of the delivery task is matched and judged with the delivery task overflow condition; in response to the delivery task matching the delivery task overflow condition, the network-wide deliveryman identifier stored in the delivery platform is obtained; a deliveryman identifier set is established based on the resident deliveryman identifier and / or resident deliveryman identifier bound to the store and the obtained network-wide deliveryman identifier; the delivery platform judges whether the deliverymen associated with each deliveryman identifier in the deliveryman identifier set meet the conditions for executing the delivery task in accordance with the order of the categories of resident deliveryman identifier, resident deliveryman identifier, and network-wide deliveryman identifier, and according to the delivery task information stored in the delivery platform associated with each deliveryman identifier in the deliveryman identifier set, and when it is judged that the deliveryman associated with a deliveryman identifier meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a deliveryman identifier in this type of deliveryman identifier, which can improve the timeliness of delivery task execution of the delivery platform.

[0134] The delivery task scheduling method provided in the embodiment of the present application forms a store set by analyzing the stores in a specified geographical area based on indicators such as the difficulty of food delivery, the degree of complementarity between the peaks and valleys of the distribution of the number of delivery orders, and the overlap of the delivery range. Furthermore, all stores in the store set are bound to resident delivery personnel, so that when the number of delivery tasks for all stores in the store set is large and the resident delivery personnel are unable to deliver on time, the delivery tasks will first overflow to the resident delivery personnel, which helps to reduce the impact of the overflowed delivery tasks on the delivery timeliness of the delivery personnel across the entire network. At the same time, since the resident delivery personnel have to undertake the overflowed delivery tasks of each store in the store set, the geographical location of the resident delivery personnel is usually near each store in the store set. The delivery tasks of the stores are first removed to the resident delivery personnel, which makes full use of the geographical location advantage of the resident delivery personnel in the delivery area, which helps to improve the execution timeliness of the delivery tasks.

[0135] Example 3

[0136] The embodiment of the present application discloses a method for dispatching a delivery task, such as Figure 4 As shown, the method includes: steps 410 to 450.

[0137] In step 410 , the delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries an identifier of the store to which the order to be delivered belongs.

[0138] The delivery platform receives a delivery task generated according to the order to be delivered. The specific implementation method of the delivery task carrying the identifier of the store to which the order to be delivered belongs is shown in Example 1 and will not be repeated in this embodiment.

[0139] In step 420, the delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store.

[0140] Among them, the delivery configuration data includes: the in-store delivery staff identification and the circle-based delivery staff identification bound to the store; the circle-based delivery staff identification is the delivery staff identification bound to the store set to which the store belongs.

[0141] The distribution platform matches the identifier with pre-stored store configuration data. The specific implementation method for obtaining the distribution configuration data of the store is shown in Example 1 and will not be repeated in this embodiment.

[0142] In some embodiments of the present application, the delivery platform matches the identifier with pre-stored store configuration data, and before the step of obtaining the delivery configuration data of the store, it also includes: the delivery platform determines a store set based on the distance between the stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set; determines the in-store delivery staff identifier configured for each of the stores based on the delivery task history data of each store in the store set, and determines the in-circle delivery staff identifier configured for the store set; binds and stores each of the stores with the in-store delivery staff identifier configured for the store, and binds and stores the store set with the in-circle delivery staff identifier configured for the store set to obtain binding data.

[0143] For the specific implementation method of obtaining the binding data of the store and the store delivery staff identification, the circle delivery identification, the store collection and other data through the above steps, please refer to Example 2, which will not be repeated in this example.

[0144] In some embodiments of the present application, the delivery platform determines the steps of a store set based on the distance between stores and the store portrait data of the stores, including: the delivery platform divides the stores in the specified geographical area into at least one candidate store set based on the distance between the geographical locations; for each of the candidate store sets, determines one or more of the following shared delivery personnel indicator scores of the corresponding candidate store set based on the store portrait data of each store in the candidate store set: a meal delivery difficulty score, a peak-valley complementarity score of the distribution of the number of delivery orders, and a delivery range overlap score; the shared delivery personnel indicator scores are weighted and summed according to preset weights to obtain the circle score of each of the candidate store sets; and the candidate store set is selected according to the circle score as the store set within the specified geographical area.

[0145] The specific implementation method of the distribution platform determining the store set based on the distance between the stores and the store portrait data of the stores is shown in Example 2 and will not be repeated in this embodiment.

[0146] In some embodiments of the present application, the steps of determining the identification of the resident delivery personnel configured for each store according to the historical data of delivery tasks of each store in the store set, and determining the identification of the resident delivery personnel configured for the store set include: determining the number of resident delivery personnel configured for each store according to the historical mean of delivery tasks of each store in the store set and the time period distribution curve of the number of delivery tasks; determining the number of resident delivery personnel configured for the store set according to the difference obtained by subtracting the number of delivery tasks undertaken by the resident delivery personnel from the number of delivery tasks for all stores in the store set within a preset time period, and the average number of delivery tasks undertaken by each resident delivery personnel in the circle; determining the identification of the resident delivery personnel configured for each store according to the number of resident delivery personnel configured for the store, and determining the identification of the resident delivery personnel configured for the store set according to the number of resident delivery personnel configured for the store set.

[0147] Based on the historical data of delivery tasks of each store in the store set, the in-store delivery staff identification configured for each store is determined, and the specific implementation method of determining the in-circle delivery staff identification configured for the store set is shown in Example 2, which will not be repeated in this example.

[0148] Step 430: Through the first preset delivery task scheduling engine, based on the delivery task information stored in the delivery platform in association with the in-store delivery person identifier, determine whether the in-store delivery person associated with the in-store delivery person identifier meets the conditions for executing the delivery task.

[0149] The first, second, and third preset delivery task scheduling engines described in this embodiment can be the same delivery task scheduling engine or different delivery task scheduling engines. When the first, second, and third preset delivery task scheduling engines are different delivery task scheduling engines, the delivery platform can implement different delivery task scheduling strategies for delivery personnel with different identity attributes to enhance the flexibility of delivery task scheduling.

[0150] In the embodiment of the present application, for store delivery tasks, priority is given to scheduling among the store's on-site delivery personnel. For example, a first preset delivery task scheduling engine first determines whether the on-site delivery personnel associated with the on-site delivery personnel identifier meets the conditions for executing the delivery task (such as whether the delivery business constraints are met and whether the delivery time has exceeded) based on the on-site delivery task information (such as the number of uncompleted delivery tasks, the delivery time required for uncompleted delivery tasks, etc.) stored in the delivery platform and associated with the on-site delivery personnel identifier.

[0151] In some embodiments of the present application, Figure 5As shown, after the step of determining whether the in-store delivery person associated with the in-store delivery person identification meets the conditions for executing the delivery task, the method further includes: step 460.

[0152] Step 460 : In response to a resident delivery person associated with the resident delivery person identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identification.

[0153] For example, the delivery platform estimates the delivery time and delivery path of each resident deliveryman associated with the resident deliveryman identifier determined by the first preset delivery task scheduling engine, and determines whether there is a resident deliveryman who meets the delivery business constraints and the delivery time is not exceeded. If so, the delivery task is assigned to the resident deliveryman with the shortest delivery time and the best delivery path. Among them, the delivery business constraints include: the maximum number of delivery tasks that a deliveryman can carry, the assessment time, the delivery distance for which resident deliverymen are given priority, and one or more other conditions. In some embodiments of the present application, the existing technology can be used to determine the delivery time and delivery path length of each deliveryman, which will not be repeated in this embodiment.

[0154] At this point, the scheduling of the delivery task is completed.

[0155] Step 440: In response to the fact that none of the in-store delivery personnel associated with the in-store delivery personnel identification meet the conditions for executing the delivery task, a second preset delivery task scheduling engine is used to determine whether the in-circle delivery personnel associated with the in-circle delivery personnel identification meet the conditions for executing the delivery task based on the in-circle delivery task information stored in the delivery platform in association with the in-circle delivery personnel identification.

[0156] For example, the delivery platform estimates the delivery time and delivery path for each in-store delivery person associated with the in-store delivery person identifier determined by the first preset delivery task scheduling engine, and determines whether there is an in-store delivery person who meets the delivery business constraints and does not exceed the delivery time. The delivery business constraints include one or more conditions such as the maximum number of delivery tasks a delivery person can handle, the assessment time, and the delivery distance for which in-store delivery persons are given priority. In some embodiments of the present application, existing technologies can be used to determine the delivery time and delivery path length of each delivery person, which will not be repeated in this embodiment.

[0157] If no in-store delivery driver exists that meets the delivery business constraints and can complete the delivery task without exceeding the time limit, the delivery platform will further estimate the delivery time and delivery route for each in-circle delivery driver associated with the in-circle delivery driver identifier through a second preset delivery task scheduling engine, and further determine whether any in-circle delivery driver exists that meets the preset business constraints and can complete the delivery task without exceeding the time limit. If so, the delivery platform will assign the delivery task to the in-circle delivery driver with the shortest delivery time and the best delivery route.

[0158] Step 450 : In response to the store-based delivery person associated with the resident delivery person identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identification.

[0159] If there is a resident deliveryman who meets the preset business constraints and can complete the delivery task without timeout, the delivery platform will assign the delivery task to the resident deliveryman with the shortest delivery time and the best delivery route.

[0160] At this point, the scheduling of the delivery task is completed.

[0161] In some embodiments of the present application, the delivery configuration data also includes: the delivery task overflow condition bound to the store, such as Figure 5 As shown, after the step of determining whether the store-based delivery personnel associated with the resident delivery personnel identification in the circle meets the conditions for executing the delivery task, it also includes: in response to the fact that none of the store-based delivery personnel associated with the resident delivery personnel identification in the circle meets the conditions for executing the delivery task, executing the following steps 470 to 490.

[0162] Step 470: Determine whether the delivery task matches the delivery task overflow condition based on the associated information of the delivery task.

[0163] Step 480: In response to the delivery task matching the delivery task overflow condition, obtain the network-wide delivery personnel identification stored in the delivery platform whose delivery range matches the delivery task.

[0164] Step 490, through the third preset delivery task scheduling engine, based on the delivery task information stored in the delivery platform in association with the full-network delivery personnel identification, it is determined whether the full-network delivery personnel associated with the full-network delivery personnel identification meets the conditions for executing the delivery task. In response to the full-network delivery personnel associated with the full-network delivery personnel identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the full-network delivery personnel identification.

[0165] For example, if no resident delivery driver exists among the delivery teams that can complete the delivery task within the specified time limit, the delivery platform will further determine, through a third preset delivery task scheduling engine, whether any resident delivery driver associated with the identified resident delivery driver identifier can complete the delivery task within the specified time limit, meeting the specified business constraints. If a resident delivery driver exists that can complete the delivery task within the specified time limit, the delivery platform will assign the delivery task to the resident delivery driver with the shortest delivery time and optimal delivery route.

[0166] In the prior art, when scheduling delivery tasks, if there is no in-store delivery person who can complete a certain delivery task without timeout, the delivery task will directly overflow to the delivery personnel of the entire network, and the preset delivery task scheduling engine will perform task scheduling among the delivery personnel of the entire network. The delivery task scheduling process in the prior art will have a certain impact on the delivery efficiency of the delivery personnel of the entire network. Taking takeout orders as an example, for some stores with unstable meal delivery times, if the delivery orders overflowed to the delivery personnel of the entire network are delayed, it will extend the delivery time of other delivery orders carried by the delivery personnel of the entire network, and even cause other delivery orders to timeout. In the delivery task scheduling process disclosed in the embodiment of the present application, by setting up in-circle delivery personnel, and overflowing the orders that the in-store delivery personnel cannot deliver on time to the in-circle delivery personnel first, the impact on the delivery efficiency of the delivery personnel of the entire network can be effectively reduced. At the same time, since the in-circle delivery personnel are the delivery personnel shared by the store with overflow orders and other stores in the designated geographical area, the activity area of ​​the in-circle delivery personnel is near the store, and they can undertake delivery tasks within a certain geographical range, so the delivery efficiency is higher. From the above analysis, it can be seen that by setting up resident delivery personnel and improving the scheduling strategy of delivery tasks, the overall delivery efficiency of the delivery platform can be improved.

[0167] In some embodiments of the present application, in response to the full-network delivery person associated with the full-network delivery person identifier not meeting the conditions for executing the delivery task, a second preset delivery task scheduling engine is used to send the delivery task to a delivery task receiving terminal bound to the resident delivery person identifier based on the in-progress delivery task information stored in the delivery platform associated with the resident delivery person identifier, or a scheduling failure is output. For example, if there is no full-network delivery person among the determined full-network delivery persons who can complete the delivery task while meeting the preset business constraints and without timeout, the second preset delivery task scheduling engine will reschedule the delivery task, or a scheduling failure is directly output.

[0168] In some embodiments of the present application, the network-wide delivery personnel include: network-wide full-time delivery personnel and network-wide part-time delivery personnel, and correspondingly, the determined network-wide delivery personnel identification includes: network-wide full-time delivery personnel identification and network-wide part-time delivery personnel identification, and the step of judging whether the network-wide delivery personnel associated with the network-wide delivery personnel identification meets the conditions for executing the delivery task through the third preset delivery task scheduling engine according to the delivery task information stored in the delivery platform in association with the network-wide delivery personnel identification includes: judging whether the network-wide delivery personnel associated with the network-wide full-time delivery personnel identification meets the conditions for executing the delivery task through the third preset delivery task scheduling engine according to the delivery task information stored in the delivery platform in association with the delivery task information stored in association with the network-wide full-time delivery personnel identification whether the deliveryman meets the conditions for executing the delivery task; in response to the deliveryman associated with the full-time deliveryman identity of the entire network meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the full-time deliveryman identity of the entire network through the third preset delivery task scheduling engine; in response to the deliveryman associated with the full-time deliveryman identity of the entire network not meeting the conditions for executing the delivery task, the third preset delivery task scheduling engine is used to determine whether the deliveryman associated with the part-time deliveryman identity of the entire network meets the conditions for executing the delivery task based on the delivery task information stored in the delivery platform in association with each part-time deliveryman identity of the entire network in the deliveryman identity set.

[0169] In some embodiments of the present application, the full-network delivery personnel may only include full-time delivery personnel registered in the delivery platform. Usually, in order to improve delivery efficiency, the full-time delivery personnel are usually provided with a delivery area. In other embodiments of the present application, the full-network delivery personnel include full-time delivery personnel (i.e., full-time delivery personnel of the whole network) and part-time delivery personnel (i.e., part-time delivery personnel of the whole network) registered in the delivery platform. When performing delivery task scheduling, the delivery platform first estimates the delivery time and delivery path of the full-time delivery personnel of the whole network associated with each full-time delivery personnel identifier of the whole network in the delivery personnel identifier set through a preset delivery task scheduling engine, and determines whether there is a full-time delivery personnel of the whole network whose estimated delivery time is less than the assessment time of the delivery task (i.e., not overtime). If so, the delivery task is dispatched to the full-time delivery personnel of the whole network with the shortest delivery time and the best delivery path. If the estimated delivery time for each full-time delivery driver on the entire network to perform the delivery task is greater than the assessment time for the delivery task (i.e., there are no delivery situations that do not exceed the time limit), the delivery platform will then use the preset delivery task scheduling engine to estimate the delivery time and delivery route for the part-time delivery driver on the entire network associated with each part-time delivery driver ID in the delivery driver ID set. Next, the delivery platform will determine whether there is a situation where the estimated delivery time of a part-time delivery driver on the entire network is less than the assessment time for the delivery task (i.e., there is no time limit). If so, the delivery task will be assigned to the part-time delivery driver on the entire network with the shortest delivery time and the best delivery route.

[0170] The delivery task scheduling method disclosed in the embodiment of the present application receives a delivery task generated according to an order to be delivered through a delivery platform, and the delivery task carries the identifier of the store to which the order to be delivered belongs; the delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store; wherein the delivery configuration data includes: the in-store delivery person identifier and the in-circle delivery person identifier bound to the store; the in-circle delivery person identifier is the delivery person identifier bound to the set of stores to which the store belongs; through a first preset delivery task scheduling engine, the in-store delivery person identifier is determined based on the delivery task information stored in the delivery platform in association with the in-store delivery person identifier. Whether the resident deliveryman associated with the deliveryman identification meets the conditions for executing the delivery task; in response to the resident deliveryman associated with the resident deliveryman identification not meeting the conditions for executing the delivery task, through the second preset delivery task scheduling engine, according to the delivery task information stored in the delivery platform in association with the resident deliveryman identification, it is judged whether the resident deliveryman associated with the resident deliveryman identification meets the conditions for executing the delivery task; in response to the resident deliveryman associated with the resident deliveryman identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident deliveryman identification, which helps to improve the overall delivery efficiency of the delivery platform.

[0171] The delivery task scheduling method provided in the embodiment of the present application determines the delivery personnel shared with multiple stores in a specified geographical area (i.e., resident delivery personnel) based on the geographical location information of the delivery tasks, and optimizes the delivery task scheduling process of the delivery platform. During the delivery task scheduling process, delivery tasks that the resident delivery personnel cannot execute on time are first overflowed to the corresponding resident delivery personnel, making full use of the geographical location advantages of the resident delivery personnel in the delivery area, which helps to improve the timeliness of delivery task execution. At the same time, it helps to reduce the impact of overflow delivery tasks on the delivery timeliness of delivery personnel across the entire network.

[0172] Example 4

[0173] The embodiment of the present application discloses a delivery task scheduling device, such as Figure 6 As shown, the device includes:

[0174] The delivery task receiving module 610 is used for the delivery platform to receive a delivery task generated according to an order to be delivered, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs;

[0175] The store configuration data acquisition module 620 is used for the delivery platform to match the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the identifier of the resident delivery person bound to the store and / or the identifier of the resident delivery person in the circle, and the delivery task overflow condition; the identifier of the resident delivery person in the circle is the identifier of the delivery person bound to the store set to which the store belongs;

[0176] A delivery task overflow judgment module 630 is configured to match the preset attribute information of the delivery task with the delivery task overflow condition;

[0177] A network-wide delivery person identification acquisition module 640 is configured to acquire network-wide delivery person identifications stored in the delivery platform in response to the delivery task matching the delivery task overflow condition;

[0178] A first delivery person identification set establishing module 650 is configured to establish a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store and the obtained network-wide delivery person identification;

[0179] The first delivery task scheduling module 660 is used for the delivery platform to judge in order whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task according to the category order of the store delivery personnel identification, the circle delivery personnel identification, and the whole network delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set, and when it is judged that the delivery personnel associated with the delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this category.

[0180] In some embodiments of the present application, Figure 7 As shown, the device also includes:

[0181] A second delivery person identification set establishing module 670 is configured to establish a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store in response to the delivery task not matching the delivery task overflow condition;

[0182] The second delivery task scheduling module 680 is used for the delivery platform to judge in order whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meets the conditions for executing the delivery task according to the category order of the store delivery personnel identification and the circle delivery personnel identification, and when it is judged that the delivery personnel associated with the delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to the delivery personnel identification in this category.

[0183] In some embodiments of the present application, the delivery task overflow condition includes one or more of the following: a delivery task overflow area, a delivery task overflow time period, and a delivery task overflow quantity threshold. The step of matching the preset attribute information of the delivery task with the delivery task overflow condition includes:

[0184] The matching result between the corresponding attribute information of the delivery task of the store and the overflow condition of the delivery task is determined based on one or more of the following comparison results:

[0185] comparing the destination of the delivery task with the overflow area of ​​the delivery task;

[0186] Comparing the overflow quantity of delivery tasks of the store to which the delivery order generating the delivery task belongs with the overflow quantity threshold of delivery tasks;

[0187] The delivery time of the delivery task is compared with the overflow time period of the delivery task.

[0188] In some embodiments of the present application, the first delivery task scheduling module 660 is further configured to:

[0189] The delivery platform determines whether the delivery person associated with the store-based delivery person identifier meets the conditions for executing the delivery task based on the delivery task information stored in the delivery platform and associated with each store-based delivery person identifier in the delivery person identifier set through a preset delivery task scheduling engine;

[0190] In response to the delivery person associated with the store-based delivery person identifier meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the store-based delivery person identifier through the preset delivery task scheduling engine; otherwise, the preset delivery task scheduling engine determines whether the delivery person associated with the store-based delivery person identifier meets the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform and associated with each store-based delivery person identifier in the delivery person identifier set;

[0191] In response to the delivery person associated with the resident delivery person identifier meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identifier through the preset delivery task scheduling engine; otherwise, the preset delivery task scheduling engine determines whether the delivery person associated with the global delivery person identifier meets the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform in association with each global delivery person identifier in the delivery person identifier set;

[0192] In response to the delivery person associated with the full-network delivery person identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the full-network delivery person identification through the preset delivery task scheduling engine.

[0193] In some embodiments of the present application, after the step of determining whether the delivery person associated with the network-wide delivery person identifier meets the conditions for executing the delivery task, the following step is further included:

[0194] In response to the delivery person associated with the network-wide delivery person identification not meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identification through the preset delivery task scheduling engine, or the output scheduling fails.

[0195] In some embodiments of the present application, Figure 7 As shown, the device also includes:

[0196] A store set determination module 690 is configured to determine a store set based on the distance between stores and the store profile data of the stores, and to bind and store the store set with the stores included in the store set;

[0197] The delivery person identification determination module 6110 is used to determine the in-store delivery person identification configured for each store and the in-circle delivery person identification configured for the store set based on the delivery task history data of each store in the store set;

[0198] The store configuration data storage module 6120 is used to bind and store each of the stores with the store-based delivery staff identification configured for the store, and to bind and store the store set with the circle-based delivery staff identification configured for the store set to obtain binding data.

[0199] In some embodiments of the present application, the step of determining a store set by the delivery platform based on the distance between stores and the store profile data of the stores includes:

[0200] The delivery platform divides the stores in the specified geographical area into at least one candidate store set based on the distance between the geographical locations;

[0201] For each candidate store set, one or more of the following shared deliveryman indicator scores are determined for the corresponding candidate store set based on the store profile data of each store in the candidate store set: a food delivery difficulty score, a delivery order quantity distribution peak-valley complementarity score, and a delivery range overlap score;

[0202] The shared deliveryman indicator scores are weighted and summed according to preset weights to obtain the circle scores of each candidate store set;

[0203] The candidate store set is selected according to the circle-residence score as the store set within the specified geographical area.

[0204] In some embodiments of the present application, the steps of determining, based on the delivery task history data of each store in the store set, a store-based delivery person identifier configured for each store, and determining a circle-based delivery person identifier configured for the store set, include:

[0205] Determine the number of on-site delivery personnel to be assigned to each store based on the historical mean of delivery tasks and the time period distribution curve of the number of delivery tasks for each store in the store set;

[0206] Determine the number of resident delivery personnel assigned to the store set based on the difference between the number of delivery tasks undertaken by the resident delivery personnel for all stores in the store set within a preset time period and the average number of delivery tasks undertaken by each resident delivery personnel;

[0207] The in-store delivery staff identification configured for each store is determined based on the number of in-store delivery staff configured for the store, and the in-store delivery staff identification configured for the store set is determined based on the number of in-circle delivery staff configured for the store set.

[0208] The delivery task scheduling device disclosed in this embodiment is used to implement the delivery task scheduling method described in Example 1 or Example 2 of this application. The specific implementation methods of each module of the device will not be repeated here. Please refer to the specific implementation methods of the corresponding steps in the method embodiment.

[0209] The delivery task scheduling device disclosed in the embodiment of the present application receives a delivery task generated according to an order to be delivered through a delivery platform, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs; the delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the in-store delivery person identifier and / or the in-circle delivery person identifier bound to the store, and the delivery task overflow condition; the in-circle delivery person identifier is the delivery person identifier bound to the set of stores to which the store belongs; the preset attribute information of the delivery task is matched and judged with the delivery task overflow condition; in response to the delivery task matching the delivery task overflow condition, the network-wide delivery person identifier stored in the delivery platform is obtained; based on A deliveryman identification set is established based on the in-store deliveryman identification and / or in-circle deliveryman identification bound to the store and the obtained network-wide deliveryman identification; the delivery platform follows the category order of the in-store deliveryman identification, the in-circle deliveryman identification, and the network-wide deliveryman identification, and based on the delivery task information stored in the delivery platform associated with each deliveryman identification in the deliveryman identification set, determines in turn whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task; and when it is determined that the deliveryman associated with a deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a deliveryman identification in this category, which can improve the timeliness of delivery task execution of the delivery platform.

[0210] The delivery task scheduling device provided in the embodiment of the present application forms a store set by analyzing the stores in a specified geographical area based on indicators such as the difficulty of food delivery, the degree of complementarity between the peaks and valleys of the distribution of the number of delivery orders, and the overlap of the delivery range. It further binds all stores in the store set with resident delivery personnel, so that when the number of delivery tasks for all stores in the store set is large and the resident delivery personnel are unable to deliver on time, the delivery tasks will first overflow to the resident delivery personnel, which helps to reduce the impact of the overflowed delivery tasks on the delivery timeliness of the delivery personnel across the entire network. At the same time, since the resident delivery personnel have to undertake the overflowed delivery tasks of each store in the store set, the geographical location of the resident delivery personnel is usually near each store in the store set. The delivery tasks of the stores are first removed to the resident delivery personnel, which makes full use of the geographical location advantage of the resident delivery personnel in the delivery area, which helps to improve the execution timeliness of the delivery tasks.

[0211] Example 5

[0212] The embodiment of the present application discloses a delivery task scheduling device, such as Figure 8 As shown, the device includes:

[0213] The delivery task receiving module 810 is used for the delivery platform to receive a delivery task generated according to an order to be delivered, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs;

[0214] The store configuration data acquisition module 820 is used for the delivery platform to match the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store; wherein the delivery configuration data includes: the in-store delivery person identifier and the circle delivery person identifier bound to the store; the circle delivery person identifier is the delivery person identifier bound to the store group to which the store belongs;

[0215] A first scheduling determination module 830 is configured to determine, through a first preset delivery task scheduling engine, whether the in-store delivery person associated with the in-store delivery person identifier meets the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the in-store delivery person identifier;

[0216] A second scheduling determination module 840 is configured to, in response to the fact that none of the resident delivery personnel associated with the resident delivery personnel identifiers meet the conditions for executing the delivery task, determine, through a second preset delivery task scheduling engine, whether the resident delivery personnel associated with the resident delivery personnel identifiers meet the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform in association with the resident delivery personnel identifiers;

[0217] The first task scheduling module 850 is configured to send the delivery task to a delivery task receiving terminal bound to the resident delivery person identification in response to the resident delivery person associated with the resident delivery person identification meeting the conditions for executing the delivery task.

[0218] In some embodiments of the present application, Figure 9 As shown, the device also includes:

[0219] The second task scheduling module 860 sends the delivery task to a delivery task receiving terminal bound to the in-store delivery person identification in response to the in-store delivery person associated with the in-store delivery person identification meeting the conditions for executing the delivery task.

[0220] In some embodiments of the present application, the delivery configuration data also includes: the overflow condition of the delivery task bound to the store, in response to the store delivery personnel associated with the circle delivery personnel identifier not meeting the conditions for executing the delivery task, such as Figure 9 As shown, the device also includes:

[0221] A delivery task overflow determination module 870 is configured to determine whether the delivery task meets the delivery task overflow condition based on the associated information of the delivery task;

[0222] A network-wide delivery person identification acquisition module 880 is configured to acquire network-wide delivery person identifications stored in the delivery platform whose delivery ranges match the delivery task in response to the delivery task matching the delivery task overflow condition;

[0223] The third scheduling judgment module 890 is used to determine whether the network-wide delivery person associated with the network-wide delivery person identifier meets the conditions for executing the delivery task based on the delivery task information stored in the delivery platform in association with the network-wide delivery person identifier through a third preset delivery task scheduling engine.

[0224] The third task scheduling module 8110 is used to send the delivery task to a delivery task receiving terminal bound to the network-wide delivery person identification in response to the network-wide delivery person associated with the network-wide delivery person identification meeting the conditions for executing the delivery task.

[0225] In some embodiments of the present application, Figure 9 As shown, the device also includes:

[0226] The store set determination module 8120 is used for the delivery platform to determine a store set based on the distance between stores and the store profile data of the stores, and to bind and store the store set with the stores included in the store set;

[0227] The delivery person identification determination module 8130 is used to determine the in-store delivery person identification configured for each store and the in-circle delivery person identification configured for the store set based on the delivery task history data of each store in the store set;

[0228] The store configuration data storage module 8140 is used to bind and store each of the stores with the store-based delivery staff identification configured for the store, and to bind and store the store set with the circle-based delivery staff identification configured for the store set to obtain binding data.

[0229] In some embodiments of the present application, the step of determining a store set by the delivery platform based on the distance between stores and the store profile data of the stores includes:

[0230] The delivery platform divides the stores in the specified geographical area into at least one candidate store set based on the distance between the geographical locations;

[0231] For each candidate store set, one or more of the following shared deliveryman indicator scores are determined for the corresponding candidate store set based on the store profile data of each store in the candidate store set: a food delivery difficulty score, a delivery order quantity distribution peak-valley complementarity score, and a delivery range overlap score;

[0232] The shared deliveryman indicator scores are weighted and summed according to preset weights to obtain the circle scores of each candidate store set;

[0233] The candidate store set is selected according to the circle-residence score as the store set within the specified geographical area.

[0234] In some embodiments of the present application, the steps of determining, based on the delivery task history data of each store in the store set, a store-based delivery person identifier configured for each store, and determining a circle-based delivery person identifier configured for the store set, include:

[0235] Determine the number of on-site delivery personnel to be assigned to each store based on the historical mean of delivery tasks and the time period distribution curve of the number of delivery tasks for each store in the store set;

[0236] Determine the number of resident delivery personnel assigned to the store set based on the difference between the number of delivery tasks undertaken by the resident delivery personnel for all stores in the store set within a preset time period and the average number of delivery tasks undertaken by each resident delivery personnel;

[0237] The in-store delivery staff identification configured for each store is determined based on the number of in-store delivery staff configured for the store, and the in-store delivery staff identification configured for the store set is determined based on the number of in-circle delivery staff configured for the store set.

[0238] The delivery task scheduling device disclosed in this embodiment is used to implement the delivery task scheduling method described in Example 3 of this application. The specific implementation methods of each module of the device will not be repeated here. Please refer to the specific implementation methods of the corresponding steps in the method embodiment.

[0239] The delivery task scheduling device disclosed in the embodiment of the present application receives the delivery task generated according to the order to be delivered through the delivery platform, and the delivery task carries the identification of the store to which the order to be delivered belongs; the delivery platform matches the identification with the pre-stored store configuration data to obtain the delivery configuration data of the store; wherein the delivery configuration data includes: the in-store delivery person identification and the in-circle delivery person identification bound to the store; the in-circle delivery person identification is the delivery person identification bound to the store set to which the store belongs; through the first preset delivery task scheduling engine, the in-store delivery person identification is judged according to the delivery task information stored in the delivery platform in association with the in-store delivery person identification. Whether the resident deliveryman associated with the deliveryman identification meets the conditions for executing the delivery task; in response to the resident deliveryman associated with the resident deliveryman identification not meeting the conditions for executing the delivery task, through the second preset delivery task scheduling engine, according to the delivery task information stored in the delivery platform in association with the resident deliveryman identification, it is judged whether the resident deliveryman associated with the resident deliveryman identification meets the conditions for executing the delivery task; in response to the resident deliveryman associated with the resident deliveryman identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident deliveryman identification, which helps to improve the overall delivery efficiency of the delivery platform.

[0240] The delivery task scheduling device provided in the embodiment of the present application determines the delivery personnel shared with multiple stores in a specified geographical area (i.e., resident delivery personnel) based on the geographical location information of the delivery tasks, and optimizes the delivery task scheduling process of the delivery platform. During the delivery task scheduling process, delivery tasks that the resident delivery personnel cannot execute on time are first overflowed to the corresponding resident delivery personnel, making full use of the geographical location advantages of the resident delivery personnel in the delivery area, which helps to improve the timeliness of delivery task execution. At the same time, it helps to reduce the impact of overflowing delivery tasks on the delivery timeliness of delivery personnel across the entire network.

[0241] Each embodiment in this specification is described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between the various embodiments can be referred to in conjunction with each other. For the device embodiments, since they are generally similar to the method embodiments, their description is relatively simple, and for relevant parts, reference can be made to the description of the method embodiments.

[0242] The above is a detailed introduction to a distribution task scheduling method and device provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, based on the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

[0243] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0244] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all of the functions of some or all of the components in the electronic device according to the embodiment of the present application. The application can also be implemented as a device or apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0245] For example, Figure 10An electronic device that can implement the method according to the present application is shown. The electronic device can be a PC, a mobile terminal, a personal digital assistant, a tablet computer, etc. The electronic device conventionally includes a processor 1010 and a memory 1020, and program code 1030 stored on the memory 1020 and executable on the processor 1010. When the processor 1010 executes the program code 1030, the method described in the above embodiments is implemented. The memory 1020 can be a computer program product or a computer-readable medium. The memory 1020 can be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read-Only Memory), an EPROM, a hard disk, or a ROM. The memory 1020 has a storage space 10201 for program code 1030 of a computer program for executing any of the method steps described above. For example, the storage space 10201 for program code 1030 can include individual computer programs for implementing various steps in the above method. The program code 1030 is computer-readable code. These computer programs can be read from or written into one or more computer program products. These computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks. The computer program includes computer readable code that, when run on an electronic device, causes the electronic device to perform the method according to the above embodiments.

[0246] An embodiment of the present application also discloses a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the delivery task scheduling method described in Examples 1 to 3 of the present application are implemented.

[0247] Such a computer program product may be a computer-readable storage medium having a computer program product. Figure 10 The memory 1020 in the electronic device shown is similarly arranged as a storage segment, storage space, etc. The program code can be compressed and stored in the computer readable storage medium in an appropriate form. The computer readable storage medium is generally as shown in FIG. Figure 11 The portable or fixed storage unit generally includes computer-readable code 1030', which is a code read by a processor and implements the steps of the above-described method when executed by the processor.

[0248] References herein to "one embodiment," "an embodiment," or "one or more embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Furthermore, please note that instances of the phrase "in one embodiment" do not necessarily all refer to the same embodiment.

[0249] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.

[0250] In the claims, any reference signs placed between brackets shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application may be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.

[0251] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A delivery task scheduling method, characterized in that: include: The delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs; The delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the in-store delivery person identifier and / or the in-circle delivery person identifier bound to the store, and a delivery task overflow condition; the in-circle delivery person identifier is the delivery person identifier bound to the store set to which the store belongs; the delivery platform determines a store set based on the distance between stores and the store portrait data of the store, and binds and stores the store set with the stores included in the store set, wherein the store set is a store of the same category, and the store set is bound and stored with the in-circle delivery person identifier configured for the store set to obtain binding data; Matching and judging the preset attribute information of the delivery task with the delivery task overflow condition; In response to the delivery task matching the delivery task overflow condition, obtaining the network-wide delivery personnel identification stored in the delivery platform; Establishing a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store and the obtained network-wide delivery person identification; The delivery platform determines whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meet the conditions for executing the delivery task in accordance with the order of the categories of the resident delivery personnel identification, the resident delivery personnel identification, and the full network delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set. When it is determined that the delivery personnel associated with a delivery personnel identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this type of delivery personnel identification. If there is no resident delivery personnel in the circle who can complete the delivery task without timeout among the resident delivery personnel, the delivery platform further determines through a third preset delivery task scheduling engine whether there is a full network delivery personnel associated with the full network delivery personnel identification who can complete the delivery task without timeout and meet the preset business constraints. If there is a full network delivery personnel who can complete the delivery task without timeout, the delivery platform dispatches the delivery task to the full network delivery personnel with the shortest delivery time and the best delivery path.

2. The method according to claim 1, characterized in that After the step of matching the preset attribute information of the delivery task with the delivery task overflow condition, the method further includes: In response to the delivery task not matching the delivery task overflow condition, establishing a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store; The delivery platform judges in order of the categories of the store-based deliveryman identification and the circle-based deliveryman identification, and based on the delivery task information stored in the delivery platform in association with each deliveryman identification in the deliveryman identification set, whether the deliveryman associated with each deliveryman identification in the deliveryman identification set meets the conditions for executing the delivery task; and when it is judged that the deliveryman associated with the deliveryman identification meets the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to the deliveryman identification in this category.

3. The method according to claim 1, characterized in that The delivery task overflow condition includes one or more of the following: a delivery task overflow area, a delivery task overflow time period, and a delivery task overflow quantity threshold. The step of matching the preset attribute information of the delivery task with the delivery task overflow condition includes: The matching result between the corresponding attribute information of the delivery task of the store and the overflow condition of the delivery task is determined based on one or more of the following comparison results: comparing the destination of the delivery task with the overflow area of ​​the delivery task; Comparing the overflow quantity of delivery tasks of the store to which the delivery order generating the delivery task belongs with the overflow quantity threshold of delivery tasks; The delivery time of the delivery task is compared with the overflow time period of the delivery task.

4. The method according to claim 1, wherein The delivery platform sequentially determines whether a delivery person associated with each delivery person identification in the delivery person identification set meets the conditions for executing the delivery task according to the order of the categories of the store delivery person identification, the circle delivery person identification, and the network-wide delivery person identification, based on the delivery task information stored in the delivery platform in association with each delivery person identification in the delivery person identification set, and when it is determined that the delivery person associated with a delivery person identification meets the conditions for executing the delivery task, sends the delivery task to a delivery task receiving terminal bound to a delivery person identification in the category of the delivery person identification, including: The delivery platform determines whether the delivery person associated with the store-based delivery person identifier meets the conditions for executing the delivery task based on the delivery task information stored in the delivery platform and associated with each store-based delivery person identifier in the delivery person identifier set through a preset delivery task scheduling engine; In response to the delivery person associated with the store-based delivery person identifier meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the store-based delivery person identifier through the preset delivery task scheduling engine; otherwise, the preset delivery task scheduling engine determines whether the delivery person associated with the store-based delivery person identifier meets the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform and associated with each store-based delivery person identifier in the delivery person identifier set; In response to the delivery person associated with the resident delivery person identifier meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identifier through the preset delivery task scheduling engine; otherwise, the preset delivery task scheduling engine determines whether the delivery person associated with the global delivery person identifier meets the conditions for executing the delivery task based on the ongoing delivery task information stored in the delivery platform in association with each global delivery person identifier in the delivery person identifier set; In response to the delivery person associated with the full-network delivery person identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the full-network delivery person identification through the preset delivery task scheduling engine.

5. The method according to claim 4, characterized in that After the step of determining whether the delivery person associated with the network-wide delivery person identification meets the conditions for executing the delivery task, the method further includes: In response to the delivery person associated with the network-wide delivery person identification not meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident delivery person identification through the preset delivery task scheduling engine, or the output scheduling fails.

6. The method according to any one of claims 1 to 5, characterized in that Before the step of matching the identifier with pre-stored store configuration data and obtaining the store's delivery configuration data, the delivery platform further includes: The distribution platform determines a store set based on the distance between stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set; Determine, based on the historical data of delivery tasks of each store in the store set, an identification of a resident delivery person configured for each store, and an identification of a resident delivery person configured for the store set; Each of the stores is bound and stored with the identification of the resident deliveryman configured for the store, and the store set is bound and stored with the identification of the resident deliveryman configured for the store set to obtain binding data.

7. The method according to claim 6, characterized in that The delivery platform determines a store set based on the distance between stores and the store portrait data of the stores, including: The delivery platform divides the stores in the specified geographical area into at least one candidate store set based on the distance between the geographical locations; For each candidate store set, one or more of the following shared deliveryman indicator scores are determined for the corresponding candidate store set based on the store profile data of each store in the candidate store set: a food delivery difficulty score, a delivery order quantity distribution peak-valley complementarity score, and a delivery range overlap score; The shared deliveryman indicator scores are weighted and summed according to preset weights to obtain the circle scores of each candidate store set; The candidate store set is selected according to the circle-residence score as the store set within the specified geographical area.

8. The method according to claim 6, characterized in that The steps of determining the in-store delivery staff identification configured for each store according to the delivery task history data of each store in the store set, and determining the in-circle delivery staff identification configured for the store set, include: Determine the number of on-site delivery personnel to be assigned to each store based on the historical mean of delivery tasks and the time period distribution curve of the number of delivery tasks for each store in the store set; Determine the number of resident delivery personnel assigned to the store set based on the difference between the number of delivery tasks undertaken by the resident delivery personnel for all stores in the store set within a preset time period and the average number of delivery tasks undertaken by each resident delivery personnel; The in-store delivery staff identification configured for each store is determined based on the number of in-store delivery staff configured for the store, and the in-store delivery staff identification configured for the store set is determined based on the number of in-circle delivery staff configured for the store set.

9. A method for dispatching a delivery task, characterized in that: include: The delivery platform receives a delivery task generated based on the order to be delivered, wherein the delivery task carries the identifier of the store to which the order to be delivered belongs; The delivery platform matches the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store; wherein the delivery configuration data includes: the in-store delivery person identifier and the in-circle delivery person identifier bound to the store; the in-circle delivery person identifier is the delivery person identifier bound to the store set to which the store belongs, and the delivery platform determines the store set based on the distance between the stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set, wherein the store set is a store of the same category, and the store set is bound and stored with the in-circle delivery person identifier configured for the store set to obtain binding data; Determining, by a first preset delivery task scheduling engine, whether the in-store delivery person associated with the in-store delivery person identifier meets the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the in-store delivery person identifier; In response to the fact that none of the resident delivery personnel associated with the resident delivery personnel identifier satisfies the conditions for executing the delivery task, determining, by a second preset delivery task scheduling engine, whether the resident delivery personnel associated with the resident delivery personnel identifier satisfies the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the resident delivery personnel identifier; In response to the store-based deliveryman associated with the resident deliveryman identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the resident deliveryman identification. If there is no resident deliveryman in the circle who can complete the delivery task without timeout, the delivery platform further determines through a third preset delivery task scheduling engine whether there is a full-network deliveryman associated with the full-network deliveryman identification who can complete the delivery task without timeout and meets the preset business constraints. If there is a full-network deliveryman who can complete the delivery task without timeout, the delivery platform dispatches the delivery task to the full-network deliveryman with the shortest delivery time and the best delivery path.

10. The method according to claim 9, characterized in that The delivery configuration data also includes: an overflow condition of the delivery task bound to the store, and after the step of determining whether the store delivery person associated with the circle delivery person identifier meets the conditions for executing the delivery task, further includes: In response to the fact that none of the store-based delivery personnel associated with the circle-based delivery personnel identifier meets the conditions for executing the delivery task, the following steps are performed: Determining whether the delivery task matches the delivery task overflow condition based on the associated information of the delivery task; In response to the delivery task matching the delivery task overflow condition, obtaining a network-wide delivery person identifier stored in the delivery platform whose delivery range matches the delivery task; Through a third preset delivery task scheduling engine, based on the delivery task information stored in the delivery platform in association with the delivery person identifier, it is determined whether the delivery person associated with the delivery person identifier meets the conditions for executing the delivery task. In response to the network-wide delivery person associated with the network-wide delivery person identification meeting the conditions for executing the delivery task, the delivery task is sent to a delivery task receiving terminal bound to the network-wide delivery person identification.

11. A delivery task scheduling device, characterized in that: include: A delivery task receiving module is used for the delivery platform to receive delivery tasks generated based on orders to be delivered, wherein the delivery tasks carry the identifier of the store to which the orders to be delivered belong; A store configuration data acquisition module is used for the delivery platform to match the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store, wherein the delivery configuration data includes: the in-store delivery person identifier and / or the circle delivery person identifier bound to the store, and the delivery task overflow condition; the circle delivery person identifier is the delivery person identifier bound to the store set to which the store belongs; the delivery platform determines the store set based on the distance between the stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set, the store set being stores of the same category, and the store set is bound and stored with the circle delivery person identifier configured for the store set to obtain binding data; A delivery task overflow judgment module, configured to match the preset attribute information of the delivery task with the delivery task overflow condition; a network-wide delivery person identification acquisition module, configured to acquire network-wide delivery person identifications stored in the delivery platform in response to the delivery task matching the delivery task overflow condition; A first delivery person identification set establishing module, configured to establish a delivery person identification set based on the store-based delivery person identification and / or the circle-based delivery person identification bound to the store and the obtained network-wide delivery person identification; The first delivery task scheduling module is used for the delivery platform to determine whether the delivery personnel associated with each delivery personnel identification in the delivery personnel identification set meet the conditions for executing the delivery task according to the category order of the store delivery personnel identification, the circle delivery personnel identification, and the whole network delivery personnel identification, based on the delivery task information stored in the delivery platform in association with each delivery personnel identification in the delivery personnel identification set. When it is determined that the delivery personnel associated with the delivery personnel identification meet the conditions for executing the delivery task, the delivery task is sent to the delivery task receiving terminal bound to a delivery personnel identification in this category of delivery personnel identification. If there is no circle delivery personnel who can complete the delivery task without timeout among the circle delivery personnel, the delivery platform further determines through a third preset delivery task scheduling engine whether there is a whole network delivery personnel associated with the whole network delivery personnel identification who can complete the delivery task without timeout and meet the preset business constraints. If there is a whole network delivery personnel who can complete the delivery task without timeout, the delivery platform dispatches the delivery task to the whole network delivery personnel with the shortest delivery time and the best delivery path.

12. A delivery task scheduling device, characterized in that: include: A delivery task receiving module is used for the delivery platform to receive delivery tasks generated based on orders to be delivered, wherein the delivery tasks carry the identifier of the store to which the orders to be delivered belong; A store configuration data acquisition module is used for the delivery platform to match the identifier with pre-stored store configuration data to obtain the delivery configuration data of the store; wherein the delivery configuration data includes: the in-store delivery person identifier and the circle delivery person identifier bound to the store; the circle delivery person identifier is the delivery person identifier bound to the store set to which the store belongs; the delivery platform determines the store set based on the distance between the stores and the store portrait data of the stores, and binds and stores the store set with the stores included in the store set, the store set being stores of the same category, and the store set is bound and stored with the circle delivery person identifier configured for the store set to obtain binding data; a first scheduling judgment module, configured to determine, through a first preset delivery task scheduling engine, whether the in-store delivery person associated with the in-store delivery person identifier meets the conditions for executing the delivery task based on the in-progress delivery task information stored in the delivery platform in association with the in-store delivery person identifier; a second scheduling judgment module for, in response to the fact that none of the resident delivery personnel associated with the resident delivery personnel identifiers meet the conditions for executing the delivery task, judging, through a second preset delivery task scheduling engine and based on the in-progress delivery task information stored in the delivery platform in association with the resident delivery personnel identifiers, whether the resident delivery personnel associated with the resident delivery personnel identifiers meet the conditions for executing the delivery task; The first task scheduling module is used to send the delivery task to a delivery task receiving terminal bound to the resident deliveryman identity in response to the resident deliveryman associated with the resident deliveryman identity meeting the conditions for executing the delivery task. If there is no resident deliveryman in the resident deliveryman circle who can complete the delivery task without timeout, the delivery platform further determines through the third preset delivery task scheduling engine whether there is a full-network deliveryman associated with the full-network deliveryman identity who can complete the delivery task without timeout and meets the preset business constraints. If there is a full-network deliveryman who can complete the delivery task without timeout, the delivery platform dispatches the delivery task to the full-network deliveryman with the shortest delivery time and the best delivery path.

13. An electronic device comprising a memory, a processor, and a program code stored in the memory and executable on the processor, wherein: When the processor executes the program code, the distribution task scheduling method according to any one of claims 1 to 10 is implemented.

14. A computer-readable storage medium having program code stored thereon, characterized in that: When the program code is executed by a processor, the steps of the distribution task scheduling method according to any one of claims 1 to 10 are implemented.

Images