Delivery person management method and system therefor

Abstract

Provided are: a method for determining whether a delivery person performs a target action unrelated to a specific delivery when the specific delivery is made, and managing the delivery person on the basis of the result of the determination; and a system therefor. The delivery person management method according to one embodiment of the present disclosure may comprise the steps of: acquiring trajectory information about a specific delivery of a delivery person; identifying a low-speed trajectory segment on the basis of the trajectory information; and determining whether the identified low-speed trajectory segment is associated with a target action unrelated to the specific delivery.

Description

Delivery Personnel Management Method and System

[0001] The present disclosure relates to a delivery worker management method and system thereof. More specifically, the present disclosure relates to a method and system for determining whether a delivery worker, while performing a specific delivery, engages in targeted behavior unrelated to the specific delivery, and managing the delivery worker based on the result.

[0002] With the emergence of delivery platforms, delivery services have become more widely used than ever before. While delivery platforms typically provide users with estimated delivery times, deliveries often occur later than expected. This can negatively impact the user experience, especially in the case of food delivery.

[0003] A delivery later than the expected delivery time can occur when a delivery person uses multiple delivery platforms to perform deliveries. For example, a delivery person may accept and perform a first delivery request using a first delivery platform, but then, to increase his or her earnings, accept a second delivery request using a second delivery platform and perform both deliveries simultaneously. This creates a stopover unrelated to the first delivery, i.e., a stopover for the second delivery, which could result in the first delivery being delayed from its original expected delivery time.

[0004] From the perspective of delivery platform operators, it's crucial to minimize such incidents, thus monitoring whether deliveries are being carried out normally (or faithfully). Conventional methods typically analyze information such as the difference between expected and actual delivery times, the difference between expected and actual delivery distances, or the similarity between a reasonable delivery route (e.g., a route recommended by a navigation system) and the actual delivery route.

[0005] However, since the difference between the expected delivery time and the actual delivery time, the difference between the expected delivery distance and the actual delivery distance, and the difference between the reasonable delivery route and the actual delivery route can occur in a wide variety of normal cases, such as when the delivery person takes a detour on a specific road depending on the road conditions or weather at the time of delivery, when an unexpected situation such as an accident occurs during delivery, or when the delivery person uses a preferred or familiar route, there was a problem in that the conventional method as above could not accurately monitor whether the delivery was being performed normally (or faithfully).

[0006] A technical problem to be solved through some embodiments of the present disclosure is to provide a method for determining whether a delivery person, while performing a specific delivery, performs a target action unrelated to the specific delivery, and a system to which the method is applied.

[0007] Another technical problem to be solved by some embodiments of the present disclosure is to provide a method and a system to which the method is applied for identifying a low-velocity trajectory segment based on trajectory information regarding a specific delivery and determining whether such a low-velocity trajectory segment is associated with a target behavior unrelated to the specific delivery.

[0008] Another technical problem to be solved through some embodiments of the present disclosure is to provide a method for managing delivery personnel based on the above judgment and a system to which the method is applied.

[0009] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art of the present disclosure from the description below.

[0010] A delivery person management method according to one embodiment of the present disclosure for solving the above technical problem may include a step of obtaining trajectory information regarding a specific delivery of a delivery person, a step of identifying a low-speed trajectory segment based on the trajectory information, and a step of determining whether the identified low-speed trajectory segment is associated with a target behavior unrelated to the specific delivery.

[0011] In one embodiment, the step of identifying the low-speed trajectory segment may include the step of identifying a section in which the average moving speed of the delivery person is below a first threshold as the low-speed trajectory segment. In this case, the first threshold may be determined based on road properties and the delivery means of the delivery person.

[0012] In one embodiment, the step of identifying as the low-speed trajectory segment may include the step of identifying as the candidate low-speed trajectory segment a section in which the average moving speed of the delivery person is less than the first threshold, and the step of identifying as the candidate low-speed trajectory segment a section in which the moving speed of the delivery person is less than the second threshold at a predetermined ratio or more within the section, wherein the second threshold is a value less than or equal to the first threshold.

[0013] In one embodiment, the step of determining whether the target behavior is associated with the delivery person may include the step of determining whether the target behavior is associated with the delivery person based on a change in the delivery person's direction of movement within the low-speed trajectory segment.

