Available delivery time control apparatus, unmanned aerial vehicle monitoring system, and available delivery time control method

Abstract

To provide an available delivery time control apparatus, an available delivery time control system, and an available delivery time control method configured to limit available delivery time that a delivery requester can select, in accordance with monitoring schedule of an operator and monitoring-required timing.SOLUTION: A monitoring task management server MS is configured to: extract a plurality of available delivery time windows for a commodity using UAVm for use in delivery of the commodity related to an order; acquire, for each of the extracted available delivery time windows, monitoring-required timing at which a monitoring task is to be executed for monitoring the UAVm for use in the delivery of the commodity related to the order, to set the monitoring-required timings to monitoring schedule of an operator On for each of the available delivery time windows; specify available delivery time windows having the monitoring-required timings continuing for a predetermined time, in the monitoring schedule with the monitoring-required timings set thereto; and control the specified available delivery time windows so as not to be selected by an orderer.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present invention relates to technical fields such as systems for monitoring unmanned aerial vehicles used for delivering goods. [Background technology]

[0002] Conventionally, as disclosed in, for example, Patent Document 1, there is known a technique in which a plurality of operators located at locations remote from the unmanned aerial vehicles (one example of an unmanned air vehicle) monitor and control a plurality of unmanned aerial vehicles in flight via computing devices. According to the technique of Patent Document 1, it is possible for one operator to monitor and control many unmanned aerial vehicles. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2022-529507 Summary of the Invention

[0004] However, it is not desirable for one operator to simultaneously monitor multiple unmanned aerial vehicles from the viewpoint of safety, etc. In the future, if deliveries are made by more unmanned aerial vehicles and the monitoring tasks of the operator increase, if there are too many consecutive monitoring timings in the operator's monitoring schedule that require monitoring each of the multiple unmanned aerial vehicles, the burden on the operator will be too great, and there is a concern that the operator's concentration will decrease.

[0005] Therefore, an example of the objective of the present invention is to provide a delivery time control device, a delivery time control system, and a delivery time control method that are capable of limiting the delivery time that a delivery requester can select based on an operator's monitoring schedule and the timing when monitoring is required. [Means for solving the problem]

[0006] (Application Example 1) In order to solve the above problem, the delivery time control device of this application example includes a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts multiple delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery times, and The system is characterized by comprising: a setting unit that sets the second monitoring timing obtained for each possible delivery time separately in the monitoring schedule so that the second monitoring timing does not overlap with the first monitoring timing; an identification unit that identifies, from the extracted possible delivery times, a possible delivery time in which the monitoring timing will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; and a presentation control unit that controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and controls the presentation control unit to prevent the delivery requester from selecting the identified possible delivery time.

[0007] (Application Example 2) The delivery time control device of this application example includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts a plurality of delivery possible times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery possible times, and a second acquisition unit that adjusts the second monitoring timing acquired for each of the extracted delivery possible times so as not to overlap with the first monitoring timing. The system is characterized in that it comprises a setting unit which sets each of the possible delivery times separately in the monitoring schedule, a load level which indicates the degree of load on the operator when executing the monitoring task is associated with the monitoring task, an identification unit which identifies from the extracted possible delivery times a possible delivery time at which the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed, the monitoring task, from which the relatively high monitoring timing should be executed, occurs n (n≧2) times or more in succession, and a presentation control unit which controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and which controls the presentation control unit so that the delivery requester cannot select the identified possible delivery times.

[0008] (Application Example 3) The delivery time control device of this application example includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts multiple delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery times, and sets the second monitoring timing acquired for each of the extracted delivery times in the monitoring schedule separately for each delivery time so as not to overlap with the first monitoring timing. The system is characterized in that it comprises a setting unit, a determination unit which corresponds to the monitoring task a load level indicating the degree of load on the operator when executing the monitoring task, determines a rest time between the end point of any of the monitoring timings and the start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and determines from the extracted possible delivery times a possible delivery time at which a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timing immediately before and after the rest time, and a presentation control unit which controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and controls the presentation control unit so that the delivery requester cannot select the determined possible delivery time.

[0009] (Application Example 4) The unmanned aerial vehicle monitoring system of this application example includes a first acquisition unit that acquires a monitoring schedule of an operator performing a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts multiple possible deliverable times for a second item by a second unmanned aerial vehicle used to deliver a second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible deliverable times, and the second monitoring timing acquired for each item in the monitoring schedule so as not to overlap with the first monitoring timing; a determination unit that determines, from the extracted available deliverable times, a available deliverable time in which the monitoring timing will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; and a presentation control unit that controls the presentation of available deliverable times for the second item to a person requesting delivery of the second item in a selectable manner, the presentation control unit controlling the delivery control unit to prevent the person requesting delivery of the second item from selecting the determined available deliverable time.

[0010] (Application Example 5) The unmanned aerial vehicle monitoring system of this application example includes a first acquisition unit that acquires a monitoring schedule of an operator performing a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts multiple possible deliverable times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible deliverable times, and a second acquisition unit that acquires the second monitoring timing acquired for each of the extracted possible deliverable times so as not to overlap with the first monitoring timing. The system is characterized in that it comprises a setting unit which sets each of the possible delivery times separately in the monitoring schedule, a load level which indicates the degree of load on the operator when executing the monitoring task is associated with the monitoring task, an identification unit which identifies from the extracted possible delivery times a possible delivery time at which the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed, the monitoring task, from which the relatively high monitoring timing should be executed, occurs n (n≧2) times or more in succession, and a presentation control unit which controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and which controls the presentation control unit so that the delivery requester cannot select the identified possible delivery times.

[0011] (Application Example 6) The unmanned aerial vehicle monitoring system of this application example includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts multiple possible deliverable times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible deliverable times, and sets the second monitoring timing acquired for each of the extracted possible deliverable times in the monitoring schedule separately for each possible deliverable time so as not to overlap with the first monitoring timing. The system is characterized in that it comprises a setting unit, a determination unit which corresponds to the monitoring task a load level indicating the degree of load on the operator when executing the monitoring task, determines a rest time between the end point of any of the monitoring timings and the start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and determines from the extracted possible delivery times a possible delivery time at which a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timing immediately before and after the rest time, and a presentation control unit which controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and controls the presentation control unit so that the delivery requester cannot select the determined possible delivery time.

[0012] (Application Example 7) The delivery time control method of this application example is a delivery time control method executed by a computer, and includes the steps of: acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; extracting multiple delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; and acquiring, for each of the extracted delivery times, a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed. The method includes a step of setting the second monitoring timing obtained for each extracted possible delivery time in the monitoring schedule separately for each possible delivery time so that the second monitoring timing does not overlap with the first monitoring timing; a step of identifying a possible delivery time from the extracted possible delivery times in which the monitoring timing will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; and a step of controlling the presentation of possible delivery times for the second item to a person requesting delivery of the second item in a selectable manner, wherein the step of controlling so that the person requesting delivery cannot select the identified possible delivery time.

[0013] (Application Example 8) A delivery possible time control method according to this application example is a delivery possible time control method executed by a computer, and includes the steps of: acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; extracting a plurality of delivery possible times for a second item by a second unmanned aerial vehicle used to deliver the second item; acquiring a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery possible times; and calculating the second monitoring timing acquired for each of the extracted delivery possible times as the first monitoring timing. a step of setting each of the possible delivery times separately in the monitoring schedule so as not to overlap with the second monitoring timing; a step of associating a load level indicating the degree of load on the operator when executing the monitoring task with the monitoring task, and a step of identifying from the extracted possible delivery times a possible delivery time at which the monitoring timing at which the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed will occur n (n≧2) times in succession; and a step of controlling the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, wherein the step of controlling so that the delivery requester cannot select the identified possible delivery times.

[0014] (Application Example 9) A delivery possible time control method according to this application example is a delivery possible time control method executed by a computer, and includes the steps of: acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; extracting a plurality of delivery possible times for a second item by a second unmanned aerial vehicle used to deliver the second item; acquiring a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery possible times; and separately calculating the second monitoring timing acquired for each of the extracted delivery possible times so as not to overlap with the first monitoring timing. The method includes a step of setting the monitoring schedule; associating a load level indicating the degree of load on the operator when executing the monitoring task with the monitoring task; identifying a rest time between an end point of any of the monitoring timings and a start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and identifying from the extracted available delivery times a delivery time at which a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timings immediately before and after the rest time; and a step of controlling the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, wherein the step of controlling so that the delivery requester cannot select the identified available delivery time. Effect of the Invention

