Method, device, equipment and storage medium for acquiring delivery time

Abstract

The application discloses a method, device and equipment for obtaining delivery time and a storage medium, and belongs to the technical field of data processing. The method comprises the following steps: obtaining an initial delivery time of a to-be-delivered order; obtaining a stay duration of a delivery object corresponding to the to-be-delivered order at a resource delivery position, wherein the resource delivery position is a position where the delivery object obtains a resource corresponding to the to-be-delivered order; and determining a target delivery time of the to-be-delivered order based on the stay duration and the initial delivery time. Since the stay duration can indirectly reflect whether the resource providing object is delivered, the target delivery time can be determined based on the stay duration and the initial delivery time, thereby improving the accuracy of the target delivery time.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device, and storage medium for obtaining shipping time. Background Technology

[0002] With the development of delivery services, the requirements for order delivery efficiency are increasing. Among the factors affecting delivery efficiency, the shipping time of the resources corresponding to an order is crucial. For example, selecting an order dispatch time based on the shipping time can effectively improve delivery efficiency. Therefore, to better improve order delivery efficiency, accurate shipping times are essential.

[0003] In related technologies, the order shipping time is manually provided by the resource provider corresponding to the order. For example, the resource provider clicks the shipping button, and the time of clicking the shipping button is determined as the order shipping time; or the resource provider places the resource corresponding to the order on the pickup locker, and the time of placing it on the pickup locker is determined as the order shipping time.

[0004] However, due to the poor controllability of manual operations, the accuracy of order delivery times obtained based on manual operations is low. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for obtaining shipping time, which can be used to solve problems in related technologies. The technical solution is as follows:

[0006] On one hand, embodiments of this application provide a method for obtaining shipping time, the method comprising:

[0007] Obtain the initial shipping time for orders awaiting delivery;

[0008] The duration of the delivery object corresponding to the order to be delivered is obtained at the resource delivery location, where the resource delivery location is the location where the delivery object obtains the resource corresponding to the order to be delivered.

[0009] Based on the dwell time and the initial shipping time, the target shipping time for the order to be delivered is determined.

[0010] In one possible implementation, obtaining the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location includes:

[0011] The system acquires multiple dwell times of the delivery object at the resource delivery location. These multiple dwell times are acquired from different sources, and each dwell time includes the arrival and departure times of the delivery object.

[0012] The duration of stay is determined based on the multiple stay data.

[0013] In one possible implementation, determining the dwell time based on the plurality of dwell data includes:

[0014] In response to a conflict among the multiple stay data, at least one stay data is retained based on priority, and the stay duration is determined based on the at least one stay data.

[0015] In one possible implementation, determining the dwell time based on the at least one dwell time data includes:

[0016] In response to the fact that the at least one dwell data includes dwell data uploaded by the delivery object, and the dwell data uploaded by the delivery object meets the filtering conditions, the dwell data uploaded by the delivery object is filtered.

[0017] The duration of stay is determined based on the filtered stay data.

[0018] In one possible implementation, determining the target shipping time for the order to be delivered based on the dwell time and the initial shipping time includes:

[0019] Based on the dwell time, it is determined that the delivery object did not engage in waiting behavior and did not leave the resource delivery location multiple times, and the initial shipping time is taken as the target shipping time.

[0020] In one possible implementation, determining the target shipping time for the order to be delivered based on the dwell time and the initial shipping time includes:

[0021] Based on the dwell time, it is determined that the delivery object is in a waiting state, and the target departure time of the delivery object is taken as the target shipment time. The target departure time is determined based on the departure time of the delivery object.

[0022] On the other hand, an apparatus for obtaining shipping time is provided, the apparatus comprising:

[0023] The acquisition module is used to obtain the initial shipping time of orders to be delivered;

[0024] The acquisition module is further configured to acquire the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location, wherein the resource delivery location is the location where the delivery object acquires the resource corresponding to the order to be delivered;

[0025] The determination module is used to determine the target shipping time of the order to be delivered based on the dwell time and the initial shipping time.

[0026] In one possible implementation, the acquisition module is configured to acquire multiple dwell times of the delivery object at the resource delivery location, the multiple dwell times being acquired from different sources, each of the multiple dwell times including the arrival time and departure time of the delivery object; and to determine the dwell duration based on the multiple dwell times.

[0027] In one possible implementation, the acquisition module is configured to, in response to a conflict between the plurality of stay data, retain at least one stay data among the plurality of stay data based on priority, and determine the stay duration based on the at least one stay data.

[0028] In one possible implementation, the acquisition module is configured to, in response to the at least one dwell data including dwell data uploaded by the delivery object and the dwell data uploaded by the delivery object satisfying the filtering conditions, filter the dwell data uploaded by the delivery object; and determine the dwell duration based on the filtered dwell data.

[0029] In one possible implementation, the determining module is used to determine, based on the dwell time, that the delivery object has not engaged in waiting behavior and has not left the resource delivery location multiple times, and to use the initial shipping time as the target shipping time.

[0030] In one possible implementation, the determining module is configured to determine that the delivery object has generated waiting behavior based on the dwell time, and to take the target departure time of the delivery object as the target shipment time, wherein the target departure time is determined based on the departure time of the delivery object.

[0031] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to enable the computer device to implement any of the above-described methods for obtaining shipping time.

[0032] On the other hand, a computer-readable storage medium is also provided, wherein at least one computer program is stored therein, the at least one computer program being loaded and executed by a processor to enable a computer to implement any of the methods for obtaining shipping time described above.

[0033] On the other hand, a computer program product or computer program is also provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform any of the methods described above for obtaining shipping time.

[0034] The technical solution provided in this application has at least the following beneficial effects:

[0035] After obtaining the initial shipping time, the duration of the delivery object's stay at the resource delivery location is also obtained. Since the stay duration can indirectly reflect whether the resource provider has shipped, the target shipping time can be determined based on the stay duration and the initial shipping time, thus improving the accuracy of the target shipping time. Attached Figure Description

[0036] 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.

[0037] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application;

[0038] Figure 2 This is a flowchart illustrating a method for obtaining shipping time provided in an embodiment of this application;

[0039] Figure 3 This is a flowchart of a method for determining the duration of stay provided in an embodiment of this application;

[0040] Figure 4 This is a schematic diagram illustrating a situation where multiple dwell times conflict, as provided in an embodiment of this application.

[0041] Figure 5 This is a schematic diagram illustrating a scenario where multiple dwell times do not conflict with each other, as provided in an embodiment of this application.

[0042] Figure 6 This is a flowchart illustrating a method for determining a target shipping time, provided in an embodiment of this application.

[0043] Figure 7 This is a flowchart of obtaining the shipping time provided in an embodiment of this application;

[0044] Figure 8 This is a schematic diagram of the structure of a device for obtaining shipping time provided in an embodiment of this application;

[0045] Figure 9 This is a schematic diagram of the structure of a server provided in an embodiment of this application;

[0046] Figure 10 This is a schematic diagram of a device structure for obtaining delivery time provided in an embodiment of this application. Detailed Implementation

[0047] 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.