[0014] In one embodiment, the step of determining whether the low-speed trajectory segment is associated with the target behavior may include a step of determining whether the low-speed trajectory segment is associated with the target behavior based on a distance between the road and the delivery person within the low-speed trajectory segment. In this case, the step of determining whether the low-speed trajectory segment is associated with the target behavior based on a distance between the road and the delivery person within the low-speed trajectory segment may include a step of determining the low-speed trajectory segment as being associated with the target behavior if a predetermined percentage or more of points within the low-speed trajectory segment where the distance between the road and the delivery person is greater than a predetermined threshold are included. In addition, the threshold may be determined based on an attribute of the road.

[0015] In one embodiment, the step of determining whether the low-speed trajectory segment is associated with the target behavior may include the step of determining whether the low-speed trajectory segment is associated with the target behavior based on a type of location corresponding to the low-speed trajectory segment.

[0016] In one embodiment, the delivery person management method may further include a step of determining the delivery person as a target for action if the identified low-speed trajectory segment is determined to be associated with the target behavior.

[0017] A delivery person management system according to another embodiment of the present disclosure for solving the above technical problem may include a memory in which a computer program is loaded and a processor for executing the computer program. In this case, the computer program may include instructions for obtaining trajectory information regarding a specific delivery of a delivery person, instructions for identifying a low-speed trajectory segment based on the trajectory information, and instructions for determining whether the identified low-speed trajectory segment is associated with a target behavior unrelated to the specific delivery.

[0018] In one embodiment, the instructions for identifying the low-speed trajectory segment may include instructions for identifying a section in which the average moving speed of the delivery person is less than a first threshold as the low-speed trajectory segment. At this time, the instructions for identifying the low-speed trajectory segment may include instructions for identifying a section in which the average moving speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment, and instructions for identifying the candidate low-speed trajectory segment as the low-speed trajectory segment if a predetermined ratio or more of points in the section in which the moving speed of the delivery person is less than a second threshold is included, wherein the second threshold is a value less than or equal to the first threshold.

[0019] In one embodiment, the instructions for determining whether the target behavior is associated with the delivery person may include instructions for determining whether the target behavior is associated with the delivery person based on a change in the delivery person's direction of movement within the low-speed trajectory segment.

[0020] In one embodiment, the delivery person management system may further include instructions for determining the delivery person as a target for action if the identified low-speed trajectory segment is determined to be associated with the target behavior.

[0021] Figure 1 is a configuration diagram of the entire system according to one embodiment of the present disclosure.

[0022] FIG. 2 is a flowchart of a delivery person management method according to one embodiment of the present disclosure.

[0023] FIG. 3 is a flowchart illustrating some operations of a delivery person management method according to one embodiment of the present disclosure.

[0024] FIGS. 4 to 6 are conceptual diagrams illustrating a process for determining whether an identified low-speed trajectory segment is associated with a target behavior according to one embodiment of the present disclosure.

[0025] FIG. 7 is a hardware configuration diagram of a computing system described in some embodiments of the present disclosure.

[0026] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. The advantages and features of the present invention, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the attached drawings. However, the technical spirit of the present invention is not limited to the following embodiments, but can be implemented in various different forms. The following embodiments are provided only to complete the technical spirit of the present invention and to fully inform those skilled in the art of the present invention of the scope of the present invention, and the technical spirit of the present invention is defined only by the scope of the claims.

[0027] In describing various embodiments of the present disclosure, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted.

[0028] Unless otherwise defined, the terms (including technical and scientific terms) used in the following examples may be used with meanings commonly understood by those of ordinary skill in the art to which this disclosure pertains; however, this may vary depending on the intentions of engineers working in the relevant field, precedents, the emergence of new technologies, etc. The terminology used in this disclosure is for the purpose of describing the embodiments and is not intended to limit the scope of this disclosure.

[0029] In the following examples, singular expressions include plural concepts unless the context clearly specifies that they are singular. Furthermore, plural expressions include singular concepts unless the context clearly specifies that they are plural.

[0030] In addition, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are only used to distinguish certain components from other components, and the nature, order, or sequence of the components are not limited by the terms.

[0031] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0032] Figure 1 is a configuration diagram of the entire system according to one embodiment of the present disclosure.

[0033] Hereinafter, the configuration and operation of the entire system according to one embodiment of the present disclosure will be described with reference to FIG. 1. As illustrated in FIG. 1, the entire system according to the present embodiment may be configured to include a delivery person management system (10), and in some embodiments, may further include at least some of a database (20) and a delivery person terminal (30).

