Food delivery method, device, equipment, medium and product

Abstract

The application discloses a take-out delivery method, device, equipment, medium and product, and belongs to the take-out field. The method comprises the following steps: a merchant client acquires a manufacturing task of a first order; a first distribution client accepts a first distribution task of the first order; a server sends selling information of at least one meal to a plurality of user clients located in a delivery area; the plurality of user clients receive the selling information of the at least one meal; in the case that at least one user client in the plurality of user clients orders a target meal in the at least one meal, the server generates a second order of the target meal; the server sends a second distribution task of the second order to a second distribution client; and the second distribution client receives and confirms the second distribution task. The method enables a take-out delivery rider to be not affected by instant ordering of a target user, thereby improving the efficiency of take-out delivery.

Description

Technical Field

[0001] This application relates to the food delivery field, and in particular to a food delivery method, apparatus, equipment, medium, and product. Background Technology

[0002] With the continuous development of society, the number of food delivery orders is also constantly increasing. In terms of related technologies, the overall process of food delivery includes user order placement, merchant production, rider pickup, rider delivery, and food arrival. During the pickup and delivery process, the number of deliveries a rider can handle within a limited timeframe is affected by the immediacy of user orders.

[0003] How to ensure that the process of riders picking up and delivering food is not affected by users' immediate orders, thereby increasing the number of deliveries per rider within the same time period and thus improving the efficiency of food delivery, is a problem that urgently needs to be solved. Summary of the Invention

[0004] This application provides a method, apparatus, equipment, medium, and product for food delivery. The technical solution is as follows:

[0005] According to one aspect of this application, a food delivery method is provided, the method being executed by a server, a merchant client, a user client, a first delivery client, and a second delivery client, the method comprising:

[0006] The merchant client accepts the production task for the first order, the delivery address of the first order is the delivery point and it is in a pre-sale state;

[0007] The first delivery client accepts a first delivery task for the first order, the first delivery task being to deliver at least one meal item ordered in the first order to the delivery point;

[0008] The server sends the sales information of at least one food item to multiple user clients located within the delivery area, where the delivery area is the service area of ​​the delivery point.

[0009] The multiple user clients receive the sales information for at least one food item;

[0010] When at least one of the multiple user clients orders the target dish from the at least one menu item, the server generates a second order for the target dish, wherein the recipient of the second order is the target user corresponding to the at least one user client.

[0011] The server sends a second delivery task for the second order to the second delivery client. The second delivery task is to deliver the target meal to the location corresponding to the target user.

[0012] The second delivery client receives and confirms the second delivery task;

[0013] The target meal corresponding to the second order is a subset of at least one meal ordered in the first order, and the target meal corresponds to the same pickup code in both the first order and the second order.

[0014] According to another aspect of this application, a computer device is provided, comprising: a processor and a memory, wherein the memory stores at least one program, said at least one program being loaded and executed by the processor to implement the steps performed by the server or any client in the food delivery method described above.

[0015] According to another aspect of this application, a computer-readable storage medium is provided that stores at least one program, which is loaded and executed by a processor to implement the steps performed by the server or any client in the food delivery method described above.

[0016] According to another aspect of this application, a computer program product is provided, comprising at least one program segment stored in a computer-readable storage medium; a processor of a computer device reads the at least one program segment from the computer-readable storage medium, and the processor executes the at least one program segment, causing the computer device to perform the steps performed by the server or any client in the food delivery method described above.

[0017] The beneficial effects of the technical solution provided in this application include at least the following:

[0018] By splitting a takeout order from a merchant to a target user into a first order (delivery from the merchant to the delivery area) and a second order (delivery from the delivery point to the target user), and by further splitting a takeout delivery task for a merchant-to-target-user order into a first delivery task for the first order and a second delivery task for the second order, the system allows the first rider for the first delivery client to focus solely on delivering the food from the merchant to the delivery point, while the second rider for the second delivery client focuses solely on delivering the food from the delivery point to the user. Furthermore, the first delivery task is completed before the user places the order, thus eliminating the impact of the order's immediacy on the rider's performance. Even when there are no orders or during off-peak hours, the first rider can avoid delivery gaps by completing the first delivery task. The second rider delivers food that has already been delivered to the delivery point, allowing them to deliver existing food and reducing transit time from the merchant to the delivery point. Since both the delivery point and the user are within the delivery area served by the delivery point, users can receive their food quickly after placing an order, improving the efficiency of their dining experience. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a structural block diagram of a food delivery system provided in an exemplary embodiment of this application;

[0021] Figure 2 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0022] Figure 3 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0023] Figure 4 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0024] Figure 5 This is a schematic diagram of a food delivery method provided in an exemplary embodiment of this application;

[0025] Figure 6 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0026] Figure 7This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0027] Figure 8 This is a schematic diagram of a first delivery task provided in an exemplary embodiment of this application;

[0028] Figure 9 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0029] Figure 10 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0030] Figure 11 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0031] Figure 12 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0032] Figure 13 This is a schematic diagram illustrating the sending of a second delivery task provided in an exemplary embodiment of this application;

[0033] Figure 14 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0034] Figure 15 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0035] Figure 16 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0036] Figure 17 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0037] Figure 18 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0038] Figure 19 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0039] Figure 20 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0040] Figure 21 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0041] Figure 22This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0042] Figure 23 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0043] Figure 24 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0044] Figure 25 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0045] Figure 26 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0046] Figure 27 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0047] Figure 28 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0048] Figure 29 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0049] Figure 30 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0050] Figure 31 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0051] Figure 32 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0052] Figure 33 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0053] Figure 34 This is a schematic diagram of the order receiving interface for a first order provided in an exemplary embodiment of this application;

[0054] Figure 35 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0055] Figure 36 This is a flowchart of a food delivery method provided in an exemplary embodiment of this application;

[0056] Figure 37This is a block diagram of a food delivery device provided in an exemplary embodiment of this application;

[0057] Figure 38 This is a block diagram of a food delivery device provided in an exemplary embodiment of this application;

[0058] Figure 39 This is a block diagram of a food delivery device provided in an exemplary embodiment of this application;

[0059] Figure 40 This is a block diagram of a food delivery device provided in an exemplary embodiment of this application;

[0060] Figure 41 This is a block diagram of a food delivery device provided in an exemplary embodiment of this application;

[0061] Figure 42 This is a schematic diagram of the device structure of a computer device provided in an exemplary embodiment of this application. Detailed Implementation

[0062] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0063] Figure 1 This application provides a structural block diagram of a food delivery system 100 according to an exemplary embodiment. The food delivery system 100 includes a client 120 and a server 140.

[0064] Client 120 connects to server 140 via wireless or wired network.

[0065] Client 120 includes merchant client 121, first delivery client 122, second delivery client 123, and user client 124.

[0066] Merchant client 121 has an application installed and running that supports receiving food delivery orders. For example, merchant client 121 is the client used by merchants participating in food delivery activities, and merchants use merchant client 121 to accept orders and prepare meals. This merchant client 121 corresponds to a specific merchant. If there is only one merchant, there is one merchant client 121. If there are multiple merchants, there are multiple merchant clients 121 corresponding to each of the multiple merchants. This application embodiment does not limit the number of merchant clients 121.

[0067] The first delivery client 122 has an application installed and running that supports receiving first delivery tasks. Exemplarily, the first delivery client 122 is a client used by the first rider to receive the first delivery task. The first delivery task is the task of delivering food from one or more merchants to one or more delivery areas. The first delivery client 122 corresponds to the first rider. If there is only one first rider, there is one first delivery client 122. If there are multiple first riders, there are multiple first delivery clients 122 corresponding one-to-one with each of the multiple first riders. This application embodiment does not limit the number of first delivery clients 122.

[0068] The second delivery client 123 has an application installed and running that supports receiving second delivery tasks. Exemplarily, the second delivery client 123 is a client used by a second rider to receive second delivery tasks. The second delivery task is the task of delivering food from a delivery area to a target user within that area. The second delivery client 123 corresponds to the second rider. If there is only one second rider, there is one second delivery client 123. If there are multiple second riders, there are multiple second delivery clients 123 corresponding one-to-one with each of the multiple second riders. This application embodiment does not limit the number of second delivery clients 123.

[0069] User client 124 has an application installed and running that supports ordering. For example, user client 124 is a client used by a user who needs to order takeout; the user uses user client 124 to place an order. This user client 124 corresponds to a user. If there is only one user, there is one user client 124. If there are multiple users, there are multiple user clients 124 corresponding one-to-one with each of the multiple users. This application embodiment does not limit the number of user clients 124.

[0070] In some embodiments, the merchant client 121, the first delivery client 122, the second delivery client 123, and the user client 124 may be of the same or different device types. These device types include at least one of the following: smartphones, smartwatches, smart TVs, tablets, e-book readers, MP3 players, MP4 players, laptops, and desktop computers. This application does not limit the device type.

[0071] Server 140 includes at least one of a single server, multiple servers, a cloud computing platform, and a virtualization center. For example, server 140 includes a processor 144 and a memory 142. Memory 142 further includes a receiving module 1421 and a sending module 1422. The receiving module 1421 is used to receive requests sent by client 120, such as receiving a request from a first delivery client 122 confirming the completion of a first delivery task. The sending module 1422 is used to send tasks to client 120, such as sending a second delivery task to a second delivery client 123. Server 140 is used to provide background services for applications installed and running on client 120. Optionally, server 140 undertakes the primary computing work, and client 120 undertakes secondary computing work; or, server 140 undertakes secondary computing work, and client 120 undertakes primary computing work; or, server 140 and client 120 use a distributed computing architecture for collaborative computing.

[0072] Server 140 is used to send the first order to merchant client 121, and the recipient of the first order is a delivery point located within the delivery area.

[0073] Server 140 is also used to send a first delivery task of the first order to the first delivery client 122 when the merchant client 121 confirms the first order. The first delivery task is a task to deliver at least one meal item ordered in the first order to a delivery point.

[0074] Server 140 is also used to send sales information for at least one food item to at least one user client 124 located in the delivery area.

[0075] Server 140 is also used to generate a second order for the target meal when user client 124 orders at least one target meal, the recipient of the second order being the target user corresponding to the user client.

[0076] Server 140 is also used to send a second delivery task for a second order to the second delivery client 123. The second delivery task is to deliver the target meal to the location corresponding to the target user.

[0077] In related technologies, the food delivery process is as follows: Figure 2 As shown, it includes the following steps:

[0078] Step 1: User places order;

[0079] Users place orders on food delivery platforms as needed, including selecting the corresponding dishes from the merchants, paying for the order, and filling in the corresponding delivery information, which includes at least one of the following: delivery address, delivery person's contact information, and delivery person's name.

[0080] Step 2: Merchant produces;

[0081] The merchant confirms whether to accept the production order, which is generated by the server based on the user's order details. Optionally, this production order is directed to the merchant. Optionally, this production order is initiated by the user. Optionally, this production order connects the merchant and the user, and the merchant and the rider.

[0082] If the merchant confirms that they will not accept production orders, inform the user that the merchant will not accept production orders and end the current step.

[0083] Once the merchant confirms acceptance of the production order, the merchant will produce the food according to the user's selection.

[0084] Step 3: The rider picks up the meal;

[0085] The rider confirms acceptance of the delivery order, which is generated by the server based on the user's order details. Optionally, the delivery order is for the rider. Optionally, the delivery order is initiated by the merchant. Optionally, the delivery order connects the rider with the merchant and the rider with the user.

[0086] If a rider confirms they will not accept the delivery order, inform the merchant of this and end the current step; or the merchant can continue to wait for a new rider to confirm whether they will accept the delivery order.

[0087] Once the rider confirms acceptance of the delivery order, the rider goes to the corresponding merchant to pick up the food.

[0088] Step 4: The rider delivers the food;

[0089] Once the rider confirms acceptance of the delivery order, the rider will deliver the food from the corresponding merchant to the target user.

