Delivery robot order combining processing method, electronic equipment and readable storage medium
By detecting orders from the same user and order-publishing orders, the problem of waste of resources and low timeliness caused by the synchronization of third-party order information is solved, and efficient order delivery is achieved.
Patent Information
- Application Number
- CN202411906295.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-23
- Publication Date
- 2025-05-02
AI Technical Summary
In the robot delivery order scenario, due to the synchronization of third-party order information, two orders of the same user may need to be delivered in two times, resulting in waste of resources and low delivery time.
By displaying the delivery robot's delivery order selection page, detect the same third-party orders as the target delivery user of the selected order, and obtain the prepared time overlap between the two. If the degree of overlap is greater than the preset threshold, the third-party order will be grouped with the order list of this shift.
It realizes the same delivery of two orders from the same user, reducing the waste of delivery robot delivery resources and improving delivery timeliness.
Smart Images

Figure CN119919028A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of robotics technology, and in particular to a delivery robot order processing method, an electronic device, and a computer-readable storage medium. Background Art
[0002] As robot technology matures and consumers’ demand for automated services increases, robots are being used in more and more scenarios, such as hotels, retail, warehousing and logistics, etc. Order delivery is an important application of robots. Currently, robot delivery order scenarios include two processes: picking and delivering goods. First, the picker selects the corresponding order for the robot to pick the goods, and then the robot completes the delivery process of the corresponding order.
[0003] However, the inventors of the present application discovered during the actual research and development process that due to the synchronization problem of third-party order information, the delivery personnel may not be able to know that the same user has two orders when delivering goods, which may result in the two orders of the same user needing to be delivered twice. For example, the same user may have a hotel order and a takeaway order, and the user's takeaway order cannot be known before the takeaway arrives. If the takeaway order arrives just after the delivery robot enters the delivery state, the two orders of the same user need to be delivered twice, which will result in a waste of resources and low delivery efficiency. Summary of the invention
[0004] The present application provides a delivery robot order grouping processing method, an electronic device and a computer-readable storage medium, which can realize the delivery of two orders from the same user together, reduce the waste of delivery robot delivery resources, and improve delivery timeliness to a certain extent.
[0005] In a first aspect, the present application provides a delivery robot order processing method, the method comprising:
[0006] Displaying a delivery order selection page for the delivery robot, wherein the delivery order selection page includes a list of orders to be delivered in the robot's delivery area;
[0007] Based on the order selection operation of the to-be-delivered order list, adding the selected order of the order selection operation to the order list of the delivery robot for this shift;
[0008] Detecting third-party orders that are the same as the target delivery user of the selected order;
[0009] Obtain the degree of overlap in preparation time between the third-party order and the order list of the current shift;
[0010] If the overlap of the preparation time is greater than a preset overlap threshold, the third-party order will be combined with the order list of this shift.
[0011] In a second aspect, the present application also provides an electronic device, comprising a processor and a memory, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it executes any one of the delivery robot order processing methods provided in the present application.
[0012] In a third aspect, the present application also provides a computer-readable storage medium on which a computer program is stored, and the computer program is loaded by a processor to execute the delivery robot order processing method.
[0013] In the present application, by displaying a distribution order selection page containing a list of orders to be delivered in the robot delivery area, the selected order of the order selection operation is added to the order list of this shift of the delivery robot. On the one hand, by detecting a third-party order with the same target delivery user as the selected order, it is determined whether there are two or more orders for the same user, and then the two orders of the same user can be delivered together, avoiding the problem that the third-party order information cannot be synchronized when the third-party order has not arrived; on the other hand, by obtaining the overlap of the preparation time between the third-party order and the order list of this shift, when the overlap of the preparation time is greater than the preset overlap threshold, the third-party order and the order list of this shift are combined, so that the combination of orders can be performed only when the preparation time of the third-party order is close to the preparation time of the order list of this shift, avoiding the problem that the timeliness of the order list of this shift is reduced after the combination of orders due to the late arrival time of the third-party order, thereby ensuring the timeliness of the order list of this shift; thereby reducing the waste of delivery resources of the delivery robot and improving the delivery timeliness to a certain extent. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.
[0015] Figure 1 is a schematic block diagram of the structure of an electronic device provided in an embodiment of the present application;
[0016] Figure 2 This is a flow chart of a method for processing a delivery robot order combination provided in an embodiment of the present application;
[0017] Figure 3 This is a schematic diagram of a scene of a distribution order selection page provided in an embodiment of the present application;
[0018] Figure 4 This is a schematic diagram of a scenario of the authorization page of the regional order placement program in an embodiment of the present application;
[0019] Figure 5 This is a schematic diagram of a scenario of an authorization page of a third-party program in an embodiment of the present application;
[0020] Figure 6 It is a flowchart of an embodiment of step 203 in the embodiment of the present application. DETAILED DESCRIPTION
[0021] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.
[0022] The flowcharts shown in the accompanying drawings are only examples and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may also be decomposed, combined or partially merged, so the actual execution order may change according to actual conditions.
[0023] In the description of the embodiments of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.
[0024] In order to enable any person skilled in the art to implement and use the present application, the following description is provided. In the following description, details are listed for the purpose of explanation. It should be understood that those of ordinary skill in the art can recognize that the present application can also be implemented without using these specific details. In other examples, the known process will not be elaborated in detail to avoid unnecessary details that make the description of the present application embodiment obscure. Therefore, the present application is not intended to be limited to the embodiments shown, but is consistent with the widest range of principles and features disclosed in accordance with the embodiments of the present application.
[0025] The embodiment of the present application provides a delivery robot order processing method, an electronic device and a computer-readable storage medium. The electronic device can be a delivery robot, a mobile phone, a computer, etc.
[0026] Some embodiments of the present application are described in detail below in conjunction with the accompanying drawings. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.
[0027] Figure 1 It is a schematic block diagram of the structure of an electronic device provided in an embodiment of the present application.
[0028] like Figure 1 As shown, the electronic device 100 includes a processor 101 and a memory 102, and the processor 101 and the memory 102 are connected via a bus 103, such as a PCIe (Peripheral Component Interconnect Express) bus.
[0029] Specifically, the processor 101 is used to provide computing and control capabilities to support the operation of the entire electronic device 100. The processor 101 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0030] Specifically, the memory 102 may be a Flash chip, a read-only memory (ROM) disk, an optical disk, a USB flash drive, or a mobile hard disk.
[0031] Those skilled in the art will understand that Figure 1 The structure shown in the figure is merely a block diagram of a partial structure related to the embodiment scheme of the present application, and does not constitute a limitation on the electronic device to which the embodiment scheme of the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.
[0032] The processor 101 is used to run the computer program stored in the memory 102, and implement any one of the delivery robot order grouping processing methods provided in the embodiments of the present application when executing the computer program. For example, the processor 101 is used to run the computer program stored in the memory 102, and can implement the following steps when executing the computer program:
[0033] Displaying a delivery order selection page for the delivery robot, wherein the delivery order selection page includes a list of orders to be delivered in the robot's delivery area;
[0034] Based on the order selection operation of the to-be-delivered order list, adding the selected order of the order selection operation to the order list of the delivery robot for this shift;
[0035] Detecting third-party orders that are the same as the target delivery user of the selected order;
[0036] Obtain the degree of overlap in preparation time between the third-party order and the order list of the current shift;
[0037] If the overlap of the preparation time is greater than a preset overlap threshold, the third-party order will be combined with the order list of this shift.
[0038] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0039] After the target delivery user places an order through the regional ordering program of the robot delivery area, an authorization page is displayed through the regional ordering program, wherein the authorization page includes an authorization consent control;
[0040] In response to a touch operation on the authorization consent control, sending an order binding request for the target delivery user to a third-party program through the regional order placement program;
[0041] When receiving the binding consent information fed back by the third-party program, adding the target delivery user to a preset user maintenance list;
[0042] If the target delivery user exists in the user maintenance list, sending an order query request to the third-party program based on the user information of the target delivery user;
[0043] An order query result fed back by the third-party program based on the order query request is received, wherein the order query result includes third-party orders that are the same as a target delivery user of the selected order.
[0044] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0045] Obtaining an estimated preparation time for the selected order;
[0046] Obtain an estimated delivery time for the third-party order;
[0047] The degree of overlap of the preparation time is determined based on a time difference between the estimated preparation time and the estimated delivery time.
[0048] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0049] If the target delivery user exists in the preset user maintenance list, sending an order query request to the third-party program based on the user information of the target delivery user;
[0050] Receive an order query result fed back by the third-party program based on the order query request, wherein the order query result includes an estimated delivery time of the third-party order.
[0051] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0052] Acquire first configuration information of the selected order, wherein the first configuration information includes at least one of order type, configuration date information, configuration season information, configuration time period information, and configuration location information;
[0053] Acquire second configuration information of each historical order in the delivery area of the robot;
[0054] Performing a prediction based on the first allocation information and the second allocation information of each of the historical orders to obtain an estimated allocation time for the selected order;
[0055] Based on the order time of the selected order and the estimated preparation time, the estimated preparation time of the selected order is determined.
[0056] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0057] Acquire the similarity between the second configuration information of each historical order and the first configuration information as the information similarity of each historical order;
[0058] From the historical orders, find a target historical order whose information similarity is greater than a preset similarity threshold;
[0059] Based on the preparation time of the target historical orders and the information similarity of the target historical orders, an estimated preparation time of the selected order is determined.
[0060] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0061] Based on a preset signature algorithm, the user information and request time of the target delivery user are signed to obtain a first signature value;
[0062] Generate an order query request based on the user information of the target delivery user, the request time and the first signature value;
[0063] Sending the order query request to the third-party program;
[0064] The receiving the order fed back by the third-party program based on the order query request as a third-party order with the same target delivery user as the selected order includes:
[0065] When the interval duration between the request time carried in the order query request and the current time is less than a preset interval duration threshold, and the first signature value carried in the order query request is consistent with the second signature value, the order fed back by the third-party program based on the order query request is received as a third-party order with the same target delivery user as the selected order, wherein the second signature value is signed by the third-party program based on the user information and request time carried in the order query request.
[0066] In some embodiments, the processor 101 is used to run a computer program stored in the memory 102, and when executing the computer program, the following steps may be implemented:
[0067] Displaying a grid configuration page of the delivery robot;
[0068] If the third-party order is combined with the order list of the current shift, in response to the slot selection operation for the selected order, the selected slot of the slot selection operation is set as the slot of the selected order and the slot of the third-party order.
[0069] It should be noted that technicians in the relevant field can clearly understand that for the convenience and conciseness of description, the specific working process of the electronic device described above can refer to the corresponding process in the following delivery robot order processing method embodiment, and will not be repeated here.
[0070] The executor of the method for processing an order by a delivery robot in the embodiment of the present application may be an electronic device, which may specifically be the front end, back end or delivery robot in the distribution system. Hereinafter, the method for processing an order by a delivery robot provided in the embodiment of the present application will be described in detail by taking the back end as the executor of the method for processing an order by a delivery robot as an example. For the sake of simplicity and ease of description, the executor will be omitted in the subsequent method embodiments.
[0071] See also Figure 2 , Figure 2201 to 205, wherein:
[0072] 201. Display a delivery order selection page for the delivery robot, wherein the delivery order selection page includes a list of to-be-delivered orders in the robot's delivery area.
[0073] In order to better understand this embodiment, the delivery process of the delivery robot is described below by taking a delivery system as an example. The delivery system may include a front end, a back end, at least one delivery robot, and an order end (such as a regional order placement program), as follows:
[0074] 1. Order: After the user places an order through the order end (such as regional order program, third-party program), the new order will be sent to the backend.
[0075] 2. Order scheduling information generation: The backend adds the new order as an unscheduled order to the order pool to be scheduled, and generates a pickup code for the unscheduled order. Alternatively, after the third-party order is delivered to the robot delivery area (such as when a takeaway order is delivered to the hotel lobby), the delivery staff enters the order information of the third delivery order through the front end, and the front end sends the order information of the third delivery order to the back end, which then adds the third delivery order as an unscheduled order to the order pool to be scheduled.
[0076] 3. Enter the delivery page: The delivery personnel scan the QR code on the delivery robot through the front end (such as mobile phone, bar gun, etc.) to enter the delivery robot's delivery page, and the front end requests the current delivery robot information from the back end. On the delivery page provided by the front end, the delivery personnel can view the delivery robot information (such as the abnormal status of the delivery robot, delivery status, order status, etc.), complete the delivery robot delivery process (such as selecting delivery orders and delivery slots for the delivery robot), etc.
[0077] 4. The backend queries the current delivery robot information (including but not limited to order status, delivery robot status, etc.) and returns it to the frontend.
[0078] 5. After the delivery personnel sees the current delivery robot information through the front end, they choose whether to deliver goods to the current delivery robot according to the situation. When it is necessary to deliver goods to the current delivery robot, the delivery operation process is carried out (including but not limited to selecting delivery orders and delivery slots); at this time, the front end will respond to the delivery personnel's delivery operation and send a delivery request to the back end.
[0079] 6. Picking: After the backend receives the picking request from the frontend, it sends a picking instruction to the current delivery robot, so that the current delivery robot can start the picking task (including but not limited to opening the hatch, waiting for picking, closing the hatch, broadcasting the door opening and closing voice, etc.).
[0080] 7. Delivery: After the distribution is completed, the distribution staff triggers the delivery operation on the front end (such as clicking the "Delivery" button on the front end); at this time, the front end sends a delivery request to the back end.
[0081] 8. After receiving the delivery request, the backend sends a delivery instruction to the current delivery robot, so that the current delivery robot enters the delivery task.
[0082] 9. The current delivery robot enters the delivery task and returns the delivery result to the backend; the backend returns the delivery result to the frontend.
[0083] 10. After the user triggers the pickup operation through the order side (such as the regional ordering program) (such as the user clicks the "open door to pick up" button in the regional ordering program, enters the pickup code, etc.), the order side (such as the regional ordering program) sends a pickup request to the backend; after receiving the pickup request, the backend sends a pickup instruction to the current delivery robot, so that the current delivery robot opens the hatch and completes the pickup.
[0084] Among them, the robot delivery area can be buildings, such as hotels, office buildings, etc.
[0085] In the embodiment of the present application, the distribution system includes but is not limited to the front end, the back end, the delivery robot and the order end (such as the regional ordering program, the third-party program).
[0086] In some embodiments, the delivery robot of the distribution system can display the distribution order selection page of the delivery robot. For example, the "distribution" button on the delivery robot can be clicked to jump the display page of the delivery robot to the distribution order selection page. At this time, the delivery robot can send an order query request to the backend. After the backend receives the order query request sent by the delivery robot, the backend sends the unscheduled orders in the order pool to be scheduled to the delivery robot; after the delivery robot receives the unscheduled orders in the order pool to be scheduled, based on the unscheduled orders in the order pool to be scheduled, the delivery robot displays the distribution order selection page containing the list of orders to be delivered. Among them, each order in the list of orders to be delivered is an unscheduled order in the order pool to be scheduled.
[0087] In some embodiments, the delivery robot's distribution order selection page can be displayed through the front end of the distribution system. For example, the distribution personnel scan the QR code labeled on the delivery robot through the front end (such as a mobile phone, a bar gun, etc.) to enter the distribution page of the delivery robot, and can click the "distribution" button on the distribution page, so that the display page of the front end jumps to the distribution order selection page. At this time, the front end can send an order query request to the back end. After the back end receives the order query request sent by the front end, the back end sends the unscheduled orders of the order pool to be scheduled to the front end; after the front end receives the unscheduled orders of the order pool to be scheduled, based on the unscheduled orders of the order pool to be scheduled, the distribution order selection page containing the list of orders to be delivered is displayed on the front end. Among them, each order in the list of orders to be delivered is an unscheduled order in the order pool to be scheduled.
[0088] 202. Based on the order selection operation of the to-be-delivered order list, add the selected order of the order selection operation to the order list of the delivery robot for this shift.
[0089] In some embodiments, the delivery robot of the distribution system can display the delivery robot's order selection page. At this time, the delivery robot sends the selected order of the order selection operation to the backend based on the order selection operation for the list of orders to be delivered. The backend adds the selected order to the delivery robot's order list for this shift and updates the unscheduled orders in the order pool to be dispatched. For example, Figure 3 As shown, Figure 3 1 is a schematic diagram of a scene of a delivery order selection page provided in an embodiment of the present application. The delivery personnel scans the QR code on the label of the delivery robot through the front end to enter the delivery robot's delivery page, and clicks the "delivery" button on the delivery page to jump to the following figure: Figure 3 The distribution order selection page is shown; then, select Order ID1, Order ID2, Order ID3, Order ID4, Order ID5, Order ID6 and Order ID7 from the list of orders to be delivered displayed on the distribution order selection page, and click "Confirm Selection"; at this time, the delivery robot can send Order ID1, Order ID2, Order ID3, Order ID4, Order ID5, Order ID6 and Order ID7 to the backend, and the backend will add the selected orders to the delivery robot's order list for this shift, and remove the selected orders from the pool of orders to be dispatched to avoid the problem of repeated allocation of orders.
[0090] In some embodiments, the front end of the delivery system may display a delivery robot's order selection page. At this time, the front end sends the selected order of the order selection operation to the back end based on the order selection operation for the list of orders to be delivered. The back end adds the selected order to the delivery robot's order list for this shift and updates the unscheduled orders in the order pool to be dispatched.
[0091] 203. Detect a third-party order whose target delivery user is the same as that of the selected order.
[0092] Among them, the delivery user refers to the recipient of the order.
[0093] Among them, the target delivery user refers to the delivery user who selects the order.
[0094] Among them, the regional ordering program refers to the ordering program set up for the robot delivery area, such as the hotel user mini program.
[0095] Among them, third-party programs refer to ordering programs other than regional ordering programs, such as takeaway programs and express delivery programs.
[0096] Among them, third-party orders refer to orders triggered by third-party programs, such as takeout orders placed by users in the takeout mini program.
[0097] There are many ways to implement step 203, which include, for example:
[0098] (1) In some embodiments, a third-party program is used to authorize the query of third-party orders that are the same as the target delivery user of the selected order. For example, please refer to Figure 5 In order to facilitate the detection of whether there is a third-party order that is the same as the target delivery user of the selected order, a user maintenance list is preset to maintain the delivery users who have been authorized to query the orders of the third-party program. At this time, the delivery robot order processing method also includes: after the target delivery user places an order through the regional ordering program of the robot delivery area, an authorization page is displayed through the regional ordering program, wherein the authorization page includes an authorization consent control; in response to a touch operation on the authorization consent control, an order binding request for the target delivery user is sent to the third-party program through the regional ordering program; upon receiving the binding consent information fed back by the third-party program, the target delivery user is added to the preset user maintenance list. For example, please refer to Figure 4 and Figure 5 For example, the robot delivery area is a hotel, the regional ordering program is the hotel user applet, and the third-party program is the food delivery applet. After the target delivery user places an order (such as a food delivery order) through the hotel user applet, the hotel user applet can be redirected to the authorization page, where the authorization consent control can be displayed, such as Figure 4 As shown in (a) in the figure; after the target delivery user clicks the authorization consent control on the authorization page of the hotel user applet, he will be redirected to the authorization page of the third-party program, as shown in Figure 4As shown in (b) in the figure, the user clicks the consent button on the authorization page of the third-party program. At this time, the third-party program will feedback the binding consent information of the target delivery user to the regional ordering program. After the regional ordering program receives the binding consent information fed back by the third-party program, it sends the binding consent information to the backend. After receiving the binding consent information, the backend sends the target delivery user (such as Figure 5 The user user5 shown in FIG. 1 is added to the preset user maintenance list, such as Figure 5 Thus, through the user maintenance list, an order query request can be sent to a third-party program to synchronize the third-party order information, so that two orders of the same user can be delivered at the same time.
[0099] At this time, if Figure 6 As shown, step 203 specifically includes the following steps 2031 to 2034:
[0100] 2031. The backend detects whether the target delivery user exists in the preset user maintenance list.
[0101] 2032. If the target delivery user exists in the user maintenance list, the backend sends the order query request to the third-party program based on the user information of the target delivery user.
[0102] There are many ways to implement step 2032, illustratively including the following ways ①, ②, and ③:
[0103] ① In some embodiments, the backend directly uses the user information of the target delivery user to generate an order query request and sends the order query request to a third-party program.
[0104] ② In some embodiments, in order to improve the order query security of the third-party program and to improve the security of user information, step 2032 may specifically include: the back-end performs signature processing on the user information and request time of the target delivery user based on a preset signature algorithm to obtain a first signature value; the back-end generates an order query request based on the user information of the target delivery user, the request time and the first signature value; the back-end sends the order query request to the third-party program.
[0105] At this time, step 2033 may specifically include: when the interval duration between the request time carried by the order query request and the current time is less than the preset interval duration threshold, and the first signature value carried by the order query request is consistent with the second signature value, the back end receives the order query result fed back by the third-party program based on the order query request, wherein the order query result includes a third-party order that is the same as the target delivery user of the selected order, wherein the second signature value is signed by the third-party program based on the user information and request time carried by the order query request.
[0106] In this way, on the first hand, after the third-party program receives the order query request sent by the back-end, the third-party program will compare whether the interval time between the request time carried by the order query request and the current time is less than the preset interval time threshold. If the interval time is less than the preset interval time threshold, the order query request is considered to be a legitimate request and can continue to be processed subsequently. The third-party program will then feedback the order query result corresponding to the order query request to the back-end; if the interval time is greater than or equal to the preset interval time threshold, it is considered that the order query request may be a request resent by an illegal attack, which may affect the order information security of the target delivery user in the third-party program. Therefore, when the interval time is greater than or equal to the preset interval time threshold, the third-party program will not feedback the order query result corresponding to the order query request to the back-end to improve the order query security of the third-party program.
[0107] Secondly, the third-party program will also sign the order query request according to the preset signature algorithm based on the user information and request time carried in the order query request to obtain a second signature value. In this way, the backend and the third-party program will use the request time to sign respectively. After the third-party program compares the first signature value and the second signature value and finds that they are consistent, the third-party program will feedback the order query result corresponding to the order query request to the backend. This can avoid the problem of clients that do not have query permissions using third-party programs to query orders.
[0108] The order query result includes the order of the target delivery user and the corresponding estimated order delivery time.
[0109] ③ In some embodiments, since the method of "comparing whether the interval time between the request time carried by the order query request and the current time is less than the preset interval time threshold, and triggering the feedback of the order query result corresponding to the order query request to the back end only when the interval time is less than the preset interval time threshold" can only filter out the interval time greater than the preset interval time threshold (for example, the interval time between the request time and the current time exceeds 2 minutes), in order to avoid illegal attacks within the preset interval time threshold, step 2032 may specifically include: the back end signs the user information and request time of the target delivery user based on a preset signature algorithm to obtain a first signature value; the back end generates a random hash value based on the user information of the target delivery user and the request time; the back end generates an order query request based on the random hash value, the user information of the target delivery user, the request time and the first signature value; the back end sends the order query request to the third-party program.
[0110] At this time, step 2033 may specifically include: when the random hash value carried by the order query request is different from the hash value in the hash cache table of the third-party program, the interval between the request time carried by the order query request and the current time is less than the preset interval threshold, and the first signature value carried by the order query request is consistent with the second signature value, the back end receives the order query result fed back by the third-party program based on the order query request, wherein the order query result includes a third-party order that is the same as the target delivery user of the selected order, and wherein the second signature value is signed by the third-party program based on the user information and request time carried by the order query request.
[0111] In this way, after the third-party program receives the order query request sent by the back-end, the third-party program compares the random hash value carried in the order query request with the hash value in the hash cache table of the third-party program to see if they are the same. When the random hash value carried in the order query request is different from the hash value in the hash cache table of the third-party program, the order query request is considered to be a legitimate request and can continue to be processed subsequently. The third-party program will then feedback the order query result corresponding to the order query request to the back-end; otherwise, when the random hash value carried in the order query request is the same as one of the hash values in the hash cache table of the third-party program, it is considered that the order query request may be a request resent by an illegal attack, which may affect the order information security of the target delivery user in the third-party program. Therefore, the third-party program will not feedback the order query result corresponding to the order query request to the back-end to improve the order query security of the third-party program.
[0112] 2033. The back end receives the order query result fed back by the third-party program based on the order query request, wherein the order query result includes third-party orders that are the same as the target delivery user of the selected order.
[0113] For example, assuming that order a is the selected order in step 202, first, the backend detects whether there is a target delivery user (such as user A) for the selected order (such as order a) in the preset user maintenance list; if there is a target delivery user (such as user A) for the selected order (such as order a) in the user maintenance list, the backend sends an order query request carrying user information of the target delivery user to a third-party program (taking the third-party program as an example of a food delivery mini program). After the third-party program (such as the food delivery mini program) receives the order query request, the third-party program (such as the food delivery mini program) will call the order query interface to query whether the third-party program (such as the food delivery mini program) has an order for the target delivery user based on the user information of the target delivery user; if it is found that the third-party program (such as the food delivery mini program) has an order for the target delivery user, the third-party program (such as the food delivery mini program) returns the queried order (such as order b) to the backend; the backend can receive the order (such as order b) fed back by the third-party program (such as the food delivery mini program) based on the order query request as a third-party order that is the same as the target delivery user (such as user A) for the selected order (such as order a).
[0114] 2034. If the target delivery user does not exist in the user maintenance list, the backend determines that there is no third-party order that is the same as the target delivery user of the selected order.
[0115] If the target delivery user does not exist in the preset user maintenance list, it proves that the target delivery user is not authorized to query the orders of the third-party program. At this time, it is necessary to wait for the order triggered by the third-party program to arrive at the robot delivery area before it can be distributed. At this time, the backend continues to detect the next selected order.
[0116] Therefore, through steps 2031 to 2034, an order query request can be sent to a third-party program, and the third-party orders of the target delivery user can be queried through the third-party program, thereby avoiding the problem of two orders from the same user needing to be delivered twice due to synchronization issues with third-party order information.
[0117] (2) In some embodiments, the user manually inputs a third-party order and its estimated delivery time. In step 202, a third-party order with the same target delivery user as the selected order is searched from the manually input order list.
[0118] 204. Obtain the degree of overlap in preparation time between the third-party order and the order list of the current shift.
[0119] There are many ways to implement step 204, illustratively including:
[0120] (1) In some embodiments, the degree of overlap of the preparation time is determined based on the estimated preparation time of the selected order and the estimated delivery time of the third-party order. In this case, step 204 may specifically include the following steps 2041A to 2043A:
[0121] 2041A. Obtain an estimated preparation time for the selected order.
[0122] In some embodiments, the preparation time for the selected order can be determined according to the order type of the selected order and the preset production time of each preset order type.
[0123] In some embodiments, in order to improve the accuracy of the estimated preparation time, the first configuration information of the selected order, the second configuration information of the historical order, and the configuration duration of the historical order can also be used to predict the rainy season configuration duration of the selected order; thereby determining the estimated preparation time of the selected order. At this time, step 2041A can specifically include the following steps A1 to A4:
[0124] A1. Obtain first equipment information of the selected order, wherein the first equipment information includes at least one of order type, equipment date information, equipment season information, equipment time period information, and equipment location information.
[0125] The first configuration information refers to the configuration information of the selected order.
[0126] A2. Obtain second configuration information of each historical order in the robot delivery area.
[0127] Among them, the second configuration information is the configuration information of the historical order.
[0128] A3. Perform prediction based on the first allocation information and the second allocation information of each historical order to obtain an estimated allocation time for the selected order.
[0129] Exemplarily, step A3 may specifically include: obtaining the similarity between the second equipment information of each historical order and the first equipment information as the information similarity of each historical order; finding out from each historical order the target historical order whose information similarity is greater than a preset similarity threshold; and determining the estimated equipment time of the selected order based on the equipment time of the target historical order and the information similarity of the target historical order.
[0130] In some embodiments, a unified representation method is first adopted, such as a BERT model, to encode the first configuration information and the second configuration information of each historical order, respectively, to obtain the encoding vector of the first configuration information and the encoding vector of each historical order; then, the cosine similarity between the encoding vector of the second configuration information of each historical order and the encoding vector of the first configuration information is calculated as the information similarity of each historical order. Then, from each historical order (such as historical orders 1, 2, 3, ..., 100), the target historical orders (such as historical orders 1, 2, 3, ..., 10) whose information similarity is greater than a preset similarity threshold are found. Finally, the average of the preparation times of the target historical orders is calculated as the estimated preparation time of the selected order; or, according to the rule that the higher the information similarity, the higher the time weight of the target historical orders, the estimated preparation time of the selected order is calculated according to the preparation time of the target historical orders and the information similarity of the target historical orders (e.g., the information similarities of historical orders 1, 2, 3, …, 10 are 80%, 80%, 80%, 90%, 90%, 90%, 95%, 95%, 95%, respectively). For example, the target historical orders are calculated first. The ratio of the information similarity of the target historical order (such as the information similarity of historical order 1 is 80%) to the sum of all information similarities (i.e. 80% + 80% + 80% + 80% + 90% + 90% + 90% + 95% + 95% + 95% = 8.75) is used as the weight ratio of the target historical order; then, the product of the weight ratio of the target historical order and the configuration time of the target historical order is calculated as the contribution time of the target historical order; finally, the result of summing up the contribution time of all target historical orders is used as the estimated configuration time of the selected order.
[0131] A4. Determine the estimated preparation time of the selected order based on the order placement time of the selected order and the estimated preparation time.
[0132] Exemplarily, the result obtained by adding the order time of the selected order and the estimated preparation time of the selected order is used as the estimated preparation time of the selected order.
[0133] 2042A. Obtain an estimated delivery time for the third-party order.
[0134] In some embodiments, the estimated delivery time of a third-party order is queried through authorization by a third-party program. At this time, step 2042A may include: first, the backend detects whether there is a target delivery user in the preset user maintenance list; if the target delivery user exists in the preset user maintenance list, the backend sends an order query request to the third-party program based on the user information of the target delivery user; the backend receives the order query result fed back by the third-party program based on the order query request, wherein the order query result includes the estimated delivery time of the third-party order. For example, assuming that order a is the selected order in step 202, first, the backend detects whether there is a target delivery user (such as user A) for the selected order (such as order a) in the preset user maintenance list; if the target delivery user (such as user A) for the selected order (such as order a) exists in the user maintenance list, the backend sends an order query request carrying the user information of the target delivery user to the third-party program (taking the third-party program as a food delivery mini program as an example). After the third-party program (such as the food delivery mini program) receives the order query request, the third-party program (such as the food delivery mini program) will call the order query interface to query the target delivery user according to the user information of the target delivery user. user information, query whether the third-party program (such as the food delivery mini program) has orders for the target delivery user; if it is found that the third-party program (such as the food delivery mini program) has orders for the target delivery user, the third-party program (such as the food delivery mini program) will return the queried order (such as order b) and the corresponding estimated order delivery time to the backend; the backend can use the order (such as order b) queried and fed back by the order query interface as the third-party order with the same target delivery user (such as user A) as the selected order (such as order a), and use the corresponding estimated order delivery time of the third-party order (such as order b) as the estimated delivery time of the third-party order.
[0135] In some embodiments, the user manually inputs a third-party order and its estimated delivery time. In step 2042A, the estimated delivery time manually input by the user may be used as the estimated delivery time of the third-party order.
[0136] 2043A. Determine the degree of overlap of the preparation time based on the time difference between the estimated preparation time and the estimated delivery time.
[0137] For example, if the time difference between the estimated preparation time and the estimated delivery time is smaller, the determined preparation time coincidence degree is higher; conversely, if the time difference between the estimated preparation time and the estimated delivery time is larger, the determined preparation time coincidence degree is lower.
[0138] (2) In some embodiments, the degree of overlap of the preparation time is determined based on the latest preparation time of the selected order and the estimated delivery time of the third-party order. In this case, step 204 may specifically include the following steps 2041B to 2043B:
[0139] 2041B. Detect the latest preparation time of the order list of this shift.
[0140] Specifically, the estimated preparation time of each order in the order list of this shift can be obtained respectively, and then the latest estimated preparation time is selected as the latest preparation time of the order list of this shift. The method for determining the estimated preparation time of each order in the order list of this shift is similar to step 2041A, and the details can be referred to the relevant description above, which will not be repeated here.
[0141] 2042B. Obtain an estimated delivery time for the third-party order.
[0142] 2043B. Determine the degree of overlap of the preparation time based on the time difference between the latest preparation time and the estimated delivery time.
[0143] For example, if the time difference between the latest preparation time and the estimated delivery time is smaller, the determined preparation time coincidence degree is higher; conversely, if the time difference between the latest preparation time and the estimated delivery time is larger, the determined preparation time coincidence degree is lower.
[0144] 205. If the overlap of the preparation time is greater than a preset overlap threshold, the third-party order is combined with the order list of the current shift.
[0145] If the overlap in preparation time between the third-party order and the order list of this shift is greater than the preset overlap threshold, the third-party order will be combined with the order list of this shift, so that the third-party order can be delivered in the same shift as the selected order, reducing the duplication rate of delivery routes and improving the delivery efficiency of the delivery robot; on the other hand, the third-party order will be combined with the order list of this shift only when the overlap in preparation time is calculated to be greater than the preset overlap threshold. Therefore, the delivery will not result in excessive waiting time after the third-party order arrives at the robot delivery area, thereby improving the delivery efficiency.
[0146] If the overlap of the preparation time is less than or equal to the preset overlap threshold, the third-party order will not be combined with the order list of this shift, and the third-party order will be added to the order pool to be scheduled, waiting for delivery after the next distribution.
[0147] Furthermore, in order to improve the efficiency of order slot selection, the slot selected by the delivery personnel for the selected order can be directly set as the slot of the third-party order, and the subsequent delivery process can complete the pickup operation according to the set slot information. At this time, the delivery robot order combination processing method also includes: displaying the slot configuration page of the delivery robot; if the third-party order is combined with the order list of the current shift, in response to the slot selection operation for the selected order, setting the selected slot of the slot selection operation as the slot of the selected order, and setting it as the slot of the third-party order.
[0148] From the above content, it can be seen that by displaying the distribution order selection page containing the list of orders to be delivered in the robot delivery area, the selected order of the order selection operation is added to the order list of this shift of the delivery robot. On the one hand, by detecting the third-party order of the same target delivery user as the selected order, it is determined whether there are two or more orders for the same user, and then the two orders of the same user can be delivered together, avoiding the problem that the third-party order information cannot be synchronized when the third-party order has not arrived; on the other hand, by obtaining the overlap of the preparation time between the third-party order and the order list of this shift, when the overlap of the preparation time is greater than the preset overlap threshold, the third-party order and the order list of this shift are combined, so that the preparation time of the third-party order is close to the preparation time of the order list of this shift. The order is combined to avoid the problem that the timeliness of the order list of this shift is reduced after the combination due to the late arrival time of the third-party order, thereby ensuring the timeliness of the order list of this shift; thereby reducing the waste of delivery resources of the delivery robot and improving the delivery timeliness to a certain extent.
[0149] Those of ordinary skill in the art will appreciate that all or part of the steps in the above-mentioned delivery robot order processing method may be completed by instructions, or by controlling related hardware through instructions, and the instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.
[0150] To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of computer programs are stored, and the computer program can be loaded by a processor to execute any one of the delivery robot order processing methods provided in the embodiment of the present application. For example, the computer program can be loaded by a processor to execute the following steps:
[0151] Displaying a delivery order selection page for the delivery robot, wherein the delivery order selection page includes a list of orders to be delivered in the robot's delivery area;
[0152] Based on the order selection operation of the to-be-delivered order list, adding the selected order of the order selection operation to the order list of the delivery robot for this shift;
[0153] Detecting third-party orders that are the same as the target delivery user of the selected order;
[0154] Obtain the degree of overlap in preparation time between the third-party order and the order list of the current shift;
[0155] If the overlap of the preparation time is greater than a preset overlap threshold, the third-party order will be combined with the order list of this shift.
[0156] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0157] In the above-mentioned delivery robot order processing method, computer-readable storage medium, and electronic device embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process and beneficial effects of the above-described computer-readable storage medium, electronic device, and its corresponding units can refer to the description of the delivery robot order processing method in the above embodiment, and will not be repeated here.
[0158] The above is a detailed introduction to a delivery robot order processing method, electronic device and computer-readable storage medium provided in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A delivery robot order processing method, characterized in that: The method comprises: Displaying a delivery order selection page for the delivery robot, wherein the delivery order selection page includes a list of orders to be delivered in the robot's delivery area; Based on the order selection operation of the to-be-delivered order list, adding the selected order of the order selection operation to the order list of the delivery robot for this shift; Detecting third-party orders that are the same as the target delivery user of the selected order; Obtaining the degree of overlap in preparation time between the third-party order and the order list of the current shift; If the overlap of the preparation time is greater than a preset overlap threshold, the third-party order will be combined with the order list of this shift.
2. The delivery robot order processing method according to claim 1, characterized in that: The method further comprises: After the target delivery user places an order through the regional ordering program of the robot delivery area, an authorization page is displayed through the regional ordering program, wherein the authorization page includes an authorization consent control; In response to a touch operation on the authorization consent control, sending an order binding request for the target delivery user to a third-party program through the regional order placement program; When receiving the binding consent information fed back by the third-party program, adding the target delivery user to a preset user maintenance list; The detecting of a third-party order having the same target delivery user as the selected order comprises: If the target delivery user exists in the user maintenance list, sending an order query request to the third-party program based on the user information of the target delivery user; An order query result fed back by the third-party program based on the order query request is received, wherein the order query result includes third-party orders that are the same as a target delivery user of the selected order.
3. The delivery robot order grouping processing method according to claim 1, characterized in that: The obtaining of the degree of overlap in preparation time between the third-party order and the order list of the current shift includes: Obtaining an estimated preparation time for the selected order; Obtain an estimated delivery time for the third-party order; The degree of overlap of the preparation time is determined based on a time difference between the estimated preparation time and the estimated delivery time.
4. The delivery robot order processing method according to claim 3, characterized in that: The obtaining of the estimated delivery time of the third-party order includes: If the target delivery user exists in the preset user maintenance list, sending an order query request to the third-party program based on the user information of the target delivery user; Receive an order query result fed back by the third-party program based on the order query request, wherein the order query result includes an estimated delivery time of the third-party order.
5. The delivery robot order processing method according to claim 3, characterized in that: The obtaining of the estimated preparation time of the selected order includes: Acquire first configuration information of the selected order, wherein the first configuration information includes at least one of order type, configuration date information, configuration season information, configuration time period information, and configuration location information; Acquire second configuration information of each historical order in the delivery area of the robot; Performing a prediction based on the first allocation information and the second allocation information of each of the historical orders to obtain an estimated allocation time for the selected order; Based on the order time of the selected order and the estimated preparation time, the estimated preparation time of the selected order is determined.
6. The delivery robot order processing method according to claim 5, characterized in that: The performing prediction based on the first allocation information and the second allocation information of each historical order to obtain the estimated allocation time of the selected order includes: Acquire the similarity between the second configuration information of each historical order and the first configuration information as the information similarity of each historical order; From the historical orders, find a target historical order whose information similarity is greater than a preset similarity threshold; Based on the preparation time of the target historical orders and the information similarity of the target historical orders, an estimated preparation time of the selected order is determined.
7. The delivery robot order processing method according to claim 2 or 4, characterized in that: The sending of the order query request to the third-party program based on the user information of the target delivery user includes: Based on a preset signature algorithm, the user information and request time of the target delivery user are signed to obtain a first signature value; Generate an order query request based on the user information of the target delivery user, the request time and the first signature value; Sending the order query request to the third-party program; The receiving the order fed back by the third-party program based on the order query request as a third-party order with the same target delivery user as the selected order includes: When the interval duration between the request time carried in the order query request and the current time is less than a preset interval duration threshold, and the first signature value carried in the order query request is consistent with the second signature value, the order fed back by the third-party program based on the order query request is received as a third-party order with the same target delivery user as the selected order, wherein the second signature value is signed by the third-party program based on the user information and request time carried in the order query request.
8. The delivery robot order grouping processing method according to claim 1, characterized in that: The method further comprises: Displaying a grid configuration page of the delivery robot; If the third-party order is combined with the order list of this shift, then in response to the slot selection operation for the selected order, the selected slot of the slot selection operation is set as the slot of the selected order and the slot of the third-party order.
9. An electronic device, characterized in that: It includes a processor and a memory, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it executes the delivery robot order grouping processing method as described in any one of claims 1 to 8.
10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is loaded by a processor to execute the delivery robot order grouping processing method as described in any one of claims 1 to 8.