[0034] Meanwhile, in FIG. 1, for convenience of explanation, the delivery management system (10) is depicted as being separate from the database (20) and the delivery terminal (30). However, it is obvious to those skilled in the art that at least a portion of the configuration and / or function of the delivery management system (10) may be implemented within the database (20) and / or the delivery terminal (30). The delivery management system (10) may also be configured using one or more physical servers included in a server farm based on cloud technology such as a virtual machine.

[0035] The database (20) may be implemented as one or more computer systems that collect, store and / or manage various geographic information and / or trajectory information related to a particular delivery necessary to determine whether a low-speed trajectory segment identified according to one embodiment of the present disclosure is associated with a target behavior unrelated to a particular delivery.

[0036] Geographic information may include, for example, map information about roads, buildings, and the surrounding environment; information about road attributes; and information about the type of place to which a specific point or area belongs. Here, information about road attributes may include information about the type of road, such as a general road, a dedicated automobile road, an alley, a hill, an intersection, or a three-way intersection; the number of lanes; and the width of the road. Information about the type of place may include information about whether the place is a residential area, whether it is a building containing a restaurant, whether there are restaurants within a certain distance, or whether it is a quiet park or a roadside area with little relevance for food delivery.

[0037] The delivery terminal (30) is a terminal used by a delivery person to perform a delivery, and may refer to a terminal having a function of transmitting the location of the delivery person to a database (20) and / or a 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, for example, a smartphone, a wearable device, a navigation device, etc. However, the type of the delivery terminal (30) or the type of positioning technology is not limited to those described above, and may be variously changed within the scope that can achieve the purpose of the present disclosure.

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

[0039] The delivery information manager (11) receives and / or collects information about 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 / point of acceptance of a delivery request, the place of receipt of the delivery item, the transit point, the delivery destination, the delivery means (motorcycle, car, etc.), from the delivery person terminal (30), and processes this into trajectory information about the specific delivery and transmits it to the database (20) and / or the trajectory information analyzer (100).

[0040] Here, the trajectory information for a specific delivery may refer to the path the delivery person moves over time from the time the delivery person accepts the request for the specific delivery to the time the delivery person arrives at the delivery destination or the time the delivery item is delivered, and the movement speed for each point where the delivery person's location is received. Generally, the delivery person's location is received at regular time intervals, so the delivery person's movement speed at a specific point (t), i.e., the movement speed for each point, can be calculated by using the delivery person's location received before (t-1, t-2, etc.) and / or after (t+1, t+2, etc.) the time point (t) at which the delivery person's location is received.

[0041] Meanwhile, a specific delivery does not necessarily mean a single delivery. It can also refer to a single delivery, such as when multiple deliveries are accepted and performed simultaneously using the same delivery platform. When performing multiple deliveries simultaneously, there may be multiple stopovers.

[0042] The points illustrated in Figures 4 through 6 (e.g., 520-1, 520-2, 610-1 through 610-5, etc.) conceptually represent portions of a trajectory for a specific delivery. The "points" described above and below may be referred to as "points" depending on the context, but the terms "point" and "point" can be understood as synonymous.

[0043] Referring back to FIG. 1, in some embodiments, the delivery information manager (11) may generate trajectory information regarding a specific delivery by performing certain preprocessing or filtering on raw data regarding the delivery person's location to obtain more accurate trajectory information analysis results. For example, the delivery information manager (11) may correct the received location or perform processing to prevent abnormal location information (e.g., location information indicating an abnormally rapid increase in movement speed) from being included in the trajectory information.

[0044] The trajectory information analyzer (100) analyzes trajectory information related to a specific delivery by a delivery person, thereby determining whether the delivery person engages in a target behavior unrelated to the specific delivery while performing the specific delivery. For example, the trajectory information analyzer (100) may obtain trajectory information related to a specific delivery by the delivery person and identify a low-speed trajectory segment based on the trajectory information. Subsequently, the analyzer may determine whether the identified low-speed trajectory segment is associated with a target behavior unrelated to the specific delivery.

[0045] Here, target behavior unrelated to a specific delivery can refer to behaviors that are difficult to consider normal behavior among the behaviors that a delivery person might engage in while performing a specific delivery. For example, a delivery person might accept a request for a first delivery using a first delivery platform, and while performing the first delivery, separately accept a request for a second delivery using a second delivery platform, and then perform both deliveries simultaneously. This target behavior could be considered suspicious behavior.