[0015] According to the present invention, it is possible to limit the available delivery times that can be selected by the delivery requester in accordance with the operator's monitoring schedule and the timing at which monitoring is required. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of a delivery management system S. [Diagram 2] This is a conceptual diagram showing how UAV1 delivers goods to a destination. [Diagram 3] 2 is a diagram illustrating an example of a schematic configuration of a monitoring task management server MS. [Figure 4] FIG. 13 is a diagram illustrating an example of a monitoring timing calculation table. [Diagram 5] 13 is a diagram showing an example of a monitoring schedule registered in the operator management database 124. FIG. [Figure 6] FIG. 2 is a diagram showing an example of functional blocks in a control unit 13. [Figure 7] FIG. 13 is a diagram showing an example of a monitoring timing group set separately for each possible delivery time in the monitoring schedule of an operator O1. [Figure 8] FIG. 13 is a diagram showing an example of a monitoring timing group set separately for each possible delivery time in the monitoring schedule of an operator O1. [Figure 9] FIG. 13 is a diagram showing an example of a delivery time selection screen displayed on the orderer terminal UT. [Figure 10] 13 is a diagram showing an example of a monitoring schedule that has been updated and registered in the operator management database 124. FIG. [Figure 11] 13 is a flowchart showing an example of a monitoring schedule update process of a control unit 13 in a monitoring task management server MS. [Figure 12] 12 is a flowchart showing a selection / deselection target specification process (example 1) executed in step S7 shown in FIG. [Figure 13] 12 is a flowchart showing a selection exclusion target specification process (example 2) executed in step S7 shown in FIG. [Figure 14] 12 is a flowchart showing a selection exclusion target specification process (example 3) executed in step S7 shown in FIG. [Figure 15] 12 is a flowchart showing a selection / deselection target specification process (example 4) executed in step S7 shown in FIG. [Figure 16] FIG. 13 is a diagram showing an example of a monitoring task execution screen displayed on an operator terminal OT1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] An embodiment of the present invention will be described below with reference to the drawings. The following embodiment is an embodiment in which the present invention is applied to a delivery management system that manages delivery of goods by unmanned aerial vehicles such as drones (hereinafter referred to as "UAVs (Unmanned Aerial Vehicles)"). A UAV is an example of an unmanned flying object. Note that the following embodiment will be described taking as an example a case in which an orderer (an example of a delivery requester) places an order for a product (an example of a product) sold at a store from a terminal (hereinafter referred to as "orderer terminal") used by the orderer (an example of a delivery requester) to an order processing server, and the product is delivered to a delivery destination.

[0018] [ 1. Overview of the configuration and operation of the delivery management system S ] First, referring to FIG. 1 and FIG. 2, the configuration and operation of the delivery management system S according to the present embodiment will be described. FIG. 1 is a diagram showing an example of the schematic configuration of the delivery management system S. As shown in FIG. 1, the delivery management system S includes an order processing server PS, a monitoring task management server MS, and a plurality of operator terminals OTn (n=1, 2, . . .), etc. Here, the monitoring task management server MS is an example of the delivery possible time control device of the present invention. The monitoring task management server MS and the plurality of operator terminals OTn can constitute the unmanned aerial vehicle monitoring system of the present invention. The monitoring task management server MS may also be configured integrally with the order processing server PS. The operator terminals OTn are used by operators On (n=1, 2, . . .). For example, the operator terminal OT1 is used by the operator O1, and the operator terminal OT2 is used by the operator O2. The order processing server PS, the monitoring task management server MS, and the operator terminals OTn are each connected to a communication network NW. The communication network NW is, for example, composed of the Internet, a mobile communication network, and its wireless base station, etc.

[0019] FIG. 2 is a conceptual diagram showing a state in which a UAV1 delivers a product to a delivery destination. In the example of FIG. 2, a plurality of UAVs (m=1, 2, 3, . . .) used for delivery of the product are arranged to be deployed at different bases Pm (m=1, 2, 3, . . .). The product is sold at a store Fo (o=1, 2, 3, . . .), so the UAVm goes from the base Pm to the store Fo to pick up the product. For example, as shown in FIG. 2, after a product order is confirmed, the UAV1 flies from the base P1 to the store F1 that sells the product, loads the product at the store F1, and flies to the delivery destination. Note that a plurality of UAVs may be deployed at one base Pm. For example, the UAV1 and the UAV2 may be deployed at the base P1. The base Pm and the store Fo may be in the same place. For example, the store F1 may be installed within the base P1. In this case, the UAV1 does not need to fly from the base P1 to the store F1.

[0020] The order processing server PS is a server that accepts and processes orders from orderer terminals UT (e.g., mobile terminals such as smartphones) accessed via the communication network NW, and transmits information related to the accepted orders to the monitoring task management server MS. Here, the information related to the order includes, for example, an order ID (identification information of the order), the user ID of the orderer (identification information of the orderer), the product ID (identification information of the product) of the product ordered by the orderer, the product name, the store ID selling the product (identification information of the store Fo), and location information of the delivery destination (e.g., latitude and longitude). The information related to the product (e.g., the product name, a photo image of the product) is presented to the orderer by the order processing server PS in a selectable manner (i.e., displayed on the orderer terminal UT).

[0021] In addition, the order processing server PS presents the orderer with the possible delivery time of the product (e.g., a plurality of different possible delivery time candidates) in a selectable manner (i.e., displays them on the orderer terminal UT). Such possible delivery time is provided by the monitoring task management server MS. The order of the product is confirmed when the orderer selects any possible delivery time from the possible delivery times presented to the orderer. Here, the possible delivery time is a time period during which the product can be delivered to the delivery destination. In other words, the possible delivery time is a time period during which the UAVm loaded with the product is scheduled to arrive at the delivery destination. Alternatively, the possible delivery time may be a time period during which the UAVm that has arrived at the delivery destination lands on the ground or the like and the recipient can receive the product from the UAVm. The possible delivery time may be a time (e.g., 12:00), but it is preferable that the time period be a time period (e.g., 12:00 to 12:15) with some leeway.

[0022] The monitoring task management server MS is a server that manages information about a monitoring task for monitoring a UAVm used for product delivery. A monitoring task can be, for example, a task (job) of monitoring the state of the UAVm and the surrounding situation of the UAVm. The monitoring task is executed by the operator On via the operator terminal OTn at a monitoring timing (monitoring timing of the UAVm) that requires monitoring of the UAVm. The monitoring timing has a predetermined time length (time width). The monitoring task may include a terminal operation (i.e., operation of the operator terminal OTn) for performing flight control (e.g., movement control, hovering control) of the UAVm depending on the situation. The monitoring task is assigned to a time period in which the monitoring task can be executed in the monitoring schedule of the operator On. As a result, the monitoring timing at which the monitoring task should be executed is set in the monitoring schedule of the operator On.

[0023] In this embodiment, for example, a situation is assumed in which an operator O1 at a monitoring base executes a monitoring task for each of a plurality of UAVm that perform delivery at different bases Pm at different monitoring timings. In order to perform safe delivery, information about UAVm is displayed on the operator terminal OT1 used by the operator O1 at a timing when a monitoring task by the operator O1 is required, such as when each UAVm arrives above the store Fo or lands. For example, even if UAV1 that departs from base P1 arrives above store F1, if UAV2 is ready for delivery at store F2 at the same timing and the operator O1 is executing the monitoring task, the monitoring task for UAV1 cannot be executed (i.e., the monitoring timings cannot overlap).

[0024] In addition, the monitoring in this embodiment includes the operator On watching (watching carefully) through the eyes. Therefore, the monitoring timing can also be called the timing of watching (watching closely). In addition, the monitoring timing is preferably a plurality of timings separated by time in the delivery schedule for one delivery by the UAVm to be monitored. This allows the operator On to efficiently execute the monitoring task that should be executed at the monitoring timing of the UAVm in the delivery schedule for one delivery. However, the monitoring timing may be one timing in the delivery schedule for one delivery by the UAVm to be monitored. The delivery schedule is, for example, a schedule from when the UAVm takes off from the base Pm, passes through the store Fo, and lands at the delivery destination (or takes off from the delivery destination).

[0025] The monitoring task management server MS is adapted to receive UAV information related to the UAVm from the UAVm periodically or irregularly via the communication network NW. Here, the UAV information includes, for example, the position, state, and remaining battery level detected by various sensors of the UAVm. The UAV information may also include UAV images captured by a camera of the UAVm. The UAV images may also include, for example, obstacles that may be obstacles to the takeoff and landing of the UAVm. The monitoring task management server MS may also receive UAV surrounding information related to the surrounding conditions of the UAVm from various sensors installed in the store Fo or the base Pm via the communication network NW periodically or irregularly. The UAV surrounding information includes wind direction, wind speed, and rainfall detected by weather sensors installed in the store Fo or the base Pm. The UAV surrounding information may also include surrounding images of the UAVm captured by cameras installed in the store Fo or the base Pm. The surrounding images may also include, for example, obstacles that may be obstacles to the takeoff and landing of the UAVm. In addition, the monitoring task management server MS may receive weather information for the area in which the UAVm is located from the weather management server as UAV surroundings information via the communication network NW on a regular or irregular basis.

[0026] [ 1-1. Configuration and functions of the monitoring task management server MS ] Next, the configuration and functions of the monitoring task management server MS will be described with reference to FIG. 3. FIG. 3 is a diagram showing an example of a schematic configuration of the monitoring task management server MS. As shown in FIG. 3, the monitoring task management server MS includes a communication unit 11, a storage unit 12, a control unit 13, and the like. The communication unit 11 is responsible for controlling communication performed via the communication network NW. The communication unit 11 receives information related to an order from the order processing server PS. The communication unit 11 also receives at least one of UAV information and UAV peripheral information from the UAVm, etc. The storage unit 12 is composed of, for example, a hard disk drive, etc., and stores various programs including an operating system and applications. Here, the application includes a program for executing the delivery possible time control method. The storage unit 12 also has a buffer memory that stores at least one of the UAV information and the UAV peripheral information received from the UAVm while sequentially updating it for each UAVm in association with the aircraft ID (identification information of the UAVm) of the UAVm.