[0048] This application provides a method for obtaining shipping time. Please refer to... Figure 1 The diagram illustrates the implementation environment of the method provided in this embodiment. This implementation environment may include: terminal 11 and server 12.

[0049] In this embodiment, terminal 11 is equipped with an application capable of obtaining the initial shipping time. After obtaining the initial shipping time, the application can send the obtained initial shipping time to server 12. Server 12 obtains the target shipping time based on the method provided in this application embodiment and stores the target shipping time. Optionally, terminal 11 obtains the target shipping time from server 12 and stores the target shipping time.

[0050] Optionally, terminal 11 is equipped with an application capable of obtaining the initial shipping time. After the application obtains the initial shipping time, terminal 11 obtains the target shipping time based on the method provided in this application embodiment, and terminal 11 stores the target shipping time. Optionally, server 12 obtains the target shipping time from terminal 11 and stores the target shipping time.

[0051] Optionally, terminal 11 obtains the initial shipping time from server 12, terminal 11 obtains the target shipping time based on the method provided in this application embodiment, and terminal 11 stores the target shipping time. Optionally, server 12 obtains the target shipping time from terminal 11 and stores the target shipping time.

[0052] Optionally, terminal 11 can be any electronic product capable of human-computer interaction with the user through one or more methods such as a keyboard, touchpad, touchscreen, remote control, voice interaction, or handwriting device, such as PC (Personal Computer), mobile phone, smartphone, PDA (Personal Digital Assistant), wearable device, PPC (Pocket PC), tablet computer, smart car system, smart TV, smart speaker, etc. Server 12 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center. Terminal 11 and server 12 establish a communication connection through wired or wireless network.

[0053] Those skilled in the art should understand that the above-described terminal 11 and server 12 are merely examples. Other existing or future terminals or servers that are applicable to this application should also be included within the scope of protection of this application, and are hereby incorporated by reference.

[0054] Based on the above Figure 1 The implementation environment shown in this application provides a method for obtaining shipping time. Figure 2 As shown, the method can be executed by a terminal or a server. Taking the application of the method to a server as an example, the method includes steps 201-203.

[0055] In step 201, the initial shipping time of the order to be delivered is obtained.

[0056] In one possible implementation, an order to be delivered is an order for which the resource provider has not yet delivered the corresponding resources to the delivery object. For example, after the resource provider completes the preparation of the resources corresponding to order one based on order one, order one is an order to be delivered before delivering the resources corresponding to order one to the delivery object; as another example, before the resource provider completes the preparation of the resources corresponding to order two based on order two, order two is an order to be delivered.

[0057] This application does not limit the method of obtaining the initial shipping time of the order to be delivered. It can trigger a confirmation time instruction based on the resource provider object and use the time of triggering the confirmation time instruction as the initial shipping time.

[0058] Optionally, the first terminal provides a confirmation time control. The resource provider triggers a confirmation time instruction by selecting the confirmation time control, and the server obtains the initial shipping time based on the communication connection with the first terminal. The first terminal is a terminal logged in with a resource provider. For example, the first terminal has an application installed and running that can provide logistics and delivery services. This application can be a food delivery application, an application for executing online group buying, or other applications that involve logistics and delivery services; this application embodiment does not limit this. Taking a food delivery application as an example, the food delivery application provides a "order now" button as a confirmation control. After the resource provider completes the preparation of the resources corresponding to the order to be delivered, clicking the "order now" button triggers a confirmation time instruction. The server then obtains the time when the resource provider clicked the "order now" button and uses this time as the initial shipping time. The method for selecting the confirmation control can be clicking the "order now" button as shown in the above embodiment, or other selection methods, such as selecting the confirmation control via voice operation.

[0059] Optionally, the resource provider triggers a confirmation time command by operating other hardware devices, and the server obtains the initial shipping time based on the communication connection with the hardware devices. The hardware devices can be a pickup locker used by the resource provider to place the resources corresponding to the order to be delivered, a barcode scanner, or other hardware devices operated by other resource providers when completing the order to be delivered; this embodiment does not limit the specific hardware device used. Taking a pickup locker as an example, the resource provider places the resources corresponding to the order to be delivered on the pickup locker, closes the locker door, and triggers a time confirmation command by closing the locker door. The server then obtains the time when the resource provider closed the locker door and uses this time as the initial shipping time.

[0060] However, sometimes the time when the resource provider triggers the confirmation instruction differs from the actual shipping time. For example, due to an increase in the number of orders to be delivered within the same time period, the resource provider may choose to trigger confirmation instructions for multiple orders at once to save time. For instance, clicking the "deliver" button for multiple orders consecutively; or, after the resources for a particular order are prepared, they are not immediately placed in the pickup locker, but wait a certain period until the resources for multiple orders are ready before placing them together in the locker and closing multiple locker doors consecutively. To reduce the impact of erroneous confirmation instruction times uploaded by the resource provider, subsequent operations need to be performed on the obtained initial shipping time.

[0061] In step 202, the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location is obtained. The resource delivery location is the location where the delivery object obtains the resource corresponding to the order to be delivered.

[0062] The methods for obtaining the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location include, but are not limited to: obtaining multiple dwell data of the delivery object at the resource delivery location, the multiple dwell data being obtained from different sources, each of the multiple dwell data including the arrival time and departure time of the delivery object; and determining the dwell time based on the multiple dwell data.

[0063] The arrival time is the moment when the delivery object arrives at the resource delivery location, and the departure time is the moment when the delivery object leaves the resource delivery location. This application does not limit the method of obtaining multiple dwell times data from different sources, including but not limited to the following two sources.

[0064] Source 1: Obtaining dwell time data based on logistics and delivery applications on a second terminal.

[0065] The second terminal is a terminal logged into with a delivery object. The second terminal has a logistics and delivery application installed and running. The logistics and delivery application used by the delivery object and the resource provider for the same order to be delivered is the same application. The logistics and delivery application provides arrival and departure controls. The delivery object can upload the arrival time by selecting the arrival control and the departure time by selecting the departure control. The server obtains the arrival and departure times uploaded by the delivery object based on the communication connection with the second terminal.

[0066] Taking the food delivery application shown in step 201 as an example, the food delivery application provides an "Arrival" button as the arrival control and a "Pick Up" button as the departure control. After arriving at the resource delivery location, the delivery person can click the "Arrival" button to select the arrival control and upload the time of clicking the "Arrival" button to the server as the arrival time. After picking up the resource corresponding to the order to be delivered, the delivery person can click the "Pick Up" button to select the departure control and upload the time of clicking the "Pick Up" button to the server as the departure time. It should be noted that since the delivery person leaves the resource delivery location to begin delivering the order after obtaining the resource corresponding to the order to be delivered, the time when the delivery person picks up the resource corresponding to the order to be delivered can be used as the departure time. Other methods for selecting the arrival and departure controls are the same as the other methods for selecting the confirmation time control shown in step 201, and will not be elaborated further here.

[0067] Source 2: Obtaining dwell time data based on the positioning device on the second terminal.