[0046] These target behaviors may include stopping at locations other than the delivery pickup location or delivery destination, where the delivery person is required to perform a specific delivery. However, the challenge is that these behaviors do not always correspond to the target behavior. For example, stopping briefly to make a phone call during a delivery, waiting for a traffic light to change at an intersection, or experiencing a traffic jam due to a nearby accident may lead to stopping at these locations in a wide variety of situations. However, such stopping in these locations is difficult to consider a target behavior.

[0047] According to embodiments of the present disclosure, such target behavior can be accurately and efficiently found, and detailed descriptions of such embodiments will be provided below.

[0048] In some embodiments, the delivery manager (12) may determine a delivery person as a target for action if a low-speed trajectory segment identified based on trajectory information related to a specific delivery by the delivery person is determined to be associated with a target behavior. In some cases, only delivery persons who are determined to have made such a trajectory at a predetermined frequency or higher may be designated as targets for such action.

[0049] Additionally, in some embodiments, the delivery manager (12) may perform a function of sending a warning message to the delivery person who is the target of the action, blocking the delivery platform from being used any longer or for a predetermined period of time, or causing such action to be taken by another system / device, etc.

[0050] The delivery person management system (10) is configured to include the above-described trajectory information analyzer (100), and in some embodiments, may further include at least some of the delivery information manager (11) and the delivery person manager (12).

[0051] Each of the trajectory information analyzer (100), the delivery information manager (11), and the delivery person manager (12) may be implemented as an independent computing system, or at least some of the trajectory information analyzer (100), the delivery information manager (11), and the delivery person manager (12) may be implemented together through one computing system.

[0052] The configuration and operation of the entire system according to the present embodiment have been described above. In particular, the operation of the trajectory information analyzer (100) will be understood in more detail through the embodiments described below. That is, the operation of the trajectory information analyzer (100) can be supplemented through the embodiments described below.

[0053] Next, a delivery worker management method according to one embodiment of the present disclosure will be described with reference to FIGS. 2 to 7. The delivery worker management method according to this embodiment may be performed by one or more computing systems. Furthermore, some operations of the delivery worker management method according to this embodiment may be performed by a first computing system, while the remaining operations may be performed by a second computing system.

[0054] For example, some operations of the delivery worker management method according to the present embodiment may be performed by an on-premise physical server, while the remaining operations may be performed by a cloud server. Hereinafter, if the entity performing each operation is omitted, it will be understood that the entity performing the operation is the computing system.

[0055] First, a delivery worker management method according to this embodiment is outlined with reference to FIG. 2. Detailed descriptions of each step may be provided later, as needed. Trajectory information regarding a specific delivery by a delivery worker is acquired (S100), and low-speed trajectory segments are identified based on the acquired trajectory information (S200).

[0056] A low-speed trajectory segment may refer to a portion of the entire trajectory that can be generated as a delivery person performs a specific delivery, with a relatively low speed. In some embodiments, if there is a portion of the entire trajectory where the delivery person's average moving speed is below a first threshold, that portion may be identified as a low-speed trajectory segment (S200).

[0057] Here, the first threshold may be determined based on road properties and the delivery method of the delivery person. For example, different first thresholds may be set for different road types, such as dedicated automobile roads, general roads, alleyways, hills, intersections, and three-way intersections, and for different combinations of delivery methods, such as cars, motorcycles, bicycles, and walking.

[0058] Figures 4 through 6 are conceptual diagrams illustrating portions of a delivery person's trajectory for a specific delivery. It should be noted that Figures 4 through 6 merely visually depict the delivery person's location (points 520-1, 520-2, etc.) and trajectory (set of points) for ease of understanding, and that these points / trajectories may not actually be drawn on a digital map.

[0059] Figure 4 conceptually illustrates a scene in which a delivery person moves from right to left (402 and 401) along a road (400), and the trajectory according to the delivery person's location is indicated by dots. Since the location of the delivery person is generally received at regular time intervals, the average moving speed of the delivery person in sections (410 and 430) with relatively wide intervals of dots may be faster than the average moving speed in sections (420) with relatively narrow intervals of dots. In addition, if the average moving speed in the section (420) is less than a first threshold determined based on the properties of the road (400) and the delivery means of the delivery person, the section (420) may be identified as a low-speed trajectory segment.