[0027] The storage unit 12 also stores a monitoring timing calculation table. FIG. 4 is a diagram showing an example of the monitoring timing calculation table. As shown in FIG. 4, the monitoring timing calculation table registers a monitoring timing name, a reference time, a task required time, and a load level in association with each other. Here, the monitoring timing name indicates a task type. In the example of FIG. 4, examples of the monitoring timing names are shown as operation decision time, base takeoff time, store landing time, store takeoff time, delivery destination flight time, and delivery destination landing time (six task types), but the task types may be less than six or more than six. Here, "time" may be read as "immediately before." Even if the task types are different monitoring tasks, the contents of the monitoring tasks (e.g., what to watch) may be the same or different. The reference time is a time for calculating the monitoring timing. The task required time is, for example, the time length (time width) required to execute the monitoring task at the monitoring timing. The task required time may be set to the maximum value of the time length required for the monitoring tasks executed in the past by multiple operators On.

[0028] The load level indicates the degree (magnitude) of the load (burden) of the operator On performing the monitoring task. For example, the load level is higher for a monitoring task that requires the operator On to perform with higher concentration (attention). The load level is associated with each monitoring task (in other words, task type). In the example of FIG. 4, the load level is divided into three stages, namely, "low", "medium", and "high", but may be divided into two stages or four or more stages. For example, if monitoring tasks with a load level of "high" are consecutive, there is a possibility that the operator On feels tired or is overburdened, so it is preferable to set the monitoring tasks with a load level of "high" not to be consecutive as much as possible. Note that, when the base Pm and the store Fo are in the same place, the base takeoff, the store landing, and the store takeoff can be combined into the store takeoff. In this case, the load level of the monitoring task to be executed at the monitoring timing corresponding to the combined store takeoff may be set to "high" regardless of the example of FIG. 4.

[0029] Here, the monitoring-required timing corresponding to the time of taking off from the store indicates, for example, the timing when the UAVm loaded with the product takes off from the store Fo for delivery (this is also called "delivery start"). This timing is set to a time period with the delivery start time T as the reference point by referring to the reference time associated with it. Such a reference point may be the end point, center point, or start point of the time period. For example, if the delivery start time T is 9:40, when the reference point is the start point, the time period is 9:40 to 9:50, when the reference point is the start point, the time period is 9:35 to 9:45 when the reference point is the center point, and when the reference point is the end point, the time period is 9:30 to 9:40. Alternatively, the reference point may vary between the start point and the end point of the time period, and in this case, the monitoring-required timing is a time period that can be changed (for example, 10 minutes within 9:30 to 9:50) (the same applies to other task types). In addition, the length of the time period may be, for example, a time length equal to the task required time required to execute the monitoring task (the same applies to other task types). In the monitoring timing calculation table, the delivery start time T is registered as, for example, "0:00" since it serves as a reference.

[0030] The monitoring timing corresponding to the time of landing at the store indicates, for example, the timing when the UAVm that has taken off from the base Pm arrives above the store and lands (for example, on the rack of the store Fo). This timing is set to a time period with a reference point of "ta" minutes (for example, 10 minutes) before the delivery start time T by referring to the reference time associated with it. Note that since takeoff and landing on the rack at the store Fo is assumed and is relatively safe, in the example of FIG. 4, the load level of the monitoring task to be executed at this monitoring timing is set to "low".

[0031] The monitoring timing corresponding to the takeoff from the base indicates, for example, the timing when UAVm takes off from the base Pm. This timing is set to a time period with a reference point of “tb” minutes before the delivery start time T by referring to the reference time associated with it. “tb” minutes is the sum of “ta” minutes and the required time “tx” minutes from the base Pm to the store Fo. The required time “tx” minutes is calculated from the flight distance from the base Pm to the store Fo and the flight speed (scheduled speed) of the UAVm. The monitoring timing corresponding to the operation decision indicates the timing at which it is determined whether or not the UAVm can be operated (fly). This timing is set to a time period with a reference point of “tc” minutes before the delivery start time T by referring to the reference time associated with it. “tc” minutes is the sum of “tb” minutes and a margin time “ty” minutes including the time required for operation decision.

[0032] The monitoring-required timing corresponding to the flight to the delivery destination indicates, for example, the timing when the UAVm that has taken off from the store Fo reaches the delivery midway position. This timing is set to a time period with a reference point being “te” minutes after the delivery start time T by referring to the reference time associated with this. “te” minutes is the time required (flight duration) from the store Fo to the delivery midway position, and is calculated from the flight distance from the store Po to the delivery midway position and the flight speed of the UAVm. The delivery midway position is a position that is a predetermined percentage (for example, 50%) of the flight route from the store Fo to the delivery destination. The monitoring-required timing corresponding to the landing to the delivery destination indicates, for example, the timing when the UAVm that has taken off from the store Fo arrives above the delivery destination and lands. This timing is set to a time period with a reference point being “tf” minutes after the delivery start time T by referring to the reference time associated with this. "tf" minutes is the time required (flight duration) from the store Fo to the delivery destination, and is calculated from the flight distance from the store Po to the delivery destination and the flight speed of the UAVm. The point in time "tf" minutes after the delivery start time T corresponds to (for example, coincides with or is included in) the above-mentioned possible delivery time.

[0033] Furthermore, in the storage unit 12, a store management database (DB) 121, a machine management database (DB) 122, a user management database (DB) 123, an operator management database (DB) 124, and a delivery plan management database (DB) 125 are constructed. The store management database 121 is a database for managing information related to the stores Fo that sell products. For example, the store ID and location information (e.g., latitude and longitude) of the stores Fo are stored (registered) in association with each store Fo in the store management database 121.

[0034] The aircraft management database 122 is a database for managing information related to UAVm used for delivery of goods. For example, the aircraft ID of the UAVm, the operating status, the available time period, and the location information of the base Pm where the UAVm is deployed are stored in the aircraft management database 122 in association with each UAVm. The operating status indicates whether the UAVm is operating (e.g., moving to prepare for delivery, being used for delivery, returning), unavailable, or on standby, and is updated as appropriate. The available time period indicates the date and time period during which the UAVm can be used for delivery.

[0035] The user management database 123 is a database for managing information about users who have created accounts as members using the delivery service. Here, users who have created accounts can place product orders as orderers at the order processing server PS via the orderer terminal UT. The user management database 123 stores a user ID, name, address, email address, and telephone number in association with each user. Note that the address or location information of the delivery destination of the product may be preregistered in the user management database 123.

[0036] The operator management database 124 is a database for managing information related to the operator On. For example, the operator On's operator ID (identification information of the operator On), the operator On's monitoring schedule, and access information (e.g., IP address) of the operator terminal OTn used by the operator On are stored in the operator management database 124 in association with each operator On. The monitoring schedule of the operator On is set with a monitoring timing at which a monitoring task for monitoring the UAVm should be executed. In other words, the monitoring schedule of the operator On includes a time period to which a monitoring task has already been assigned (a time period in which the monitoring task is already included).

[0037] Fig. 5 is a diagram showing an example of a monitoring schedule registered in the operator management database 124. In the example of Fig. 5, a monitoring schedule is associated with each operator On (operator ID). For example, in the monitoring schedule associated with the operator ID "O0001" (monitoring schedule of operator O1), a monitoring timing for each task type is set for each of the order ID "d0001" (delivery a) and order ID "d0002" (delivery b). Note that in the example of Fig. 5, the monitoring timing is expressed as a time period (for convenience, the date is omitted), and the monitoring task will be executed within this time period.

[0038] The delivery plan management database 125 is a database for managing information related to delivery plans. In the delivery plan management database 125, an order ID, a determined delivery plan, etc. are stored in association with each order (delivery). The delivery plan includes, for example, the product ID of the product to be delivered, the aircraft ID of the UAVm that delivers the product, and a delivery schedule of the UAVm. The UAVm shown in the delivery plan is the UAVm that has been determined to be used for delivery. The delivery schedule includes the available delivery time and the delivery start time. Note that one delivery corresponds to one order ID and one UAVm. For example, a product related to an order identified by an order ID "d0001" is delivered by UAV1, and a product related to an order identified by an order ID "d0002" is delivered by UAV2.

[0039] The control unit 13 includes a central processing unit (CPU), a read only memory (ROM), and a random access memory (RAM). Fig. 6 is a diagram showing an example of functional blocks in the control unit 13. The control unit 13 functions as a possible delivery time extraction unit 131 (an example of an extraction unit), a monitoring schedule acquisition unit 132 (an example of a first acquisition unit), a monitoring timing acquisition unit 133 (an example of a second acquisition unit), a monitoring timing setting unit 134 (an example of a setting unit), a selection exclusion target specification unit 135 (an example of a specification unit), a presentation control unit 136, and a monitoring schedule update unit 137, for example, according to a program (a group of program codes) stored in the ROM or the storage unit 12, as shown in Fig. 6.