[0068] Regarding the positioning device, it can be a device capable of positioning installed and running on the second terminal. For example, a device that achieves positioning based on GPS (Global Positioning System) (GPS device), or a device that achieves positioning based on the BeiDou Navigation Satellite System. It can also be an IoT (Internet of Things) device with positioning functionality on the second terminal. For example, Bluetooth, WIFI (Wireless Fidelity), or other devices that can achieve positioning by acquiring location information; this application embodiment does not limit this. The second terminal obtains the arrival and departure times of the delivery object at the resource delivery location based on the aforementioned positioning device. The server obtains the arrival and departure times uploaded by the second terminal based on the communication connection with the second terminal, as dwell data.

[0069] It should be noted that the server can obtain multiple stay data points based on the aforementioned devices, or it can obtain them based on other devices; this application embodiment does not limit this. The multiple stay data points can be two, three, or other quantities; this application embodiment does not limit this as well. Specifically, the arrival time and departure time included in one stay data point are obtained from the same source.

[0070] For example, taking the two sources shown in the above embodiments as examples, the arrival time and departure time obtained based on the GPS device constitute a dwell time data; the arrival time and departure time obtained based on the IoT device constitute a dwell time data; and the arrival time and departure time uploaded by the delivery object constitute a dwell time data.

[0071] After acquiring multiple stay data, the stay duration can be determined based on the multiple stay data. In one possible implementation, in response to the situation where multiple stay data conflict with each other, at least one stay data among the multiple stay data is retained based on priority, and the stay duration is determined based on at least one stay data.

[0072] For example, the process of determining the duration of stay based on multiple stay data is as follows: Figure 3 As shown, this includes, but is not limited to, the following three steps.

[0073] Step 1: Determine if there are any conflicts among the multiple stay data.

[0074] In one possible implementation, conflicts between multiple stay data points occur when there is no unique overlap between the multiple stay data points. For example, Figure 4 This illustrates a situation where multiple stay data points conflict with each other. The following section discusses... Figure 4 This will be explained. Taking the three dwell times data shown in the above embodiment as examples, Figure 4In this context, "T" refers to time. "To 1" refers to the arrival time obtained from a GPS device, "Departure 1" refers to the departure time obtained from a GPS device, and the time interval between "To 1" and "Departure 1" represents the dwell time data obtained from a GPS device. Similarly, "To 2" refers to the arrival time obtained from an IoT device, "Departure 2" refers to the departure time obtained from an IoT device, and the time interval between "To 2" and "Departure 2" represents the dwell time data obtained from an IoT device. Finally, "To 3" refers to the arrival time uploaded by the delivery recipient, "Departure 3" refers to the departure time uploaded by the delivery recipient, and the time interval between "To 3" and "Departure 3" represents the dwell time data uploaded by the delivery recipient. For example... Figure 4 As shown, the three dwell times include the following three conflict types.

[0075] Conflict type one: No overlap in the three dwelling data.

[0076] For example, the IoT device did not acquire any dwell time data, and the other two dwell time data did not overlap (abnormal case 1). For example, all three dwell time data did not overlap (abnormal case 2).

[0077] Conflict type two: Two stay data points overlap, and neither overlaps with a third stay data point.

[0078] For example, the dwell data uploaded by the delivery object overlaps with the dwell data obtained from IoT devices, but neither overlaps with the dwell data obtained from GPS devices (abnormal case 3).

[0079] Conflict type 3: One stop data point overlaps with two other stop data points, but the other two stop data points do not overlap with each other.

[0080] For example, the dwell time data uploaded by the delivery recipient overlaps with two other dwell time data sets, but the other two dwell time data sets do not overlap with each other (abnormal case 4). For example, the dwell time data obtained from the IoT device overlaps with two other dwell time data sets, but the other two dwell time data sets do not overlap with each other (abnormal case 5).

[0081] It should be noted that the examples above are intended to illustrate that there are multiple types of conflicts between multiple stay data, rather than limiting the types of conflicts. Conflict types can be... Figure 4 The type shown may also be other types, and this application does not limit this type in the embodiments.

[0082] In one possible implementation, there are no conflicts between the multiple stay data points. "No conflicts" means that there is a unique overlapping portion among the multiple stay data points. For example, Figure 5 The data shows multiple scenarios where the stay data do not conflict with each other, namely, normal scenario 1, normal scenario 2, and normal scenario 3. Figure 5The meanings of "T", "to 1", "away from 1", "to 2", "away from 2", "to 3" and "away from 3" are as follows: Figure 4 The meaning is the same as in [the previous sentence], so I won't elaborate further here. Based on Figure 5 It can be seen that the order of arrival and departure times in the three stop data is not limited. There is a unique overlapping part among the three stop data, which means that the three stop data do not conflict with each other.

[0083] Step 2: Based on the judgment result, retain at least one of the multiple stay data.

[0084] In response to the situation shown in the above embodiments, where multiple stay data conflict with each other, at least one stay data among the multiple stay data can be retained based on priority, including but not limited to the following three retention methods.

[0085] Method 1: For conflict type 1, retain one dwell data based on the first priority.

[0086] This application does not limit the first priority in the embodiments. Optionally, the first priority is: stay data obtained based on IoT devices > stay data uploaded based on delivery objects ≥ stay data obtained based on GPS devices.

[0087] Regarding the retention of the highest priority dwell data based on the first priority, for example, taking the exception case 1 shown in the above embodiment as an example, dwell data uploaded by the delivery object is retained based on the first priority; taking the exception case 2 shown in the above embodiment as an example, dwell data obtained from IoT devices is retained based on the first priority.

[0088] Method 2: For the case of conflict type 2, retain the two overlapping dwell times.

[0089] For example, taking the abnormal situation 3 shown in the above embodiment as an example, the two types of stay data are retained: the stay data uploaded by the delivery object and the stay data obtained by the IoT device.

[0090] Method 3: For the case of conflict type 3, retain two overlapping stay data based on the second priority.

[0091] This application does not limit the second priority in its embodiments. Optionally, the second priority is: IoT device & delivery object > IoT device & GPS device > delivery object & GPS device. Here, "IoT device & delivery object" refers to the overlap between the dwell data obtained from the IoT device and the dwell data uploaded by the delivery object; "IoT device & GPS device" refers to the overlap between the dwell data obtained from the IoT device and the dwell data obtained from the GPS device; and "delivery object & GPS device" refers to the overlap between the dwell data uploaded by the delivery object and the dwell data obtained from the GPS device in terms of time.

[0092] Regarding the retention of two overlapping stay data based on the second priority, taking the abnormal situation 4 shown in the above embodiment as an example, the stay data obtained based on the IoT device and the stay data uploaded by the delivery object are retained based on the second priority; taking the abnormal situation 5 shown in the above embodiment as an example, the stay data obtained based on the IoT device and the stay data uploaded by the delivery object are retained based on the second priority.

[0093] In one possible implementation, multiple stay data points can be retained if there is no conflict between them, as shown in the above embodiments.

[0094] Regarding the retention of multiple stay data points, all stay data can be retained, or multiple stay data points can be selectively retained; this application embodiment does not limit this. For example, as... Figure 3 As shown, in cases where there is a unique overlap among the three stop data points, all three stop data points are retained.

[0095] Step 3: Determine the duration of stay based on at least one stay data point.