[0060] FIG. 5 conceptually illustrates a scene in which a delivery person makes a left turn (501, 502, and 503) at a three-way intersection (500), and the trajectory according to the location of the delivery person is indicated by points (520-1, 520-2, 530-1, 530-2, etc.). As in FIG. 4, the average moving speed of the delivery person in sections (510 and 530) with relatively wide intervals between points may be faster than the average moving speed in sections (520) with relatively narrow intervals between points. In addition, if the average moving speed in the section (520) is less than a first threshold determined based on the properties of the road (500) and the delivery means of the delivery person, the section (520) may be identified as a low-speed trajectory segment.

[0061] FIG. 6 conceptually illustrates a scene in which a delivery person visits (601, 602, and 603) a restaurant (610) located slightly off a road (600), and the trajectory according to the location of the delivery person is indicated by points (610-1 to 610-5, etc.). FIG. 6 conceptually illustrates an enlarged view of a low-speed trajectory segment identified according to one embodiment of the present disclosure, and all of the points (610-1 to 610-5, etc.) illustrated in FIG. 6 may be included in such a low-speed trajectory segment.

[0062] Meanwhile, in some embodiments, a low-velocity trajectory segment may be merged with another low-velocity trajectory segment. For example, if a first low-velocity trajectory segment and a second low-velocity trajectory segment are temporally and spatially close, the first low-velocity trajectory segment and the second low-velocity trajectory segment may be merged and identified as a single low-velocity trajectory segment.

[0063] In some other embodiments, after identifying candidate low-speed trajectory segments, a low-speed trajectory segment may be identified among these candidate low-speed trajectory segments. This will be described in more detail with reference to FIG. 3. If there is a section (e.g., 410 in FIG. 4, 520 in FIG. 5) among the entire trajectories of the delivery person where the average moving speed of the delivery person is less than a first threshold, the section can be identified as a candidate low-speed trajectory segment (S210). Then, if among the points included in the section, i.e., the candidate low-speed trajectory segments (e.g., 520-1 and 520-2 in FIG. 5, 610-1 to 610-5 in FIG. 6, etc.), a point where the moving speed of the delivery person is less than a second threshold is included at a predetermined ratio or more (S220), the candidate low-speed trajectory segment can be identified as a low-speed trajectory segment (S230). At this time, the second threshold may be a value less than or equal to the first threshold.

[0064] When a delivery person engages in a targeted behavior unrelated to a specific delivery, such as stopping at a restaurant unrelated to the delivery to pick up another meal, or stopping at an unrelated stopover to deliver another meal to someone, the delivery person typically remains in a certain location, even for a short time. Therefore, when a delivery person engages in such targeted behavior, among the candidate low-speed trajectory segments where the delivery person's average moving speed is below the first threshold, there is a high probability that a certain percentage of points are very slow, i.e., points with speeds below the second threshold. Therefore, according to the above-described embodiment, low-speed trajectory segments can be identified more accurately, and furthermore, since the number of judgment targets in the judgment step (S300) described below is reduced, more cost-effective computations can be performed.

[0065] Referring again to FIG. 2, it is determined whether a low-speed trajectory segment identified according to one embodiment of the present disclosure is associated with a target behavior unrelated to a specific delivery of the delivery person (S300).

[0066] Even if a delivery person is identified as a low-speed trajectory segment, the delivery person's behavior within that low-speed trajectory segment may be unrelated to the target behavior. In other words, a low-speed trajectory segment is not necessarily associated with the target behavior. For example, a delivery person may move slowly or pause for a reasonable reason even while normally performing a specific delivery, and the low-speed trajectory segment in such cases is not associated with the target behavior. Therefore, criteria are needed to determine whether a low-speed trajectory segment identified according to one embodiment of the present disclosure is associated with the target behavior. The present disclosure proposes the following three criteria.

[0067] The first criterion is the change in the delivery person's direction of movement within the low-speed trajectory segment. That is, in some embodiments, whether a low-speed trajectory segment is associated with a target behavior can be determined based on the change in the delivery person's direction of movement within the low-speed trajectory segment. For example, if the average change in direction of movement of the delivery person within the low-speed trajectory segment exceeds a predetermined threshold, the low-speed trajectory segment can be determined to be associated with the target behavior. This average change in direction can be calculated by using the change in angle between each directional line connecting adjacent points within the low-speed trajectory segment and a predetermined axis (e.g., the horizontal axis).