[0040] For example, when information about an order is received, the available delivery time extraction unit 131 extracts a predetermined number (e.g., three or more) of available delivery times for the ordered product based on the estimated time required to deliver the ordered product (an example of a second item). Here, the estimated time required to deliver the product is estimated from the preparation time for picking up and loading the product, and the time required for the UAVm to reach the delivery destination. This required time is calculated, for example, from the flight distance specified from the location information of the base Pm where the UAVm is waiting, the location information of the store Fo, and the location information of the delivery destination, and the flight speed of the UAVm. When extracting the available delivery time, the available time zone of the UAVm managed in the aircraft management database 122 may be referred to as appropriate. A number of possible delivery times are extracted, for example, "11:50 (start point) - 12:05" (end point), "12:00 - 12:15", "12:10 - 12:25", "12:20 - 12:35", "12:30 - 12:45", "12:40 - 12:55", "12:50 - 13:05", ... In this example, the length of the time slot is 15 minutes, but this is not particularly limited. The extracted possible delivery time is associated with the order ID and the UAVm (aircraft ID) that can deliver the product at the delivery destination at the possible delivery time.

[0041] For example, when information about an order is received, the monitoring schedule acquisition unit 132 acquires a monitoring schedule of any operator On (for example, operator O1) and the operator ID of the operator On from the operator management database 124. For example, a monitoring schedule is acquired in which a first monitoring timing (for example, a monitoring timing for each task type) for executing a first monitoring task for monitoring a UAV1 (an example of a first unmanned aerial vehicle) used to deliver a product (an example of a first product) related to an order different from a product (an example of a second product) related to an order is already set. In the monitoring schedule acquired in this way, the monitoring timings for executing the respective monitoring tasks of a plurality of UAVm (for example, UAV1 and UAV2) may be set so as not to overlap. Note that the acquired monitoring schedule and operator ID are associated with an order ID.

[0042] The monitoring timing acquisition unit 133 acquires a second monitoring timing (e.g., a monitoring timing for each task type) at which a second monitoring task for monitoring a UAV3 (an example of a second unmanned aerial vehicle) used to deliver the ordered product should be executed for each possible delivery time extracted by the possible delivery time extraction unit 131. For example, the monitoring timing acquisition unit 133 acquires each monitoring timing (i.e., a monitoring timing for each task type) that requires monitoring of the UAV3 associated with the possible delivery time based on the possible delivery time extracted by the possible delivery time extraction unit 131 and a monitoring timing calculation table stored in the storage unit 12. Hereinafter, each monitoring timing in one delivery is also referred to as a "monitoring timing group."

[0043] More specifically, a delivery start time T (e.g., 11:20) is calculated (that is, calculated backwards) from the start point of the delivery possible time extracted by the delivery possible time extraction unit 131 (e.g., 11:50) and the time required from the store Fo to the delivery destination (e.g., 30 minutes). The calculated delivery start time T is associated with the order ID and the delivery possible time. Then, the calculated delivery start time T is applied to the monitoring timing calculation table to obtain a monitoring timing group. For example, the delivery start time T in the monitoring timing calculation table shown in FIG. 4 is set to 11:20 (in other words, updated from the default 0:00 to 11:20), and each reference time is specified to calculate the monitoring timing for each task type. Here, the monitoring timing may be calculated as a time period that can be changed depending on how the reference point is taken, as described above. Note that a monitoring timing group associated with each of the multiple delivery possible times extracted by the delivery possible time extraction unit 131 is obtained.

[0044] The monitoring timing setting unit 134 sets (adds) the monitoring timing (second monitoring timing) acquired by the monitoring timing acquisition unit 133 for each possible delivery time to the monitoring schedule separately (independently) for each possible delivery time so as not to overlap with the monitoring timing (first monitoring timing) that has already been set (changing the time period as necessary). Note that among the possible delivery times extracted by the possible delivery time extraction unit 131, a possible delivery time in which the monitoring timing acquired by the monitoring timing acquisition unit 133 overlaps with a monitoring timing that has already been set is not presented. In other words, a monitoring timing associated with such a possible delivery time is not set to the monitoring schedule.

[0045] 7 and 8 are diagrams showing examples of monitoring timing groups set separately for each possible delivery time in the monitoring schedule of the operator O1. In the monitoring schedules (a) and (b) shown in FIG. 7 and the monitoring schedules (c) and (d) shown in FIG. 8, the monitoring timing groups TG1 and TG2 are already set. In the monitoring schedule (a) shown in FIG. 7, the monitoring timing group TG3a corresponding to the possible delivery time PTa is set, and in the monitoring schedule (b) shown in FIG. 7, the monitoring timing group TG3b corresponding to the possible delivery time PTb is set (that is, set so as not to overlap with the monitoring timings in TG1 and TG2). In the monitoring schedule (c) shown in FIG. 8, the monitoring timing group TG3c corresponding to the possible delivery time PTc is set, and in the monitoring schedule (d) shown in FIG. 8, the monitoring timing group TG3d corresponding to the possible delivery time PTd is set.

[0046] Each of the monitoring timing groups TG1, TG2, TG3a, TG3b, TG3c, and TG3d is composed of a monitoring timing T1 corresponding to flight decision, a monitoring timing T2 corresponding to departure from the base, a monitoring timing T3 corresponding to landing at the store, a monitoring timing T4 corresponding to departure from the store, a monitoring timing T5 corresponding to flight to the delivery destination, and a monitoring timing T6 corresponding to landing at the delivery destination. In the example of Fig. 8, the monitoring timing T2 corresponding to departure from the base (i.e., the monitoring task at departure from the base) and the monitoring timing T6 corresponding to landing at the delivery destination (i.e., the monitoring task at landing at the delivery destination) are associated with a load level L of "high".

[0047] In the monitoring schedule (a) shown in FIG. 7, the continuous monitoring time CTa during which the monitoring timings are consecutive (in this example, the monitoring timings are consecutive 15 times in chronological order) is the time length (2 hours 30 minutes) from the end of the break time RTa1 to the start of the break time RTa2. On the other hand, in the monitoring schedule (b) shown in FIG. 7, the continuous monitoring time CTb during which the monitoring timings are consecutive (in this example, the monitoring timings are consecutive 8 times in chronological order) is the time length (1 hour 20 minutes) from the end of the break time RTb1 to the start of the break time RTb2. Here, a time period during which no monitoring timing is set (i.e., a time period during which no monitoring task is assigned) is, for example, 5 minutes or more, is called a break time. In the continuous monitoring time CTa or the continuous monitoring time CTb, the time length (interval) from the end of any of the monitoring timings (for example, T1 in TG1) to the start of the following monitoring timing (for example, T1 in TG2) is "0". However, even if the time length from the end point of one monitoring timing to the start point of another subsequent monitoring timing is greater than "0," if it is shorter than the above-mentioned break time, these monitoring timings may be interpreted as being consecutive.

[0048] The selection exclusion target specifying unit 135 specifies, as a selection exclusion target, from the possible deliverable times extracted by the possible deliverable time extracting unit 131, a possible deliverable time in which the monitoring timing continues for a predetermined time or more in the monitoring schedule in which the monitoring timing is set by the monitoring timing setting unit 134. Here, the monitoring timing continues for a predetermined time or more means that the continuous monitoring time is a predetermined time or more. The predetermined time is not particularly limited, but is set to about 2 hours, for example. According to the example of FIG. 7 to FIG. 8, since the continuous monitoring time CTa is a predetermined time or more (2 hours) in the monitoring schedule (a) shown in FIG. 7, the possible deliverable time PTa associated with the monitoring timing group TG3a added at this time is specified as a selection exclusion target. This makes it possible to effectively prevent the decrease in concentration and fatigue of the operator On due to the monitoring timings at which the monitoring task for monitoring each of the multiple UAVm should be executed being too continuous (i.e., the continuous monitoring time is too long), while allowing the operator On to appropriately execute the monitoring task.

[0049] The selection exclusion target specifying unit 135 may specify, as a selection exclusion target, a deliverable time in which monitoring timings corresponding to a relatively high load level "high" in the monitoring schedule in which the monitoring timings are set by the monitoring timing setting unit 134 are to be executed n (n≧2) or more times in succession. Here, n can be set arbitrarily, but when n is set to "2", according to the example of Figs. 7 to 8, the monitoring timing T2 (within TG3c) in which the monitoring task corresponding to the load level "high" in the monitoring schedule (c) shown in Fig. 8 is to be executed and the monitoring timing T6 (within TG1) are to be executed in succession, so that the deliverable time PTc corresponding to the monitoring timing group TG3c added at this time is specified as a selection exclusion target. This effectively prevents the operator On from losing concentration or becoming fatigued due to successive monitoring timings in which the monitoring task corresponding to a relatively high load level is to be executed, while allowing the operator On to appropriately execute the monitoring task. In addition, when n is set to "3", there is no monitoring schedule with consecutive monitoring timings at which a monitoring task associated with a load level of "high" should be executed, so the delivery time PTc is not identified as a selection exclusion target.