[0096] In one possible implementation, in response to at least one dwell data including dwell data uploaded by the delivery object, and the dwell data uploaded by the delivery object satisfying the filtering conditions, the dwell data uploaded by the delivery object is filtered; the dwell duration is determined based on the filtered dwell data.

[0097] The methods for determining whether the dwell data uploaded by the delivery recipient meets the filtering conditions include, but are not limited to, the following two methods.

[0098] Method 1: When the IoT / GPS device is waiting, determine whether the delivery object continuously uploads its arrival and departure times.

[0099] For example, when the IoT device / GPS device determines that the delivery person is waiting, if the delivery person continuously uploads arrival and departure times, then the dwell data uploaded by the delivery person meets the filtering conditions, and the dwell data uploaded by the delivery person is filtered out. For example, when the IoT device / GPS device determines that the delivery person is waiting, if the delivery person does not continuously upload arrival and departure times, then the dwell data uploaded by the delivery person does not meet the filtering conditions, and the dwell data uploaded by the delivery person is retained.

[0100] The "waiting time" metric for IoT / GPS devices refers to a situation where the dwell time data obtained from IoT / GPS devices exceeds a waiting threshold. This waiting threshold can be obtained through surveys, optionally based on data from offline or online surveys, analyzing statistical distribution to determine the threshold. The waiting thresholds for IoT devices (the first waiting threshold) and GPS devices (the second waiting threshold) can be the same or different; for example, the first waiting threshold could be 3 minutes, and the second waiting threshold 5 minutes.

[0101] Regarding the continuous upload of arrival and departure times for delivery objects, this refers to the interval between the uploaded arrival and departure times being less than a continuous threshold (the dwell time is less than the continuous threshold). The process of obtaining the continuous threshold is similar to the process of obtaining the waiting threshold described above, and will not be elaborated further here. Optionally, the continuous threshold can be set to 10 seconds.

[0102] Taking GPS-based devices as an example to determine whether to wait, with a second waiting threshold of 5 minutes and a continuous threshold of 10 seconds, and the delivery recipient uploading the arrival time by clicking the arrival button and the departure time by clicking the pick-up button, the implementation process of the first judgment method is explained.

[0103] In one possible scenario, the arrival time obtained from the GPS device is 10:37:00, the departure time obtained from the GPS device is 10:42:00, the arrival time uploaded by the delivery object is 10:40:10, the departure time uploaded by the delivery object is 10:40:19, and the dwell time data obtained from the GPS device is 5 minutes, which is greater than the second waiting threshold. The GPS device determines to wait. While the GPS device determines to wait, the dwell time data uploaded by the delivery object is 9 seconds, which is less than the continuous threshold. At this time, the delivery object continuously uploads the arrival time and departure time. The dwell time data uploaded by the delivery object meets the filtering conditions and needs to be filtered.

[0104] For example, a delivery person arrives within the GPS device's detection range at 10:37:00, reaches the resource delivery location at 10:38:00, waits for 2 minutes to retrieve the resources corresponding to the order to be delivered, and remembers that they haven't clicked the "Arrived" and "Pick Up" buttons when preparing to leave the resource delivery location. So they click the "Arrived" button at 10:40:10 and then click the "Pick Up" button at 10:40:19 before leaving the resource delivery location. They leave the GPS device's detection range at 10:42:00. At this point, the delivery person's uploaded dwell data meets the filtering criteria and needs to be filtered.

[0105] In one possible scenario, the arrival time obtained from the GPS device is 10:37:00, the departure time obtained from the GPS device is 10:42:00, the arrival time uploaded by the delivery object is 10:40:10, the departure time uploaded by the delivery object is 10:41:10, and the dwell time data obtained from the GPS device is 5 minutes, which is greater than the second waiting threshold. The GPS device determines to wait. While the GPS device determines to wait, the dwell time data uploaded by the delivery object is 1 minute, which is greater than the continuous threshold. At this time, the delivery object has not continuously uploaded the arrival and departure times, and the dwell time data uploaded by the delivery object does not meet the filtering conditions and is retained.

[0106] For example, if the delivery person arrives within the GPS device's detection range at 10:37:00, reaches the resource delivery location at 10:40:10 and clicks the "Arrived" button, waits one minute at the resource delivery location to obtain the resources corresponding to the order to be delivered, clicks the "Pick Up" button at 10:41:10 and leaves the resource delivery location, and leaves the GPS device's detection range at 10:42:00, the delivery person's uploaded dwell data does not meet the filtering conditions and is retained.

[0107] Method 2: The IoT device waits and determines whether the delivery object continuously uploads its arrival and departure times if the interval between the departure time uploaded by the delivery object and the departure time obtained by the IoT device is less than a preset first value.

[0108] For example, when the IoT device determines that it is waiting, if the interval between the departure time uploaded by the delivery object and the departure time obtained by the IoT device is less than a preset first value, and the delivery object continuously uploads arrival and departure times, then the dwell data uploaded by the delivery object meets the filtering conditions, and the dwell data uploaded by the delivery object is filtered. For example, when the IoT device determines that it is waiting, if the interval between the departure time uploaded by the delivery object and the departure time obtained by the IoT device is greater than a preset first value, or if the delivery object does not continuously upload arrival and departure times, then the dwell data uploaded by the delivery object does not meet the filtering conditions, and the dwell data uploaded by the delivery object is retained.

[0109] In this context, "waiting time" for IoT devices refers to a situation where the dwell time data obtained from the IoT device exceeds a first waiting threshold. The meanings of the continuously uploaded arrival and departure times of the delivery object are consistent with those shown in judgment method one, and will not be elaborated further here. The acquisition process for the first value is similar to that shown in the above embodiments for acquiring the waiting threshold, and will not be elaborated further here. Optionally, the first value is set to 60 seconds.

[0110] Taking a first waiting threshold of 3 minutes, a continuous threshold of 10 seconds, and a first value of 60 seconds as an example, the implementation process of judgment method two is explained, with the delivery recipient uploading the arrival time by clicking the arrival button and the departure time by clicking the pick-up button.

[0111] In one possible scenario, the arrival time obtained from the IoT device is 10:37:00, the departure time obtained from the IoT device is 10:41:00, the arrival time uploaded by the delivery object is 10:40:10, the departure time uploaded by the delivery object is 10:40:19, and the dwell time obtained from the IoT device is 4 minutes, which is greater than the first waiting threshold. The IoT device judges it as waiting. While the IoT device judges it as waiting, the dwell time uploaded by the delivery object is 9 seconds, which is less than the continuous threshold, and the interval between the departure time uploaded by the delivery object and the departure time obtained from the IoT device is 41 seconds, which is less than 60 seconds. At this time, the dwell time uploaded by the delivery object meets the filtering conditions.

[0112] For example, a delivery person arrives within the detection range of an IoT device at 10:37:00, arrives at a resource delivery location at 10:38:00, waits for 2 minutes to obtain the resources corresponding to the order to be delivered, and then remembers that they haven't clicked the "Arrived" and "Pick Up" buttons when preparing to leave the resource delivery location. So they click the "Arrived" button at 10:40:10 and then click the "Pick Up" button at 10:40:19 before leaving the resource delivery location. They leave the detection range of the IoT device at 10:41:00. At this point, the dwell data uploaded by the delivery person meets the filtering conditions and needs to be filtered.