[0068] Referring to FIG. 4, since the delivery person is simply moving from right to left (402 and 401) along the road (400), the average change in direction of movement of the directional lines connecting adjacent points within the low-speed trajectory segment (420) will be minimal. Therefore, the low-speed trajectory segment (420) may be determined to be unrelated to the target action.

[0069] Referring to Fig. 5, for convenience of explanation, it is assumed that all segments (510, 520, and 530) are identified as a single low-speed trajectory segment. Since the delivery person turns left (501, 502, and 503) at the three-way intersection (500), the average change in the delivery person's moving direction within the low-speed trajectory segments (510, 520, and 530) may be greater than that in Fig. 4, but may still be below a predetermined threshold. Therefore, the low-speed trajectory segments (510, 520, and 530) may be determined not to be associated with the target behavior.

[0070] Referring to FIG. 6, a delivery person visits a restaurant (610) slightly off the road (600) (601, 602, and 603), and thus, an average change in direction calculated by using directional lines connecting adjacent points within a low-speed trajectory segment, for example, a directional line from point (610-1) to point (610-2), a directional line from point (610-2) to point (610-3), a directional line from point (610-3) to point (610-4), and a directional line from point (610-4) to point (610-5), may be greater than a predetermined threshold (in particular, the change in direction when the directional line from point (610-3) to point (610-4) changes to a directional line from point (610-4) to point (610-5) will be nearly 180 degrees). Therefore, the low-speed trajectory segment including the points illustrated in Fig. 6 can be determined to be associated with the target behavior.

[0071] The second criterion is the distance between the road and the delivery person within the low-speed trajectory segment. That is, in some embodiments, whether a low-speed trajectory segment is associated with a target behavior can be determined based on the distance between the road and the delivery person within the low-speed trajectory segment. For example, if a low-speed trajectory segment includes a predetermined percentage of points where the distance between the road and the delivery person is greater than a predetermined threshold, the low-speed trajectory segment can be determined to be associated with the target behavior. Here, the road subject to distance calculation may refer to the road closest to the delivery person's location. Furthermore, the predetermined threshold may be determined based on road properties. That is, the predetermined threshold is not uniformly determined for all roads, but may be determined differently depending on various road properties, such as road width and whether the road is an alley or a main road.

[0072] Referring to FIG. 6, the distance between a point (610-4) indicating the location of a delivery person at a specific point in time and a road (600) may mean the distance between the point (600-4) closest to the point (610-4) on the road (600) and the point (610-4). Assuming that among the points included in the low-speed trajectory segment (such as 610-1 to 610-5; point (600-4) is not included here), points (or points) whose distance from the road (600) is greater than a predetermined threshold are included in a predetermined proportion, a low-speed trajectory segment including the points illustrated in FIG. 6 may be determined to be associated with a target action.

[0073] On the other hand, since the points shown in FIGS. 4 and 5 are adjacent to the roads (400 and 500), the distance from the roads (400 and 500) may be less than a predetermined threshold, and even if the distance between some points and the roads is greater than a predetermined threshold, such points will be included in the low-speed trajectory segments at a rate less than a predetermined ratio, so the low-speed trajectory segments in FIGS. 4 and 5 may be determined not to be associated with the target behavior.

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

[0075] Meanwhile, it will be apparent to those skilled in the art that not all of the three criteria described above need to be used in determining whether a low-speed trajectory segment is associated with a target action, and only some of them may be used.

[0076] In some embodiments, if a location corresponding to a low-speed trajectory segment identified based on trajectory information about a specific delivery of a delivery person corresponds to a location associated with that specific delivery, such as a location where a request for that specific delivery was accepted, a location where the delivery item was received, a stopover, a delivery destination, etc., and is a location where the delivery person must naturally stay in order to perform that specific delivery, the low-speed trajectory segment may be determined not to be associated with the target behavior.

[0077] FIG. 7 is an exemplary hardware configuration diagram illustrating a computing system (1000) according to some embodiments of the present disclosure.