[0050] In addition, the selection exclusion target specifying unit 135 may specify, as a selection exclusion target, a deliverable time in which the monitoring timing associated with the load level "medium" (higher than "low") in the monitoring schedule in which the monitoring timing is set by the monitoring timing setting unit 134 occurs n (n≧2) or more consecutive times, at which the monitoring task should be executed. In this case, n may be set to a value larger than the load level "high". For example, n is set to "2" when the load level is "high", while n is set to "3" or more when the load level is "medium". In this way, n may be set to a larger value as the load level is lower. This makes it possible to appropriately control the number of times that the operator On is allowed to execute the monitoring task in succession according to the load level of the monitoring task.

[0051] In addition, the selection exclusion target specifying unit 135 may specify a break time between the end point of any monitoring timing and the start point of the following monitoring timing in the monitoring schedule in which the monitoring timing is set by the monitoring timing setting unit 134, and specify a deliverable time in which a relatively high load level is associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time as a selection exclusion target. According to the example of Figs. 7 to 8, since a load level "high" is associated with each monitoring task to be executed at the monitoring timing T2 (within TG3d) immediately before the break time RTd and the monitoring timing T6 (within TG2) immediately after the break time RTd in the monitoring schedule (d) shown in Fig. 8, the deliverable time PTd associated with the monitoring timing group TG3d added at this time is specified as a selection exclusion target. This effectively prevents the decrease in concentration and fatigue of the operator On due to the relatively high load level being associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time, and allows the operator On to appropriately execute the monitoring task.

[0052] The presentation control unit 136 controls the presentation of possible delivery times (candidates) of the product by the UAVm to the orderer of the product in a selectable manner (i.e., displaying them on the orderer terminal UT of the orderer). Here, the presentation of the possible delivery times is performed, for example, by the order processing server PS sending presentation information indicating the possible delivery times provided by the presentation control unit 136 to the orderer terminal UT. Such presentation information may include the order ID. The possible delivery times to be presented are the possible delivery times extracted by the possible delivery time extraction unit 131, which are associated with a group of monitoring timings set in the monitoring schedule without overlapping with other monitoring timings.

[0053] The presentation control unit 136 then performs control (selection exclusion control) so that the orderer of the product cannot select the available delivery time (available delivery time of the selected excluded target) identified by the selection exclusion target identification unit 135 as a selected excluded target. For example, the presentation control unit 136 performs selection exclusion control by not including the available delivery time of the selected excluded target in the presentation information. Alternatively, the presentation control unit 136 may perform selection exclusion control by including the available delivery time of the selected excluded target and information indicating that the available delivery time is not selectable in the presentation information. Note that the presentation control unit 136 may perform control so that the presentation information is sent directly from the monitoring task management server MS to the orderer terminal UT without going through the order processing server PS.

[0054] FIG. 9 is a diagram showing an example of a possible delivery time selection screen displayed on the orderer terminal UT. The possible delivery time selection screen shown in FIG. 9 displays the possible delivery times "11:40-11:55", "11:50-12:05", "12:10-12:25", "12:30-12:45", and "12:50-13:05". Among these, "11:50-12:05" is a possible delivery time that cannot be selected, and the "Select" button B1 is grayed out so that the product orderer cannot select it. The possible delivery times that cannot be selected may be configured not to be displayed on the possible delivery time selection screen. On the other hand, "12:10-12:25", "12:30-12:45", and "12:50-13:05" can be selected by the product orderer. For example, when the "Select" button B2 corresponding to "12:10-12:25" is selected by the orderer, the button B2 changes to "Selected." Then, selection information indicating the selected available delivery time is transmitted from the orderer terminal UT to the monitoring task management server MS via the order processing server PS. Such selection information may include the order ID.

[0055] The monitoring schedule update unit 137 updates the monitoring schedule of the operator On in the operator management database 124 based on the monitoring schedule in which the monitoring timing is set by the monitoring timing setting unit 134 and the selection information indicating the possible delivery time selected by the orderer of the product. That is, the monitoring schedule in which the monitoring timing group associated with the possible delivery time selected by the orderer of the product is set is updated and registered in the operator management database 124. FIG. 10 is a diagram showing an example of the monitoring schedule updated and registered in the operator management database 124. In the example of FIG. 10, a monitoring timing group (TG3b shown in FIG. 7) associated with the possible delivery time "12:10-12:25" is newly registered in the monitoring schedule of the operator O1 in association with the order ID "d0003" (delivery c).

[0056] [ 2. Operation of the delivery management system S ] Next, the operation of the delivery management system S will be described with reference to Figs. 11 to 15 etc. Fig. 11 is a flowchart showing an example of a monitoring schedule update process of the control unit 13 in the monitoring task management server MS. Figs. 12 to 15 are flowcharts showing the selection / exclusion target specification process (Example 1 to Example 4) executed in step S7 shown in Fig. 11, respectively. As a premise of the process shown in Fig. 11, it is assumed that an orderer selects an order-related product and a delivery destination on the orderer terminal UT, and the order is accepted by the order processing server PS. Then, the process shown in Fig. 11 is started when the monitoring task management server MS receives information related to the order from the order processing server PS. The information related to the order includes, for example, an order ID, the user ID of the orderer, information related to the order-related product, and location information of the delivery destination.

[0057] 11 is started, the control unit 13 estimates the estimated time required for delivery of the ordered product based on the received information about the order (step S1), as described above. Next, the control unit 13 extracts multiple possible delivery times for the ordered product based on the estimated time estimated in step S1, etc., using the possible delivery time extraction unit 131, as described above (step S2).

[0058] Next, the control unit 13 refers to the aircraft management database 122 (i.e., refers to the available time period of each UAVm, etc.) and identifies one UAVm that can deliver the product at the delivery destination during each available delivery time extracted in step S2 (step S3). The UAVm (aircraft ID) thus identified is associated with the order ID included in the information related to the order and the available delivery time extracted in step S2.

[0059] Next, the control unit 13 acquires the monitoring schedule of an operator On (e.g., operator O1) selected from among the multiple operators On and the operator ID of the operator On from the operator management database 124 by the monitoring schedule acquisition unit 132 (step S4). Here, the operator On may be selected according to a predetermined selection order or may be selected randomly. The acquired monitoring schedule and operator ID are associated with an order ID.

[0060] Next, the control unit 13 acquires a group of monitoring timings that require monitoring of the UAVm associated with the possible delivery times based on the possible delivery times extracted in step S2 and the monitoring timing calculation table stored in the storage unit 12, for each possible delivery time, by the monitoring timing acquisition unit 133 as described above (step S5). Note that the acquired group of monitoring timings is associated with each possible delivery time.

[0061] Next, based on the monitoring schedule acquired in step S4 and the group of monitoring timings acquired in step S5, the control unit 13 sets (adds) each of the monitoring timings in the group of monitoring timings to the monitoring schedule separately for each possible delivery time using the monitoring timing setting unit 134 so that they do not overlap with each of the monitoring timings that have already been set (step S6).

[0062] Next, the control unit 13 executes a selection exclusion target specification process (step S7). In the selection exclusion target specification process (example 1) shown in FIG. 12, the control unit 13 selects one of the monitoring schedules (for example, the monitoring schedule (a) shown in FIG. 7) for which a monitoring timing group is set in step S6 (step S701). Next, the control unit 13 judges whether or not the monitoring timing continues for a predetermined time or more in the monitoring schedule selected in step S701 (step S702). If it is judged that the monitoring timing continues for a predetermined time or more (step S702: YES), the process proceeds to step S703. On the other hand, if it is judged that the monitoring timing does not continue for a predetermined time or more (step S702: NO), the process proceeds to step S704.

[0063] In step S703, the control unit 13 specifies the possible delivery times associated with the monitoring timing group set (added) to the monitoring schedule selected in step S701 as selection exclusion targets by the selection exclusion target specifying unit 135, and proceeds to step S704. In step S704, the control unit 13 judges whether or not there is a monitoring schedule that has not yet been selected among the monitoring schedules for which the monitoring timing group has been set in step S6. If it is judged that there is a monitoring schedule that has not yet been selected (step S704: YES), the process returns to step S701, a monitoring schedule that has not yet been selected (for example, the monitoring schedule (b) shown in FIG. 7) is selected, and the process of step S702 is performed for the selected monitoring schedule. On the other hand, if it is judged that there is no monitoring schedule that has not yet been selected (step S704: NO), the process returns to the process shown in FIG. 11.

[0064] On the other hand, in the selection / exclusion target specification process (example 2) shown in FIG. 13, similarly to step S701, the control unit 13 selects one monitoring schedule for which a monitoring timing group is set in step S6 (step S711). Next, the control unit 13 judges whether or not the monitoring timing for which a monitoring task associated with a relatively high load level in the monitoring schedule selected in step S711 should be executed occurs n times or more consecutively (step S712). For example, it is judged whether or not the load level "high" occurs two or more consecutively. If it is judged that the monitoring timing occurs n times or more consecutively (step S712: YES), the process proceeds to step S713. On the other hand, if it is judged that the monitoring timing does not occur n times or more consecutively (step S712: NO), the process proceeds to step S714. Note that, for example, if it is judged that the load level "high" does not occur two or more consecutively, the process returns to step S712, and it may be judged whether or not the load level "medium" occurs three or more consecutively.