[0113] In one possible scenario, the arrival time obtained from the IoT device is 10:37:00, the departure time obtained from the IoT device is 10:41:00, the arrival time uploaded by the delivery object is 10:37:10, the departure time uploaded by the delivery object is 10:37:19, and the dwell time obtained from the IoT device is 4 minutes, which is greater than the first waiting threshold. The IoT device judges it as waiting. When the IoT device judges it as waiting, the dwell time uploaded by the delivery object is 9 seconds, which is less than the continuous threshold. The interval between the departure time uploaded by the delivery object and the departure time obtained from the IoT device is 221 seconds, which is greater than 60 seconds. At this time, the dwell time uploaded by the delivery object does not meet the filtering conditions and is retained.

[0114] For example, if a delivery person arrives within the detection range of an IoT device at 10:37:00, arrives at the resource delivery location at 10:37:10, finds that the resources corresponding to the order to be delivered are ready, clicks the "Arrived" button at 10:37:10, clicks the "Pick Up" button at 10:37:19, and then leaves the resource delivery location, leaving the detection range of the IoT device at 10:41:00, the dwell data uploaded by the delivery person at this time does not meet the filtering conditions and can be retained.

[0115] It should be noted that the above operation is only performed if the at least one retained stop data includes the stop data uploaded by the delivery recipient. If the at least one retained stop data does not include the stop data uploaded by the delivery recipient, the above operation will not be performed, and the stop duration will be determined based on the at least one retained stop data.

[0116] This application does not limit the method for determining the duration of stay. Optionally, when more than one set of stay data is retained, the latest arrival time among the retained arrival times is selected as the target arrival time, and the earliest departure time among the retained departure times is selected as the target departure time. Optionally, when only one set of stay data is retained, the retained arrival time is used as the target arrival time, and the retained departure time is used as the target departure time. The duration of stay is determined based on the target arrival time and the target departure time.

[0117] By acquiring multiple dwell time data from different sources and then using these data to determine the dwell time, erroneous dwell time data uploaded by the delivery recipient can be corrected, thus improving the accuracy of the final dwell time obtained.

[0118] In step 203, the target shipping time for the orders to be delivered is determined based on the dwell time and the initial shipping time.

[0119] This application does not limit the method of determining the target shipment time of an order to be delivered based on dwell time and initial shipment time. Methods include, but are not limited to: determining that the delivery object has not engaged in waiting behavior and has not left the resource delivery location multiple times based on dwell time, and using the initial shipment time as the target shipment time; or determining that the delivery object has engaged in waiting behavior based on dwell time, and using the target departure time of the delivery object as the target shipment time, with the target departure time determined based on the departure time of the delivery object. The process of determining the target departure time based on the departure time of the delivery object is described in the above embodiments and will not be repeated here.

[0120] For example, the process of determining the target delivery time is as follows: Figure 6 As shown, this includes, but is not limited to, the following two determining steps.

[0121] Step 1: Determine whether the initial shipment time meets the retention conditions.

[0122] In one possible implementation, before determining whether a delivery recipient is waiting based on dwell time, it's necessary to determine if the initial shipping time meets the retention criteria. Meeting the retention criteria means the resource provider's reported shipping is reliable, and the initial shipping time is no later than the target's departure time. The reliability of the resource provider's reported shipping is determined through multiple experiments. By conducting these experiments, the accuracy rate of the initial shipping time uploaded by the resource provider is obtained. Once the accuracy rate exceeds a reliability threshold, the resource provider is considered to have reported reliable shipping. The accuracy rate of the initial shipping time uploaded by the resource provider is determined when the initial shipping time is obtained. The reliability threshold can be set based on empirical values; for example, an 80% reliability threshold can be set.

[0123] For example, in multiple experiments retrieving shipping times, if 90% of the initial shipping times uploaded by resource provider A were selected as the target shipping time (accuracy rate of 90%), which is above the reliability threshold, then resource provider A's reported shipping times are reliable. Conversely, if 40% of the initial shipping times uploaded by resource provider B were selected as the target shipping time (accuracy rate of 40%), which is below the reliability threshold, then resource provider B's reported shipping times are unreliable.

[0124] Step 2: Based on the judgment result of Step 1, determine whether the delivery object is waiting. Based on the determination result, obtain the target delivery time.

[0125] Regarding the methods for determining whether a delivery recipient is waiting, based on different judgment results in step one, there are two methods, including but not limited to the following.

[0126] Method 1: If the initial shipment time meets the retention conditions, determine whether the target departure time - max (maximum) (target arrival time, initial shipment time) is greater than the first threshold.

[0127] Optionally, max(target arrival time, initial shipment time) selects the latest time between the target arrival time and the initial shipment time. For example, if the target arrival time is 10:35:00 and the initial shipment time is 10:36:00, then the initial shipment time is selected. Or, for another example, if the target arrival time is 10:35:00 and the initial shipment time is 10:34:00, then the target arrival time is selected.

[0128] Optionally, the first threshold can be obtained by weighted summation of the waiting thresholds for IoT devices (first waiting threshold), GPS devices (second waiting threshold), and the waiting threshold for the delivery object (third waiting threshold). In one possible implementation, obtaining the first threshold by weighted summation means obtaining the first threshold by providing the waiting thresholds corresponding to the devices providing the target arrival time and target departure time. For example, taking the arrival time obtained based on the IoT device as the target arrival time and the departure time obtained based on the GPS device as the target departure time, with the first waiting threshold being 3 minutes as shown in the above embodiment, the second waiting threshold being 5 minutes as shown in the above embodiment, the weight of the first waiting threshold being 0.6, and the weight of the second waiting threshold being 0.4, then the first threshold is 3 minutes × 0.6 + 5 minutes × 0.4 = 3.8 minutes. As another example, if the arrival time uploaded by the delivery object is selected as the target arrival time, and the departure time uploaded by the delivery object is selected as the target departure time, then the first threshold and the third waiting threshold have the same value.

[0129] The principle for obtaining the third waiting threshold is the same as that for the first waiting threshold, and will not be elaborated further here. The weighting of the waiting threshold for different devices can be set based on empirical values; this application does not impose any limitations on this.

[0130] Optionally, in response to the target departure time - max(target arrival time, initial shipping time) being greater than a first threshold, the delivery object engages in a waiting behavior, and the target departure time is used as the target shipping time.

[0131] In one possible scenario, the target arrival time is 10:35:00, the target departure time is 10:40:00, the initial shipment time is 10:36:00, and the first threshold is 3.8 minutes. Then, the target departure time - max(target arrival time, initial shipment time) equals the target departure time minus the initial shipment time, which is 4 minutes. This is greater than the first threshold, so the delivery object will wait, and the target departure time will be used as the target shipment time.

[0132] For example, if the delivery recipient arrives at the resource delivery location at 10:35:00, and the resource provider is still preparing the resources corresponding to the order to be delivered, at 10:36:00, in order to save time, the provider uploads the initial shipping time of the order to be delivered while processing other orders. However, the delivery recipient only obtains the resources corresponding to the order to be delivered at 10:40:00 and leaves the resource delivery location to deliver the order. In this case, the initial shipping time is unreliable, and the target departure time of the delivery recipient is selected as the target shipping time.