[0090] Step 5: Delivery by rider.

[0091] In related technologies, riders have a limited delivery capacity within a given timeframe due to the immediacy of user orders. To increase the number of deliveries per rider within a given timeframe and improve delivery efficiency, this application proposes a food delivery method. For example, as shown... Figure 3 As shown, it includes the following steps:

[0092] Step 6: Estimate the first order;

[0093] The first order was predicted based on delivery data from the food delivery platform. This data includes at least one of the following: the number of dishes, the region, and the order time.

[0094] In some embodiments, the first order is an order for at least one meal from at least one merchant, with the recipient being at least one delivery point.

[0095] Step 7: Merchant produces;

[0096] The merchant confirms whether to accept the production order, which is generated by the server based on the information from the first order. Optionally, this production order is specific to the merchant. Optionally, this production order is used to connect the merchant with the delivery point and / or the merchant with the rider.

[0097] If the merchant confirms that they will not accept production orders, end the current step.

[0098] Once the merchant confirms acceptance of the production order, the merchant will produce the food items according to the order.

[0099] Step 8: The first rider picks up the meal;

[0100] The first rider confirms whether to accept the delivery order, which is generated by the server based on the details of the first order. Optionally, this delivery order is specific to the first rider. Optionally, this delivery order connects the first rider with the merchant and the first rider with the delivery point.

[0101] Once the first rider confirms they will not accept the delivery order, the current step ends.

[0102] Once the first rider confirms acceptance of the delivery order, the first rider will go to at least one merchant to pick up the food.

[0103] Step 9: The first rider delivers the food;

[0104] Once the first rider confirms acceptance of the delivery order, the first rider will deliver the food from at least one merchant to at least one delivery point.

[0105] Step 10: The first rider delivers the goods;

[0106] Step 11: User places order;

[0107] Users within the delivery area served by each delivery point can place an order, including selecting the food at the delivery point, paying for the order, and filling in the corresponding delivery information, which includes at least one of the following: delivery address, recipient's contact information, and recipient's name.

[0108] Step 12: Second rider delivers.

[0109] The second rider at each delivery point will deliver the user's order.

[0110] The food delivery method provided in this application divides the task of delivering food from a merchant to a user, which is completed by one rider, into two parts: first, the first rider completes the delivery from the merchant to the delivery point, and then the second rider completes the delivery from the delivery point to the user. This allows riders to be unaffected by the target user's immediate order, thereby improving the efficiency of food delivery.

[0111] Figure 4 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The method is executed by server 140 in the food delivery system 100 shown. The method includes:

[0112] Step 200: Send the first order to the merchant's client;

[0113] The server sends a first order to the merchant client. The shipper or recipient of this first order is the merchant corresponding to the merchant client, and the recipient is a delivery point located within a delivery area. This delivery area is the service area of ​​the delivery point. Optionally, there is a one-to-one correspondence between the delivery area and the delivery point. Optionally, there is not a one-to-one correspondence between the delivery area and the delivery point, such as one delivery point corresponding to multiple delivery areas. In this embodiment, an example of a one-to-one correspondence between the delivery area and the delivery point is used for illustration.

[0114] In some embodiments, the delivery area includes at least one of residential communities, office buildings, and commercial districts. In some embodiments, the delivery point within the delivery area includes at least one of mobile delivery boxes, mobile food carts, and robot food carts.

[0115] Optionally, the merchant client includes at least one, such as Figure 1 The merchant client 121 in the food delivery system 100 shown. Optionally, the delivery point includes at least one. For example, as... Figure 5 As shown, a first order is sent to the merchant client corresponding to the first merchant 41, the merchant client corresponding to the second merchant 42, and the merchant client corresponding to the third merchant 43, respectively. The recipient of the first order is the first delivery point 52 located in the first delivery area 50 and the second delivery point 62 located in the second delivery area 60.

[0116] In some embodiments, the first order includes an order for at least one food item from a merchant corresponding to at least one merchant client, with the recipient being at least one delivery point. For example, the first order includes an order for at least one food item from a merchant corresponding to one merchant client, with the recipient being one delivery point. For example, the first order includes an order for at least two food items from two merchants corresponding to two merchant clients, with the recipient being one delivery point. For example, the first order includes an order for at least two food items from a merchant corresponding to one merchant client, with the recipient being two delivery points.

[0117] In some embodiments, the merchant client obtains the production task for the first order through other means. For example, the merchant client obtains the production task for the first order through a verbal agreement. It should be understood that the merchant client does not necessarily need to receive and acknowledge the first order sent by the server to obtain the production task for the first order. This application embodiment only uses the server sending the first order as an example for illustration; any method that enables the merchant client to obtain the production task for the first order is within the scope of protection of this application embodiment.

[0118] Step 220: If the merchant client confirms the first order, send the first delivery task of the first order to the first delivery client;

[0119] Based on the received first order, the merchant client confirms whether to accept it. If the merchant client does not accept the first order, the current step ends and / or step 200 is re-executed. If the merchant client accepts the first order, the server sends the first delivery task for the first order to the first delivery client.

[0120] Optionally, the first delivery client includes at least one, such as Figure 1 The first delivery client 122 in the food delivery system 100 shown.

[0121] The first delivery task is to deliver at least one meal item ordered in a first order to a delivery point. For example, the first delivery task is to deliver at least one meal item ordered from a merchant corresponding to one merchant client to one delivery point. For example, the first delivery task is to deliver at least two meal items ordered from two merchants corresponding to two merchant clients to one delivery point. For example, the first delivery task is to deliver an order containing at least two meal items ordered from a merchant client to two delivery points.

[0122] For example, such as Figure 5 As shown, the first delivery task is for the first rider 40 corresponding to the first delivery client to deliver at least one meal from the first merchant 41, at least one meal from the second merchant 42, and at least one meal from the third merchant 43 to the first delivery point 52 within the first delivery area 50 and the second delivery point 62 within the second delivery area 60.

[0123] In some embodiments, the first delivery client obtains the first delivery task of the first order through other means. For example, the first delivery client obtains the first delivery task of the first order through a verbal agreement. It should be understood that the first delivery client is not necessarily required to receive and acknowledge the first delivery task of the first order sent by the server. This application embodiment only uses the example of the server sending the first delivery task for illustration; any method that enables the first delivery client to obtain the first delivery task is within the scope of protection of this application embodiment.

[0124] Step 240: Send sales information for at least one meal item to multiple user clients located within the delivery area;

[0125] In some embodiments, each delivery area includes at least one user client. Sales information for at least one meal item to be delivered to a delivery point within each delivery area is sent to at least one user client in each delivery area. This sales information includes meal information for at least one meal item to be delivered to a delivery point within each delivery area. For example, assuming two delivery areas are included, a first delivery area and a second delivery area, sales information for at least one meal item to be delivered to a delivery point within the first delivery area is sent to at least one user client in the first delivery area, and sales information for at least one meal item to be delivered to a delivery point within the second delivery area is sent to at least one user client in the second delivery area. The sum of at least one meal item delivered to a delivery point within the first delivery area and at least one meal item delivered to a delivery point within the second delivery area equals the at least one meal item ordered in the first order.

[0126] In some embodiments, at a target time, sales information for at least one food item is sent to multiple user clients located within the delivery area. This target time is determined based on the confirmation time of the first order by the merchant client, or the confirmation time of the first delivery task by the first delivery client, or the completion time of the first delivery task.

[0127] Step 260: If at least one user client among multiple user clients orders at least one target meal item, generate a second order for the target meal item;

[0128] In some embodiments, the user client is a user client within each delivery region. Optionally, the user client includes at least one, such as Figure 1 The user client 124 in the food delivery system 100 shown.

[0129] In some embodiments, the target meal is one or more meals selected by the user corresponding to the user client from at least one meal. In some embodiments, the target meal is selected from at least one meal within the delivery area where the user client is located. For example, if the user client is within a first delivery area and the first delivery area includes 10 first meals, then the target meal is at least one of the 10 first meals selected.

[0130] In some embodiments, the second order is an order corresponding to the target food item. The shipper or recipient of the second order is a delivery point within the delivery area, and the recipient of the second order is the target user corresponding to the user client.

[0131] Step 280: Send the second delivery task for the second order to the second delivery client.

[0132] The server sends a second delivery task for the second order to a second delivery client. Optionally, the second delivery client may include at least one, such as Figure 1 The second delivery client 123 in the food delivery system 100 shown. This second delivery task is the task of delivering the target meal to the location corresponding to the target user.

[0133] For example, such as Figure 5 As shown, the second delivery task includes, within the first delivery area 50, rider 51 delivers the target food from the first delivery point 52 to different floors of the first building 53. Alternatively, the second delivery task includes, within the second delivery area 60, rider 61 delivers the target food from the second delivery point 62 to the second building 63 and the third building 64.

[0134] In summary, the method provided in this embodiment, by dividing a takeaway order from a merchant to a target user into a first order from the merchant to a delivery point within the delivery area and a second order from the delivery point to the target user, and by dividing a takeaway delivery task for a takeaway order from a merchant to a target user into a first takeaway delivery task for the first order and a second takeaway delivery task for the second order, enables riders to be unaffected by the target user's immediate order placement, thereby improving the efficiency of takeaway delivery.

[0135] In some embodiments, the aforementioned merchant clients include m instances, and the aforementioned delivery points include n instances, where at least one of m and n is an integer greater than 1. Optionally, m = 1 and n > 1. Optionally, m > 1 and n = 1. Optionally, m > 1 and n > 1. Figure 6 As shown, step 200 above also includes the following sub-steps:

[0136] Step 201: Send at least one first order to each of the m merchant clients.

[0137] In some embodiments, each of the m merchant clients has at least one corresponding first order, and the at least one first order corresponding to the same merchant client corresponds to y delivery points out of n delivery points, where y is a positive integer less than or equal to n.

[0138] For example, suppose there are 2 merchant clients and 3 delivery points. A first order 1 is sent to merchant client 1, which corresponds to delivery point 2 and delivery point 3. A first order 2 and a first order 3 are sent to merchant client 3, which corresponds to delivery point 1 and delivery point 3, respectively.

[0139] In some embodiments, such as Figure 7 As shown, step 220 above also includes the following sub-steps:

[0140] Step 221: If m merchant clients confirm their respective first orders, combine at least two first orders from the m merchant clients to generate the first delivery task;

[0141] In some embodiments, if at least one of m and n is an integer greater than 1, the first order comprises at least two.

[0142] For example, assuming there is a merchant client 1, and delivery point 1 and delivery point 2, that is, when m=1 and n=2, the first order includes a first order 1 ordering at least one meal from the merchant corresponding to merchant client 1, with the recipient being delivery point 1; and a first order 2 ordering at least one meal from the merchant corresponding to merchant client 1, with the recipient being delivery point 2.

[0143] For example, assuming there are merchant client 1 and merchant client 2, and delivery point 1, that is, when m=2 and n=1, the first order includes a first order 1 that orders at least one meal from the merchant corresponding to merchant client 1, with the recipient being delivery point 1; and a first order 2 that orders at least one meal from the merchant corresponding to merchant client 2, with the recipient being delivery point 1.

[0144] For example, assuming there are merchant client 1 and merchant client 2, and delivery point 1 and delivery point 2, that is, when m=2 and n=2, the first order includes at least the first order 1, which orders at least one meal from the merchant corresponding to merchant client 1 and / or the merchant corresponding to merchant client 2, with the recipient being delivery point 1; and the first order 2, which orders at least one meal from the merchant corresponding to merchant client 1 and / or the merchant corresponding to merchant client 2, with the recipient being delivery point 2.

[0145] Given that m merchant clients each accept their respective first orders, at least two first orders are combined to generate a first delivery task. This first delivery task is used to deliver at least one meal item ordered from the m merchant clients to n delivery points.

[0146] In some embodiments, orders are combined according to the principle of the same destination.