[0065] In step S713, the control unit 13 specifies the possible delivery times associated with the monitoring timing group set in the monitoring schedule selected in step S711 as selection exclusion targets by the selection exclusion target specifying unit 135, and proceeds to step S714. The processing in step S714 is similar to step S704. Note that, before the processing in step S712, it may be determined whether the monitoring timing continues for a predetermined time or more in the monitoring schedule selected in step S711. In this case, the processing in step S712 is performed when it is determined that the monitoring timing does not continue for a predetermined time or more, whereas the processing in step S713 is performed when it is determined that the monitoring timing continues for a predetermined time or more.

[0066] 14, in the selection / exclusion target specification process (example 3), similarly to step S701, the control unit 13 selects one monitoring schedule for which a group of monitoring timings is set in step S6 (step S721). Next, the control unit 13 specifies a break time between the end point of any monitoring timing and the start point of the following monitoring timing in the monitoring schedule selected in step S721 (step S722). Note that if there are multiple break times spaced apart in the selected monitoring schedule, each break time is specified.

[0067] Next, the control unit 13 judges whether or not a relatively high load level is associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time specified in step S722 (step S723). If it is judged that a relatively high load level is associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time (step S723: YES), the process proceeds to step S724. On the other hand, if it is judged that a relatively high load level is not associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time (step S723: NO), the process proceeds to step S725. Note that, if there are a plurality of break times spaced apart in the selected monitoring schedule, the process of step S723 is performed for each break time.

[0068] In step S724, the control unit 13 specifies the possible delivery times associated with the monitoring timing group set in the monitoring schedule selected in step S721 as selection exclusion targets by the selection exclusion target specifying unit 135, and proceeds to step S725. The processing in step S725 is similar to that in step S704. Note that, before the processing in step S722, it may be determined whether or not the monitoring timing continues for a predetermined time or more in the monitoring schedule selected in step S721. In this case, the processing in step S722 is performed when it is determined that the monitoring timing does not continue for a predetermined time or more, whereas the processing in step S724 is performed when it is determined that the monitoring timing continues for a predetermined time or more.

[0069] On the other hand, in the selection / exclusion target specification process (example 4) shown in Fig. 15, the control unit 13 selects one monitoring schedule for which a monitoring timing group is set in step S6, similar to step S701 (step S731). Next, the control unit 13 judges whether or not the monitoring timing continues for a predetermined time or more in the monitoring schedule selected in step S731 (step S732). If it is judged that the monitoring timing continues for a predetermined time or more (step S732: YES), the process proceeds to step S736. On the other hand, if it is judged that the monitoring timing does not continue for a predetermined time or more (step S732: NO), the process proceeds to step S733.

[0070] In step S733, the control unit 13 judges whether or not there are n or more consecutive monitoring timings at which a monitoring task associated with a relatively high load level in the monitoring schedule selected in step S731 should be executed. If it is judged that there are n or more consecutive monitoring timings (step S733: YES), the process proceeds to step S736. On the other hand, if it is judged that there are not n or more consecutive monitoring timings (step S733: NO), the process proceeds to step S734.

[0071] In step S734, the control unit 13 identifies a break time between the end point of any monitoring timing and the start point of the following monitoring timing in the monitoring schedule selected in step S731. Next, the control unit 13 judges whether or not a relatively high load level is associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time identified in step S734 (step S735). If it is judged that a relatively high load level is associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time (step S735: YES), the process proceeds to step S736. On the other hand, if it is judged that a relatively high load level is not associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time (step S735: NO), the process proceeds to step S737.

[0072] In step S736, the control unit 13 specifies the possible delivery times associated with the monitoring timing group set in the monitoring schedule selected in step S731 as selection exclusion targets by the selection exclusion target specifying unit 135, and proceeds to step S737. The process of step S737 is the same as step S704. Note that the processes of steps S734 and S735 may be performed before the process of step S733. In this case, if it is determined in step S735 that a relatively high load level is not associated with each of the monitoring tasks to be executed at the monitoring timings immediately before and after the break time, the process of step S733 will be performed.

[0073] Returning to the process of FIG. 11, the control unit 13 causes the presentation control unit 136 to transmit presentation information (including, for example, the order ID) indicating possible delivery times (candidates) associated with the monitoring timing group set in the monitoring schedule in step S6 to the orderer terminal UT of the orderer (step S8). As a result, the possible delivery times are displayed selectably on the orderer terminal UT. In other words, the possible delivery times are presented to the orderer selectably. At this time, as described above, if a possible delivery time is specified as a selection exclusion target in the selection exclusion target specification process in step S7, the presentation control unit 136 controls so that the orderer cannot select the specified possible delivery time. Then, when the orderer selects any one of the possible delivery times displayed on the orderer terminal UT, selection information (including, for example, the order ID) indicating the selected possible delivery time is transmitted from the orderer terminal UT to the monitoring task management server MS via the order processing server PS. This confirms the accepted order.

[0074] The processes in steps S4 to S7 may be performed for each of the multiple operators On. In this case, presentation information indicating the available delivery time associated with any one operator On selected from the available delivery times associated with the multiple operators On (operator IDs) is transmitted to the orderer terminal UT. Here, it is preferable to select an operator On associated with the available delivery time expected to be most desired by the orderer (for example, the earliest available delivery time or the most available delivery time within a predetermined time).

[0075] Next, when the control unit 13 receives selection information indicating the available delivery time selected by the orderer (step S9), it updates and registers the monitoring schedule in which the monitoring timing group is set based on the selected available delivery time (i.e., the monitoring schedule of the operator On corresponding to the operator ID associated with the order ID) in the operator management database 124 (step S10), and ends the processing shown in Fig. 11. When the processing shown in Fig. 11 ends, the control unit 13 determines a delivery plan including the delivery schedule of the UAVm corresponding to the selected available delivery time, and registers it in the delivery plan management database 125 in association with the order ID of the confirmed order.

[0076] In addition, in response to the arrival of a monitoring timing for the UAVm to be monitored, the control unit 13 transmits (e.g., pushes) monitoring task information to the operator terminal OTn used by the operator On to cause the operator On to execute the monitoring task to be executed at the monitoring timing. Here, "in response to the arrival of the monitoring timing" means when the current time becomes the start point of the monitoring timing or when the current time becomes a few seconds before the start point. The monitoring task information may include a message prompting the operator On to execute the monitoring task. Such a message may include information indicating the contents of the monitoring task. In addition, the monitoring task information may include a control command to display (e.g., pop up) a monitoring task execution screen on the operator terminal OTn.

[0077] FIG. 16 is a diagram showing an example of a monitoring task execution screen displayed on the operator terminal OT1. The monitoring task execution screen shown in FIG. 16 displays UAV information related to the UAV1 to be monitored and UAV surrounding information related to the surrounding situation of the UAV1, as well as a message M that prompts the operator O1 to execute the monitoring task. The UAV information and UAV surrounding information are sequentially received from the monitoring task management server MS. As shown in FIG. 16, the UAV position display area 51 displays the position of the UAV1. The UAV status display area 52 displays the status of the UAV1. The UAV battery display area 53 displays the remaining battery power of the UAV1. It should be noted that a different monitoring task execution screen may be displayed for each task type.

[0078] In addition, the wind direction and wind speed display area 54 displays the wind direction and wind speed detected by a weather sensor installed in the store Fo or base P1 where the UAV1 is located. The rainfall amount display area 55 displays the amount of rainfall detected by a weather sensor installed in the store Fo or base P1 where the UAV1 is located. The weather display area 56 displays the weather in the area where the UAV1 is located. The UAV camera image display area 57 displays the UAV image captured by the camera of the UAV1. The surrounding camera image display area 58 displays the surrounding image of the UAV1 captured by the camera installed in the store Fo or base P1 where the UAV1 is located. The operator O1 will perform the monitoring task while looking at the information displayed on the monitoring task execution screen.

[0079] As described above, according to the above embodiment, the monitoring task management server MS extracts a plurality of possible delivery times of the ordered product by the UAVm used for delivery of the ordered product, acquires a monitoring timing for executing a monitoring task for monitoring the UAVm used for delivery of the ordered product for each extracted possible delivery time, sets the monitoring timing separately for each possible delivery time in the monitoring schedule of the operator On, specifies a possible delivery time in which the monitoring timing continues for a predetermined period of time or more in the monitoring schedule in which the monitoring timing is set, and controls so that the specified possible delivery time cannot be selected by the orderer. Therefore, it is possible to limit the possible delivery time that the orderer can select according to the monitoring schedule and the monitoring timing of the operator On. Therefore, it is possible to effectively prevent the decrease in the concentration of the operator On due to the monitoring timing for monitoring each of the multiple UAVm being too continuous, while allowing the operator On to appropriately execute the monitoring task.

