Delivery driver management method and system

Abstract

A method and system are provided for managing delivery personnel based on the results of determining whether a delivery person will perform a target action unrelated to a specific delivery while performing that specific delivery. A delivery personnel management method according to one embodiment of the present disclosure may include the steps of: acquiring trajectory information relating to a delivery person's specific delivery; identifying a slow trajectory segment based on the trajectory information; and determining whether the identified slow trajectory segment is associated with a target action unrelated to the specific delivery.

Description

Technical Field

[0001] The present disclosure relates to a delivery staff management method and its system. More specifically, it relates to a method and its system for managing a delivery staff by determining whether the delivery staff performs a target action unrelated to a specific delivery when performing the specific delivery and managing the delivery staff based on the result.

Background Art

[0002] With the emergence of delivery platforms, delivery services are more widely used than in the past. Delivery platforms generally provide users with an estimated delivery time, but delays in delivery compared to the estimated delivery time often occur. In such cases, especially in the delivery of food and beverages, it has an adverse impact on the user experience of the delivery platform.

[0003] Delays in delivery compared to the estimated delivery time can occur when a delivery staff uses multiple delivery platforms to perform deliveries. For example, while a delivery staff accepts a request for a first delivery using a first delivery platform and is in the process of performing it, and then separately accepts a request for a second delivery using a second delivery platform in order to increase their income, and then performs the first delivery and the second delivery together, a route unrelated to the performance of the first delivery, that is, a route for performing the second delivery, will occur, so there is a possibility that the first delivery will be delayed compared to the original estimated delivery time.

[0004] From the perspective of delivery platform operators, it is necessary to minimize such situations, so it is necessary to monitor whether the delivery is being performed normally (or honestly). According to the prior art, such monitoring is performed using methods such as analyzing information such as the difference between the estimated delivery time and the actual delivery time, the difference between the estimated delivery distance and the actual delivery distance, or analyzing information such as the similarity between a reasonable delivery route, for example, a route recommended by a navigation system, and the actual delivery route.