[0078] As illustrated in FIG. 7, the computing system (1000) of FIG. 7 may include one or more processors (1100), a system bus (1600), a communication interface (1200), a memory (1400) for loading a computer program (1500) executed by the processor (1100), and a storage (1300) for storing the computer program (1500). However, only components related to the embodiment of the present disclosure are illustrated in FIG. 7. Therefore, a person skilled in the art to which the present disclosure pertains will appreciate that other general components may be included in addition to the components illustrated in FIG. 7. That is, the computing system (1000) may further include various components in addition to the components illustrated in FIG. 7. Furthermore, in some cases, the computing system (1000) may be configured in a form in which some of the components illustrated in FIG. 7 are omitted. Hereinafter, each component of the computing system (1000) will be described.

[0079] The processor (1100) can control the overall operation of each component of the computing system (1000). The processor (1100) can be configured to include at least one of a Central Processing Unit (CPU), a Micro Processor Unit (MPU), a Micro Controller Unit (MCU), a Graphic Processing Unit (GPU), a Neural Processing Unit (NPU), or any other type of processor well known in the technical field of the present disclosure. In addition, the processor (1100) can perform operations for at least one application or program for executing operations / methods according to various embodiments of the present disclosure. The computing system (1000) can include one or more processors.

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

[0081] Next, the system bus (1600) can provide communication functions between 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.

[0082] Next, the communication interface (1200) can support wired and wireless Internet communication of the computing system (1000). Furthermore, the communication interface (1200) can also support various communication methods other than Internet communication. To this end, the communication interface (1200) can be configured to include a communication module well known in the technical field of the present disclosure.

[0083] Next, the storage (1300) can non-temporarily store one or more computer programs (1500). The storage (1300) can be configured to include 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 the present disclosure pertains.

[0084] 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 the memory (1400). That is, when the computer program (1500) is loaded into the memory (1400), the processor (1100) may execute the one or more instructions, thereby performing the methods / operations according to various embodiments of the present disclosure.

[0085] In some embodiments, the computer program (1500) may include instructions for obtaining trajectory information regarding a particular delivery of a delivery person, instructions for identifying a low-velocity trajectory segment based on the trajectory information, and instructions for determining whether the identified low-velocity trajectory segment is associated with a target behavior unrelated to the particular delivery.

[0086] In one embodiment, the instructions for identifying the low-speed trajectory segment may include instructions for identifying a section in which the average moving speed of the delivery person is less than a first threshold as the low-speed trajectory segment. At this time, the instructions for identifying the low-speed trajectory segment may include instructions for identifying a section in which the average moving speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment, and instructions for identifying the candidate low-speed trajectory segment as the low-speed trajectory segment if a predetermined ratio or more of points in the section in which the moving speed of the delivery person is less than a second threshold is included, wherein the second threshold is a value less than or equal to the first threshold.

[0087] In one embodiment, the instructions for determining whether the target behavior is associated with the delivery person may include instructions for determining whether the target behavior is associated with the delivery person based on a change in the delivery person's direction of movement within the low-speed trajectory segment.

[0088] In one embodiment, the computer program (1500) may further include instructions for determining the delivery person as a target for action if the identified low-speed trajectory segment is determined to be associated with the target behavior.

[0089] Meanwhile, in some embodiments, the computing system (1000) illustrated in FIG. 7 may refer to a virtual machine implemented based on cloud technology. For example, the computing system (1000) may be a virtual machine operating on one or more physical servers included in a server farm. In this case, at least some of the processor (1100), memory (1400), and storage (1300) illustrated in FIG. 7 may be virtual hardware, and the communication interface (1200) may also be implemented as a virtualized networking element, such as a virtual switch.

[0090] So far, with reference to FIG. 7, an exemplary computing system (1000) capable of implementing a delivery person management system (10) according to some embodiments of the present disclosure has been described.

[0091] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 through 7. The effects according to the technical concept of the present disclosure are not limited to the effects described above, and other effects not mentioned will be clearly understood by those skilled in the art from the above description.

[0092] Furthermore, even though the above embodiments have described multiple components as being combined or operating in combination, the technical concept of the present disclosure is not necessarily limited to these embodiments. That is, within the scope of the technical concept of the present disclosure, all of the components may be selectively combined and operated one or more times.

[0093] The technical concepts of the present disclosure described so far can be implemented as computer-readable code on a computer-readable medium. A computer program recorded on a computer-readable recording medium can be transmitted to another computing system via a network such as the Internet, installed on said other computing system, and thus used on said other computing system.

[0094] Although the operations are depicted in a particular order in the drawings, this should not be construed as requiring that the operations be performed in the particular order depicted, or in any sequential order, or that all depicted operations must be performed to achieve the desired results. In certain situations, multitasking and parallel processing may be advantageous.