[0147] In some embodiments, at least two first orders are combined according to the principle of ordering along the same route. For example, suppose the first orders include: first order 1, ordering at least one meal from the merchant corresponding to merchant client 1, with delivery point 1 as the recipient; first order 2, ordering at least one meal from the merchant corresponding to merchant client 2, with delivery point 1 as the recipient; and first order 3, ordering at least one meal from the merchant corresponding to merchant client 3, with delivery point 1 as the recipient. Figure 8 As shown, the first order 1 corresponds to the route from merchant 1 20 corresponding to merchant client 1 to delivery point 1 23, the first order 2 corresponds to the route from merchant 2 21 corresponding to merchant client 2 to delivery point 1 23, and the first order 3 corresponds to the route from merchant 3 22 corresponding to merchant client 3 to delivery point 1 23. Figure 8 As can be seen from the data, route 1, which delivers goods from merchant 120 to delivery point 123, intersects with route 2, which delivers goods from merchant 221 to delivery point 123. Therefore, order 1 and order 2 are combined into one order.

[0148] In some embodiments, at least two first orders are combined to obtain at least one combined order. A first delivery task is generated based on the at least one combined order. For example, in the case of first order 1, first order 2, and first order 3, first order 1 and first order 2 are combined to obtain combined order 1. Then the first delivery task includes the delivery task corresponding to combined order 1 and the delivery task corresponding to first order 3.

[0149] In some embodiments, at least two first orders are combined according to the principle of shortest delivery time. For example, suppose there are three first orders: First Order 1, First Order 2, and First Order 3. The delivery time for First Order 1 is 2 seconds, for First Order 2 it is 3 seconds, and for First Order 3 it is 6 seconds. Since 2 + 3 = 5 < 6, First Order 1 and First Order 2 are combined. It is worth noting that combining at least two first orders according to the principle of shortest delivery time requires that the combined delivery time of the combined order is less than or equal to the longest delivery time of each first order within the combined order. For example, suppose the longest delivery time for First Order 1 is 4 seconds. Since 2 + 3 = 5 > 4, First Order 1 and First Order 2 cannot be combined.

[0150] Step 222: Send the first delivery task for at least two first orders to the first delivery client.

[0151] In some embodiments, a first delivery task comprising a combined order is sent to a first delivery client.

[0152] In summary, the method provided in this embodiment combines at least two first orders corresponding to m merchant clients, changing the first delivery task from corresponding to each first order individually to corresponding to the combined order. By combining orders, the tasks corresponding to the first orders become more compact, thereby enabling the first rider corresponding to the first delivery client to complete the first delivery task more efficiently according to the principle of following the route or the shortest delivery time.

[0153] In some embodiments, the above n delivery points are at least two delivery points. For example... Figure 9 As shown, step 221 above also includes the following sub-steps:

[0154] Step 2211: Given that m merchant clients accept their respective first orders and n delivery points are at least two delivery points, combine the at least two first orders corresponding to the m merchant clients to generate a first delivery task including n delivery sub-tasks.

[0155] In some embodiments, the first delivery task includes n delivery sub-tasks corresponding to n delivery points, each delivery sub-task being used to deliver at least one meal ordered by the merchant's client to the corresponding delivery point.

[0156] The j-th delivery subtask in n delivery subtasks is used to deliver at least one meal ordered by x merchant clients to the j-th delivery point, where j is a positive integer less than or equal to n and x is a positive integer less than or equal to m.

[0157] In some embodiments, the first delivery task further includes m sub-tasks for picking up meals corresponding to m merchant clients. For example... Figure 10 As shown, step 221 above also includes the following sub-steps:

[0158] Step 2212: Given that m merchant clients accept their respective first orders and n delivery points are at least two delivery points, merge the at least two corresponding orders from the m merchant clients to generate a first delivery task that includes m pickup sub-tasks and n delivery sub-tasks.

[0159] In some embodiments, each pickup subtask is used to retrieve at least one ordered meal from the corresponding merchant client.

[0160] The i-th subtask in the m subtasks is used to pick up food from the i-th merchant's client, where i is a positive integer less than or equal to m.

[0161] In some embodiments, the m1 food pickup subtasks out of the m food pickup subtasks and the n1 delivery subtasks out of the n delivery subtasks correspond to each other, where m1 is a positive integer less than or equal to m and n1 is a positive integer less than or equal to n.

[0162] The m food pickup subtasks are generated according to the principle of shortest pickup time; or, according to the principle of convenient route; and / or, the n delivery subtasks are generated according to the principle of shortest delivery time; or, according to the principle of convenient route.

[0163] In summary, the method provided in this embodiment divides the first delivery task into multiple delivery sub-tasks corresponding to multiple delivery points, or into multiple delivery sub-tasks corresponding to multiple delivery points and multiple pickup sub-tasks corresponding to multiple merchant clients, so that the first rider can target multiple delivery sub-tasks and multiple pickup sub-tasks when completing the first delivery task, thus ensuring the efficiency of completing the first delivery task.

[0164] In some embodiments, each delivery area includes at least one user client, and each user client corresponds to a user who can order at least one meal item from a delivery point within the delivery area as the target meal item. In some embodiments, the second order corresponding to the target meal item includes at least two, and at least two second orders correspond to delivery points corresponding to the second delivery client. The ordering times for the at least two second orders are the same or different.

[0165] In some embodiments, such as Figure 11 As shown, step 280 above also includes the following sub-steps:

[0166] Step 281: At predetermined time intervals, send the second delivery task to the second delivery client for at least two second orders generated in the most recent time interval.

[0167] The scheduled time interval is preset by the server. The scheduled time interval may be fixed or dynamically adjusted.

[0168] The duration of this scheduled time interval is set based on empirical values. When the scheduled time interval is fixed, its duration is set based on at least t days of delivery activity within the delivery area, where t is a positive integer. When the scheduled time interval is dynamically adjusted, its duration is adjusted in real time according to the delivery activity within the time period. For example, the scheduled time interval is set to 15 minutes between 10:00 AM and 11:00 AM, and to 10 minutes between 11:00 AM and 1:00 PM.

[0169] In some embodiments, a second delivery task for at least two second orders generated within the most recent time interval is sent to a second delivery client at predetermined time intervals. For example, assuming the predetermined time interval is 10 minutes, a second delivery task is sent to the second delivery client every 10 minutes. For instance, if a second delivery task is sent to the second delivery client at 10:10 AM, the next second delivery task will be sent to the second delivery client at 10:20 AM.

[0170] In some embodiments, if no user client has ordered the target meal item in at least one meal item within the most recent time interval, i.e., there is no second order for the target meal item, a notification message indicating that at least two second orders have not been generated within the most recent time interval is sent to the second delivery client, or the sending is stopped within the most recent time interval.

[0171] In some embodiments, such as Figure 12 As shown, step 280 above also includes the following sub-steps:

[0172] Step 282: If the number of orders in at least two second orders reaches the quantity threshold, send the second delivery task of at least two second orders to the second delivery client.

[0173] This quantity threshold is preset by the server and is used to indicate the maximum quantity for a second order. This quantity threshold can be fixed or dynamically adjusted.

[0174] The quantity threshold is set based on empirical values. When the quantity threshold is fixed, it is set based on at least t days of delivery activity within the delivery area, where t is a positive integer. When the quantity threshold is dynamically adjusted, it is adjusted in real time according to the delivery activity within a time period. For example, between 10:00 AM and 11:00 AM, the quantity threshold is set to 20, meaning that if at least 20 second orders are generated, a second delivery task for at least two second orders is sent to the second delivery client. Between 11:00 AM and 1:00 PM, the quantity threshold is set to 15, meaning that if at least 15 second orders are generated, a second delivery task for at least two second orders is sent to the second delivery client.

[0175] In some embodiments, steps 281 and 282 are performed separately. In some embodiments, steps 281 and 282 are performed jointly, without regard to the order in which they are performed. For example, as shown... Figure 13 As shown, assuming the predetermined time interval is 10 minutes and the quantity threshold is 20, if the number of at least two second orders generated within 0-10 minutes does not reach the quantity threshold, a second delivery task for the at least two second orders generated within 0-10 minutes is sent to the second delivery client at the 10th minute. If, within 10-20 minutes, the number of at least two second orders generated reaches the quantity threshold twice, then, in the first instance of reaching the quantity threshold, a second delivery task for the 20 second orders generated after the 10th minute is sent to the second delivery client; in the second instance of reaching the quantity threshold, a second delivery task for the 20 second orders generated between the first and second instances of reaching the quantity threshold is sent to the second delivery client; and at the 20th minute, a second delivery task for the at least two second orders generated between the second instance of reaching the quantity threshold and the 20th minute is sent to the second delivery client.

[0176] In some embodiments, the second delivery tasks correspond to a delivery sequence. The second delivery tasks for at least two second orders are sorted according to the delivery sequence.

[0177] The delivery order is determined by at least one of the following factors:

[0178] • The location of the target user within the delivery area;

[0179] • Prioritize the consumption of the target food items;

[0180] • The ordering time for the target meal.

[0181] Optionally, the delivery order can be determined based on the target user's location within the delivery area. For example, assuming the target user's location within the delivery area is determined by floor level, the second delivery tasks for at least two second orders are ordered according to the floor the target user is located on. For instance, if the target user is located on both the first and fifth floors, the second order corresponding to the target user on the first floor is delivered first, followed by the second order corresponding to the target user on the fifth floor. Alternatively, the delivery order can be determined based on the target user's location within the delivery area and the delivery point's location within the delivery area. For instance, if the target user is located on both the first and fifth floors, and the delivery point is on the sixth floor, since the fifth floor is closer to the sixth floor than the first floor, the second order corresponding to the target user on the fifth floor is delivered first, followed by the second order corresponding to the target user on the first floor.

[0182] Optionally, the delivery order can be determined based on the consumption priority of the target meals. For example, the second delivery tasks of at least two second orders can be sorted according to the consumption priority of the target meals. Assuming that the consumption priority of target meal 1 is higher than that of target meal 2, the second order corresponding to target meal 1 will be delivered first, followed by the second order corresponding to target meal 2.

[0183] Optionally, the delivery order can be determined based on the order time of the target meal. For example, assuming that the order time for the target meal includes a first time and a second time, and the first time is before the second time, then the second order corresponding to the first time will be delivered first, and then the second order corresponding to the second time will be delivered.

[0184] In summary, the method provided in this embodiment determines the timing of sending at least two second orders to the second delivery client based on a predetermined time interval and / or a quantity threshold, ensuring delivery efficiency for the second rider corresponding to the second delivery client when delivering the second orders. Furthermore, by sorting the second delivery tasks according to the delivery order, the second delivery tasks can be planned in advance, thereby further improving the completion efficiency of the second delivery tasks.

[0185] In some embodiments, the first and second orders mentioned above are associated via a pickup code. For example... Figure 14 As shown, the above steps also include:

[0186] Step 320: Generate a pickup code corresponding to each of the at least one meal items ordered in the first order;

[0187] This pickup code corresponds one-to-one with each item in at least one meal. Optionally, the pickup codes for the same two meals can be different.

[0188] The pickup code is a food identification code. It is worth noting that the format of the pickup code is not limited in this embodiment. In some embodiments, the pickup code may be formatted as at least one of numeric encoding, alphanumeric encoding, or a mixed encoding including numbers and letters.

[0189] Step 340: Send the pickup code corresponding to each of the at least one meal items ordered in the first order to the first delivery client.

[0190] The pickup code is used to instruct the first rider corresponding to the first delivery client to deliver the corresponding meal.

[0191] In some embodiments, the delivery point includes a compartment for storing each of at least one meal item ordered in the first order. Optionally, the compartment corresponds one-to-one with the meal item, meaning each compartment is used to store one meal item.

[0192] In some embodiments, such as Figure 15 As shown, the above steps also include:

[0193] Step 360: Send the corresponding pickup code and compartment to the second delivery client for each of the at least one meal items ordered in the first order.