[0005] However, discrepancies between estimated and actual delivery times, estimated and actual delivery distances, and reasonable and actual delivery routes can occur in a variety of normal circumstances, such as when delivery personnel detour due to road conditions or weather at the time of delivery, when unexpected situations such as accidents occur during delivery, or when they use their own preferred or familiar routes. Therefore, the conventional methods described above have the problem of not being able to accurately monitor whether deliveries are being carried out normally (or honestly). [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Korean Registered Patent No. 10-1876713 (Published April 26, 2018) [Overview of the project] [Problems that the invention aims to solve]

[0007] The technical problem that some embodiments of this disclosure aim to solve is to provide a method for determining whether a delivery person will perform a target action unrelated to a specific delivery while performing that specific delivery, and a system to which this method is applied.

[0008] Another technical problem that some embodiments of this disclosure seek to solve is to provide a method for identifying slow trajectory segments based on trajectory information relating to a particular delivery, and for determining whether such slow trajectory segments are associated with target behavior unrelated to the particular delivery, and a system to which this method is applied.

[0009] Another technical problem that some embodiments of this disclosure seek to solve is to provide a method for managing delivery personnel based on the above-mentioned decisions and a system to which this method is applied.

[0010] The technical challenges of this disclosure are not limited to those described above, and other technical challenges not mentioned can be clearly understood by a person of the ordinary skill in the art of this disclosure from the following description. [Means for solving the problem]

[0011] A delivery person management method according to one embodiment of the present disclosure for solving the aforementioned technical problems may include the steps of: acquiring trajectory information relating to a specific delivery by a delivery person; identifying a slow trajectory segment based on the trajectory information; and determining whether the identified slow trajectory segment is associated with a target behavior unrelated to the specific delivery.

[0012] In one embodiment, the step of identifying the slow-speed trajectory segment may include identifying a section in which the average travel speed of the delivery person is less than a first threshold as the slow-speed trajectory segment. In this case, the first threshold may be determined based on the attributes of the road and the delivery means of the delivery person.

[0013] In one embodiment, the step of identifying a low-speed trajectory segment may include the steps of identifying a section in which the average travel speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment, and identifying the candidate low-speed trajectory segment as the low-speed trajectory segment if a predetermined proportion or more of the section contains points in which the travel speed of the delivery person is less than the second threshold, and the second threshold is less than or equal to the first threshold.

[0014] In one embodiment, the step of determining whether or not the target behavior is associated with the target behavior may include the step of determining whether or not the target behavior is associated with the change in the direction of movement of the delivery person within the slow trajectory segment.

[0015] In one embodiment, the step of determining whether or not a segment is related to the target behavior may include the step of determining whether or not a segment is related to the target behavior based on the distance between the road and the delivery person within the slow-speed trajectory segment. In this case, the step of determining whether or not a segment is related to the target behavior based on the distance between the road and the delivery person within the slow-speed trajectory segment may include the step of determining that a slow-speed trajectory segment is related to the target behavior if a predetermined proportion or more of the segments within the slow-speed trajectory segment contain points where the distance between the road and the delivery person is greater than or equal to a predetermined threshold. The threshold may be determined based on the attributes of the road.

[0016] In one embodiment, the step of determining whether or not the target behavior is associated with the target behavior may include the step of determining whether or not the target behavior is associated with the type of location corresponding to the slow trajectory segment.

[0017] In one embodiment, the delivery person management method may further include the step of determining the delivery person to be subject to action if the identified slow trajectory segment is determined to be associated with the target behavior.

[0018] A delivery driver management system according to another embodiment of the present disclosure for solving the aforementioned technical problems may include a communication interface, a memory on which a computer program is loaded, and a processor for executing the computer program. The computer program may include instructions for acquiring trajectory information relating to a specific delivery by a delivery driver, instructions for identifying slow trajectory segments based on the trajectory information, and instructions for determining whether the identified slow trajectory segments are associated with target behavior unrelated to the specific delivery.

[0019] In one embodiment, the instruction for identifying the low-speed trajectory segment may include an instruction for identifying a section where the average moving speed of the delivery person is less than a first threshold as the low-speed trajectory segment. At this time, the instruction for identifying as the low-speed trajectory segment may include an instruction for identifying a section where the average moving speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment, and an instruction for identifying the candidate low-speed trajectory segment as the low-speed trajectory segment when a predetermined ratio or more of points where the moving speed of the delivery person is less than a second threshold is included within the section, where the second threshold is a value not exceeding the first threshold.

[0020] In one embodiment, the instruction for determining whether it is related to the target behavior may include an instruction for determining whether it is related to the target behavior based on a change in the moving direction of the delivery person within the low-speed trajectory segment.

[0021] In one embodiment, when it is determined that the identified low-speed trajectory segment is related to the target behavior, the delivery person management system may further include an instruction for determining the delivery person as a measure target.

Brief Description of Drawings

[0022] [Figure 1] It is a configuration diagram of an overall system according to an embodiment of the present disclosure. [Figure 2] It is a flowchart of a delivery person management method according to an embodiment of the present disclosure. [Figure 3] It is a flowchart for explaining some operations of a delivery person management method according to an embodiment of the present disclosure. [Figure 4] It is a conceptual diagram for explaining a process of determining whether a low-speed trajectory segment identified according to an embodiment of the present disclosure is related to a target behavior. [Figure 5] It is a conceptual diagram for explaining a process of determining whether a low-speed trajectory segment identified according to an embodiment of the present disclosure is related to a target behavior. [Figure 6] It is a conceptual diagram for explaining the process of determining whether a low - speed trajectory segment identified according to an embodiment of the present disclosure is related to a target behavior. [Figure 7] It is a hardware configuration diagram of a computing system described in some embodiments of the present disclosure.

Embodiments for Carrying out the Invention

[0023] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The advantages and features of the present invention, as well as the methods for achieving them, will become clear by referring to the embodiments described in detail later together with the attached drawings. However, the technical idea of the present invention is not limited to the following embodiments, and can be realized in various different forms. The following embodiments are merely to complete the technical idea of the present invention and to fully inform those with ordinary knowledge in the technical field to which the present invention belongs of the scope of the present invention. The technical idea of the present invention is defined only by the scope of the claims.

[0024] In describing various embodiments of the present disclosure, when it is determined that a specific description of a related known configuration or function obscures the gist of the present invention, the detailed description thereof will be omitted.

[0025] Unless otherwise defined, the terms (including technical and scientific terms) used in the following embodiments are used in a meaning commonly understood by those having ordinary knowledge in the technical field to which the present disclosure belongs. However, this may vary depending on the intention or precedent of those skilled in the relevant field, the emergence of new technologies, etc. The terms used in the present disclosure are for explaining the embodiments and are not intended to limit the scope of the present disclosure.

[0026] The singular expressions used in the following embodiments include plural concepts unless specifically identified as singular in the context. Also, plural expressions include singular concepts unless specifically identified as plural in the context.

[0027] Furthermore, terms such as First, Second, A, B, (a), (b), etc., used in the following embodiments are used solely to distinguish one component from another, and the nature, order, or sequence of the component in question is not limited by these terms.

[0028] Various embodiments of this disclosure will be described in detail below with reference to the attached drawings.

[0029] Figure 1 is a diagram showing the overall system configuration according to one embodiment of the present disclosure.

[0030] The configuration and operation of the overall system according to one embodiment of the present disclosure will be described below with reference to Figure 1. As shown in Figure 1, the overall system according to this embodiment may consist of a delivery driver management system 10, and in some embodiments, may further consist of a database 20 and at least a portion of the delivery driver terminal 30.

[0031] Furthermore, although Figure 1 shows the delivery driver management system 10 as separate from the database 20 and the delivery driver terminal 30 for illustrative purposes, it is obvious to those skilled in the art that at least part of the configuration and / or functions of the delivery driver management system 10 can be implemented within the database 20 and / or the delivery driver terminal 30. The delivery driver management system 10 may also be configured using one or more physical servers included in a server farm based on cloud technology such as virtual machines.

[0032] Database 20 may be implemented as one or more computer systems that collect, store, and / or manage diverse geographical information and / or trajectory information relating to a specific delivery, which is necessary to determine whether a slow trajectory segment identified by one embodiment of the present disclosure is associated with target behavior unrelated to a specific delivery.

[0033] Geographic information may include, for example, map information regarding roads, buildings, and the surrounding environment; information regarding the attributes of roads; and information regarding the type of place to which a particular point or area belongs. Here, information regarding the attributes of roads may include information such as the type of road, which can be classified into general roads, expressways, alleys, slopes, intersections, three-way intersections, etc., as well as information such as the number of lanes on the road and the width of the road. Furthermore, information regarding the type of place may include information such as whether the place is a residential area, whether it is a building containing restaurants, whether there are restaurants within a certain distance from the surrounding area, or whether it is a quiet park or roadside area with little relevance to food delivery.

[0034] The delivery person terminal 30 is a terminal used by a delivery person to carry out deliveries, and is equipped with the function to transmit the delivery person's location to the database 20 and / or the delivery person management system 10 using various known positioning technologies such as GNSS (Global Navigation Satellite System) based positioning technology and beacon based positioning technology. Examples include smartphones, wearable devices, and navigation devices. However, the type of delivery person terminal 30 and the type of positioning technology are not limited to those described above and can be varied in various ways to achieve the purpose of this disclosure.

[0035] The database 20 and / or the delivery person terminal 30 can communicate with the delivery person management system 10 via a communication network (not shown). In some cases, the database 20 and the delivery person terminal 30 can also communicate directly via the communication network. The communication network can be any type of wired / wireless network, such as a local area network (LAN), wide area network (WAN), mobile radio communication network, or Wibro (Wireless Broadband Internet).

[0036] The delivery information manager 11 can receive and / or collect information from the delivery person terminal 30, such as the location of the delivery person at a specific point in time, information about a specific delivery performed by the delivery person, such as the time / location of acceptance of the delivery request, the place where the delivered goods were received, intermediate stops, delivery destination, and means of delivery (motorcycle, car, etc.), process this information as trajectory information for that specific delivery, and transmit it to the database 20 and / or trajectory information analyzer 100.

[0037] Here, the trajectory information for a specific delivery refers to the route taken by the delivery person and the speed of movement at each point where the delivery person's position is received, from the time the delivery person accepts the request for that specific delivery until they arrive at the delivery destination or deliver the goods, as time progresses. Generally, the delivery person's position is received at regular time intervals, so by using the delivery person's position received before (t-1, t-2, etc.) and / or after (t+1, t+2, etc.) the time (t) when the delivery person's position is received, the speed of movement of the delivery person at a specific point in time (t), i.e., the speed of movement at each point, can be calculated.

[0038] Furthermore, a specific delivery does not necessarily mean that a single delivery is performed. If multiple delivery requests are accepted and performed simultaneously using the same delivery platform, it may refer to those deliveries performed at once. When multiple deliveries are performed simultaneously, there may be multiple transit points.

[0039] The locations shown in Figures 4 through 6 (for example, 520-1, 520-2, 610-1 through 610-5, etc.) conceptually represent a portion of the trajectory related to a specific delivery. Furthermore, the terms "location" as described above and below may sometimes be referred to as "points" depending on the context, but locations and points can be understood as the same concept.

[0040] Referring again to Figure 1, in some embodiments, the delivery information manager 11 can generate trajectory information for a specific delivery by performing predetermined preprocessing and filtering on raw data regarding the delivery person's location in order to obtain more accurate trajectory information analysis results. For example, the delivery information manager 11 can correct the received location or process the data so that abnormal location information (e.g., location information where the speed of movement increases abnormally) is not included in the trajectory information.

[0041] The trajectory information analyzer 100 can determine whether a delivery person engages in target behavior unrelated to a specific delivery while performing that delivery, by analyzing the trajectory information of a delivery person related to that specific delivery. For example, the trajectory information analyzer 100 can acquire trajectory information related to a delivery person's specific delivery and identify slow trajectory segments based on the trajectory information. Subsequently, it can determine whether the identified slow trajectory segments are related to target behavior unrelated to the specific delivery.

[0042] Here, "target behavior unrelated to a specific delivery" refers to actions that a delivery person may take while performing a specific delivery but that are not considered to fall within the normal range of behavior. For example, an action that suggests a delivery person is using the first delivery platform to accept a request for the first delivery and is in the process of performing the first delivery, while simultaneously using the second delivery platform to accept a request for the second delivery and performing both the first and second deliveries, could fall under this category of target behavior.

[0043] Such targeted behaviors may include actions such as staying at a location other than the designated delivery location or destination where the delivery person needs to remain in order to complete a specific delivery. However, the problem is that such actions do not always qualify as targeted behavior. For example, a delivery person may stay at such a location in a wide variety of situations, such as temporarily stopping to make a phone call during a delivery, waiting for a traffic light to change at an intersection, or causing a traffic jam due to a nearby accident. It is difficult to recognize such instances of staying at a location as targeted behavior.

[0044] According to embodiments of this disclosure, such target behavior can be detected accurately and efficiently, and a detailed description of such embodiments will follow later.

[0045] In some embodiments, the delivery driver manager 12 can determine that a delivery driver is subject to action if it determines that a slow trajectory segment identified based on the trajectory information of a delivery driver's specific delivery is associated with target behavior. In some cases, only delivery drivers who are determined to be subject to such action at a predetermined frequency or more may be designated as subject to such action.

[0046] In some embodiments, the delivery driver manager 12 can also perform functions such as sending a warning message to the delivery driver subject to action, blocking the delivery platform so that it cannot be used any further or for a predetermined period of time, or causing other systems / devices to take such action.

[0047] The delivery driver management system 10 is configured to include the trajectory information analyzer 100 described above, and in some embodiments, it may further include at least a portion of the delivery information manager 11 and the delivery driver manager 12.

[0048] Each of the trajectory information analyzer 100, the delivery information manager 11, and the delivery person manager 12 may be implemented as its own computing system, or at least parts of the trajectory information analyzer 100, the delivery information manager 11, and the delivery person manager 12 may be implemented together through a single computing system.

[0049] The configuration and operation of the overall system according to this embodiment have been described above. In particular, the operation of the trajectory information analyzer 100 can be understood in more detail by the embodiments described later. That is, the operation of the trajectory information analyzer 100 can be supplemented by the embodiments described later.

[0050] Next, a delivery person management method according to one embodiment of the present disclosure will be described with reference to Figures 2 to 7. The delivery person management method according to this embodiment can be executed by one or more computing systems. Furthermore, in the delivery person management method according to this embodiment, some operations may be performed by a first computing system and the remaining operations may be performed by a second computing system.

[0051] For example, some operations of the delivery person management method according to this embodiment may be performed by an on-premise physical server, while the remaining operations may be performed by a cloud server. In the following, if the entity executing each operation is omitted, it can be understood that the entity executing it is the computing system.

[0052] First, the delivery person management method according to this embodiment will be briefly explained with reference to Figure 2. Detailed information on each stage will be described later as needed. Trajectory information related to a specific delivery by a delivery person is acquired (S100), and a low-speed trajectory segment is identified based on the acquired trajectory information (S200).

[0053] A low-speed trajectory segment refers to a portion of the overall trajectory that can be generated by a delivery person performing a specific delivery, where the speed is relatively low. In some embodiments, if there is a portion of the overall trajectory where the average speed of the delivery person is below a first threshold, that portion can be identified as a low-speed trajectory segment (S200).

[0054] Here, the first threshold is determined based on the attributes of the road and the delivery means of the delivery person. For example, various first thresholds may be set for each of the various combinations of road types such as expressways, general roads, alleys, slopes, intersections, and three-way intersections, and delivery means such as automobiles, motorcycles, bicycles, and walking.

[0055] Figures 4 through 6 are conceptual diagrams showing a portion of the delivery person's trajectory related to a specific delivery. It should be understood that Figures 4 through 6 merely visually represent the delivery person's location (points such as 520-1, 520-2, etc.) and trajectory (set of points) to aid understanding, and that such points / trajectories may not necessarily be depicted on an actual digital map.

[0056] Figure 4 conceptually illustrates a scenario in which a delivery person moves along road 400 from right to left (402 and 401), with the trajectory based on the delivery person's position shown as dots. Generally, since the delivery person's position is received at regular time intervals, the average speed of the delivery person in sections with relatively wide dot intervals (410 and 430) will be faster than the average speed in section 420 with relatively narrow dot intervals. Furthermore, if the average speed in section 420 is below a first threshold determined based on the attributes of road 400 and the delivery person's means of delivery, section 420 may be identified as a low-speed trajectory segment.

[0057] Figure 5 conceptually illustrates a scenario in which a delivery person makes a left turn (501, 502, and 503) at a three-way intersection 500, with the delivery person's trajectory represented by points (520-1, 520-2, 530-1, 530-2, etc.). Similar to Figure 4, the average speed of the delivery person in sections with relatively wide spacing between points (510 and 530) may be faster than the average speed in section 520 with relatively narrow spacing between points. Furthermore, if the average speed in section 520 is below a first threshold determined based on the attributes of road 500 and the delivery person's means of delivery, section 520 may be identified as a low-speed trajectory segment.

[0058] Figure 6 conceptually illustrates a scenario in which a delivery person visits restaurants 610 (601, 602, and 603) located slightly off road 600, with the delivery person's trajectory shown as points (610-1 to 610-5, etc.). Figure 6 is a magnified conceptual illustration of a slow trajectory segment identified in one embodiment of the present disclosure, and all points shown in Figure 6 (610-1 to 610-5, etc.) may be included in such a slow trajectory segment.

[0059] In some embodiments, slow-speed trajectory segments may be merged with other slow-speed trajectory segments. For example, if the first slow-speed trajectory segment and the second slow-speed trajectory segment are close in time and space, they may be merged and identified as a single slow-speed trajectory segment.

[0060] In some other embodiments, after identifying candidate slow-speed trajectory segments, slow-speed trajectory segments can also be identified from among such candidate slow-speed trajectory segments. This will be explained more specifically with reference to Figure 3. If there is a section in the delivery person's overall trajectory where the delivery person's average movement speed is less than a first threshold (e.g., 410 in Figure 4, 520 in Figure 5), then that section can be identified as a candidate slow-speed trajectory segment (S210). Subsequently, if a predetermined proportion or more of the points included within that section, i.e., candidate slow-speed trajectory segment (e.g., 520-1, 520-2 in Figure 5, 610-1 to 610-5 in Figure 6, etc.), are points where the delivery person's movement speed is less than a second threshold (S220), then that candidate slow-speed trajectory segment can be identified as a slow-speed trajectory segment (S230). In this case, the second threshold may be a value less than or equal to the first threshold.

[0061] When a delivery driver engages in target behavior unrelated to a specific delivery, for example, by stopping at a restaurant unrelated to the delivery to pick up other food, or by stopping at a transit point unrelated to the delivery to deliver other food to someone, they generally stay in a certain location temporarily. Therefore, when a delivery driver engages in such target behavior, it is highly likely that a certain proportion of the points included in the candidate low-speed trajectory segment, where the average speed of the delivery driver is below the first threshold, will be points where the speed is very slow, i.e., points where the speed is below the second threshold. Accordingly, according to the embodiment described above, low-speed trajectory segments can be identified more accurately, and furthermore, the number of items to be judged in the judgment stage (S300) described later is reduced, making it possible to perform calculations in a more cost-effective manner.

[0062] Referring again to Figure 2, it is determined whether the slow trajectory segment identified by one embodiment of the present disclosure is associated with a target behavior unrelated to the delivery person's specific delivery (S300).

[0063] Even if a slow-moving trajectory segment is identified, the delivery person's actions within that segment may be unrelated to the target behavior. In other words, slow-moving trajectory segments are not necessarily associated with target behavior. For example, a delivery person may move slowly or stop temporarily for legitimate reasons even while successfully carrying out a specific delivery, and in such cases, the slow-moving trajectory segment is not associated with the target behavior. Therefore, a criterion is needed to determine whether a slow-moving trajectory segment identified by one embodiment of this disclosure is related to target behavior, and this disclosure presents the following three criteria.

[0064] The first criterion is the change in the delivery person's direction of movement within the slow-movement trajectory segment. That is, in some embodiments, whether a slow-movement trajectory segment is associated with a target behavior can be determined based on the change in the delivery person's direction of movement within that segment. For example, if the change in the average direction of movement of the delivery person within the slow-movement trajectory segment is greater than or equal to a predetermined threshold, the segment may be determined to be associated with a target behavior. Such a change in average direction of movement can be calculated using the change in the angle between each direction line connecting adjacent points within the slow-movement trajectory segment and a predetermined axis (e.g., the horizontal axis).

[0065] Referring to Figure 4, since the delivery person is simply moving along road 400 from right to left (402 and 401), the change in the average direction of movement of the direction lines connecting adjacent points within the slow trajectory segment 420 is negligible. Therefore, the slow trajectory segment 420 can be determined to be unrelated to the target behavior.

[0066] Referring to Figure 5, for the sake of explanation, we will assume that all sections (510, 520, and 530) are identified as a single slow-movement trajectory segment. Because the delivery person turns left at the three-way intersection 500 (501, 502, and 503), the change in the delivery person's average direction of movement within the slow-movement trajectory segment (510, 520, and 530) is greater than that in Figure 4, but it may still be below a predetermined threshold. Therefore, the slow-movement trajectory segment (510, 520, and 530) can be determined to be unrelated to the target behavior.

[0067] Referring to Figure 6, the delivery person visited restaurants 610 (601, 602, and 603) located slightly off road 600. As a result, the average change in direction of movement, calculated using directional lines connecting adjacent points within the slow-movement trajectory segment, such as the directional line from point 610-1 to point 610-2, from point 610-2 to point 610-3, from point 610-3 to point 610-4, and from point 610-4 to point 610-5, may exceed a predetermined threshold (in particular, the change in direction of movement when the directional line from point 610-3 to point 610-4 changes to the directional line from point 610-4 to point 610-5 is approximately 180 degrees). Therefore, the slow-movement trajectory segment containing the points shown in Figure 6 can be judged to be associated with target behavior.

[0068] The second criterion is the distance between the road and the delivery person within the slow-speed trajectory segment. That is, in some embodiments, whether or not a slow-speed trajectory segment is associated with a target behavior can be determined based on the distance between the road and the delivery person within that slow-speed trajectory segment. For example, if a slow-speed trajectory segment contains a predetermined proportion or more of points where the distance between the road and the delivery person is greater than or equal to a predetermined threshold, then that slow-speed trajectory segment may be determined to be associated with a target behavior. Here, the road subject to distance calculation means the road closest to the delivery person's location. The predetermined threshold is determined based on the attributes of the road. That is, the predetermined threshold is not uniformly set for all roads, but may be determined differently depending on various road attributes such as the width of the road and whether the road is an alley or a main road.

[0069] Referring to Figure 6, the distance between point 610-4, which indicates the delivery person's position at a specific point in time, and road 600 represents the distance between point 610-4 and the closest point 600-4 on road 600. Assuming that a predetermined proportion of the points included in the slow-moving trajectory segment (such as 610-1 to 610-5; point 600-4 is not included) have a distance from road 600 greater than or equal to a predetermined threshold, the slow-moving trajectory segment including the points shown in Figure 6 can be judged to be associated with target behavior.

[0070] On the other hand, the points shown in Figures 4 and 5 are adjacent to the roads (400 and 500), so the distance from the roads (400 and 500) may be less than a predetermined threshold. Even if the distance between some points and the roads is greater than a predetermined threshold, such points are included in the slow-speed trajectory segment in a proportion less than a predetermined value. Therefore, the slow-speed trajectory segments in Figures 4 and 5 may be judged as not being related to target behavior.

[0071] The third criterion is the type of location corresponding to the slow-moving trajectory segment. That is, in some embodiments, whether or not a slow-moving trajectory segment is related to target behavior can be determined based on the type of location corresponding to the slow-moving trajectory segment. For example, if the location corresponding to a slow-moving trajectory segment is not a type of location highly related to food delivery, such as a residential area, a building containing restaurants, or a location with restaurants within a certain distance, but rather a type of location less related to food delivery, such as a deserted park or roadside, then the slow-moving trajectory segment may be judged not to be related to target behavior.

[0072] On the other hand, it is obvious to those skilled in the art that, in determining whether a slow trajectory segment is associated with target behavior, not all three criteria mentioned above must be applied, and only some of them may be applied.

[0073] In some embodiments, if a location corresponding to a slow trajectory segment identified based on the trajectory information of a delivery person regarding a specific delivery is a location associated with that particular delivery, such as the point where the request for that particular delivery was accepted, the location where the delivered items were received, a transit point, or the delivery destination, then that slow trajectory segment may be determined to be unrelated to the target behavior because it is a location where the delivery person would necessarily have to stay in order to carry out that particular delivery.

[0074] Figure 7 is an exemplary hardware configuration diagram showing a computing system 1000 according to several embodiments of the present disclosure.

[0075] As shown in Figure 7, the computing system 1000 in Figure 7 may include one or more processors 1100, a system bus 1600, a communication interface 1200, a memory 1400 for loading computer programs 1500 executed by the processors 1100, and storage 1300 for storing the computer programs 1500. However, only components related to embodiments of this disclosure are shown in Figure 7. Therefore, a person ordinary in the art to which this disclosure belongs will understand that other general-purpose components other than those shown in Figure 7 may be included. In other words, the computing system 1000 may include a variety of other components besides those shown in Figure 7. Also, in some cases, the computing system 1000 may be configured in a form in which some of the components shown in Figure 7 are omitted. The following describes each component of the computing system 1000.

[0076] The processor 1100 can control the overall operation of each component of the computing system 1000. The processor 1100 may be configured to include at least one of a CPU (Central Processing Unit), MPU (Micro Processor Unit), MCU (Micro Controller Unit), GPU (Graphic Processing Unit), NPU (Neural Processing Unit), or any form of processor well known in the art of this disclosure. The processor 1100 may also perform calculations relating to at least one application or program for performing operations / methods according to various embodiments of this disclosure. The computing system 1000 may comprise one or more processors.

[0077] Next, the memory 1400 may store various data, instructions, and / or information. The memory 1400 may load a computer program 1500 from the storage 1300 to perform the methods / operations according to various embodiments of the disclosure. The memory 1400 may be implemented as volatile memory such as RAM, but the technical scope of the disclosure is not limited thereto.

[0078] Next, the system bus 1600 can provide communication functions between the components of the computing system 1000. The system bus 1600 can be implemented as various types of buses, such as an address bus, a data bus, and a control bus.

[0079] Next, the communication interface 1200 can support wireless internet communication of the computing system 1000. Furthermore, the communication interface 1200 can also support a variety of communication methods other than internet communication. For this purpose, the communication interface 1200 may be configured to include communication modules well known in the art of this disclosure.

[0080] Next, the storage 1300 may non-temporarily store one or more computer programs 1500. The storage 1300 may consist of non-volatile memory such as flash memory, a hard disk, a removable disk, or any form of computer-readable recording medium well known in the art to which this disclosure belongs.

[0081] Next, the computer program 1500 may include one or more instructions that cause the processor 1100 to perform operations / methods according to various embodiments of the present disclosure when loaded into memory 1400. That is, when the computer program 1500 is loaded into memory 1400, the processor 1100 may perform operations / methods according to various embodiments of the present disclosure by executing the one or more instructions.

[0082] In some embodiments, the computer program 1500 may include instructions for obtaining trajectory information relating to a specific delivery by a delivery person, instructions for identifying slow trajectory segments based on the trajectory information, and instructions for determining whether the identified slow trajectory segments are associated with target behavior unrelated to the specific delivery.

[0083] In one embodiment, the instructions for identifying the slow-speed trajectory segment may include instructions for identifying a section in which the average travel speed of the delivery person is less than a first threshold as the slow-speed trajectory segment. In this case, the instructions for identifying the slow-speed trajectory segment may include instructions for identifying a section in which the average travel speed of the delivery person is less than the first threshold as a candidate slow-speed trajectory segment, and instructions for identifying the candidate slow-speed trajectory segment as the slow-speed trajectory segment if a predetermined proportion or more of the section contains points in which the travel speed of the delivery person is less than a second threshold, and the second threshold is less than or equal to the first threshold.

[0084] In one embodiment, the instructions for determining whether or not the target behavior is related may include instructions for determining whether or not the target behavior is related based on a change in the direction of movement of the delivery person within the slow trajectory segment.

[0085] In one embodiment, the computer program 1500 may further include instructions to determine the delivery person to be subject to action if it is determined that the identified slow trajectory segment is associated with the target behavior.

[0086] On the other hand, in some embodiments, the computing system 1000 shown in Figure 7 may represent a virtual machine implemented based on cloud technology. For example, the computing system 1000 may be a virtual machine running on one or more physical servers included in a server farm. In this case, at least a portion of the processor 1100, memory 1400, and storage 1300 shown in Figure 7 may be virtual hardware, and the communication interface 1200 may also be implemented as a virtualized networking element such as a virtual switch.

[0087] With reference to Figure 7, exemplary computing systems 1000 that can realize the delivery driver management system 10 according to several embodiments of the present disclosure have been described.

[0088] We have described various embodiments of this disclosure and the effects of those embodiments with reference to Figures 1 through 7. The effects of the technical concept of this disclosure are not limited to those described above, and other effects not described can be clearly understood by a person of the ordinary skill from the above description.

[0089] Furthermore, even if multiple components are described as being combined as a whole or operating in combination in the embodiments described above, the technical idea of ​​this disclosure is not necessarily limited to these embodiments. That is, within the scope of the technical idea of ​​this disclosure, all of these components can also be selectively combined into one or more configurations and operate together.

[0090] The technical concepts of this disclosure described herein can be realized as computer-readable code on a computer-readable medium. Computer programs recorded on a computer-readable recording medium can be transferred to other computing systems via a network such as the Internet, installed on those other computing systems, and thereby used on those other computing systems.

[0091] While the diagrams may show operations in a specific order, it is not necessarily required that the operations be executed in that specific or sequential order, nor should it be understood that the desired result cannot be obtained unless all the shown operations are performed. In certain situations, multitasking or parallel processing may be advantageous.

[0092] Although various embodiments of this disclosure have been described above with reference to the accompanying drawings, those skilled in the art in which this disclosure pertains will understand that the technical idea of ​​this disclosure can be implemented in other specific forms without altering the technical idea or essential features. Therefore, the embodiments described above are illustrative in all respects and should not be construed as limiting. The scope of protection of this disclosure should be construed as defined by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of rights of the technical idea as defined hereby. [Explanation of Symbols]

[0093] 10. Delivery Driver Management System 11. Delivery Information Manager 12 Delivery driver management device 20 Databases 30 Delivery driver terminal 100 Trajectory information analyzer 400,500,600 roads 401,402,501,502,503,601,602,603 ​​direction 410, 420, 430, 510, 520, 530 Track Segments 520-1,520-2,530-1,530-2,600-4,610-1,610-2,610-3,610-4,610-5 Point 610 Restaurants S100, S200, S210, S220, S230, S300 stages

Claims

1. In the method performed by a computing system, The stage of obtaining trajectory information related to the delivery of a specific delivery person, The steps include identifying a low-speed trajectory segment based on the aforementioned trajectory information, A delivery driver management method comprising the step of determining whether the identified slow trajectory segment is associated with target behavior unrelated to the specific delivery.

2. The step of identifying the low-speed trajectory segment is: The delivery person management method according to claim 1, further comprising the step of identifying a section in which the average movement speed of the delivery person is less than a first threshold as the low-speed trajectory segment.

3. The delivery person management method according to claim 2, wherein the first threshold is determined based on the attributes of the road and the delivery means of the delivery person.

4. The step of identifying the aforementioned low-speed trajectory segment is: The steps include identifying a section in which the average movement speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment, The delivery person management method according to claim 2, further comprising the steps of identifying the candidate low-speed trajectory segment as the low-speed trajectory segment if a predetermined proportion or more of the sections within the section contain points where the delivery person's movement speed is less than a second threshold, and the second threshold is less than or equal to the first threshold.

5. The step of determining whether or not it is related to the aforementioned target behavior is: The delivery person management method according to claim 1, further comprising the step of determining whether or not a change in the direction of movement of the delivery person within the low-speed trajectory segment is related to the target action.

6. The step of determining whether or not it is related to the aforementioned target behavior is: The delivery person management method according to claim 1, further comprising the step of determining whether or not the target behavior is associated with the distance between the road and the delivery person within the low-speed trajectory segment.

7. The step of determining whether or not the target behavior is related based on the distance between the road and the delivery person within the low-speed trajectory segment is: The delivery person management method according to claim 6, further comprising the step of determining that the low-speed trajectory segment is associated with the target behavior if the low-speed trajectory segment contains a predetermined proportion or more of points where the distance between the road and the delivery person is greater than or equal to a predetermined threshold.

8. The delivery person management method according to claim 7, wherein the threshold is determined based on the attributes of the road.

9. The step of determining whether or not it is related to the aforementioned target behavior is: The delivery person management method according to claim 1, further comprising the step of determining whether or not the target behavior is associated with the type of location corresponding to the low-speed trajectory segment.

10. The delivery person management method according to claim 1, further comprising the step of determining the delivery person to be subject to action if the identified slow trajectory segment is determined to be associated with the target behavior.

11. Communication interface, The memory into which a computer program is loaded, Includes a processor that executes the aforementioned computer program, The aforementioned computer program, Instructions for obtaining delivery driver tracking information related to specific deliveries, Instructions for identifying a low-speed trajectory segment based on the aforementioned trajectory information, A delivery driver management system including instructions for determining whether the identified slow-moving trajectory segment is associated with a target behavior unrelated to the specific delivery.

12. The instructions for identifying the low-speed trajectory segment are: The delivery driver management system according to claim 11, further comprising instructions for identifying a section in which the average travel speed of the delivery driver is less than a first threshold as the low-speed trajectory segment.

13. The instruction to be identified as the low-speed trajectory segment is: Instructions for identifying a section in which the average movement speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment, The delivery person management system according to claim 12, which includes instructions that if a predetermined proportion or more of the sections within the section contain points where the delivery person's movement speed is less than a second threshold, the candidate low-speed trajectory segment is identified as the low-speed trajectory segment, and the second threshold is less than or equal to the first threshold.

14. Instructions for determining whether or not the aforementioned target behavior is related are: The delivery person management system according to claim 11, further comprising instructions for determining whether or not a change in the direction of movement of the delivery person within the low-speed trajectory segment is related to the target action.

15. Instructions for determining whether or not the aforementioned target behavior is related are: The delivery person management system according to claim 11, comprising instructions for determining whether or not the target behavior is associated with the distance between the road and the delivery person within the low-speed trajectory segment.

16. The delivery driver management system according to claim 11, further comprising instructions for determining the delivery driver to be subject to action if the identified slow trajectory segment is determined to be associated with the target behavior.

Images