[0133] In one possible scenario, the target arrival time is 10:35:00, the target departure time is 10:40:00, the initial shipping time is 10:34:00, and the first threshold is 3.8 minutes. Then, the target departure time - max(target arrival time, initial shipping time) equals the target departure time minus the target arrival time, which is 5 minutes. Since this is greater than the first threshold, the delivery object will wait, and the target departure time will be used as the target shipping time.

[0134] For example, if the resource provider uploads the initial shipping time at 10:34:00, and the delivery recipient arrives at the resource delivery location at 10:35:00, it is discovered that the resource provider has not completed the preparation of the resources corresponding to the order to be delivered. After waiting for 5 minutes at the resource delivery location, the delivery recipient finally obtains the resources corresponding to the order to be delivered at 10:40:00 and leaves the resource delivery location to deliver the order. In this case, the initial shipping time is unreliable, and the target departure time of the delivery recipient is selected as the target shipping time.

[0135] Optionally, in response to the situation where the target departure time - max(target arrival time, initial shipment time) is not greater than the first threshold and the delivery object does not exhibit waiting behavior, it is determined whether the delivery object has left the resource delivery location multiple times.

[0136] In response to the delivery recipient not leaving the resource delivery location multiple times, the initial shipping time is used as the target shipping time. Multiple departures from the resource delivery location refer to the delivery recipient having multiple arrival and departure times within a certain time range, including but not limited to, the IoT device detecting that the delivery recipient arrives and leaves the resource delivery location multiple times within a certain time range, and the IoT device acquiring multiple arrival and departure times. Optionally, the certain time range can be set based on empirical values; this embodiment does not set such a range.

[0137] In one possible scenario, the target arrival time is 10:35:00, the target departure time is 10:36:00, the initial shipment time is 10:33:00, and the first threshold is 3.8 minutes. Then, the target departure time - max(target arrival time, initial shipment time) equals the target departure time minus the target arrival time, which is 1 minute, less than the first threshold. The delivery object did not exhibit any waiting behavior, and the delivery object did not leave the resource delivery location multiple times. Therefore, the initial shipment time is taken as the target shipment time.

[0138] For example, if the resource provider completes the preparation of the resources corresponding to the order to be delivered at 10:33:00, and the delivery person arrives at the resource delivery location at 10:35:00, spends 1 minute acquiring the resources corresponding to the order to be delivered, and leaves the resource delivery location at 10:36:00, then the initial shipping time is reliable and will be used as the target shipping time.

[0139] In one possible scenario, the target arrival time is 10:35:00, the target departure time is 10:40:00, the initial shipment time is 10:39:00, and the first threshold is 3.8 minutes. Then, the target departure time - max(target arrival time, initial shipment time) equals the target departure time minus the initial shipment time, which is 1 minute, less than the first threshold. The delivery object did not exhibit any waiting behavior, and the delivery object did not leave the resource delivery location multiple times. Therefore, the initial shipment time is taken as the target shipment time.

[0140] For example, if the delivery recipient arrives at the resource delivery location at 10:35:00 and finds that the resource provider has not yet prepared the resources corresponding to the order to be delivered, the resource provider stays at the delivery location for 4 minutes before finally completing the preparation and uploading the initial shipping time at 10:39:00. The delivery recipient then retrieves the resources for the order at 10:40:00 and leaves the delivery location. In this case, the delivery recipient did not engage in any waiting behavior after the resource provider uploaded the initial shipping time, indicating that the initial shipping time is reliable. Therefore, the initial shipping time is used as the target shipping time.

[0141] It should be noted that, as Figure 6 As shown in the examples above, there is also a situation where, based on the dwell time, it is determined that the delivery recipient did not engage in waiting behavior, but the delivery recipient left the resource delivery location multiple times. In this case, neither the initial delivery time nor the target departure time is reliable, and there is no target delivery time. For example, after arriving at the resource delivery location, the delivery recipient finds that the resource provider has not prepared the resources corresponding to the order to be delivered, and leaves the resource delivery location to retrieve the resources corresponding to other orders to be delivered. Meanwhile, the resource provider prepares the resources corresponding to the order to be delivered during the delivery recipient's absence. In this case, the target delivery time cannot be obtained.

[0142] Method 2: For cases where the initial shipment time does not meet the retention conditions, determine whether the target departure time minus the target arrival time is greater than the second threshold.

[0143] The second threshold is obtained in a similar manner to the first threshold, and will not be elaborated further here. Optionally, in response to the target departure time minus the target arrival time being greater than the second threshold, the delivery object engages in waiting behavior, and the target departure time of the delivery object is taken as the target shipment time.

[0144] In one possible scenario, the target arrival time is 10:35:00, the target departure time is 10:40:00, the second threshold is 3.5 minutes, and the target departure time minus the target arrival time equals 5 minutes, which is greater than the second threshold. In this case, the delivery recipient will engage in waiting behavior, and the target departure time will be used as the target shipment time.

[0145] For example, if the delivery object arrives at the resource delivery location at 10:35:00, and the resource provider is still preparing the resources corresponding to the order to be delivered, and the delivery object waits for 5 minutes before obtaining the resources corresponding to the order to be delivered at 10:40:00 and leaving the resource delivery location, the delivery object's target departure time can be used as the target shipment time.

[0146] Optionally, such as Figure 6 As shown, in response to the target departure time minus the target arrival time not exceeding a second threshold, the delivery object does not engage in waiting behavior, and there is no target shipping time. For example, the resource provider completes the preparation of the resources corresponding to the order to be delivered before the delivery object arrives, but fails to upload the initial shipping time in a timely manner. After arriving at the resource delivery location, the delivery object finds that the resources corresponding to the order to be delivered are already prepared, acquires them, and immediately leaves the resource delivery location. The resource provider only uploads the initial shipping time after the delivery object has left. In this case, neither the initial shipping time nor the target departure time can be used as the target shipping time.

[0147] It should be noted that, in addition to being used when the initial shipping time does not meet the retention conditions, method two can also be used when the resource provider has not uploaded the initial shipping time.

[0148] In summary, the embodiments of this application obtain multiple dwell times data of delivery objects at resource delivery locations from different sources, and then determine the dwell time based on multiple dwell times data. This can effectively correct erroneous dwell times uploaded by delivery objects and improve the accuracy of the obtained dwell times. The target shipping time determined based on the more accurate dwell time and initial shipping time has a higher accuracy rate. In addition, for cases where there is no initial shipping time, when the dwell time of the delivery object is less than the second threshold, the target departure time can also be selected as the target shipping time, which improves order coverage while ensuring high accuracy.

[0149] In one possible implementation, see details. Figure 7 , Figure 7 A flowchart for obtaining the shipping time is shown, with an example of the method being applied to a terminal.

[0150] Step 701: Obtain the initial shipping time and obtain multiple dwell times data of the delivery object.