[0194] In some embodiments, a pickup code and its corresponding compartment are sent to a second delivery client. The pickup code instructs a second delivery rider corresponding to the second delivery client to deliver the corresponding meal. This pickup code and compartment mapping associates each meal with both a pickup code and a compartment. For example, assuming meal 1 has a pickup code of 1, and the pickup code and compartment mapping indicates that pickup code 1 corresponds to compartment 1, then meal 1 is placed in compartment 1.

[0195] It is worth noting that steps 340 and 360 are not ordered. In some embodiments, step 340 is executed before step 360. In some embodiments, step 360 is executed before step 340. In some embodiments, steps 340 and 360 are executed simultaneously.

[0196] In some embodiments, a pickup code corresponding to the target meal in the second order is sent to the second delivery client. The target meal corresponds to the same pickup code in both the first and second orders. Since the target meal in the second order is a subset of at least one meal in the first order, the pickup code corresponding to the target meal is a subset of the pickup codes corresponding to each of the at least one meal in the first order. For example, suppose the at least one meal in the first order includes four meals, each with pickup codes "A, B, C, D", and the target meal is a subset of the at least one meal in the first order, then the pickup code corresponding to the target meal is a subset of "A, B, C, D".

[0197] In summary, the method provided in this embodiment uses the same pickup code in both the first and second orders, ensuring a one-to-one correspondence between the food items in the first and second orders. Furthermore, by mapping the pickup code to the designated compartment, the food items are coded or arranged, allowing delivery riders to quickly locate the correct food item based on the pickup code and compartment, thus preventing order confusion and reduced delivery efficiency.

[0198] Figure 16 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The first delivery client 122 in the food delivery system 100 shown is executed. The method includes:

[0199] Step 420: Display the order acceptance interface for the first order;

[0200] In some embodiments, the order acceptance interface of the first order displays a first delivery task, which is a task to deliver at least one meal item ordered in the first order to a delivery point. The sender or receiver of the first order is the merchant corresponding to the merchant client, and the recipient of the first order is the delivery point. At least one meal item is used to deliver from the delivery point to the target user corresponding to the user client within the delivery area.

[0201] In some embodiments, the first order includes an order for at least one food item from a merchant corresponding to at least one merchant client, with the recipient being at least one delivery point. For example, the first order includes an order for at least one food item from a merchant corresponding to one merchant client, with the recipient being one delivery point. For example, the first order includes an order for at least two food items from two merchants corresponding to two merchant clients, with the recipient being one delivery point. For example, the first order includes an order for at least two food items from a merchant corresponding to one merchant client, with the recipient being two delivery points.

[0202] In some embodiments, the delivery area includes at least one of residential communities, office buildings, and commercial districts. In some embodiments, the delivery point includes at least one of mobile delivery boxes, mobile food carts, and robot food carts.

[0203] The first delivery task is to deliver at least one meal item ordered in a first order to a delivery point. For example, the first delivery task is to deliver at least one meal item ordered from a merchant corresponding to one merchant client to one delivery point. For example, the first delivery task is to deliver at least two meal items ordered from two merchants corresponding to two merchant clients to one delivery point. For example, the first delivery task is to deliver an order containing at least two meal items ordered from a merchant client to two delivery points.

[0204] Step 440: In response to the confirmation operation for the first delivery task, display the delivery interface for the first order;

[0205] In some embodiments, the confirmation operation for the first delivery task includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, several of the above-mentioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application's embodiments.

[0206] In some embodiments, the delivery-pending interface for the first order displays the delivery-pending information for that first order. This delivery-pending information corresponds one-to-one with the first order. The delivery-pending information includes at least one of the following: quantity of food items, region information, and delivery time.

[0207] Step 460: In response to the confirmation operation of the delivery information for the first order, display the delivery interface for the first order.

[0208] In some embodiments, the confirmation operation for the delivery information of the first order includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, several of the above-mentioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application.

[0209] In some embodiments, the delivery interface of the first order displays delivery information, which indicates that the first order has been delivered.

[0210] In summary, the method provided in this embodiment displays the delivery interface of the first order in response to the confirmation operation for the first delivery task; and displays the delivery interface of the first order in response to the confirmation operation for the delivery information of the first order. This allows the first rider corresponding to the first delivery client to only need to complete the task of delivering the food from the merchant to the delivery point within the delivery point, and the first rider is not subject to the immediacy of the user's order placement.

[0211] In some embodiments, the aforementioned merchant clients include m instances, and the aforementioned delivery points include n instances, where at least one of m and n is an integer greater than 1. Optionally, m = 1 and n > 1. Optionally, m > 1 and n = 1. Optionally, m > 1 and n > 1. Figure 17 As shown, step 440 above also includes the following sub-steps:

[0212] Step 441: In response to the confirmation operation for the first delivery task, display the delivery interface for the first order within the n delivery points.

[0213] In some embodiments, the first delivery task is used to deliver at least one meal ordered by m merchant clients to n delivery points. Each of the m merchant clients has at least one corresponding first order, and each first order includes at least one meal. The at least one first order corresponding to the same merchant client corresponds to y delivery points out of the n delivery points, where y is a positive integer less than or equal to n.

[0214] The delivery interface for the first order at n delivery points displays the delivery information for the first order corresponding to each of the n delivery points.

[0215] In some embodiments, the n delivery points are at least two delivery points, and the first delivery task includes n delivery sub-tasks. Each delivery sub-task is used to deliver at least one meal ordered by the merchant's client to the corresponding delivery point.

[0216] The j-th delivery subtask in n delivery subtasks is used to deliver at least one meal ordered by x merchant clients to the j-th delivery point, where j is a positive integer less than or equal to n and x is a positive integer less than or equal to m.

[0217] In some embodiments, such as Figure 18 As shown, step 441 above also includes the following sub-steps:

[0218] Step 4411: In response to the confirmation operation for the j-th delivery subtask out of n delivery subtasks, display the delivery interface for the first order at the j-th delivery point out of n delivery points.

[0219] The delivery interface for the first order at the j-th delivery point displays the delivery information for the first order corresponding to the j-th delivery point.

[0220] In some embodiments, the first delivery task further includes m sub-tasks for picking up meals. For example... Figure 19 As shown, prior to step 441 above, the following steps are also included:

[0221] Step 430: Display the first order pickup screen.

[0222] The first order pickup interface includes m pickup sub-tasks, each of which is used to retrieve at least one ordered meal from the corresponding merchant's client.

[0223] The i-th subtask in the m subtasks is used to pick up food from the i-th merchant's client, where i is a positive integer less than or equal to m.

[0224] In some embodiments, the m1 food pickup subtasks out of the m food pickup subtasks and the n1 delivery subtasks out of the n delivery subtasks correspond to each other, where m1 is a positive integer less than or equal to m and n1 is a positive integer less than or equal to n.

[0225] The m food pickup subtasks are generated according to the principle of shortest pickup time; or, according to the principle of convenient route; and / or, the n delivery subtasks are generated according to the principle of shortest delivery time; or, according to the principle of convenient route.

[0226] In the case where the first delivery task includes m pickup sub-tasks and n delivery sub-tasks, such as Figure 20 As shown, step 441 above also includes the following sub-steps:

[0227] Step 4412: In response to the confirmation operation for m food pickup sub-tasks, display the second food pickup interface;

[0228] In some embodiments, the confirmation operation for m food pickup sub-tasks includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, the aforementioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application's embodiments.

[0229] The m food pickup sub-tasks are displayed in the first waiting-to-pickup interface, and the second waiting-to-pickup interface includes n first delivery sub-tasks.

[0230] Step 4413: In response to the confirmation operation for n delivery sub-tasks, display the delivery interface for the first order at n delivery points;

[0231] In some embodiments, the confirmation operation for n delivery sub-tasks includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, the aforementioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application's embodiments.

[0232] In summary, the method provided in this embodiment divides the first delivery task into multiple delivery sub-tasks corresponding to multiple delivery points, or into multiple delivery sub-tasks corresponding to multiple delivery points and multiple pickup sub-tasks corresponding to multiple merchant clients, so that the first rider can target multiple delivery sub-tasks and multiple pickup sub-tasks when completing the first delivery task, thus ensuring the efficiency of completing the first delivery task.

[0233] Figure 21 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The first delivery client 122 in the food delivery system 100 shown is executed. The method also includes:

[0234] Step 480: Receive the pickup code corresponding to each of the at least one meal items ordered in the first order.

[0235] This pickup code corresponds one-to-one with each item in at least one meal. Optionally, the pickup codes for the same two meals can be different.

[0236] The pickup code is a food identification code. It is worth noting that the format of the pickup code is not limited in this embodiment. In some embodiments, the pickup code may be formatted as at least one of numeric encoding, alphanumeric encoding, or a mixed encoding including numbers and letters.

[0237] The pickup code is used to instruct the first rider corresponding to the first delivery client to deliver the corresponding meal.

[0238] Figure 22 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The second delivery client 123 in the food delivery system 100 shown is executed. The method includes:

[0239] Step 520: Display the order acceptance interface for the second order;

[0240] In some embodiments, the order acceptance interface for the second order displays a second delivery task. This second delivery task involves delivering the ordered food from the delivery point to the location corresponding to the target user. The recipient of the second order is the target user, who is located within the delivery area, which is the service area of ​​the delivery point. The target user corresponds to a user client located within the delivery area, and the food is pre-delivered from at least one merchant client to the delivery point.

[0241] Step 540: In response to the confirmation operation for the second delivery task, display the delivery screen for the second order;

[0242] In some embodiments, the confirmation operation for the second delivery task includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, several of the above-mentioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application's embodiments.

[0243] In some embodiments, the delivery-pending interface for the second order displays the delivery-pending information for that second order. This delivery-pending information corresponds one-to-one with the second order. The delivery-pending information includes at least one of the following: quantity of food items, region information, and delivery time.

[0244] Step 560: In response to the confirmation operation for the delivery information of the second order, display the delivery interface of the second order.

[0245] In some embodiments, the confirmation operation for the delivery information of the second order includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, several of the above-mentioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application.

[0246] In some embodiments, the delivery interface of the second order displays delivery information, which is used to indicate that the first order has been delivered.

[0247] In summary, the method provided in this embodiment displays the delivery interface of the second order in response to the confirmation operation for the second delivery task; and displays the delivery interface of the second order in response to the confirmation operation for the delivery information of the second order. This allows the second rider corresponding to the second delivery client to only complete the task of delivering the food from the delivery point to the user. The food delivered by the second rider is delivered to the delivery point in advance, so the second rider can deliver existing food, reducing the transit time from the merchant to the delivery point.

[0248] In some embodiments, each delivery area includes at least one user client, and each user client corresponds to a user who can order at least one meal item as the target meal item from the delivery point. In some embodiments, the second order corresponding to the target meal item includes at least two, and at least two second orders correspond to the delivery point corresponding to the second delivery client. The ordering times of the at least two second orders are the same or different.

[0249] In some embodiments, such as Figure 23 As shown, prior to step 540 above, the method further includes:

[0250] Step 531: Receive at least two second delivery tasks for the second orders at predetermined time intervals.

[0251] The scheduled time interval is preset by the server. The scheduled time interval may be fixed or dynamically adjusted.

[0252] The duration of this scheduled time interval is set based on empirical values. When the scheduled time interval is fixed, its duration is set based on at least t days of delivery activity within the delivery area, where t is a positive integer. When the scheduled time interval is dynamically adjusted, its duration is adjusted in real time according to the delivery activity within the time period. For example, the scheduled time interval is set to 15 minutes between 10:00 AM and 11:00 AM, and to 10 minutes between 11:00 AM and 1:00 PM.

[0253] In some embodiments, the order acceptance interface for the second order is updated at predetermined time intervals. In some embodiments, at least two second delivery tasks for the second orders are received at predetermined time intervals.