[0095] Although various embodiments of the present disclosure have been described with reference to the attached drawings, those skilled in the art will appreciate that the technical concepts of the present disclosure can be implemented in other specific forms without changing the technical concepts or essential features thereof. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical concepts within a scope equivalent thereto should be interpreted as being included within the scope of the technical concepts defined by the present disclosure.

Claims

1. In a method performed by a computing system, A step of obtaining trajectory information regarding a specific delivery of a delivery person; A step of identifying a low-speed trajectory segment based on the above trajectory information; and A step of determining whether the identified low-speed trajectory segment is associated with a target behavior unrelated to the specific delivery, How to manage delivery drivers.

2. In paragraph 1, The step of identifying the above low-speed trajectory segment is: A step of identifying a section in which the average moving speed of the delivery person is less than a first threshold as the low-speed trajectory segment, How to manage delivery drivers.

3. In paragraph 2, The above first threshold is determined based on the properties of the road and the delivery means of the delivery person. How to manage delivery drivers.

4. In paragraph 2, The step of identifying the above low-speed trajectory segment is: A step of identifying a section in which the average moving speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment; and If a predetermined ratio or more of points where the delivery person's moving speed is less than a second threshold are included within the above section, the candidate low-speed trajectory segment is identified as the low-speed trajectory segment, wherein the second threshold is a value less than or equal to the first threshold. How to manage delivery drivers.

5. In paragraph 1, The step of determining whether or not it is related to the above target behavior is: A step of determining whether the change in the direction of movement of the delivery person within the low-speed trajectory segment is associated with the target action, How to manage delivery drivers.

6. In paragraph 1, The step of determining whether or not it is related to the above target behavior is: A step of determining whether the target behavior is associated with the distance between the road and the delivery person within the low-speed trajectory segment, How to manage delivery drivers.

7. In paragraph 6, The step of determining whether the target behavior is associated with the distance between the road and the delivery person within the low-speed trajectory segment is as follows: A step of determining that the low-speed trajectory segment is associated with the target behavior, if a predetermined percentage or more of points in the low-speed trajectory segment where the distance between the road and the delivery person is greater than a predetermined threshold are included. How to manage delivery drivers.

8. In paragraph 7, The above threshold is determined based on the properties of the road. How to manage delivery drivers.

9. In paragraph 1, The step of determining whether or not it is related to the above target behavior is: Comprising a step of determining whether the type of location corresponding to the low-speed trajectory segment is associated with the target behavior, How to manage delivery drivers.

10. In paragraph 1, If the identified low-speed trajectory segment is determined to be associated with the target behavior, further comprising the step of determining the delivery person as a target for action. How to manage delivery drivers.

11. Communication interface; Memory into which computer programs are loaded; and Including a processor for executing the above computer program, The above computer program, Instructions for obtaining trajectory information about a specific delivery by a delivery person; Instructions for identifying a low-speed trajectory segment based on the above trajectory information; and Including instructions for determining whether the identified low-speed trajectory segment is associated with a target action unrelated to the specific delivery. Delivery person management system.

12. In paragraph 11, Instructions for identifying the above low-speed trajectory segments are: Including instructions for identifying a section in which the average moving speed of the delivery person is less than a first threshold as the low-speed trajectory segment, Delivery person management system.

13. In paragraph 12, Instructions that identify the above low-speed trajectory segments are: Instructions for identifying a section in which the average moving speed of the delivery person is less than the first threshold as a candidate low-speed trajectory segment; and If a predetermined ratio or more of points where the delivery person's moving speed is less than a second threshold are included within the above section, the candidate low-speed trajectory segment is identified as the low-speed trajectory segment, wherein the second threshold is a value less than or equal to the first threshold, including instructions. Delivery person management system.

14. In paragraph 11, Instructions that determine whether the above target behavior is related to: Including instructions for determining whether a change in the direction of movement of the delivery person within the low-speed trajectory segment is associated with the target action. Delivery person management system.

15. In paragraph 11, Instructions that determine whether the above target behavior is related to: Instructions for determining whether the target action is associated with the delivery person based on the distance between the road and the delivery person within the low-speed trajectory segment. Delivery person management system.

16. In paragraph 11, Further comprising instructions for determining the delivery person as a target for action if the identified low-speed trajectory segment is determined to be associated with the target behavior. Delivery person management system.

Images