[0151] For example, the resource provider obtains the initial delivery time uploaded by the food delivery application on the first terminal, the delivery object obtains the dwell data uploaded by the food delivery application on the second terminal, the GPS device on the second terminal obtains the dwell data uploaded by the second terminal, and the IoT device on the second terminal obtains the dwell data uploaded by the second terminal.

[0152] Step 702: Retain at least one stop data point from the multiple stop data points.

[0153] For example, if the three stop data do not conflict with each other, the three stop data are retained; if the stop data uploaded by the delivery object meets the filtering conditions, the stop data uploaded by the delivery object is filtered.

[0154] Step 703: Determine the duration of stay based on the retained stay data.

[0155] For example, the arrival time uploaded by the IoT device is selected as the target arrival time, and the departure time uploaded by the GPS device is selected as the target departure time. The duration of stay is determined based on the target arrival time and the target departure time.

[0156] Step 704: Determine the target shipping time based on the dwell time and the initial shipping time.

[0157] For example, if the initial shipping time does not meet the retention conditions and the dwell time is less than the second threshold, then the target departure time is taken as the target shipping time.

[0158] See Figure 8 This application provides an apparatus for obtaining shipping time, which includes: an acquisition module 801 and a determination module 802.

[0159] The acquisition module 801 is used to acquire the initial shipping time of the orders to be delivered;

[0160] The acquisition module 801 is also used to acquire the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location, where the resource delivery location is the location where the delivery object acquires the resource corresponding to the order to be delivered;

[0161] The determination module 802 is used to determine the target shipping time for orders to be delivered based on the dwell time and the initial shipping time.

[0162] Optionally, the acquisition module 801 is used to acquire multiple dwell times of the delivery object at the resource delivery location. The multiple dwell times are acquired from different sources, and each dwell time includes the arrival time and departure time of the delivery object. The dwell time is determined based on the multiple dwell times.

[0163] Optionally, the acquisition module 801 is used to, in response to a situation where multiple stay data conflict with each other, retain at least one stay data among the multiple stay data based on priority, and determine the stay duration based on at least one stay data.

[0164] Optionally, the acquisition module 801 is configured to, in response to at least one dwell data including dwell data uploaded by the delivery object, and the dwell data uploaded by the delivery object satisfying the filtering conditions, filter the dwell data uploaded by the delivery object; and determine the dwell duration based on the filtered dwell data.

[0165] Optionally, the determination module 802 is used to determine, based on the dwell time, that the delivery object has not engaged in waiting behavior and has not left the resource delivery location multiple times, and to use the initial delivery time as the target delivery time.

[0166] Optionally, the determining module 802 is used to determine the waiting behavior of the delivery object based on the dwell time, and to take the target departure time of the delivery object as the target delivery time, wherein the target departure time is determined based on the departure time of the delivery object.

[0167] After obtaining the initial shipping time, the device also obtains the dwell time of the delivery object at the resource delivery location. Since the dwell time can indirectly reflect whether the resource provider has shipped, the target shipping time can be determined based on the dwell time and the initial shipping time, thus improving the accuracy of the target shipping time.

[0168] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0169] Figure 9 This is a schematic diagram of a server structure provided in an embodiment of this application. The server can vary significantly due to differences in configuration or performance. It may include one or more Central Processing Units (CPUs) 901 and one or more memories 902. The one or more memories 902 store at least one computer program, which is loaded and executed by the one or more processors 901 to enable the server to implement the methods for obtaining shipping time provided in the various method embodiments described above. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated upon here.

[0170] Figure 10This is a schematic diagram of a device structure for obtaining shipping time according to an embodiment of this application. The device can be a terminal, such as a smartphone, tablet, MP3 (Moving Picture Experts Group Audio Layer III) player, MP4 (Moving Picture Experts Group Audio Layer IV) player, laptop, or desktop computer. The terminal may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0171] Typically, a terminal includes a processor 1001 and a memory 1002.

[0172] Processor 1001 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1001 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1001 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), 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 1001 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the screen. In some embodiments, processor 1001 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0173] The memory 1002 may include one or more computer-readable storage media, which may be non-transitory. The memory 1002 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 1002 are used to store at least one instruction, which is executed by the processor 1001 to cause the terminal to implement the method for obtaining shipping time provided in the method embodiments of this application.

[0174] In some embodiments, the terminal may also optionally include: a peripheral device interface 1003 and at least one peripheral device. The processor 1001, memory 1002, and peripheral device interface 1003 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1003 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of: a radio frequency circuit 1004, a display screen 1005, a camera assembly 1006, an audio circuit 1007, a positioning assembly 1008, and a power supply 1009.

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

[0176] The radio frequency (RF) circuit 1004 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1004 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1004 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1004 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 1004 can communicate with other terminals via at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: metropolitan area networks (MANs), various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks (WLANs), and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1004 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

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

[0178] The camera assembly 1006 is used to acquire images or videos. Optionally, the camera assembly 1006 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1006 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 refers to a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0179] The audio circuit 1007 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 the processor 1001 for processing, or input to the radio frequency circuit 1004 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1001 or the radio frequency circuit 1004 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, the audio circuit 1007 may also include a headphone jack.

[0180] The positioning component 1008 is used to determine the current geographical location of the terminal in order to enable navigation or LBS (Location Based Service). The positioning component 1008 can be a positioning component based on the US GPS (Global Positioning System), China's BeiDou system, Russia's Granas system, or the EU's Galileo system.

[0181] The power supply 1009 is used to power the various components in the terminal. The power supply 1009 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When the power supply 1009 includes a rechargeable battery, the rechargeable battery can support wired or wireless charging. The rechargeable battery can also be used to support fast charging technology.

[0182] In some embodiments, the terminal further includes one or more sensors 1010. The one or more sensors 1010 include, but are not limited to: an accelerometer 1011, a gyroscope 1012, a pressure sensor 1013, a fingerprint sensor 1014, an optical sensor 1015, and a proximity sensor 1016.

[0183] Accelerometer 1011 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by the terminal. For example, accelerometer 1011 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 1001 can control display screen 1005 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1011. Accelerometer 1011 can also be used for games or for acquiring user motion data.

[0184] The gyroscope sensor 1012 can detect the terminal's orientation and rotation angle. The gyroscope sensor 1012 can work in conjunction with the accelerometer sensor 1011 to collect the user's 3D movements on the terminal. Based on the data collected by the gyroscope sensor 1012, the processor 1001 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.

[0185] The pressure sensor 1013 can be disposed on the side bezel of the terminal and / or the lower layer of the display screen 1005. When the pressure sensor 1013 is disposed on the side bezel of the terminal, it can detect the user's grip signal on the terminal, and the processor 1001 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1013. When the pressure sensor 1013 is disposed on the lower layer of the display screen 1005, the processor 1001 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 1005. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0186] The fingerprint sensor 1014 is used to collect a user's fingerprint. The processor 1001 identifies the user based on the fingerprint collected by the fingerprint sensor 1014, or vice versa. When the user's identity is identified as trusted, the processor 1001 authorizes the user to perform relevant sensitive operations, including unlocking the screen, viewing encrypted information, downloading software, making payments, and changing settings. The fingerprint sensor 1014 can be located on the front, back, or side of the terminal. When the terminal has physical buttons or a manufacturer's logo, the fingerprint sensor 1014 can be integrated with the physical buttons or the manufacturer's logo.