[0254] In some embodiments, such as Figure 24 As shown, step 540 above also includes the following sub-steps:

[0255] Step 541: In response to a confirmation operation for at least two second delivery tasks within the most recent time interval, display the delivery screen for the second orders.

[0256] In some embodiments, the confirmation operation for at least two second delivery tasks within a recent time interval includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, the aforementioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application.

[0257] In some embodiments, such as Figure 25 As shown, prior to step 540 above, the method further includes:

[0258] Step 532: If the number of orders in at least two second orders reaches the quantity threshold, receive the second delivery task for at least two second orders.

[0259] This quantity threshold is preset by the server and is used to indicate the maximum quantity for a second order. This quantity threshold can be fixed or dynamically adjusted.

[0260] The quantity threshold is set based on empirical values. When the quantity threshold is fixed, it is set based on at least t days of delivery activity within the delivery area, where t is a positive integer. When the quantity threshold is dynamically adjusted, it is adjusted in real time according to the delivery activity within a time period. For example, between 10:00 AM and 11:00 AM, the quantity threshold is set to 20, meaning that if at least 20 second orders are generated, at least two second orders will be accepted for delivery. Between 11:00 AM and 1:00 PM, the quantity threshold is set to 15, meaning that if at least 15 second orders are generated, at least two second orders will be accepted for delivery.

[0261] In some embodiments, the order acceptance interface for the second orders is updated when the number of orders in at least two generated second orders reaches a quantity threshold.

[0262] In some embodiments, such as Figure 26 As shown, step 540 above also includes the following sub-steps:

[0263] Step 542: In response to the confirmation operation for the second delivery task for at least two second orders whose order quantity has reached the quantity threshold, display the delivery interface for the second orders.

[0264] In some embodiments, the confirmation operation for a second delivery task of at least two second orders where the order quantity reaches a quantity threshold includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, several of the above-mentioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of the embodiments of this application.

[0265] In some embodiments, steps 541 and 542 are performed separately. In some embodiments, steps 281 and 282 are performed jointly, without regard to the order. For example, Figure 13 As shown, assuming the predetermined time interval is 10 minutes and the quantity threshold is 20, if the number of at least two second orders generated within 0-10 minutes does not reach the quantity threshold, then at the 10th minute, a second delivery task for at least two second orders generated within 0-10 minutes is received. If, within 10-20 minutes, the number of at least two second orders generated reaches the quantity threshold twice, then, in the case of the first time the quantity threshold is reached, a second delivery task for 20 second orders generated after the 10th minute is received; in the case of the second time the quantity threshold is reached, a second delivery task for 20 second orders generated between the first and second times the quantity threshold is reached is received; and at the 20th minute, a second delivery task for at least two second orders generated between the second time the quantity threshold is reached is received.

[0266] In some embodiments, the second delivery task corresponds to a delivery sequence. For example... Figure 27 As shown, after step 540 above, the following is also included:

[0267] Step 550: Receive the delivery sequence of at least two second delivery tasks for the second orders.

[0268] The delivery order is determined by at least one of the following factors:

[0269] • The location of the target user within the delivery area;

[0270] • Prioritize the consumption of the target food items;

[0271] • The ordering time for the target meal.

[0272] In some embodiments, the location of the target user within the delivery area includes first-floor information. For example... Figure 28 As shown, step 550 above also includes the following sub-steps:

[0273] Step 551: Receive the delivery sequence of the second delivery tasks for at least two second orders generated based on the first floor information.

[0274] In some embodiments, the first floor information is used to indicate the location of the target user within the delivery area. In some embodiments, the first floor information includes the floor number. For example, if the first floor information is floor 5, it means that the target user is on the 5th floor of the delivery area. Second delivery tasks for at least two second orders are sorted according to the first floor information. For example, if the first floor information indicates that it includes floors 1 and 5, the second order corresponding to floor 1 is delivered first, and then the second order corresponding to floor 5 is delivered.

[0275] In some embodiments, such as Figure 29 As shown, the above method also includes:

[0276] Step 500: Obtain the second floor information of the second delivery client within the delivery area.

[0277] In some embodiments, the second floor information is used to indicate the location of the second rider corresponding to the second delivery client within the delivery area, or the second floor information is used to indicate the location of the delivery point within the delivery area. It should be understood that, generally, the location of the second rider corresponding to the second delivery client within the delivery area and the location of the delivery point within the delivery area are the same. For example, assuming the delivery point is a mobile food cart, the mobile food cart is moved and controlled by the second rider corresponding to the second delivery client within the delivery area.

[0278] In some embodiments, the second floor information includes the floor number. For example, if the second floor information is the 7th floor, it means that the second rider corresponding to the second delivery client is on the 7th floor of the delivery area.

[0279] In some embodiments, when both first floor information and second floor information are included, such as Figure 30 As shown, step 551 above also includes:

[0280] Step 552: Receive the delivery sequence of the second delivery tasks for at least two second orders generated based on the first floor information and the second floor information.

[0281] In some embodiments, the second delivery tasks of at least two second orders are sorted according to first floor information and second floor information. For example, if the first floor information indicates that target user 1 is on the 1st floor and target user 2 is on the 5th floor, and the second floor information indicates that the delivery point is on the 7th floor, since the delivery point is closer to the target user 2's location, that is, the time it takes for the delivery point to move from the 7th floor to the 5th floor is shorter than the time it takes for the delivery point to move from the 7th floor to the 1st floor, the second order corresponding to the 5th floor is delivered first, and then the second order corresponding to the 1st floor is delivered.

[0282] In summary, the method provided in this embodiment determines the timing of receiving at least two second orders for a second delivery task based on a predetermined time interval and / or a quantity threshold, ensuring delivery efficiency for the second rider corresponding to the second delivery client when delivering the second orders. Furthermore, by sorting the second delivery tasks according to the delivery order, the second delivery tasks can be planned in advance, thereby further improving the completion efficiency of the second delivery tasks.

[0283] Figure 31 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The second delivery client 123 in the food delivery system 100 shown is executed. The method also includes:

[0284] Step 580: Receive the pickup code corresponding to the target meal ordered in the second order.

[0285] The target meal item corresponds to the same pickup code in both the first and second orders. Since the target meal item in the second order is a subset of at least one meal item ordered in the first order, the pickup code for that target meal item is a subset of the pickup codes for each of the at least one meal item ordered in the first order. For example, suppose the first order includes at least four meal items, each with pickup codes "A, B, C, D". If the target meal item is a subset of the at least one meal item ordered in the first order, then the pickup code for the target meal item is a subset of "A, B, C, D".

[0286] In some embodiments, the delivery point within the delivery area includes compartments for storing meals. Optionally, each compartment corresponds one-to-one with a meal, meaning each compartment is used to store one meal.

[0287] In some embodiments, such as Figure 32 As shown, the above steps also include:

[0288] Step 590: Receive the correspondence between the pickup code and the compartment corresponding to each of the at least one meal items ordered in the first order.

[0289] The pickup code is used to instruct the second rider corresponding to the second delivery client to deliver the corresponding meal. The mapping between the pickup code and the storage compartment is used to associate each meal with both the pickup code and the storage compartment. For example, assuming that the pickup code for meal 1 is 1, and the mapping between the pickup code and the storage compartment indicates that pickup code 1 corresponds to storage compartment 1, then meal 1 will be placed in storage compartment 1.

[0290] It is worth noting that steps 580 and 590 are not ordered. In some embodiments, step 580 is executed before step 590. In some embodiments, step 590 is executed before step 580. In some embodiments, steps 580 and 590 are executed simultaneously.

[0291] In summary, the method provided in this embodiment uses the same pickup code in both the first and second orders, ensuring a one-to-one correspondence between the food items in the first and second orders. Furthermore, by mapping the pickup code to the designated compartment, the food items are coded or arranged, allowing delivery riders to quickly locate the correct food item based on the pickup code and compartment, thus preventing order confusion and reduced delivery efficiency.

[0292] Figure 33This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The merchant client 121, the first delivery client 122, and the server 140 in the food delivery system 100 shown in the diagram work together. The method includes:

[0293] Step 601: The server sends the first order to the merchant's client;

[0294] For specific implementation details, please refer to step 200 above.

[0295] Step 602: The merchant's client receives and confirms the first order;

[0296] The merchant client receives the first order, and the merchant corresponding to the merchant client confirms whether to accept the first order.

[0297] Optionally, if the merchant confirms acceptance of the order, proceed to step 603 below.

[0298] Optionally, if the merchant confirms that they will not accept the order, the current step will end and / or step 601 will be re-executed.

[0299] Step 603: Merchant confirms order acceptance;

[0300] Step 604: The merchant client responds to the confirmation operation for the first order by sending an order acceptance confirmation message;

[0301] In some embodiments, the confirmation operation for the first order includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the confirmation operation includes, but is not limited to, several of the above-mentioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of the embodiments of this application.

[0302] This order confirmation message is used to indicate to the merchant client that the corresponding merchant has confirmed the order.

[0303] Step 605: The server receives confirmation of order acceptance;

[0304] Step 606: The server sends the first delivery task of the first order to the first delivery client;

[0305] For specific implementation details, please refer to step 220 above.

[0306] Step 607: The first delivery client receives the first delivery task;

[0307] In some embodiments, the first delivery client receives delivery information related to the first delivery task. This delivery information includes at least one of merchant information, delivery area information, and meal information. The merchant information includes at least one of merchant name, merchant location, and merchant meal preparation time. The delivery area information includes at least one of delivery area name, delivery area location, and delivery point location within the delivery area. The meal information includes at least one of meal name, meal quantity, and corresponding pickup code.

[0308] Step 608: The first delivery client displays the order acceptance interface for the first order;

[0309] In some embodiments, the order acceptance interface for the first order includes a first delivery task. For example, such as... Figure 34 As shown, the order acceptance interface 30 for the first order displays at least one of the following: merchant information, delivery area information, and food information. The merchant information includes the merchant name 31 and the merchant's food preparation time 35; the delivery area information includes the delivery area name 32; and the food information includes the food name 34 and the corresponding pickup code 33.

[0310] For a detailed implementation method, please refer to step 420 above.

[0311] In some embodiments, the first rider corresponding to the first delivery client confirms whether to accept the first delivery task.

[0312] Optionally, if the first rider confirms acceptance of the first delivery task, proceed to step 609 below.

[0313] Optionally, if the first rider confirms that they will not accept the first delivery task, the current step ends and / or step 606 is re-executed.

[0314] Step 609: The first rider confirms the first delivery task;

[0315] In some embodiments, the order acceptance interface for the first order displays an acceptance control for the first delivery task. The first rider confirms the first delivery task by touching the acceptance control for the first delivery task.

[0316] Step 610: The first delivery client responds to the confirmation operation for the first delivery task and displays the delivery interface for the first order;

[0317] For a detailed implementation method, please refer to step 440 above.

[0318] Step 611: The first rider confirms delivery;

[0319] In some embodiments, a delivery confirmation control is displayed on the delivery screen of the first order. The first rider confirms the completion of the first order by touching the delivery confirmation control, that is, confirms that the corresponding meal has been delivered from the merchant to the delivery point.

[0320] Step 612: The first delivery client responds to the confirmation operation of the food delivery information for the first order and displays the delivery interface of the first order;

[0321] For a detailed implementation method, please refer to step 460 above.

[0322] Step 613: The server receives the confirmation delivery information for the first order.

[0323] The confirmation delivery information for the first order indicates that the first delivery task has been completed.

[0324] It is worth noting that steps 612 and 613 are not ordered. In some embodiments, step 612 is executed before step 613. In some embodiments, step 613 is executed before step 612. In some embodiments, steps 612 and 613 are executed simultaneously.

[0325] Figure 35 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The second delivery client 123, user client 124, and server 140 in the food delivery system 100 shown collaborate. The method includes:

[0326] Step 701: The server sends sales information for at least one food item to multiple user clients located within the delivery area;