[0080] Further, according to the above embodiment, the monitoring task management server MS extracts a plurality of possible delivery times of the ordered product by the UAVm used for delivery of the ordered product, acquires a monitoring timing for executing a monitoring task for monitoring the UAVm used for delivery of the ordered product for each extracted possible delivery time, sets the monitoring timing separately for each possible delivery time in the monitoring schedule of the operator On, specifies a possible delivery time in which the monitoring timing for executing a monitoring task associated with a relatively high load level occurs n (n≧2) times in succession in the monitoring schedule in which the monitoring timing is set, and controls so that the specified possible delivery time cannot be selected by the orderer, so that the possible delivery time that the orderer can select can be limited according to the monitoring schedule and the monitoring timing of the operator On. Therefore, it is possible to effectively prevent the concentration of the operator On from decreasing due to the succession of monitoring timing for executing a monitoring task associated with a relatively high load level, while allowing the operator On to appropriately execute the monitoring task.

[0081] Further, according to the above embodiment, the monitoring task management server MS extracts a plurality of possible delivery times of the ordered product by the UAVm used for delivery of the ordered product, acquires a monitoring timing at which a monitoring task for monitoring the UAVm used for delivery of the ordered product should be executed for each extracted possible delivery time, and sets the monitoring timing separately for each possible delivery time in the monitoring schedule of the operator On, specifies a rest time between the end point of any of the monitoring timings and the start point of the following monitoring timing in the monitoring schedule in which the monitoring timing is set, specifies a possible delivery time at which a relatively high load level is associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the rest time, and controls so that the specified possible delivery time cannot be selected by the orderer, so that the possible delivery time that the orderer can select can be limited according to the monitoring schedule and the monitoring timing of the operator On. Therefore, it is possible to effectively prevent the decrease in the concentration of the operator On due to the relatively high load level being associated with each monitoring task to be executed at the monitoring timing immediately before and immediately after the break time, while allowing the operator On to appropriately execute the monitoring task.

[0082] The above embodiment is one embodiment of the present invention, and the present invention is not limited to the above embodiment. Various configurations and the like may be changed from the above embodiment without departing from the gist of the present invention, and such changes are also included in the technical scope of the present invention. In the above embodiment, the case where an orderer orders a product sold at a store Fo is described as an example, but the present invention can also be applied to the delivery of items other than products. An example of such a case is the delivery of relief supplies or support supplies requested by a delivery requester to an evacuation site. In addition, in the above embodiment, a UAV is described as an example of an unmanned aerial vehicle, but the present invention can also be applied to a flying robot or the like as an example of an unmanned aerial vehicle.

[0083] <Additional Notes> [1] A delivery time control device according to the present disclosure includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; an extraction unit that extracts a plurality of delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; a second acquisition unit that acquires, for each of the extracted delivery times, a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed; and The system is characterized by comprising: a setting unit that sets the acquired second monitoring timing in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a specifying unit that specifies a possible delivery time in which the monitoring timing continues for a predetermined time or more in the monitoring schedule in which the second monitoring timing is set from the extracted possible delivery time; and a presentation control unit that controls the presentation of the possible delivery time of the second item to a delivery requester of the second item in a selectable manner, and controls the presentation control unit so that the delivery requester cannot select the specified possible delivery time. This makes it possible to limit the possible delivery time that the orderer can select according to the monitoring schedule and the monitoring timing of the operator. Therefore, it is possible to effectively prevent the operator's concentration from decreasing due to the monitoring timings at which the monitoring task for monitoring each of the multiple unmanned aerial vehicles should be executed being too consecutive, while allowing the operator to properly execute the monitoring task.

[0084] [2] In the delivery time control device described in [1] above, the monitoring task is associated with a load level indicating the load of the operator executing the monitoring task, and the identifying unit identifies, from the extracted delivery time, a delivery time during which the monitoring timing at which the monitoring task associated with the relatively high load level should be executed in the monitoring schedule in which the second monitoring timing is set occurs n (n≧2) times in succession. This makes it possible to allow the operator to properly execute the monitoring task while effectively preventing a decrease in the operator's concentration due to successive monitoring timings at which the monitoring task associated with the relatively high load level should be executed.

[0085] [3] The delivery time control device of the present disclosure includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts a plurality of delivery possible times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery possible times, and a delivery time control unit that controls the delivery time so that the second monitoring timing acquired for each of the extracted delivery possible times does not overlap with the first monitoring timing. The present invention is characterized in that it includes a setting unit that sets each possible delivery time separately in the monitoring schedule, a load level indicating the degree of load of the operator performing the monitoring task is associated with the monitoring task, a specifying unit that specifies a possible delivery time from the extracted possible delivery times at which the monitoring timing for executing the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring timing is set will occur n (n≧2) times or more in succession, and a presentation control unit that controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and controls the delivery requester not to be able to select the specified possible delivery time. This makes it possible to limit the possible delivery times that an orderer can select according to the monitoring schedule and the monitoring timing of the operator. Therefore, it is possible to effectively prevent the operator's concentration from decreasing due to the continuous monitoring timing for executing the monitoring task associated with the relatively high load level, while allowing the operator to properly execute the monitoring task.

[0086] [4] In the delivery time control device described in [2] or [3] above, the n is set to a larger value as the load level is lower. This makes it possible to appropriately control the number of times an operator is allowed to execute a monitoring task consecutively, depending on the load level of the monitoring task.

[0087] [5] In the delivery time control device described in any one of [1] to [4] above, the monitoring task is associated with a load level indicating the load of the operator performing the monitoring task, and the identification unit identifies a break time between the end point of any of the monitoring timings and the start point of the following monitoring timing in the monitoring schedule in which the second monitoring timing is set, and identifies a delivery time from the extracted delivery time in which a relatively high load level is associated with each of the monitoring tasks to be performed at the monitoring timings immediately before and immediately after the break time. This makes it possible to effectively prevent the operator's concentration from decreasing due to a relatively high load level being associated with each of the monitoring tasks to be performed at the monitoring timings immediately before and immediately after the break time, while allowing the operator to properly perform the monitoring task.

[0088] [6] The delivery time control device of the present disclosure includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts a plurality of delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery times, and a setting unit that sets the second monitoring timing acquired for each of the extracted delivery times in the monitoring schedule separately for each delivery time so as not to overlap with the first monitoring timing. The system is characterized in that it includes a monitoring task-related load level indicating the load of the operator performing the monitoring task, a determination unit that determines a break time between the end point of any of the monitoring timings and the start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and determines from the extracted possible delivery times a possible delivery time at which a relatively high load level is associated with each of the monitoring tasks to be performed at the monitoring timings immediately before and immediately after the break time, and a presentation control unit that controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and controls the delivery requester not to be able to select the determined possible delivery time. This makes it possible to limit the possible delivery time that the orderer can select according to the monitoring schedule and the monitoring timing of the operator. Therefore, it is possible to effectively prevent the decrease in the operator's concentration, etc., caused by the relatively high load level being associated with each of the monitoring tasks to be performed at the monitoring timings immediately before and immediately after the break time, while allowing the operator to properly perform the monitoring task.

[0089] [7] The unmanned aerial vehicle monitoring system of the present disclosure includes a first acquisition unit that acquires a monitoring schedule of an operator performing a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts a plurality of possible delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times, and the second monitoring timing acquired by the second monitoring timing acquisition unit 203 and the first monitoring timing acquisition unit 213, the second monitoring timing acquired by the second monitoring timing acquisition unit 204, the monitoring schedule being set for each possible delivery time separately so as not to overlap with the first monitoring timing; a determination unit 222 that determines, from the extracted possible delivery times, a possible delivery time in which the monitoring timing will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; and a presentation control unit 223 that controls the presentation of possible delivery times for the second item to a person requesting delivery of the second item in a selectable manner, the presentation control unit 223 that controls the delivery control unit 203 so that the person requesting delivery of the second item cannot select the determined possible delivery time.

[0090] [8] The unmanned aerial vehicle monitoring system of the present disclosure includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts a plurality of possible deliverable times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible deliverable times, and an extraction unit that extracts a plurality of possible deliverable times so as not to overlap with the first monitoring timing. The system is characterized in that it comprises a setting unit which sets each possible delivery time separately in the monitoring schedule, a load level which indicates the degree of load on the operator when executing the monitoring task is associated with the monitoring task, an identification unit which identifies from the extracted possible delivery times a possible delivery time at which the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed, the monitoring task, from which the relatively high monitoring timing should be executed, occurs n (n≧2) times or more in succession, and a presentation control unit which controls the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and which controls the presentation control unit so that the delivery requester cannot select the identified possible delivery times.

[0091] [9] The unmanned aerial vehicle monitoring system of the present disclosure includes a first acquisition unit that acquires a monitoring schedule of an operator that executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed, an extraction unit that extracts a plurality of possible deliverable times for a second item by a second unmanned aerial vehicle used to deliver the second item, a second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible deliverable times, and a setting unit that sets the second monitoring timing acquired for each of the extracted possible deliverable times in the monitoring schedule separately for each possible deliverable time so as not to overlap with the first monitoring timing. a determination unit which determines a rest time between an end point of any one of the monitoring timings and a start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and determines from the extracted possible delivery times a possible delivery time at which a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timing immediately before and after the rest time; and a presentation control unit which controls the presentation of possible delivery times for the second item to a person requesting delivery of the second item in a selectable manner, the presentation control unit controlling so that the person requesting delivery cannot select the determined possible delivery time.

[0092]