[0187] An optical sensor 1015 is used to collect ambient light intensity. In one embodiment, the processor 1001 can control the display brightness of the display screen 1005 based on the ambient light intensity collected by the optical sensor 1015. Specifically, when the ambient light intensity is high, the display brightness of the display screen 1005 is increased; when the ambient light intensity is low, the display brightness of the display screen 1005 is decreased. In another embodiment, the processor 1001 can also dynamically adjust the shooting parameters of the camera assembly 1006 based on the ambient light intensity collected by the optical sensor 1015.

[0188] The proximity sensor 1016, also known as a distance sensor, is typically mounted on the front panel of a terminal. The proximity sensor 1016 is used to detect the distance between the user and the front of the terminal. In one embodiment, when the proximity sensor 1016 detects that the distance between the user and the front of the terminal is gradually decreasing, the processor 1001 controls the display screen 1005 to switch from a screen-on state to a screen-off state; when the proximity sensor 1016 detects that the distance between the user and the front of the terminal is gradually increasing, the processor 1001 controls the display screen 1005 to switch from a screen-off state to a screen-on state. Those skilled in the art will understand that... Figure 10 The structure shown does not constitute a limitation on the equipment for obtaining delivery time and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0189] In an exemplary embodiment, a computer device is also provided, comprising a processor and a memory storing at least one computer program. The at least one computer program is loaded and executed by one or more processors to enable the computer device to implement any of the methods described above for obtaining shipping time.

[0190] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one computer program that is loaded and executed by a processor of a computer device to enable the computer to implement any of the methods described above for obtaining the shipping time.

[0191] In one possible implementation, the aforementioned computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0192] In an exemplary embodiment, a computer program product or computer program is also provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform any of the methods described above for obtaining the shipping time.

[0193] It should be noted that all information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in this application are authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the initial shipping times of orders awaiting delivery involved in this application were obtained with full authorization.

[0194] 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.

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

Claims

1. A method for obtaining shipping time, characterized in that, The method includes: Obtain the initial shipping time for orders awaiting delivery; The duration of the delivery object corresponding to the order to be delivered is obtained at the resource delivery location, where the resource delivery location is the location where the delivery object obtains the resource corresponding to the order to be delivered. Based on the dwell time and the initial shipping time, the target shipping time for the order to be delivered is determined; Determining the target shipping time for the orders to be delivered includes: Determine whether the initial shipment time meets the retention conditions. The retention conditions are that the shipment reported by the resource provider is reliable and the initial shipment time is not later than the target departure time. The reliability of the shipment reported by the resource provider is based on the fact that the accuracy of the initial shipment time uploaded by the resource provider is higher than the reliability threshold, which was determined by multiple experiments. In response to the initial shipment time satisfying the retention condition, it is determined whether the larger value of the target departure time minus the target arrival time and the initial shipment time is greater than a first threshold. The first threshold is obtained by weighted summation to provide the waiting threshold corresponding to the device with the target arrival time and the target departure time. In response to the fact that the larger of the target departure time minus the target arrival time and the initial shipment time is greater than the first threshold, the target departure time is taken as the target shipment time; If the larger of the target departure time minus the target arrival time and the initial shipment time is not greater than the first threshold, it is determined whether the delivery object has left the resource delivery location multiple times. If the delivery object has not left the resource delivery location multiple times, the initial shipment time is taken as the target shipment time. In response to the initial shipment time not meeting the retention condition, it is determined whether the target departure time minus the target arrival time is greater than a second threshold. In response to the target departure time minus the target arrival time being greater than the second threshold, the target departure time is taken as the target shipment time.

2. The method according to claim 1, characterized in that, The step of obtaining the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location includes: The system acquires multiple dwell times of the delivery object at the resource delivery location. These multiple dwell times are acquired from different sources, and each dwell time includes the arrival and departure times of the delivery object. The duration of stay is determined based on the multiple stay data.

3. The method according to claim 2, characterized in that, Determining the duration of stay based on the multiple stay data includes: In response to a conflict among the multiple stay data, at least one stay data is retained based on priority, and the stay duration is determined based on the at least one stay data.

4. The method according to claim 3, characterized in that, Determining the duration of stay based on the at least one stay data includes: In response to the fact that the at least one dwell data includes dwell data uploaded by the delivery object, and the dwell data uploaded by the delivery object meets the filtering conditions, the dwell data uploaded by the delivery object is filtered. The duration of stay is determined based on the filtered stay data.

5. The method according to any one of claims 1-4, characterized in that, Determining the target shipping time for the order to be delivered based on the dwell time and the initial shipping time includes: Based on the dwell time, it is determined that the delivery object did not engage in waiting behavior and did not leave the resource delivery location multiple times, and the initial shipping time is taken as the target shipping time.

6. The method according to any one of claims 2-4, characterized in that, Determining the target shipping time for the order to be delivered based on the dwell time and the initial shipping time includes: Based on the dwell time, it is determined that the delivery object is in a waiting state, and the target departure time of the delivery object is taken as the target shipment time. The target departure time is determined based on the departure time of the delivery object.

7. An apparatus for obtaining delivery time, characterized in that, The device includes: The acquisition module is used to obtain the initial shipping time of orders to be delivered; The acquisition module is further configured to acquire the dwell time of the delivery object corresponding to the order to be delivered at the resource delivery location, wherein the resource delivery location is the location where the delivery object acquires the resource corresponding to the order to be delivered; The determination module is used to determine the target shipping time for the order to be delivered based on the dwell time and the initial shipping time; Specifically, the determining module is used for: Determine whether the initial shipment time meets the retention conditions. The retention conditions are that the shipment reported by the resource provider is reliable and the initial shipment time is not later than the target departure time. The reliability of the shipment reported by the resource provider is based on the fact that the accuracy of the initial shipment time uploaded by the resource provider is higher than the reliability threshold, which was determined by multiple experiments. In response to the initial shipment time satisfying the retention condition, it is determined whether the larger value of the target departure time minus the target arrival time and the initial shipment time is greater than a first threshold. The first threshold is obtained by weighted summation to provide the waiting threshold corresponding to the device with the target arrival time and the target departure time. In response to the fact that the larger of the target departure time minus the target arrival time and the initial shipment time is greater than the first threshold, the target departure time is taken as the target shipment time; If the larger of the target departure time minus the target arrival time and the initial shipment time is not greater than the first threshold, it is determined whether the delivery object has left the resource delivery location multiple times. If the delivery object has not left the resource delivery location multiple times, the initial shipment time is taken as the target shipment time. In response to the initial shipment time not meeting the retention condition, it is determined whether the target departure time minus the target arrival time is greater than a second threshold. In response to the target departure time minus the target arrival time being greater than the second threshold, the target departure time is taken as the target shipment time.

8. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to enable the computer device to implement the method for obtaining shipping time as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one computer program, which is loaded and executed by a processor to enable the computer to implement the method for obtaining shipping time as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program or instructions that are executed by a processor to enable a computer to implement the method for obtaining shipping time as described in any one of claims 1 to 6.

Images