[0327] For details on the implementation method, please refer to step 240.

[0328] Step 702: Multiple user clients receive sales information;

[0329] The user client receives sales information for at least one food item.

[0330] Step 703: User places order;

[0331] Users can select at least one dish from the sales information, and then select one or more dishes as their target dishes.

[0332] In some embodiments, the user client displays a purchase control for the target dish. The user places an order by touching the purchase control for the target dish.

[0333] Step 704: At least one of the multiple user clients responds to the purchase operation for the target meal by sending a purchase confirmation message;

[0334] In some embodiments, the purchase operation for a target food item includes at least one of the following: single click, double click, left / right swipe, up / down swipe, long press, hover, facial recognition, and voice recognition. It is worth noting that the purchase operation includes, but is not limited to, the aforementioned methods. Those skilled in the art should understand that any operation capable of achieving the above functions falls within the protection scope of this application's embodiments.

[0335] This purchase confirmation information is used to indicate to the user on the client that the order has been placed.

[0336] Step 705: The server receives confirmation of the purchase information;

[0337] Step 706: The server generates a second order for the target meal;

[0338] For specific implementation details, please refer to step 260 above.

[0339] Step 707: The server sends the second delivery task for the second order to the second delivery client;

[0340] For specific implementation details, please refer to step 280 above.

[0341] Step 708: The second delivery client receives and confirms the second delivery task;

[0342] In some embodiments, the second delivery client receives delivery information related to the second delivery task. This delivery information includes at least one of target meal information and user information. The target meal information includes at least one of the target meal name, target meal quantity, and corresponding pickup code. The user information includes at least one of the user's contact information, user location, and user nickname.

[0343] Step 709: The second delivery client displays the order acceptance interface for the second order;

[0344] For specific implementation details, please refer to step 520 above.

[0345] In some embodiments, the second rider corresponding to the second delivery client determines whether to accept the second delivery task.

[0346] Optionally, if the second rider confirms acceptance of the second delivery task, proceed to step 710 below.

[0347] Optionally, if the second rider confirms that they will not accept the second delivery task, the current step ends and / or step 707 is re-executed.

[0348] Step 710: The second rider confirms the second delivery task;

[0349] In some embodiments, the order acceptance interface for the second order displays an acceptance control for the second delivery task. The second rider confirms acceptance of the second delivery task by touching the acceptance control for the second delivery task.

[0350] Step 711: The second delivery client responds to the confirmation operation for the second delivery task and displays the delivery interface for the second order;

[0351] For specific implementation details, please refer to step 540 above.

[0352] Step 712: The second rider confirms delivery;

[0353] In some embodiments, a delivery confirmation control is displayed on the delivery screen of the second order. The second rider confirms the completion of the second order by touching the delivery confirmation control, that is, confirms that the target meal has been delivered to the user from the delivery point.

[0354] Step 713: The second delivery client responds to the confirmation operation of the pending delivery information for the second order and displays the delivery interface for the second order;

[0355] For specific implementation details, please refer to step 560 above.

[0356] Step 714: The server receives the confirmation delivery information for the second order.

[0357] The confirmation delivery information for the second order is used to indicate that the second delivery task has been completed.

[0358] It is worth noting that steps 713 and 714 are not ordered. In some embodiments, step 713 is executed before step 714. In some embodiments, step 714 is executed before step 713. In some embodiments, steps 713 and 714 are executed simultaneously.

[0359] Figure 36 This is a flowchart illustrating a food delivery method provided in an exemplary embodiment of this application. The method comprises, as... Figure 1 The client 120 and server 140 in the food delivery system 100 shown work together. The method includes:

[0360] Step 801: The server sends the first order to the merchant's client;

[0361] For specific implementation details, please refer to step 601 above.

[0362] Step 802: The merchant's client receives and confirms the first order;

[0363] For specific implementation details, please refer to step 602 above.

[0364] Step 803: Merchant confirms order acceptance;

[0365] For specific implementation details, please refer to step 603 above.

[0366] Step 804: The merchant client responds to the confirmation operation for the first order by sending an order confirmation message;

[0367] For a detailed implementation method, please refer to step 604 above.

[0368] Step 805: The server receives confirmation of order acceptance;

[0369] For specific implementation details, please refer to step 605 above.

[0370] Step 806: The server sends the first delivery task of the first order to the first delivery client;

[0371] For specific implementation details, please refer to step 606 above.

[0372] Step 807: The first delivery client receives the first delivery task;

[0373] For specific implementation details, please refer to step 607 above.

[0374] Step 808: The first delivery client displays the order acceptance interface for the first order;

[0375] For specific implementation details, please refer to step 608 above.

[0376] Step 809: The first rider confirms the first delivery task;

[0377] For specific implementation details, please refer to step 609 above.

[0378] Step 810: The first delivery client responds to the confirmation operation for the first delivery task and displays the delivery interface for the first order;

[0379] For specific implementation details, please refer to step 610 above.

[0380] Step 811: The first rider confirms delivery;

[0381] For specific implementation details, please refer to step 611 above.

[0382] Step 812: The first delivery client responds to the confirmation operation of the food delivery information for the first order and displays the delivery interface of the first order;

[0383] For specific implementation details, please refer to step 612 above.

[0384] Step 813: The server receives confirmation of delivery for the first order;

[0385] For specific implementation details, please refer to step 613 above.

[0386] Step 814: The server sends sales information for at least one meal item to multiple user clients located within the delivery area;

[0387] For specific implementation details, please refer to step 701 above.

[0388] It is worth noting that steps 813 and 814 are not ordered. In some embodiments, step 813 is executed before step 814. In some embodiments, step 814 is executed before step 813. In some embodiments, steps 813 and 814 are executed simultaneously.

[0389] Step 815: Multiple user clients receive sales information;

[0390] For specific implementation details, please refer to step 702 above.

[0391] Step 816: User places order;

[0392] For specific implementation details, please refer to step 703 above.

[0393] Step 817: At least one of the multiple user clients responds to the purchase operation for the target meal by sending a purchase confirmation message;

[0394] For specific implementation details, please refer to step 704 above.

[0395] Step 818: The server receives confirmation of the purchase information;

[0396] For specific implementation details, please refer to step 705 above.

[0397] Step 819: The server generates a second order for the target meal;

[0398] For a detailed implementation method, please refer to step 706 above.

[0399] Step 820: The server sends the second delivery task for the second order to the second delivery client;

[0400] For specific implementation details, please refer to step 707 above.

[0401] Step 821: The second delivery client receives and confirms the second delivery task;

[0402] For specific implementation details, please refer to step 708 above.

[0403] Step 822: The second delivery client displays the order acceptance interface for the second order;

[0404] For specific implementation details, please refer to step 709 above.

[0405] Step 823: The second rider confirms the second delivery task;

[0406] For specific implementation details, please refer to step 710 above.

[0407] Step 824: The second delivery client responds to the confirmation operation for the second delivery task and displays the delivery interface for the second order;

[0408] For specific implementation details, please refer to step 711 above.

[0409] Step 825: The second rider confirms delivery;

[0410] For specific implementation details, please refer to step 712 above.

[0411] Step 826: The second delivery client responds to the confirmation operation of the food delivery information for the second order and displays the delivery interface of the second order;

[0412] For specific implementation details, please refer to step 713 above.

[0413] Step 827: The server receives the confirmation delivery information for the second order.

[0414] For a detailed implementation method, please refer to step 714 above.

[0415] Figure 37 A schematic diagram of a food delivery device provided in an exemplary embodiment of this application is shown. The device includes:

[0416] The sending module 3710 is used to send the first order to the merchant client, and the recipient of the first order is the delivery point.

[0417] The sending module 3710 is also used to send a first delivery task of the first order to the first delivery client when the merchant client confirms the first order. The first delivery task is a task to deliver at least one meal item ordered in the first order to a delivery point.

[0418] The sending module 3710 is also used to send sales information for at least one food item to multiple user clients located in the delivery area.

[0419] The sending module 3710 is also used to send sales information for at least one food item to multiple user clients located within the delivery area at a target time.

[0420] The target time can be determined based on the confirmation time of the first order by the merchant client, or based on the confirmation time of the first delivery task by the first delivery client, or based on the completion time of the first delivery task.

[0421] The generation module 3720 is used to generate a second order for the target meal when at least one user client among multiple user clients orders at least one target meal, wherein the recipient of the second order is the target user corresponding to at least one user client.

[0422] The sending module 3710 is also used to send a second delivery task of the second order to the second delivery client. The second delivery task is to deliver the target meal to the location corresponding to the target user.

[0423] In some embodiments, the merchant clients include m, and the delivery points include n, where at least one of m and n is an integer greater than 1.

[0424] The generation module 3720 is also used to generate a first delivery task by merging at least two first orders corresponding to the m merchant clients after the m merchant clients have confirmed their respective first orders.

[0425] The sending module 3710 is also used to send the first delivery task of at least two first orders to the first delivery client.

[0426] The first delivery task is used to deliver at least one meal ordered by m merchant clients to n delivery points.

[0427] The generation module 3720 is also used to generate a first delivery task including n delivery sub-tasks after merging at least two first orders corresponding to m merchant clients and n delivery points being at least two delivery points, when m merchant clients confirm their respective first orders.

[0428] Among the n delivery subtasks, the j-th delivery subtask is used to deliver at least one meal ordered by x merchant clients to the j-th delivery point, where j is a positive integer less than or equal to n, and x is a positive integer less than or equal to m.

[0429] The generation module 3720 is also used to generate a first delivery task, which includes m pickup sub-tasks and n delivery sub-tasks, after merging at least two first orders corresponding to m merchant clients and n delivery points, when m merchant clients confirm their respective first orders and n delivery points are at least two delivery points.

[0430] Among the m subtasks for picking up food, the i-th subtask is used to pick up food from the i-th merchant's client, where i is a positive integer less than or equal to m.

[0431] In some embodiments, the m food pickup subtasks are generated according to the principle of shortest food pickup time; or, according to the principle of convenient route; and / or, the n delivery subtasks are generated according to the principle of shortest delivery time; or, according to the principle of convenient route.

[0432] In some embodiments, the delivery point is at least one of a mobile delivery box, a mobile food cart, or a robotic food cart.

[0433] The sending module 3710 is also configured to send a second delivery task of at least two second orders generated within the most recent time interval to the second delivery client at predetermined time intervals; and / or, if the number of orders of the at least two second orders generated reaches a quantity threshold, send a second delivery task of at least two second orders to the second delivery client.

[0434] At least two of the second orders correspond to the delivery point of the second delivery client.

[0435] In some embodiments, the device further includes:

[0436] The sorting module 3730 is used to sort the second delivery tasks of at least two second orders according to the delivery order.

[0437] The delivery order is determined by at least one of the following factors:

[0438] The location of the target user within the delivery area;

[0439] Prioritize the consumption of the target food items;

[0440] The ordering time for the target meal.

[0441] The sending module 3710 is also used to send at least one first order to each of the m merchant clients, and the at least one first order corresponding to the same merchant client corresponds to y delivery points out of n delivery points.

[0442] Where y takes the value of a positive integer less than or equal to n.

[0443] The generation module 3720 is also used to generate a pickup code corresponding to each of the at least one meal items ordered in the first order.

[0444] The sending module 3710 is also used to send a pickup code corresponding to each of the at least one meal items ordered in the first order to the first delivery client. The pickup code is used to associate the first order and the second order.

[0445] In some embodiments, the delivery point includes a compartment for storing each of at least one meal item ordered in the first order.

[0446] The sending module 3710 is also used to send the correspondence between the pickup code and the compartment corresponding to each of the at least one meal items ordered in the first order to the second delivery client.

[0447] The sending module 3710 is also used to send the pickup code corresponding to the target meal ordered in the second order to the second delivery client. The pickup code corresponding to the target meal is a subset of the pickup codes corresponding to each of the at least one meal ordered in the first order.