[10] The delivery time control method of the present disclosure is a delivery time control method executed by a computer, comprising the steps of: acquiring a monitoring schedule of an operator performing a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; extracting multiple delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; and acquiring, for each of the extracted delivery times, a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed; The method includes a step of setting the second monitoring timing obtained for each extracted possible delivery time in the monitoring schedule separately for each possible delivery time so that the second monitoring timing does not overlap with the first monitoring timing; a step of identifying a possible delivery time from the extracted possible delivery times in which the monitoring timing will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; and a step of controlling the presentation of possible delivery times for the second item to a person requesting delivery of the second item in a selectable manner, wherein the step of controlling so that the person requesting delivery cannot select the identified possible delivery time.

[0093]

[11] The delivery time control method of the present disclosure is a delivery time control method executed by a computer, comprising the steps of: acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; extracting a plurality of delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; acquiring a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery times; and calculating the second monitoring timing acquired for each of the extracted delivery times based on the first monitoring timing. a step of setting each of the possible delivery times separately in the monitoring schedule so as not to overlap with a second monitoring timing; a step of associating a load level indicating the degree of load on the operator when executing the monitoring task with the monitoring task, and a step of identifying from the extracted possible delivery times a possible delivery time at which the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed, the possible delivery time being n (n≧2) or more consecutive times; and a step of controlling the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, wherein the step of controlling so that the delivery requester cannot select the identified possible delivery times.

[0094]

[12] The delivery time control method of the present disclosure is a delivery time control method executed by a computer, comprising the steps of: acquiring a monitoring schedule of an operator performing a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule being set with a first monitoring timing at which the first monitoring task should be executed; extracting a plurality of delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; acquiring a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted delivery times; and pre-registering the second monitoring timing acquired for each of the extracted delivery times separately for each of the delivery times so as not to overlap with the first monitoring timing. The method includes a step of setting the monitoring schedule, a step of associating a load level indicating the degree of load on the operator when executing the monitoring task with the monitoring task, a step of identifying a rest time between an end point of any of the monitoring timings and a start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and a step of identifying from the extracted possible delivery times a possible delivery time at which a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timing immediately before and after the rest time, and a step of controlling the presentation of possible delivery times for the second item to a delivery requester of the second item in a selectable manner, and a step of controlling so that the delivery requester cannot select the identified possible delivery time. [Explanation of symbols]

[0095] 11 Communications Department 12 Storage section 13 Control section 131 Delivery time extraction part 132 Monitoring schedule acquisition unit 133 Monitoring Timing Acquisition Section 134 Monitoring timing setting section 135 Selection and exclusion specific section 136 Presentation control unit 137 Monitoring Schedule Update Section PS Order Processing Server MS Monitoring Task Management Server OTn Operator Terminal UT Orderer Terminal S Delivery Management System NW Communication network

Claims

1. a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; An extraction unit that extracts a plurality of possible delivery times of the second item by a second unmanned aerial vehicle used to deliver the second item; A second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times; a setting unit that sets the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a specification unit that specifies, from the extracted possible delivery times, a possible delivery time during which the monitoring timings will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; a presentation control unit that controls the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the presentation control unit controlling the presentation control unit to prevent the delivery requester from selecting the specified available delivery times; A delivery time control device comprising:

2. A load level indicating a load of the operator performing the monitoring task is associated with the monitoring task; and The delivery time control device according to claim 1, characterized in that the identification unit identifies, from the extracted delivery time, a delivery time during which the monitoring task associated with the relatively high load level in the monitoring schedule in which the second monitoring time is set will have n (n≧2) or more consecutive monitoring times at which the monitoring task should be executed.

3. a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; An extraction unit that extracts a plurality of possible delivery times of the second item by a second unmanned aerial vehicle used to deliver the second item; A second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times; a setting unit that sets the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a determining unit which determines, from the extracted possible deliverable time, a possible deliverable time during which the monitoring task associated with a load level indicating the degree of load of the operator executing the monitoring task will have n (n≧2) or more consecutive monitoring timings during which the monitoring task associated with a relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed; a presentation control unit that controls the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the presentation control unit controlling the presentation control unit to prevent the delivery requester from selecting the specified available delivery times; A delivery time control device comprising:

4. 4. The delivery time control device according to claim 2, wherein the n is set to a larger value as the load level is lower.

5. A load level indicating a load of the operator performing the monitoring task is associated with the monitoring task; and The delivery time control device according to claim 1, characterized in that the identification unit identifies a break time between the end point of any of the monitoring timings and the start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and identifies from the extracted delivery time a delivery time at which a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timings immediately before and after the break time.

6. a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; An extraction unit that extracts a plurality of possible delivery times of the second item by a second unmanned aerial vehicle used to deliver the second item; A second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times; a setting unit that sets the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a specifying unit which specifies a rest time between an end point of any one of the monitoring timings and a start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and specifies from the extracted possible deliverable times a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timings immediately before and after the rest time; a presentation control unit that controls the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the presentation control unit controlling the presentation control unit to prevent the delivery requester from selecting the specified available delivery times; A delivery time control device comprising:

7. a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; An extraction unit that extracts a plurality of possible delivery times of the second item by a second unmanned aerial vehicle used to deliver the second item; A second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times; a setting unit that sets the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a specification unit that specifies, from the extracted possible delivery times, a possible delivery time during which the monitoring timings will continue for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; a presentation control unit that controls the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the presentation control unit controlling the presentation control unit to prevent the delivery requester from selecting the specified available delivery times; An unmanned aerial vehicle monitoring system comprising:

8. a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; An extraction unit that extracts a plurality of possible delivery times of the second item by a second unmanned aerial vehicle used to deliver the second item; A second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times; a setting unit that sets the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a determining unit which determines, from the extracted possible deliverable time, a possible deliverable time during which the monitoring task associated with a load level indicating the degree of load of the operator executing the monitoring task will have n (n≧2) or more consecutive monitoring timings during which the monitoring task associated with a relatively high load level in the monitoring schedule in which the second monitoring timing is set should be executed; a presentation control unit that controls the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the presentation control unit controlling the presentation control unit to prevent the delivery requester from selecting the specified available delivery times; An unmanned aerial vehicle monitoring system comprising:

9. a first acquisition unit that acquires a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; An extraction unit that extracts a plurality of possible delivery times of the second item by a second unmanned aerial vehicle used to deliver the second item; A second acquisition unit that acquires a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted possible delivery times; a setting unit that sets the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a specifying unit which specifies a rest time between an end point of any one of the monitoring timings and a start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and specifies from the extracted possible deliverable times a relatively high load level will be associated with each of the monitoring tasks to be executed at the monitoring timings immediately before and after the rest time; a presentation control unit that controls the presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the presentation control unit controlling the presentation control unit to prevent the delivery requester from selecting the specified available delivery times; An unmanned aerial vehicle monitoring system comprising:

10. 1. A computer-implemented method for controlling delivery times, comprising the steps of: A step of acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; Extracting a plurality of possible delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; Obtaining a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted available delivery times; setting the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; specifying, from the extracted possible delivery times, a possible delivery time during which the monitoring timing continues for a predetermined period of time or more in the monitoring schedule in which the second monitoring timing is set; a step of controlling a presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the step of controlling so that the delivery requester cannot select the specified available delivery times; A method for controlling delivery time, comprising:

11. 1. A computer-implemented method for controlling delivery times, comprising the steps of: A step of acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; Extracting a plurality of possible delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; Obtaining a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted available delivery times; setting the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a step of associating a load level indicating the load of the operator performing the monitoring task with the monitoring task, and identifying, from the extracted possible delivery time, a possible delivery time during which the monitoring task associated with a relatively high load level in the monitoring schedule in which the second monitoring timing is set will have n (n≧2) or more consecutive monitoring timings during which the monitoring task should be executed; a step of controlling a presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the step of controlling so that the delivery requester cannot select the specified available delivery times; A method for controlling delivery time, comprising:

12. 1. A computer-implemented method for controlling delivery times, comprising the steps of: A step of acquiring a monitoring schedule of an operator who executes a first monitoring task for monitoring a first unmanned aerial vehicle used to deliver a first item, the monitoring schedule having a first monitoring timing set for executing the first monitoring task; Extracting a plurality of possible delivery times for a second item by a second unmanned aerial vehicle used to deliver the second item; Obtaining a second monitoring timing at which a second monitoring task for monitoring the second unmanned aerial vehicle should be executed for each of the extracted available delivery times; setting the second monitoring timing acquired for each of the extracted possible delivery times in the monitoring schedule separately for each possible delivery time so as not to overlap with the first monitoring timing; a step of associating a load level indicating the load of the operator performing the monitoring task with the monitoring task, identifying a rest period between an end point of any one of the monitoring timings and a start point of the subsequent monitoring timing in the monitoring schedule in which the second monitoring timing is set, and identifying from the extracted possible deliverable times a relatively high load level will be associated with each of the monitoring tasks to be performed at the monitoring timings immediately before and after the rest period; a step of controlling a presentation of available delivery times for the second item to a delivery requester of the second item in a selectable manner, the step of controlling so that the delivery requester cannot select the specified available delivery times; A method for controlling delivery time, comprising:

Images