[0448] In some embodiments, the device further includes:

[0449] The receiving module 3740 is used to receive the confirmation delivery information of the first order.

[0450] The receiving module 3740 is also used to receive confirmation delivery information for the second order.

[0451] Figure 38 A schematic diagram of a food delivery device provided in an exemplary embodiment of this application is shown. The device includes:

[0452] Display module 3810 is used to display the order acceptance interface of the first order. The order acceptance interface of the first order displays the first delivery task. The first delivery task is to deliver at least one meal item ordered in the first order to the delivery point. The first order is an order for at least one meal item from the merchant corresponding to the merchant client. The recipient of the first order is the delivery point. The merchant client includes at least one, and the delivery point includes at least one.

[0453] The display module 3810 is also used to respond to the confirmation operation for the first delivery task by displaying the delivery interface of the first order, which displays the delivery information of the first order.

[0454] The display module 3810 is also used to display the delivery interface of the first order in response to the confirmation operation of the delivery information of the first order.

[0455] In this process, at least one food item is used to deliver from the delivery point to the target user in the second delivery task corresponding to the second order. The target user is located within the delivery area, which is the service area of ​​the delivery point. The second delivery task corresponds to the second delivery client, which is a different delivery client from the first delivery client.

[0456] In some embodiments, the merchant clients include m, and the delivery points include n, where at least one of m and n is an integer greater than 1.

[0457] The display module 3810 is also used to display the delivery interface of the first order within n delivery points in response to a confirmation operation for the first delivery task.

[0458] The first delivery task is used to deliver at least one meal ordered by m merchant clients to n delivery points.

[0459] In some embodiments, the n delivery points are at least two delivery points, and the first delivery task includes n delivery sub-tasks.

[0460] The display module 3810 is also used to display the delivery interface of the first order of the jth delivery point out of the n delivery points in response to a confirmation operation for the jth delivery subtask out of the n delivery subtasks.

[0461] The j-th delivery subtask is used to deliver at least one meal ordered by x merchant clients to the j-th delivery point, where j is a positive integer less than or equal to n and x is a positive integer less than or equal to m.

[0462] In some embodiments, the first delivery task further includes m sub-tasks for picking up meals.

[0463] The display module 3810 is also used to display the first waiting-to-pickup interface, which includes m sub-tasks for picking up food.

[0464] The display module 3810 is also used to display a second waiting-to-pickup interface in response to a confirmation operation for m food pickup sub-tasks. The second waiting-to-pickup interface displays n delivery sub-tasks.

[0465] The display module 3810 is also used to display the delivery interface of the first order at n delivery points in response to the confirmation operation for n delivery sub-tasks.

[0466] Among the m subtasks for picking up food, the i-th subtask is used to pick up food from the i-th merchant's client, where i is a positive integer less than or equal to m.

[0467] In some embodiments, the m food pickup subtasks are generated according to the principle of shortest food pickup time; or, according to the principle of convenient route; and / or, the n delivery subtasks are generated according to the principle of shortest delivery time; or, according to the principle of convenient route.

[0468] In some embodiments, the device further includes:

[0469] The receiving module 3820 is used to receive the pickup code corresponding to each of the at least one meal items ordered in the first order.

[0470] The sending module 3830 is used to send confirmation of delivery information for the first order.

[0471] Figure 39 A schematic diagram of a food delivery device provided in an exemplary embodiment of this application is shown. The device includes:

[0472] The sending module 3910 is used to send a first order to the merchant client. The first order is an order for at least one food item from the merchant corresponding to the merchant client. The recipient of the first order is the delivery point. The merchant client includes at least one, and the delivery point includes at least one.

[0473] The sending module 3910 is also used to send a first delivery task of the first order to the first delivery client when the merchant client confirms the first order. The first delivery task is a task to deliver at least one meal item ordered in the first order to a delivery point.

[0474] The receiving module 3920 is used to receive the confirmation delivery information of the first order, which indicates that the first delivery task has been completed.

[0475] In this process, at least one food item is used to deliver from the delivery point to the target user in the second delivery task corresponding to the second order. The target user is located within the delivery area, which is the service area of ​​the delivery point. The second delivery task corresponds to the second delivery client, which is a different delivery client from the first delivery client.

[0476] In some embodiments, the merchant clients include m, and the delivery points include n, where at least one of m and n is an integer greater than 1.

[0477] In some embodiments, the device further includes:

[0478] The generation module 3930 is used to combine at least two first orders from the m merchant clients to generate a first delivery task, provided that the m merchant clients have confirmed their respective first orders.

[0479] The sending module 3910 is also used to send the first delivery task of at least two first orders to the first delivery client.

[0480] The first delivery task is used to deliver at least one meal ordered by m merchant clients to n delivery points.

[0481] The generation module 3930 is also used to generate a first delivery task including n delivery sub-tasks after merging at least two first orders corresponding to m merchant clients and n delivery points being at least two delivery points, when m merchant clients confirm their respective first orders.

[0482] Among the n delivery subtasks, the j-th delivery subtask is used to deliver at least one meal ordered by x merchant clients to the j-th delivery point, where j is a positive integer less than or equal to n, and x is a positive integer less than or equal to m.

[0483] The generation module 3930 is also used to generate a first delivery task, which includes m pickup sub-tasks and n delivery sub-tasks, when m merchant clients accept their respective first orders and n delivery points are at least two delivery points.

[0484] Among the m subtasks for picking up food, the i-th subtask is used to pick up food from the i-th merchant's client, where i is a positive integer less than or equal to m.

[0485] In some embodiments, the m food pickup subtasks are generated according to the principle of shortest food pickup time; or, according to the principle of convenient route; and / or, the n delivery subtasks are generated according to the principle of shortest delivery time; or, according to the principle of convenient route.

[0486] In some embodiments, the merchant clients include m, and the delivery points include n, where at least one of m and n is an integer greater than 1.

[0487] The sending module 3910 is also used to send at least one first order to each of the m merchant clients, and the at least one first order corresponding to the same merchant client corresponds to y delivery points out of n delivery points.

[0488] Where y takes the value of a positive integer less than or equal to n.

[0489] The generation module 3930 is also used to generate a pickup code corresponding to each of the at least one meal items ordered in the first order.

[0490] The sending module 3910 is also used to send a pickup code corresponding to each of the at least one meal items ordered in the first order to the first delivery client.

[0491] Figure 40 A schematic diagram of a food delivery device provided in an exemplary embodiment of this application is shown. The device includes:

[0492] Display module 4010 is used to display the order acceptance interface of the second order. The order acceptance interface of the second order displays the second delivery task. The second delivery task is to deliver the target meal ordered in the second order from the delivery point to the location corresponding to the target user. The second order is an order for the target meal from at least one meal at the delivery point. The recipient of the second order is the target user, who is located within the delivery area, which is the service area of ​​the delivery point.

[0493] The display module 4010 is also used to respond to the confirmation operation for the second delivery task by displaying the delivery interface of the second order, which displays the delivery information of the second order.

[0494] The display module 4010 is also used to display the delivery interface of the second order in response to the confirmation operation of the delivery information for the second order.

[0495] The target meal is a subset of at least one meal, and at least one meal is delivered to the delivery point in advance by the first delivery task corresponding to the first order. The first delivery task corresponds to the first delivery client, and the first delivery client and the second delivery client are different delivery clients.

[0496] In some embodiments, the device further includes:

[0497] The receiving module 4020 is used to receive at least two second delivery tasks for second orders at predetermined time intervals.

[0498] The display module 4010 is also configured to display the delivery interface of the second order in response to a confirmation operation for at least two second orders within the most recent time interval.

[0499] At least two of the second orders correspond to the delivery point of the second delivery client.

[0500] The receiving module 4020 is also used to receive a second delivery task for at least two second orders when the number of orders for at least two second orders reaches a quantity threshold.

[0501] The display module 4010 is also configured to display the delivery interface of the second order in response to a confirmation operation for at least two second orders whose order quantity has reached a quantity threshold.

[0502] At least two of the second orders correspond to the delivery point of the second delivery client.

[0503] The receiving module 4020 is also used to receive the delivery sequence of the second delivery tasks of at least two second orders.

[0504] The delivery order is determined by at least one of the following factors:

[0505] The location of the target user within the delivery area;

[0506] Prioritize the consumption of the target food items;

[0507] The ordering time for the target meal.

[0508] In some embodiments, the location of the target user within the delivery area includes first floor information.

[0509] The receiving module 4020 is also used to receive the delivery sequence of the second delivery tasks of at least two second orders generated based on the first floor information.

[0510] In some embodiments, the device further includes:

[0511] The acquisition module 4030 is used to acquire the second floor information of the second delivery client within the delivery area.

[0512] The receiving module 4020 is also used to receive the delivery sequence of the second delivery tasks of at least two second orders generated based on the first floor information and the second floor information.

[0513] The receiving module 4020 is also used to receive the pickup code corresponding to the target meal ordered in the second order, and the pickup code corresponding to the target meal is a subset of the pickup codes.

[0514] In some embodiments, the delivery point includes a compartment for storing each of at least one meal item ordered in the first order.

[0515] The receiving module 4020 is also used to receive the correspondence between the pickup code and the compartment corresponding to each of the at least one meal items ordered in the first order.

[0516] In some embodiments, the device further includes:

[0517] The sending module 4040 is used to send confirmation delivery information for the second order.

[0518] Figure 41 A schematic diagram of a food delivery device provided in an exemplary embodiment of this application is shown. The device includes:

[0519] Sending module 4110 is used to send sales information for at least one type of meal to a user client located in the delivery area.

[0520] The generation module 4120 is used to generate a second order for the target meal when a user client orders at least one meal item. The second order is an order for the target meal item from at least one meal item at a delivery point, and the recipient of the second order is the target user corresponding to at least one user client.

[0521] The sending module 4110 is also used to send a second delivery task of the second order to the second delivery client. The second delivery task is to deliver the target meal from the delivery point to the location corresponding to the target user.

[0522] The receiving module 4130 is used to receive the confirmation delivery information of the second order, which is used to indicate that the second delivery task has been completed.

[0523] The target meal is a subset of at least one meal, and at least one meal is delivered to the delivery point in advance by the first delivery task corresponding to the first order. The first delivery task corresponds to the first delivery client, and the first delivery client and the second delivery client are different delivery clients.

[0524] The sending module 4110 is also configured to send a second delivery task for at least two second orders generated within the most recent time interval to the second delivery client at predetermined time intervals; and / or, if the number of orders for at least two second orders generated reaches a quantity threshold, send a second delivery task for at least two second orders to the second delivery client.

[0525] At least two of the second orders correspond to the delivery point of the second delivery client.

[0526] In some embodiments, the device further includes:

[0527] The sorting module 4140 is used to sort the second delivery tasks of at least two second orders according to the delivery order.

[0528] The delivery order is determined by at least one of the following factors:

[0529] The location of the target user within the delivery area;

[0530] Prioritize the consumption of the target food items;

[0531] The ordering time for the target meal.

[0532] In some embodiments, the location of the target user within the delivery area includes first floor information.

[0533] The sending module 4110 is also used to send the delivery sequence generated based on the first floor information to the second delivery client.

[0534] The receiving module 4130 is also used to receive second floor information within the delivery area sent by the second delivery client.

[0535] The sending module 4110 is also used to send the delivery sequence generated based on the first floor information and the second floor information to the second delivery client.

[0536] The sending module 4110 is also used to send the pickup code corresponding to the target meal ordered in the second order to the second delivery client. The pickup code corresponding to the target meal is a subset of the pickup codes.

[0537] In some embodiments, the delivery point includes a compartment for storing each of at least one meal item ordered in the first order.

[0538] The sending module 4110 is also used to send the correspondence between the pickup code and the compartment corresponding to each of the at least one meal ordered in the first order to the second delivery client.

[0539] Figure 42 This illustration shows a structural block diagram of a computer device 4200 provided in an exemplary embodiment of this application. The computer device 4200 may be a portable mobile terminal, such as a smartphone, tablet computer, or a Moving Picture Experts Group Audio Layer III (MP3) or Moving Picture Experts Group Audio Layer IV (MP4) player. The computer device 4200 may also be referred to as a user device, portable terminal, or other names.

[0540] Typically, computer device 4200 includes a processor 4201 and a memory 4202.

[0541] Processor 4201 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 4201 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). Processor 4201 may also include a main processor and a coprocessor. The main processor, also known as the Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 4201 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 4201 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0542] The memory 4202 may include one or more computer-readable storage media, which may be tangible and non-transitory. The memory 4202 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 4202 is used to store at least one instruction, which is executed by the processor 4201 to implement the gift-giving method based on a live-streaming room provided in this embodiment.

[0543] In some embodiments, the computer device 4200 may also optionally include: a peripheral device interface 4203 and at least one peripheral device. Specifically, the peripheral device includes at least one of: a radio frequency circuit 4204, a touch display screen 4205, a camera 4206, an audio circuit 4207, and a power supply 4208.

[0544] Peripheral interface 4203 can be used to connect at least one input / output (I / O) related peripheral device to processor 4201 and memory 4202. In some embodiments, processor 4201, memory 4202 and peripheral interface 4203 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 4201, memory 4202 and peripheral interface 4203 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0545] The radio frequency (RF) circuit 4204 is used to receive and transmit radio frequency (RF) signals, also known as electromagnetic signals. The RF circuit 4204 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 4204 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 4204 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 4204 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or Wireless Fidelity (Wi-Fi) networks. In some embodiments, the RF circuit 4204 may also include circuitry related to Near Field Communication (NFC), which is not limited in this application.

[0546] The touch display screen 4205 is used to display a user interface (UI). This UI may include graphics, text, icons, videos, and any combination thereof. The touch display screen 4205 also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to the processor 4201 for processing. The touch display screen 4205 is used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one touch display screen 4205, located on the front panel of the computer device 4200; in other embodiments, there may be at least two touch display screens, respectively located on different surfaces of the computer device 4200 or in a folded design; in some embodiments, the touch display screen 4205 may be a flexible display screen, located on a curved or folded surface of the computer device 4200. Furthermore, the touch display screen 4205 may be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The touch display screen 4205 may be made of materials such as Liquid Crystal Display (LCD) or Organic Light-Emitting Diode (OLED).

[0547] Camera 4206 is used to capture images or videos. Optionally, camera 4206 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is used for video calls or selfies, and the rear-facing camera is used for taking photos or videos. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, and a wide-angle camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, and panoramic shooting and virtual reality (VR) shooting by fusion of the main camera and the wide-angle camera. In some embodiments, camera 4206 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash is a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0548] Audio circuitry 4207 provides an audio interface between the user and computer device 4200. Audio circuitry 4207 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting the sound waves into electrical signals that are input to processor 4201 for processing, or input to radio frequency circuitry 4204 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each located at a different location within computer device 4200. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from processor 4201 or radio frequency circuitry 4204 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, audio circuitry 4207 may also include a headphone jack.

[0549] Power supply 4208 is used to supply power to the various components in computer device 4200. Power supply 4208 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 4208 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged via a wired line, and a wireless rechargeable battery is a battery that is charged via a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0550] In some embodiments, the computer device 4200 further includes one or more sensors 4209. The one or more sensors 4209 include, but are not limited to, an accelerometer 4210, a gyroscope 4211, a pressure sensor 4212, an optical sensor 4213, and a proximity sensor 4214.

[0551] Accelerometer 4210 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by computer device 4200. For example, accelerometer 4210 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 4201 can control touchscreen display 4205 to display the user interface in landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 4210. Accelerometer 4210 can also be used for games or for acquiring user motion data.

[0552] The gyroscope sensor 4211 can detect the orientation and rotation angle of the computer device 4200. The gyroscope sensor 4211 can work in conjunction with the accelerometer sensor 4210 to collect 3D motion data from the user on the computer device 4200. Based on the data collected by the gyroscope sensor 4211, the processor 4201 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0553] The pressure sensor 4212 can be disposed on the side bezel of the computer device 4200 and / or on the lower layer of the touch display screen 4205. When the pressure sensor 4212 is disposed on the side bezel of the computer device 4200, it can detect the user's grip signal on the computer device 4200 and perform left / right hand recognition or quick operation based on the grip signal. When the pressure sensor 4212 is disposed on the lower layer of the touch display screen 4205, it can control the operable controls on the UI interface based on the user's pressure operation on the touch display screen 4205. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0554] Optical sensor 4213 is used to collect ambient light intensity. In one embodiment, processor 4201 can control the display brightness of touch display screen 4205 based on the ambient light intensity collected by optical sensor 4213. Specifically, when the ambient light intensity is high, the display brightness of touch display screen 4205 is increased; when the ambient light intensity is low, the display brightness of touch display screen 4205 is decreased. In another embodiment, processor 4201 can also dynamically adjust the shooting parameters of camera assembly 4206 based on the ambient light intensity collected by optical sensor 4213.

[0555] The proximity sensor 4214, also known as a distance sensor, is typically located on the front of the computer device 4200. The proximity sensor 4214 is used to detect the distance between the user and the front of the computer device 4200. In one embodiment, when the proximity sensor 4214 detects that the distance between the user and the front of the computer device 4200 is gradually decreasing, the processor 4201 controls the touch display screen 4205 to switch from a screen-on state to a screen-off state; when the proximity sensor 4214 detects that the distance between the user and the front of the computer device 4200 is gradually increasing, the processor 4201 controls the touch display screen 4205 to switch from a screen-off state to a screen-on state.

[0556] Those skilled in the art will understand that Figure 42 The structure shown does not constitute a limitation on the computer device 4200, and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0557] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one program, which is loaded and executed by the processor to implement the food delivery method provided in the above-described method embodiments.

[0558] This application also provides a computer storage medium, which stores at least one program. The at least one program is loaded and executed by a processor to implement the food delivery method provided in the above-described method embodiments.

[0559] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. The computer program is read from and executed by a processor of a computer device, causing the computer device to perform the food delivery method provided in the above-described method embodiments.

[0560] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0561] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0562] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent switching, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for food delivery, characterized in that, The method is executed by a server, a merchant client, a user client, a first delivery client, and a second delivery client, and the method includes: The merchant client obtains the production task for the first order, the delivery address of the first order is the delivery point and it is in a pre-sale state; The first delivery client obtains a first delivery task for the first order, wherein the first delivery task is to deliver at least one meal item ordered in the first order to the delivery point; The server sends the sales information of at least one food item to multiple user clients located within the delivery area, where the delivery area is the service area of ​​the delivery point. The multiple user clients receive the sales information for at least one food item; When at least one of the multiple user clients orders the target dish from the at least one meal, the server generates a second order for the target dish, wherein the recipient of the second order is the target user corresponding to the at least one user client. The server sends a second delivery task for the second order to the second delivery client. The second delivery task is to deliver the target meal to the location corresponding to the target user. The second delivery client receives and confirms the second delivery task; The target meal corresponding to the second order is a subset of at least one meal ordered in the first order, and the target meal corresponds to the same pickup code in both the first order and the second order.

2. The method according to claim 1, characterized in that, The merchant clients include m, and the delivery areas include n, where at least one of m and n is an integer greater than 1; The step of sending the first delivery task of the first order to the first delivery client when the merchant client confirms the first order includes: If m merchant clients confirm their respective first orders, the first delivery task is generated by merging at least two first orders from the m merchant clients. Send the first delivery task of the at least two first orders to the first delivery client; The first delivery task is used to deliver at least one meal ordered by the m merchant clients to n delivery areas.

3. The method according to claim 2, characterized in that, When m merchant clients confirm their respective first orders, the step of merging at least two first orders from the m merchant clients to generate the first delivery task includes: If the m merchant clients confirm their respective first orders and the n delivery areas are at least two delivery areas, the at least two first orders corresponding to the m merchant clients are combined to generate a first delivery task including m pickup sub-tasks and the n delivery sub-tasks; Wherein, the i-th subtask among the m subtasks is used to pick up food from the i-th merchant client, and the j-th subtask among the n subtasks is used to deliver at least one food item ordered by x merchant clients to the j-th delivery point, where i is a positive integer less than or equal to m, j is a positive integer less than or equal to n, and x is a positive integer less than or equal to m.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The server sends a pickup code to the first delivery client for each of the at least one meal items ordered in the first order. The first delivery client receives the pickup code.

5. The method according to any one of claims 1 to 3, characterized in that, The delivery point includes compartments for storing each of the at least one meal item ordered in the first order; The method further includes: The server sends to the second delivery client the corresponding pickup code and the corresponding compartment for each of the at least one meal items ordered in the first order; The second delivery client receives the correspondence.

6. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The server sends the pickup code corresponding to the target meal ordered in the second order to the second delivery client; The second delivery client receives the pickup code corresponding to the target meal, which is a subset of the pickup codes corresponding to each of the at least one meal ordered in the first order.

7. The method according to any one of claims 1 to 3, characterized in that, Sending the sales information of at least one meal item to multiple user clients located within the delivery area includes: At a target time, the sales information of at least one meal item is sent to the multiple user clients located within the delivery area; The target time is determined based on the confirmation time of the first order by the merchant client, or the target time is determined based on the confirmation time of the first delivery task by the first delivery client, or the target time is determined based on the completion time of the first delivery task.

8. The method according to any one of claims 1 to 3, characterized in that, The second delivery task of sending the second order to the second delivery client includes: At predetermined time intervals, send a second delivery task to the second delivery client for at least two second orders generated within the most recent time interval; And / or, If the number of orders in the at least two second orders reaches a certain threshold, a second delivery task for the at least two second orders is sent to the second delivery client. The at least two second orders each correspond to the delivery area corresponding to the second delivery client.

9. The method according to claim 8, characterized in that, The method further includes: The second delivery tasks of the at least two second orders are sorted according to the delivery order; wherein the delivery order is determined by at least one of the following factors: The location of the target user within the delivery area; The consumption priority of the target meal; The ordering time for the target meal.

10. The method according to any one of claims 1 to 3, characterized in that, The delivery point is at least one of a mobile delivery box, a mobile food cart, or a robot food cart.

11. A food delivery system, characterized in that, The system includes a server, a merchant client, a user client, a first delivery client, and a second delivery client; The merchant client is used to obtain the production task of the first order, the delivery address of the first order is the delivery point and it is in a pre-sale state; The first delivery client is used to obtain a first delivery task for the first order, wherein the first delivery task is to deliver at least one meal item ordered in the first order to the delivery point; The server is used to send sales information of at least one food item to multiple user clients located within the delivery area, where the delivery area is the service area of ​​the delivery point. The plurality of user clients are used to receive sales information for at least one food item; The server is configured to generate a second order for the target meal when at least one of the plurality of user clients orders the target meal from the at least one meal menu item, wherein the recipient of the second order is the target user corresponding to the at least one user client; The server is used to send a second delivery task for the second order to the second delivery client. The second delivery task is to deliver the target meal to the location corresponding to the target user. The second delivery client is used to receive and confirm the second delivery task; The target meal corresponding to the second order is a subset of at least one meal ordered in the first order, and the target meal corresponds to the same pickup code in both the first order and the second order.

12. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one program, the at least one program being loaded and executed by the processor to implement the steps performed by the server or any client in the food delivery method as described in any one of claims 1 to 10.

13. A computer storage medium, characterized in that, The computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the steps performed by the server or any client in the food delivery method as described in any one of claims 1 to 10.

14. A computer program product, characterized in that, The computer program product includes a computer program stored in a computer-readable storage medium; the computer program is read from and executed by a processor of a computer device, causing the computer device to perform the steps performed by the server or any client in the food delivery method as described in any one of claims 1 to 10.

Images