Surveillance plan determination device, unmanned aerial vehicle surveillance system, and surveillance plan determination method

Abstract

To provide a monitoring plan determination device capable of properly determining a monitoring plan about whether an operator monitors an unmanned areal vehicle at which monitoring timing in consideration of a deliverable time selected by a delivery client, an unmanned area vehicle monitoring system, and a monitoring plan determination method.SOLUTION: A monitoring task management server MS is configured to: acquire a monitoring schedule including a time zone in which an operator On can execute a monitoring task; extract a plurality of deliverable times of a commodity by a UAVm; acquire a required monitoring timing requiring the monitoring of the UAVm associated with the deliverable times per deliverable time; generate a monitoring plan associated with the deliverable times per deliverable time on the basis of the monitoring schedule and the required monitoring timing per deliverable time; present the plurality of deliverable times to an orderer of the commodity in a selectable manner; and determine a monitoring plan corresponding to one deliverable time selected by the orderer from among the plurality of presented deliverable times.SELECTED DRAWING: Figure 12

Description

Technical Field

[0001] The present invention relates to the technical field of systems for monitoring unmanned aerial vehicles used for delivering goods and the like.

Background Art

[0002] Conventionally, as disclosed in Patent Document 1 for example, there is known a technique in which a plurality of operators located at a location separate from an unmanned aerial vehicle (an example of an unmanned flying object) monitor and control a plurality of unmanned aerial vehicles in flight via a computing device. According to the technique of Patent Document 1, one operator can monitor and control a larger number of unmanned aerial vehicles.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

[0004] By the way, it is not desirable for one operator to monitor a plurality of unmanned aerial vehicles simultaneously from the viewpoint of safety and the like. In the future, when goods are delivered by a plurality of unmanned aerial vehicles from a plurality of bases, it is desirable to adjust the monitoring schedules of the operators so that the monitoring timing requirements for each of the plurality of unmanned aerial vehicles do not overlap. Furthermore, since such monitoring timing requirements vary according to the deliverable time selected by the delivery requester, it is necessary to consider the deliverable time in the above adjustment.

[0005] Therefore, an example of an object of the present invention is to provide a monitoring plan determination device, an unmanned flying object monitoring system, and a monitoring plan determination method that can appropriately determine a monitoring plan for an operator to monitor an unmanned aerial vehicle at which monitoring timing, taking into account the deliverable time selected by the delivery requester.

Means for Solving the Problems

[0006] (Application Example 1) To solve the above problems, the monitoring plan determination device according to this application example is a monitoring schedule of an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering goods, and includes a first acquisition unit that acquires the monitoring schedule including the time zone in which the operator can execute the monitoring task, an extraction unit that extracts a plurality of deliverable times of the goods by the unmanned aerial vehicle, a second acquisition unit that acquires, for each of the deliverable times, a monitoring timing that requires monitoring of the unmanned aerial vehicle associated with the deliverable time, a generation unit that generates, for each of the deliverable times, a monitoring plan for the unmanned aerial vehicle associated with the deliverable time based on the monitoring schedule and the monitoring timing for each of the deliverable times, a presentation control unit that presents the plurality of deliverable times extracted by the extraction unit to the delivery requester of the goods in a selectable manner, and a determination unit that determines one monitoring plan from among the plurality of monitoring plans generated by the generation unit, wherein the determination unit determines a monitoring plan corresponding to one of the deliverable times selected by the delivery requester from among the plurality of deliverable times presented by the presentation control unit.

[0007] (Application Example 2) The unmanned aircraft monitoring system according to this application example is a monitoring schedule for an operator who executes a monitoring task for monitoring an unmanned aircraft used for delivering goods, including a first acquisition unit that acquires the monitoring schedule including a time period during which the operator can execute the monitoring task, an extraction unit that extracts a plurality of deliverable times of the goods by the unmanned aircraft, a second acquisition unit that acquires, for each of the deliverable times, a monitoring timing that requires monitoring of the unmanned aircraft associated with the deliverable time, a generation unit that generates, for each of the deliverable times, a monitoring plan for the unmanned aircraft associated with the deliverable time based on the monitoring schedule and the monitoring timing for each of the deliverable times, a presentation control unit that presents the plurality of deliverable times extracted by the extraction unit to the delivery requester of the goods in a selectable manner, and a determination unit that determines one monitoring plan from among the plurality of monitoring plans generated by the generation unit, wherein the determination unit determines a monitoring plan corresponding to one of the deliverable times selected by the delivery requester from among the plurality of deliverable times presented by the presentation control unit.

[0008] (Application Example 3) The monitoring plan determination method according to this application example is a monitoring plan determination method executed by a computer, which is a monitoring schedule of an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering goods. The method includes: obtaining the monitoring schedule including the time periods during which the operator can execute the monitoring task; extracting a plurality of deliverable times of the goods by the unmanned aerial vehicle; obtaining, for each of the deliverable times, the monitoring timing that requires monitoring of the unmanned aerial vehicle associated with the deliverable time; generating, for each of the deliverable times, a monitoring plan for the unmanned aerial vehicle associated with the deliverable time based on the monitoring schedule and the monitoring timing for each of the deliverable times; presenting the extracted plurality of deliverable times to the delivery requester of the goods in a selectable manner; and a determination step of determining one monitoring plan from among the generated plurality of monitoring plans. In the determination step, a monitoring plan corresponding to one of the deliverable times selected by the delivery requester from among the plurality of deliverable times presented to the delivery requester is determined.

Effect of the Invention

[0009] According to the present invention, in consideration of the deliverable times selected by the delivery requester, it is possible to appropriately determine a monitoring plan for at which monitoring timings the operator monitors the unmanned aerial vehicle.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Mode for Carrying Out the Invention

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following embodiment is an embodiment when the present invention is applied to a delivery management system for managing the delivery of articles by an unmanned aerial vehicle (hereinafter referred to as "UAV (Unmanned Aerial Vehicle)") such as a drone. The UAV is an example of an unmanned flying body. In the following embodiment, a case will be described as an example in which a product (an example of an article) sold in a store is ordered from an orderer (an example of a delivery requester) using a terminal (hereinafter referred to as an "orderer terminal") to an order processing server, and the product is delivered to the delivery destination.

[0012] 1. Configuration and Operational Overview of Delivery Management System S First, referring to FIGS. 1 and 2, the configuration and operation overview of the delivery management system S according to this 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 deliverable 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. Further, the monitoring task management server MS may be integrally configured with the order processing server PS. The operator terminal OTn is used by an operator 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 terminal OTn are each connected to a communication network NW. The communication network NW is composed of, for example, the Internet, a mobile communication network, and its radio base stations, etc.

[0013] FIG. 2 is a conceptual diagram showing how the UAV1 delivers goods to the delivery destination. In the example of FIG. 2, a plurality of UAVm (m = 1, 2, 3,...) used for the delivery of goods are each deployed at different bases Pm (m = 1, 2, 3,...). Since the goods are sold in stores Fo (o = 1, 2, 3,...), the UAVm goes from the base Pm to the store Fo to pick up the goods. For example, as shown in FIG. 2, after the order for the goods is confirmed, the UAV1 flies from the base P1 to the store F1 where the goods are sold, loads the goods at the store F1, and then flies to the delivery destination. Note that a plurality of UAVm may be deployed at one base Pm. For example, UAV1 and UAV2 may be deployed at the base P1. Also, the base Pm and the store Fo may be in the same location. 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. ​​

[0014] The order processing server PS is a server that receives and processes orders from an orderer terminal UT (for example, a mobile terminal such as a smartphone) that has accessed via a communication network NW, and transmits information regarding the received order to a monitoring task management server MS. Here, the information regarding the order includes, for example, an order ID (identification information of the order), a user ID of the orderer (identification information of the orderer), a product ID of the product ordered by the orderer (identification information of the product), the product name, a store ID of the store selling the product (identification information of store Fo), and location information of the delivery destination (for example, latitude and longitude). Note that information regarding the product (for example, the product name, a photographic image of the product) is presented to the orderer in a selectable manner from the order processing server PS (that is, displayed on the orderer terminal UT).

[0015] In addition, the order processing server PS presents to the orderer in a selectable manner the delivery available times of the product (for example, a plurality of different delivery available times) (that is, displays them on the orderer terminal UT). Such delivery available times are provided by the monitoring task management server MS. When an arbitrary delivery available time is selected by the orderer from the delivery available times presented to the orderer, the order for the product is confirmed. Here, the delivery available time is a time period during which the product can be delivered to the delivery destination. In other words, the delivery available time is a scheduled time period when the UAVm loaded with the product arrives at the delivery destination. Alternatively, the delivery available time may be a scheduled time period when 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. Note that the delivery available time may be a time (for example, 12:00), but it is desirable that it be a time period (for example, 12:00 to 12:15) considering a certain margin.

[0016] The monitoring task management server MS is a server that manages information related to monitoring tasks for monitoring UAVm used for product delivery. The monitoring task can be, for example, an operation (task) of monitoring the state of UAVm and the surrounding situation of UAVm. The monitoring task is executed by operator On via the operator terminal OTn at the timing that requires monitoring of UAVm (the timing that requires monitoring of UAVm). The monitoring task may include a terminal operation (that is, an operation of the operator terminal OTn) for performing flight control (for example, movement control, hovering control) of UAVm according to the situation. Also, the monitoring task is assigned to a time zone in which the monitoring task can be executed in the monitoring schedule of operator On.

[0017] In the present embodiment, for example, a scenario is assumed in which operator O1 at the monitoring base performs monitoring tasks for each of a plurality of UAVm that perform delivery at different bases Pm. In order to perform safe delivery, information about UAVm is displayed on the operator terminal OT1 used by operator O1 at the timing when a monitoring task by operator O1 is required, such as when each UAVm arrives over or lands at store Fo. That is, for example, even if UAV1 that has departed from base P1 has arrived over store F1, if the delivery preparation of UAV2 has been completed at store F2 at the same timing and operator O1 is executing the monitoring task for it, the monitoring task for UAV1 cannot be executed.

[0018] Note that the monitoring in this embodiment includes the operator On visually observing (paying close attention). Therefore, the timing to be monitored can also be referred to as the timing to be observed (requiring observation). Also, it is desirable that the timing to be monitored be multiple timings separated by time in the delivery schedule related to one delivery by the UAVm to be monitored. This enables the operator On to efficiently execute the monitoring tasks to be performed at the timing to be monitored of the UAVm in the delivery schedule related to one delivery. However, the timing to be monitored may be one timing in the delivery schedule related to one delivery by the UAVm to be monitored. Here, the timing may be a point in time (in other words, a time), or it may be a time zone (that is, it may have a certain time width). The delivery schedule is, for example, the schedule from when the UAVm takes off from the base Pm until it lands at the delivery destination via the store Fo (or until it takes off from the delivery destination).

[0019] In addition, the monitoring task management server MS is configured to periodically or aperiodically receive UAV information regarding UAVm from UAVm via the communication network NW. Here, the UAV information includes, for example, the position, status, and remaining battery level detected by various sensors of UAVm. The UAV information may also include the UAV video captured by the camera of UAVm. The UAV video may include, for example, obstacles that may pose an obstacle to the takeoff and landing of UAVm. Further, the monitoring task management server MS may periodically or aperiodically receive UAV surrounding information regarding the surrounding situation of UAVm from various sensors installed in the store Fo or the base Pm via the communication network NW. The UAV surrounding information includes the wind direction, wind speed, and rainfall amount detected by the weather sensors installed in the store Fo or the base Pm. The UAV surrounding information may also include the surrounding video of UAVm captured by the cameras installed in the store Fo or the base Pm. The surrounding video may include, for example, obstacles that may pose an obstacle to the takeoff and landing of UAVm. Additionally, the monitoring task management server MS may periodically or aperiodically receive from the weather management server the weather of the area where UAVm is located as UAV surrounding information via the communication network NW.

[0020] 1-1. Configuration and Functions of Monitoring Task Management Server MS ​​Next, with reference to FIG. 3, the configuration and functions of the monitoring task management server MS will be described. FIG. 3 is a diagram showing a schematic configuration example 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 regarding an order from the order processing server PS. Further, the communication unit 11 receives at least one of UAV information and UAV surrounding information from the UAVm or the like. The storage unit 12 is composed of, for example, a hard disk drive or the like, and stores various programs including an operating system and applications. Here, the application includes a program for executing the delivery available time control method. In addition, the storage unit 12 has a buffer memory that sequentially updates and accumulates at least one of the UAV information and the UAV surrounding information received from the UAVm for each UAVm in association with the aircraft ID (identification information of the UAVm) of the UAVm.

[0021] In addition, the storage unit 12 stores a table for calculating the timing to be monitored. FIG. 4 is a diagram showing an example of the table for calculating the timing to be monitored. As shown in FIG. 4, in the table for calculating the timing to be monitored, the timing to be monitored, the reference time, and the task required time are registered in association with each other. Here, the reference time is the time for calculating the timing to be monitored associated therewith. The task required time is the length of time required for executing the monitoring task at the timing to be monitored associated therewith. In the example of FIG. 4, as examples of the timing to be monitored, the time of operation determination, the time of leaving the base, the time of landing at the store, the time of leaving the store, the time of flying to the delivery destination, and the time of landing at the delivery destination are shown (seven). Here, "time" may be "immediately before". The task types of the monitoring tasks to be executed at each timing to be monitored are different from each other. Note that the number of task types may be less than or more than the number (seven) shown in FIG. 4. In addition, when the base Pm and the store Fo are in the same location, the time of leaving the base, the time of landing at the store, and the time of leaving the store can be grouped together as the time of leaving the store.

[0022] Here, when the UAV departs from the store, it indicates the timing at which the UAVm loaded with goods departs from the store Fo for delivery (this is also referred to as "start of delivery"). This timing is set to the delivery start time T (time point) or the time zone based on the delivery start time T by referring to the associated reference time. The length of such a time zone may be equal to the task required time for executing the monitoring task at the timing to be monitored (the same applies to other timings to be monitored). In the table for calculating the timing to be monitored, the delivery start time T is registered as, for example, "0:00" for reference. When the UAV arrives at the store, it indicates the timing at which the UAVm that has departed from the base Pm arrives over the store and lands (for example, lands on the pedestal of the store Fo). This timing is set to the time point "ta" minutes (for example, 10 minutes) before the delivery start time T or the time zone based on this time point by referring to the associated reference time.

[0023] When the UAV departs from the base, it indicates the timing at which the UAVm departs from the base Pm. This timing is set to the time point "tb" minutes before the delivery start time T or the time zone based on this time point by referring to the associated reference time. "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 (planned speed) of the UAVm. When the operation is judged, it indicates the timing at which the flightability of the UAVm is judged. This timing is set to the time point "tc" minutes before the delivery start time T or the time zone based on this time point by referring to the associated reference time. "tc" minutes is the sum of "tb" minutes and the margin time "ty" minutes including the time required for the operation judgment.

[0024] During the flight to the delivery destination, for example, it indicates the timing when the UAVm that has taken off from the store Fo reaches the position during the delivery. This timing is set to the time point “te” minutes after the delivery start time T or the time zone based on this time point by referring to the reference time associated with it. The “te” minutes is the required time (flight duration) from the store Fo to the position during the delivery, and is calculated from the flight distance from the store Po to the position during the delivery and the flight speed of the UAVm. Note that the position during the delivery is a position at a predetermined ratio (for example, 50%) of the flight path from the store Fo to the delivery destination. During the landing at the delivery destination, for example, it indicates the timing when the UAVm that has taken off from the store Fo arrives over the delivery destination and lands. This timing is set to the time point “tf” minutes after the delivery start time T or the time zone based on this time point by referring to the reference time associated with it. The “tf” minutes is the required time (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 time point “tf” minutes after the delivery start time T corresponds to (for example, coincides with, or is included in) the above-mentioned deliverable time.

[0025] As described above, the monitoring tasks can be distinguished into a plurality of different task types. For example, the monitoring task at the time of operation determination, the monitoring task at the time of departure from the base, the monitoring task at the time of landing at the store, the monitoring task at the time of departure from the store, the monitoring task during the flight to the delivery destination, and the monitoring task at the time of landing at the delivery destination have different task types from each other. However, even for monitoring tasks with different task types, the content of the monitoring tasks (for example, what to focus on) may be the same or different.

[0026] Furthermore, in the memory unit 12, a store management database (DB) 121, an aircraft management database (DB) 122, a user management database (DB) 123, an operator management database (DB) 124, a delivery plan management database (DB) 125, a monitoring plan management database (DB) 126, etc. are constructed. The store management database 121 is a database for managing information regarding the store Fo that sells products. In the store management database 121, for example, a store ID, location information of the store Fo (e.g., latitude and longitude), etc. are associated and stored (registered) for each store Fo.

[0027] The aircraft management database 122 is a database for managing information regarding the UAVm used for product delivery. In the aircraft management database 122, for example, the aircraft ID of the UAVm, operating status, available time zone, and location information of the base Pm where the UAVm is deployed, etc. are associated and stored for each UAVm. The operating status indicates in operation (e.g., moving for delivery preparation, being used for delivery, returning), unavailable for use, or on standby, and is updated as appropriate. The available time zone indicates the year, month, day, and time zone when the UAVm can be used for delivery.

[0028] The user management database 123 is a database for managing information regarding users who have created accounts as members using the delivery service. Here, users who have created accounts can place orders for products through the orderer terminal UT as orderers to the order processing server PS. In the user management database 123, a user ID, name, address, email address, and phone number are associated and stored for each user. Note that the address or location information of the product delivery destination may be pre-registered in the user management database 123.

[0029] The operator management database 124 is a database for managing information regarding Operator On. In the operator management database 124, for example, the operator ID of Operator On (identification information of Operator On), the monitoring schedule of Operator On, access information (e.g., IP address) of the operator terminal OTN used by Operator On, etc. are stored in association with each Operator On. The monitoring schedule of Operator On includes, for example, at least one of the time periods (date and time period) during which Operator On can execute the monitoring task and the time periods (date and time period) during which it cannot. The time periods during which the monitoring task cannot be executed include, for example, the time periods during which a monitoring task for monitoring other UAVm has already been assigned (i.e., the time periods during which a monitoring task already exists) and rest time periods, etc.

[0030] The delivery plan management database 125 is a database for managing information regarding delivery plans. In the delivery plan management database 125, the order ID, the 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, the delivery schedule of the UAVm, etc. The UAVm shown in the delivery plan is the UAVm whose use for delivery has been determined. The delivery schedule includes the deliverable time, the delivery start time, etc. Note that one delivery corresponds to one order ID and one UAVm. For example, the product related to the order identified by the order ID "d0001" is delivered by UAV1, and the product related to the order identified by the order ID "d0002" is delivered by UAV2.

[0031] The monitoring plan management database 126 is a database for managing information related to the monitoring plan. In the monitoring plan management database 126, the order ID and the determined monitoring plan, etc. are stored in association with each order. Here, the monitoring plan is a plan indicating which operator On executes the monitoring task for which UAVm at which monitoring timing (in other words, the execution plan of the monitoring task). FIG. 5 is a diagram showing an example of the contents of the monitoring plan management database 126. As shown in FIG. 5, in the monitoring plan associated with the order ID "d0001", the operator ID of the operator On who executes the monitoring task is associated with each task type. Further, in the monitoring plan, it is preferable that the aircraft ID of the UAVm that requires monitoring at the monitoring timing is associated with the operator ID. In the example of FIG. 5, the monitoring timing is represented by a time zone (for convenience, the year, month, and day are omitted), and the monitoring task will be executed in this time zone (the time zone related to the monitoring timing).

[0032] The control unit 13 includes a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like. FIG. 6 is a diagram showing an example of the functional blocks in the control unit 13. The control unit 13 functions as, for example, a delivery available time extraction unit 131, a monitoring schedule acquisition unit 132 (an example of the first acquisition unit), a monitoring timing acquisition unit 133 (an example of the second acquisition unit), a monitoring plan generation unit 134, a presentation control unit 135, a monitoring task information transmission unit 136 (an example of the transmission unit), and a delay control unit 137, etc. according to a program (a program code group) stored in the ROM or the storage unit 12 as shown in FIG. 6.

[0033] When information regarding an order is received, for example, the delivery possible time extraction unit 131 extracts a predetermined number (for example, three or more) of delivery possible times for the product related to the order based on the estimated time required for delivering the product related to the order. Here, the estimated time required for delivering the product is estimated from the preparation time such as picking up and loading the product, and the time required until UAVm reaches the delivery destination. Such required time is calculated from, for example, the flight distance specified from the position information of the base Pm where UAVm waits, the position information of the store Fo, and the position information of the delivery destination, and the flight speed of UAVm. In addition, when extracting the delivery possible time, the available time zone of UAVm managed in the aircraft management database 122 may be referred to as appropriate.

[0034] For example, multiple delivery possible times are extracted such as “12:00 (start point) ~ 12:15 (end point)”, “12:15 ~ 12:30”, “12:30 ~ 12:45”, “12:45 ~ 13:00”, “13:00 ~ 13:15” ···. A part of the time zones corresponding to each of such multiple delivery possible times may overlap. In this case, for example, multiple delivery possible times are extracted such as “12:00 ~ 12:15”, “12:10 ~ 12:25”, “12:20 ~ 12:35”. In this example, the length of the time zone is 15 minutes, but it is not particularly limited. Note that the order ID and the UAVm (aircraft ID) capable of delivering the product at the delivery destination are associated with the extracted delivery possible time.

[0035] When information regarding an order is received, for example, the monitoring schedule acquisition unit 132 acquires the monitoring schedules of each of the plurality of operators On from the operator management database 124. The monitoring timing acquisition unit 133 that requires monitoring acquires the timing that requires monitoring of UAVm. For example, the monitoring timing acquisition unit 133 that requires monitoring acquires each monitoring timing (a plurality of monitoring timings) that requires monitoring of UAVm associated with the deliverable time based on the deliverable time extracted by the deliverable time extraction unit 131 and the monitoring timing calculation table stored in the storage unit 12. Here, each monitoring timing required for one delivery is hereinafter also referred to as a "monitoring timing group".

[0036] More specifically, the delivery start time T (for example, 11:20) is calculated (that is, calculated backward) from the start point of the deliverable time (for example, 12:00) extracted by the deliverable time extraction unit 131 and the time required from the store Fo to the delivery destination (for example, 40 minutes). The order ID and the deliverable time are associated with the calculated delivery start time T. Then, the calculated delivery start time T is applied to the monitoring timing calculation table, and the monitoring timing group is acquired. For example, when 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, the monitoring timing group is calculated. When a plurality of deliverable times are extracted by the deliverable time extraction unit 131, a monitoring timing group corresponding to each deliverable time is acquired.

[0037] The monitoring plan generation unit 134 generates a monitoring plan for the UAVm associated with the deliverable time based on the monitoring schedule acquired by the monitoring schedule acquisition unit 132 and the monitoring timing to be monitored (for example, the group of monitoring timings to be monitored) acquired by the monitoring timing acquisition unit 133. For example, the monitoring plan generation unit 134, based on the respective monitoring schedules of the operators O1 and O2 (that is, a plurality of monitoring schedules) and the group of monitoring timings corresponding to the deliverable time, determines that among the plurality of monitoring schedules, at a time zone when any one of the operators O1 among the plurality of operators O1 and O2 can execute the monitoring task in any one of the monitoring schedules. For example, by allocating the monitoring tasks to be executed at each of the monitoring timings within the group of monitoring timings of UAV1, a monitoring plan is generated. Thereby, the monitoring tasks to be executed at each of the monitoring timings within the group of monitoring timings of one UAV1 can be more efficiently executed by one operator O1 (operator ID "o0001") in one go (for example, refer to the order ID "d0001" shown in FIG. 5).

[0038] As described above, the process for generating the monitoring plan is performed for each deliverable time extracted by the deliverable time extraction unit 131. And when the monitoring plan is generated, the monitoring plan is associated with the order ID and the deliverable time. Note that, for example, in the monitoring schedule of the operator O1, there may already be a monitoring task assigned for monitoring another UAV2 deployed at a base P2 different from the base P1 of the UAV1, for example. Thereby, the monitoring tasks to be executed at the monitoring timings of the UAVm deployed at each of the plurality of bases Pm can be efficiently executed by one operator O1.

[0039] FIG. 7 is a conceptual diagram showing the temporal relationship between the respective monitoring schedules SC1 and SC2 of operators O1 and O2 and the groups of monitoring timing TG1 to TG3. The groups of monitoring timing TG1 to TG3 respectively correspond to the deliverable times PT1 to PT3. For the sake of convenience of explanation, the groups of monitoring timing TG1 to TG3 are each composed of three monitoring timings TBD (for example, at the time of operation determination, at the time of departure from the store, and at the time of arrival at the delivery destination). In addition, in each of the monitoring schedules SC1 and SC2, a time period TOK during which each of the operators O1 and O2 can execute a monitoring task and a time period TNG during which execution is not possible are shown. In this example, the monitoring tasks to be executed at each of the three monitoring timings TBD within the group of monitoring timing TG3 are assigned to the time period TOK during which they can be executed by the operator O1. Thereby, a monitoring plan corresponding to the deliverable time PT3 is generated.

[0040] Note that in FIG. 7, at least one of the three monitoring timings TBD within the group of monitoring timing TG1 corresponding to the deliverable time PT1 partially overlaps with the time period TNG during which the operator O1 cannot execute. Similarly, at least one of the three monitoring timings TBD within the group of monitoring timing TG1 partially overlaps with the time period TNG during which the operator O2 cannot execute. Therefore, a monitoring plan corresponding to the deliverable time PT1 is not generated. On the other hand, among the deliverable times extracted by the deliverable time extraction unit 131, if there is a deliverable time to which the monitoring tasks to be executed at each of the monitoring timings TBD can be assigned to the time period TOK during which the monitoring tasks can be executed, a monitoring plan corresponding to the deliverable time is also generated. That is, in one order, monitoring plans corresponding to each of a plurality of deliverable times may be generated. In this case, the monitoring plan corresponding to one deliverable time selected by the order placer is determined.

[0041] As another example, the monitoring plan generation unit 134 may generate a monitoring plan by allocating the monitoring tasks to be executed at the first monitoring timing within the group of monitoring timings to be monitored to the time period during which the operator O1 can execute the monitoring tasks in the monitoring schedule of the operator O1, and allocating the monitoring tasks to be executed at the second monitoring timing within the group of monitoring timings to be monitored to the time period during which the operator O2 can execute the monitoring tasks in the monitoring schedule of the operator O2. Thereby, the execution burden of the monitoring tasks to be executed at each of the monitoring timings within the group of monitoring timings of one UAVm can be distributed among a plurality of operators On. In this case, in FIG. 7, one of the three monitoring timings TBD within the group of monitoring timings TG2 corresponding to the deliverable time PT2 (the right TBD in the example of FIG. 7) for which the monitoring task to be executed is allocated to the time period TOK during which the operator O1 can execute, and the monitoring tasks to be executed at the remaining two (the left and center TBDs in the example of FIG. 7) are allocated to the time period TOK during which the operator O2 can execute. Thereby, a monitoring plan corresponding to the deliverable time PT2 is generated.

[0042] Alternatively, as another example, the operator On who executes the monitoring task may be fixed for each task type (i.e., complete division of labor for each task type). As a result, the monitoring tasks to be executed at the respective monitoring timing of the plurality of UAVm can be divided among a plurality of operators On for each task type. Therefore, it becomes possible to enhance the expertise of the monitoring tasks for each task type, and the operator On can execute the monitoring task more appropriately. In this case, the monitoring plan generation unit 134, for example, in the monitoring schedule of the operator O1, at a time zone when the operator O1 can execute the monitoring task, assigns the monitoring task of the first task type (for example, the monitoring task at the time of store landing) to be executed at the monitoring timing of UAV1 and the monitoring task of the first task type to be executed at the monitoring timing of UAV2, and in the monitoring schedule of the operator O2, at a time zone when the operator O2 can execute the monitoring task, assigns the monitoring task of the second task type (for example, the monitoring task at the time of store takeoff) to be executed at the monitoring timing of UAV1 and the monitoring task of the second task type to be executed at the monitoring timing of UAV2 to generate a monitoring plan.

[0043] FIG. 8 is a diagram showing an example of the content of the monitoring plan management database 126 when the operator On who executes the monitoring task is fixed for each task type. In the example of FIG. 8, the monitoring task at the time of store landing is assigned to be executed by the operator O1 (operator ID “o0001”). Also, the monitoring task at the time of operation determination and the monitoring task at the time of store takeoff are assigned to be executed by the operator O2 (operator ID “o0002”). Further, the monitoring task at the time of base takeoff, the monitoring task during flight to the delivery destination, and the monitoring task at the time of delivery destination landing are assigned to be executed by the operator O3 (operator ID “o0003”).

[0044] The prompting control unit 135 controls to prompt the orderer of the product to be able to select the deliverable time of the product by the UAVm (that is, display it on the orderer's terminal UT). Such prompting of the deliverable time is performed by the order processing server PS transmitting information indicating the deliverable time provided by the prompting control unit 135 to the orderer's terminal UT. At this time, the prompting control unit 135 controls, based on the above-described monitoring schedule and the timing to be monitored, so that the orderer cannot select some of the deliverable times. Thereby, it is possible to appropriately prevent the operator On from being unable to execute the monitoring task. Also, it is possible to limit the deliverable times that the orderer can select according to the monitoring schedule of the operator On and the timing to be monitored of the UAVm. Therefore, it is possible to appropriately cause the operator On to execute the monitoring task to be performed at the timing to be monitored that requires monitoring of the UAVm.

[0045] For example, the prompting control unit 135 controls so as not to include the above-mentioned part of the deliverable times in the information provided to the order processing server PS. Alternatively, the prompting control unit 135 may control to include in the information provided to the order processing server PS the above-mentioned part of the deliverable times and information indicating that the deliverable times cannot be selected. Note that the prompting control unit 135 may control to directly transmit the information indicating the deliverable time from the monitoring task management server MS to the orderer's terminal UT without passing through the order processing server PS. Here, the above-mentioned part of the deliverable times is, for example, among the plurality of deliverable times extracted by the deliverable time extraction unit 131, the deliverable times corresponding to the timing to be monitored (for example, the group of timings to be monitored) at which the operator On (for example, all of the plurality of operators On) becomes unable to execute the monitoring task. Thereby, if it is the timing to be monitored at which even one of the plurality of operators On can execute the monitoring task, the deliverable time corresponding to such timing to be monitored can be presented to the orderer. Therefore, it is possible to efficiently cause the operator On to execute the monitoring task to be performed at the timing to be monitored that requires monitoring of the UAVm.

[0046] Note that, separately from the monitoring plan generation process by the monitoring plan generation unit 134, the presentation control unit 135, based on the monitoring schedule for Operator On and the group of monitoring timing requirements corresponding to the above-extracted deliverable times, performs an allocation process for allocating the monitoring tasks to be executed at each of the monitoring timing requirements within the group of monitoring timing requirements during the time period when Operator On can execute the monitoring tasks. Such an allocation process is performed for each of the above-extracted multiple deliverable times. Then, based on the result of the allocation process, the presentation control unit 135 identifies, as the above partial deliverable times, the deliverable times corresponding to the monitoring timing requirements for which Operator On cannot execute the monitoring tasks among the above-extracted multiple deliverable times. Thereby, it is possible to quickly identify the deliverable times that limit the presentation to the orderer.

[0047] FIG. 9 is a diagram showing an example of a deliverable time selection screen displayed on the orderer terminal UT. On the deliverable time selection screen shown in FIG. 9, “12:45~13:00”, “13:00~13:15”, and “13:15~13:30” are displayed as deliverable times. Among these, “13:00~13:15” and “13:15~13:30” are the deliverable times presented as selectable. For example, when the “Select” button B associated with “13:00~13:15” is specified by the orderer, the display content of button B changes to “Selecting”. Then, the information indicating the selected deliverable time (for example, including the order ID) is transmitted from the orderer terminal UT to the monitoring task management server MS via the order processing server PS. Thereby, the monitoring plan corresponding to the selected deliverable time is determined and the delivery plan related to the order is determined. Note that, in the example of FIG. 9, although the above partial deliverable times are not displayed on the deliverable time selection screen, the above partial deliverable times may be displayed on the deliverable time selection screen and the display content of the “Select” button may be grayed out so that the above partial deliverable times cannot be selected.

[0048] The monitoring task information transmission unit 136 transmits (for example, push delivery) information (hereinafter referred to as "monitoring task information") for causing operator On to execute a monitoring task to be executed at the timing of monitoring necessity to the operator terminal OTn used by operator On in response to the arrival of the timing of monitoring necessity of the UAVm to be monitored. Thereby, the operator On can be caused to execute the monitoring task to be executed at the timing of monitoring necessity of the UAVm quickly and appropriately. Note that "in response to the arrival of the timing of monitoring necessity" means a case where the current time becomes the start point of the time zone related to the timing of monitoring necessity, or a case where the current time becomes several seconds before the start point. The monitoring task information may include a message for prompting operator On to execute the monitoring task. Such a message may include information indicating the content of the monitoring task. Further, the monitoring task information may include a control command for causing the operator terminal OTn to display (for example, pop up) a monitoring task execution screen.

[0049] FIG. 10 is a diagram showing an example of a monitoring task execution screen displayed on the operator terminal OT1. On the monitoring task execution screen shown in FIG. 10, UAV information regarding the UAV1 to be monitored and UAV surrounding information regarding the surrounding situation of the UAV1 are displayed, and a message M for prompting operator O1 to execute the monitoring task is displayed. The UAV information and the UAV surrounding information are sequentially received from the monitoring task management server MS. As shown in FIG. 10, the UAV position display area 51 displays the position of the UAV1. The UAV state display area 52 displays the state of the UAV1. The UAV battery display area 53 displays the remaining battery level of the UAV1. Note that different monitoring task execution screens may be displayed for each task type.

[0050] In the wind direction & wind speed display area 54, the wind direction and wind speed detected by the weather sensor installed at the store Fo or the base P1 where the UAV 1 is located are displayed. In the rainfall display area 55, the rainfall detected by the weather sensor installed at the store Fo or the base P1 where the UAV 1 is located is displayed. In the weather display area 56, the weather of the area where the UAV 1 is located is displayed. In the UAV camera video display area 57, the UAV video taken by the camera of the UAV 1 is displayed. In the surrounding camera video display area 58, the surrounding video of the UAV 1 taken by the cameras installed at the store Fo or the base P1 where the UAV 1 is located is displayed. The operator O1 will execute the monitoring task while viewing the information displayed on the monitoring task execution screen.

[0051] By the way, if a delay occurs in the delivery schedule due to, for example, the state of the UAV 1 or the surrounding situation when the delivery schedule is determined, the delay control unit 137 delays the monitoring timing of the UAV 1. That is, the delay control unit 137 updates (changes) the monitoring timing of the UAV 1 in the monitoring plan registered in the monitoring plan management database 126 to be delayed according to the delay time of the delivery schedule of the UAV 1. Further, the delay control unit 137 updates (changes) the time zone in which the monitoring task is assigned in the monitoring schedule of the operator O1 who executes the monitoring task at the changed monitoring timing to be delayed according to the delay time of the delivery schedule of the UAV 1.

[0052] When the monitoring timing of UAV1 is delayed in this way, and when a monitoring task for monitoring, for example, UAV2 other than UAV1 is assigned to the monitoring schedule of operator O1, the delay control unit 137 determines whether at least a part of the monitoring timing of UAV1 after the delay overlaps with the monitoring timing of UAV2. Then, when at least a part of the monitoring timing of UAV1 after the delay overlaps with the monitoring timing of UAV2, the delay control unit 137 changes the monitoring plan by assigning the monitoring task to be executed at the monitoring timing of UAV2 to a time zone in which the monitoring task can be executed in the monitoring schedule of another operator On other than operator O1. That is, the monitoring task to be executed at the monitoring timing of UAV2 is reassigned from operator O1 to another operator On (that is, the monitoring schedule of operator On). As a result, even when at least a part of the monitoring timing of UAV1 after the delay overlaps with the monitoring timing of UAV2 due to a delay occurring in the delivery schedule of UAV1, the monitoring tasks to be executed at the respective monitoring timings of UAV1 and UAV2 can be appropriately executed by operator O1 and other operator On.

[0053] FIG. 11 is a conceptual diagram showing an example in which the monitoring task to be executed at the monitoring timing of UAV2 is reassigned from the monitoring schedule of operator O1 to the monitoring schedule of operator O4. In the example of FIG. 11, due to a delay occurring in the determined delivery schedule of UAV1, the monitoring timing “11:20 to 11:40” corresponding to the operation determination time is changed to “11:40 to 12:00”, and the monitoring timing “12:55 to 13:05” corresponding to the delivery destination landing time is changed to “13:15 to 13:25”. Therefore, since at least a part of the monitoring timing of UAV1 after the delay overlaps with the monitoring timing of UAV2, the monitoring task to be executed at the monitoring timing of UAV2 is reassigned from the monitoring schedule of operator O1 to the monitoring schedule of operator O4.

[0054] In addition, when there is no operator On who can change the monitoring task to be executed at the monitoring timing of the UAV 2, the delay control unit 137 may notify the orderer of a message indicating delivery cancellation. Such notification of the message may be performed by sending an e-mail with the message described thereto to the e-mail address of the orderer, or may be performed by sending the message by SMS to the phone number of the orderer. Alternatively, the notification of the message may be performed by push-distributing the message to a notification application resident in the orderer terminal UT of the orderer.

[0055] 2. Operation of Delivery Management System S Next, with reference to FIGS. 12 and 13, the operation of the delivery management system S will be described. FIG. 12 is a flowchart showing an example of the monitoring plan determination process of the control unit 13 in the monitoring task management server MS. FIG. 13 is a flowchart showing an example of the monitoring task information transmission process of the control unit 13 in the monitoring task management server MS.

[0056] (2-1. Monitoring Plan Determination Process) First, as a premise of the process shown in FIG. 12, it is assumed that an order from the orderer terminal UT has been received by the order processing server PS. The process shown in FIG. 12 is started, for example, when information regarding the order is received by the monitoring task management server MS from the order processing server PS.

[0057] When the process shown in FIG. 12 is started, the control unit 13 estimates the estimated time required for delivering the product related to the order based on the information regarding the received order, as described above (step S1).

[0058] Next, based on the estimated time and the like estimated in step S1, the control unit 13 extracts a plurality (for example, three) of deliverable times for the product related to the order by the deliverable time extraction unit 131 as described above (step S2).

[0059] ​​Next, the control unit 13 refers to the aircraft management database 122 (that is, refers to the available time zones of each UAVm, etc.), and for each deliverable time extracted in step S2, identifies one UAVm that can deliver the goods to the delivery destination at that deliverable time (step S3). The UAVm (aircraft ID) thus identified is associated with the order ID included in the information regarding the order and the deliverable time extracted in step S2.

[0060] Next, the control unit 13 acquires the monitoring schedule of each of the plurality of operators On from the operator management database 124 by the monitoring schedule acquisition unit 132 (step S4). Next, the control unit 13, based on the deliverable time extracted in step S2 and the table for calculating the monitoring timing stored in the storage unit 12, acquires, for each deliverable time, the group of monitoring timing that requires monitoring of the UAVm associated with that deliverable time by the monitoring timing acquisition unit 133 as described above (step S5).

[0061] Next, the control unit 13 generates a monitoring plan for the UAVm associated with the deliverable time extracted in step S2 based on the monitoring schedule acquired in step S4 and the group of monitoring timing acquired in step S5 by the monitoring plan generation unit 134 as described above (step S6). The monitoring plan thus generated is associated with the deliverable time. Note that there may be deliverable times for which no monitoring plan is generated among the plurality of deliverable times extracted in step S2.

[0062] Next, the control unit 13 causes the presentation control unit 135 to transmit the information indicating the deliverable time extracted in step S2 to the orderer's orderer terminal UT (step S7). As a result, the deliverable time is displayed selectably on the orderer terminal UT. That is, the deliverable time is presented to the orderer so that it can be selected. At this time, as described above, the presentation control unit 135 controls so that the orderer cannot select the deliverable time corresponding to the monitoring task execution impossible timing of the operator On (in other words, the deliverable time for which the monitoring plan was not generated). Note that the deliverable time to be displayed on the orderer terminal UT may be only the deliverable time for which the monitoring plan was generated, but is not limited thereto. For example, a simple time table that has nothing to do with the deliverable time may be displayed on the orderer terminal UT, and only the portion corresponding to the deliverable time for which the monitoring plan was generated may be configured to be selectable therefrom.

[0063] Then, when any one of the deliverable times displayed on the orderer terminal UT is selected by the orderer, the information indicating the selected deliverable time (for example, including the order ID) is transmitted from the orderer terminal UT to the monitoring task management server MS via the order processing server PS. As a result, the received order is confirmed.

[0064] Next, when the control unit 13 receives the information indicating the deliverable time selected by the orderer (step S8), it determines the monitoring plan associated with the selected deliverable time as the monitoring plan of the UAVm associated with the deliverable time (step S9). The monitoring plan thus determined is associated with the order ID of the confirmed order and stored in the monitoring plan management database 126. Next, the control unit 13 determines a delivery plan including the delivery schedule of the UAVm associated with the selected deliverable time (step S10), and ends the process shown in FIG. 12. The delivery plan thus determined is associated with the order ID of the confirmed order and stored in the delivery plan management database 125.

[0065] (2-2. Monitoring Task Information Transmission Process) Next, as a premise for the process shown in FIG. 13, among the monitoring plans stored in the monitoring plan management database 126, a monitoring list for registering a monitoring plan including a monitoring timing to arrive within a predetermined time (for example, 24 hours) from the current time is used. The process shown in FIG. 13 is started, for example, at a predetermined cycle (for example, at several-second intervals).

[0066] When the process shown in FIG. 13 is started, the control unit 13 determines whether there is a monitoring plan in which the monitoring timing has arrived (for example, the starting point of the monitoring timing has passed the current time) among the monitoring plans registered in the monitoring list (step S21). If it is determined that there is a monitoring plan in which the monitoring timing has arrived (step S21: YES), the process proceeds to step S22. On the other hand, if it is determined that there is no monitoring plan in which the monitoring timing has arrived (step S21: NO), the process ends.

[0067] In step S22, the control unit 13 acquires, for example, access information of the operator terminal OT1 used by the operator O1 associated with the monitoring timing included in the monitoring plan in which the monitoring timing has arrived, and the aircraft ID of, for example, UAV1 that requires monitoring at the monitoring timing. Next, the control unit 13 acquires the UAV information and UAV surrounding information of UAV1 specified by the aircraft ID acquired in step S22 from the buffer memory (step S23).

[0068] Next, the control unit 13 establishes access with the operator terminal OT1 via the communication network NW according to the access information acquired in step S22, and transmits the above-described monitoring task information, as well as the UAV information and UAV surrounding information acquired in step S23, to the operator terminal OT1 by the monitoring task information transmission unit 136 (step S24). Note that the control unit 13 controls to sequentially transmit the UAV information and UAV surrounding information of UAV1 to the operator terminal OT1 while the access with the operator terminal OT1 is established.

[0069] When the operator terminal OT1 receives the monitoring task information, UAV information, and UAV surrounding information, for example, as shown in FIG. 10, it displays the UAV information and UAV surrounding information of UAV1 on the monitoring task execution screen together with a message M prompting the operator O1 to execute the monitoring task. As a result, the operator O1 will execute the monitoring task for monitoring UAV1.

[0070] As described above, according to the above embodiment, the monitoring task management server MS acquires a monitoring schedule including the time zone when the operator On can execute the monitoring task, extracts a plurality of deliverable times for the delivery of goods by UAVm, and acquires, for each deliverable time, the monitoring timing that requires monitoring of UAVm associated with the deliverable time. Based on the monitoring schedule and the monitoring timing for each deliverable time, a monitoring plan (monitoring plan for UAVm) associated with the deliverable time is generated for each deliverable time, and the plurality of the above deliverable times are presented to the orderer of the goods in a selectable manner, and the monitoring plan corresponding to one deliverable time selected by the orderer from the plurality of presented deliverable times is determined. Therefore, considering the deliverable time selected by the orderer of the goods, it is possible to appropriately determine the monitoring plan for when the operator On monitors UAVm at which monitoring timing.

[0071] Note that the above embodiment is an 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 in that case, it is also included in the technical scope of the present invention. In the above embodiment, the case where an orderer orders a product sold at the store Fo has been described as an example, but the present invention is also applicable to the case of delivering articles other than products. Examples of such cases include the case where relief supplies or support supplies requested by the delivery requester are delivered to an evacuation site or the like. Also, in the above embodiment, the UAV has been described as an example of the unmanned aerial vehicle, but the present invention is also applicable to flying robots and the like as examples of the unmanned aerial vehicle.

[0072] <Supplementary Note> [1] The delivery available time control device according to the present disclosure is a monitoring schedule of an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering an article, the monitoring schedule including a time zone during which the operator can execute the monitoring task, a first acquisition unit that acquires the monitoring schedule, a second acquisition unit that acquires a monitoring timing required for monitoring the unmanned aerial vehicle, and a presentation control unit that controls to present the delivery available time of the article by the unmanned aerial vehicle to a delivery requester of the article in a selectable manner, the presentation control unit controlling so that a part of the delivery available time cannot be selected by the delivery requester based on the monitoring schedule and the monitoring timing. Thereby, it is possible to limit the delivery available time that can be selected by the delivery requester according to the monitoring schedule of the operator and the monitoring timing required for the unmanned aerial vehicle. Therefore, it is possible to appropriately cause the operator to execute the monitoring task to be executed at the monitoring timing required for monitoring the unmanned aerial vehicle.

[0073] [2] In the delivery available time control device according to [1] above, the presentation control unit is characterized in that it controls so that the delivery available time corresponding to the monitoring timing at which the operator cannot execute the monitoring task at the monitoring timing cannot be selected by the delivery requester. Thereby, it is possible to appropriately prevent the operator from being unable to execute the monitoring task.

[0074] [3] In the deliverable time control device according to [1] or [2] above, the first acquisition unit acquires the monitoring schedules of each of the plurality of operators, and the presentation control unit controls so that the deliverable time corresponding to the monitoring timing at which all of the plurality of operators cannot execute the monitoring task at the monitoring timing cannot be selected by the delivery requester. As a result, if there is a monitoring timing at which even one of the plurality of operators can execute the monitoring task, the deliverable time corresponding to such a monitoring timing can be presented to the delivery requester. Therefore, the monitoring task to be executed at the monitoring timing of the unmanned aerial vehicle can be efficiently executed by the operator.

[0075] [4] In the deliverable time control device according to any one of [1] to [3] above, the second acquisition unit acquires a plurality of the monitoring timings, and the presentation control unit controls so that the deliverable time corresponding to the plurality of monitoring timings at which the operator cannot execute the monitoring task cannot be selected by the delivery requester. As a result, the monitoring tasks to be executed at each of the plurality of monitoring timings of one unmanned aerial vehicle can be appropriately executed by the operator.

[0076] [5] In the deliverable time control device according to any one of [1] to [4] above, the presentation control unit performs an allocation process for allocating the monitoring task to be executed at the monitoring timing to a time period in which the operator can execute the monitoring task in the monitoring schedule of the operator, and based on the result of the allocation process, specifies the deliverable time corresponding to the monitoring timing at which the operator cannot execute the monitoring task as the partial deliverable time. As a result, the deliverable time that restricts the presentation to the delivery requester can be quickly specified.

[0077] [6] In the deliverable time control device according to any one of [1] to [5] above, the monitoring schedule already has a monitoring task assigned for monitoring another unmanned aerial vehicle deployed at a base different from the base of the unmanned aerial vehicle. This enables the operator to efficiently execute the monitoring tasks that should be executed at the monitoring timing required for monitoring each unmanned aerial vehicle deployed at multiple bases.

[0078] [7] In the deliverable time control device according to any one of [1] to [6] above, the device further includes a transmission unit that transmits, in response to the arrival of the monitoring timing required, information for causing the operator to execute the monitoring task to be executed at the monitoring timing required to a terminal used by the operator. This enables the operator to quickly and appropriately execute the monitoring tasks that should be executed at the monitoring timing required for the unmanned aerial vehicle.

[0079] [8] In the deliverable time control device according to any one of [1] to [7] above, the monitoring timing required is at least one timing among a plurality of timings spaced apart in time in the delivery schedule related to one delivery by the unmanned aerial vehicle. This enables the operator to efficiently execute the monitoring tasks that should be executed at the monitoring timing required for the unmanned aerial vehicle in the delivery schedule related to one delivery.

[0080] [9] The monitoring schedule of an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering goods in the unmanned aerial vehicle monitoring system according to the present disclosure, the first acquisition unit that acquires the monitoring schedule including the time period during which the operator can execute the monitoring task, the second acquisition unit that acquires the monitoring timing that requires monitoring of the unmanned aerial vehicle, and a presentation control unit that controls to present the delivery available time of the goods by the unmanned aerial vehicle to the delivery requester of the goods in a selectable manner, the presentation control unit that controls so that the delivery requester cannot select some of the delivery available times based on the monitoring schedule and the monitoring timing, and is characterized by including the above.

[0081]

[10] The delivery available time control method according to the present disclosure is a delivery available time control method executed by a computer, the monitoring schedule of an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering goods, the step of acquiring the monitoring schedule including the time period during which the operator can execute the monitoring task, the step of acquiring the monitoring timing that requires monitoring of the unmanned aerial vehicle, and the step of controlling to present the delivery available time of the goods by the unmanned aerial vehicle to the delivery requester of the goods in a selectable manner, the step of controlling so that the delivery requester cannot select some of the delivery available times based on the monitoring schedule and the monitoring timing, and is characterized by including the above.

Explanation of symbols

[0082] 11 Communication unit 12 Storage unit 13 Control unit 131 Delivery available time extraction unit 132 Monitoring schedule acquisition unit 133 Monitoring timing acquisition unit 134 Monitoring plan generation unit 135 Presentation control unit 136 Monitoring task information transmission unit 137 Delay control unit 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 monitoring schedule for an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering an item, the monitoring schedule including a first acquisition unit that acquires the monitoring schedule including a time period during which the operator can execute the monitoring task, an extraction unit that extracts a plurality of delivery available times of the item by the unmanned aerial vehicle, a second acquisition unit that acquires, for each of the delivery available times, a monitoring required timing that requires monitoring of the unmanned aerial vehicle associated with the delivery available time, a generation unit that generates, for each of the delivery available times, a monitoring plan for the unmanned aerial vehicle associated with the delivery available time based on the monitoring schedule and the monitoring required timing for each of the delivery available times, a presentation control unit that presents the plurality of delivery available times extracted by the extraction unit to the item delivery requester in a selectable manner, a determination unit that determines one monitoring plan from among the plurality of monitoring plans generated by the generation unit, and comprising The determination unit is characterized in that it determines a monitoring plan corresponding to one delivery available time selected by the delivery requester from among the plurality of delivery available times presented by the presentation control unit. A monitoring plan determination device.

2. The presentation control unit is characterized in that it controls so that the delivery requester cannot select a delivery available time corresponding to the monitoring required timing at which the operator cannot execute the monitoring task at the monitoring required timing. The monitoring plan determination device according to claim 1.

3. The first acquisition unit acquires the monitoring schedule of each of the plurality of operators, The presentation control unit is characterized in that it controls so that the delivery requester cannot select a delivery available time corresponding to the monitoring required timing at which all of the plurality of operators cannot execute the monitoring task at the monitoring required timing. The monitoring plan determination device according to claim 1.

4. The second acquisition unit acquires a plurality of the monitoring required timings for each of the delivery available times, The presentation control unit is characterized in that it controls so that the delivery requester cannot select a delivery available time corresponding to the plurality of monitoring required timings at which the operator cannot execute the monitoring task. The monitoring plan determination device according to claim 1.

5. The prompting control unit performs an assignment process for assigning the monitoring task to be executed at the monitoring timing to a time period during which the operator can execute the monitoring task in the monitoring schedule of the operator, and based on the result of the assignment process, controls so that the delivery requester cannot select the deliverable time corresponding to the monitoring timing at which the operator cannot execute the monitoring task. The monitoring plan determination device according to any one of claims 1 to 4.

6. In the monitoring schedule, a monitoring task for monitoring another unmanned aerial vehicle deployed at a base different from the base of the unmanned aerial vehicle is already assigned. The monitoring plan determination device according to any one of claims 1 to 4.

7. The monitoring plan determination device according to any one of claims 1 to 4, further comprising a transmission unit that transmits, to a terminal used by the operator, information for causing the operator to execute the monitoring task to be executed at the monitoring timing in response to the arrival of the monitoring timing.

8. The monitoring timing is at least one timing among a plurality of timings separated by time in a delivery schedule related to one delivery by the unmanned aerial vehicle. The monitoring plan determination device according to any one of claims 1 to 4.

9. A monitoring schedule for an operator who executes a monitoring task for monitoring an unmanned aerial vehicle used for delivering an article, the monitoring schedule including a first acquisition unit that acquires the monitoring schedule including a time period during which the operator can execute the monitoring task, an extraction unit that extracts a plurality of deliverable times for delivering the article by the unmanned aerial vehicle, a second acquisition unit that acquires, for each deliverable time, a monitoring timing that requires monitoring of the unmanned aerial vehicle associated with the deliverable time, a generation unit that generates, for each deliverable time, a monitoring plan for the unmanned aerial vehicle associated with the deliverable time based on the monitoring schedule and the monitoring timing for each deliverable time, a prompting control unit that prompts the delivery requester of the article to be able to select the plurality of deliverable times extracted by the extraction unit, a determination unit that determines one monitoring plan from among the plurality of monitoring plans generated by the generation unit, and comprising The determination unit determines a monitoring plan corresponding to one of the plurality of deliverable times selected by the delivery requester from among the plurality of deliverable times presented by the presentation control unit. A drone monitoring system characterized by that.

10. A monitoring plan determination method executed by a computer, A monitoring schedule of an operator who executes a monitoring task for monitoring a drone used for delivering an article, the step of obtaining the monitoring schedule including a time period during which the operator can execute the monitoring task; The step of extracting a plurality of deliverable times of the article by the drone; The step of obtaining, for each of the deliverable times, a monitoring timing that requires monitoring of the drone associated with the deliverable time; Based on the monitoring schedule and the monitoring timings for each of the deliverable times, the step of generating, for each of the deliverable times, a monitoring plan for the drone associated with the deliverable time; The step of presenting the plurality of extracted deliverable times to the delivery requester of the article so that they can be selected; A determination step of determining one monitoring plan from among the plurality of generated monitoring plans; Including, In the determination step, a monitoring plan corresponding to one of the plurality of deliverable times selected by the delivery requester from among the plurality of deliverable times presented to the delivery requester is determined. A monitoring plan determination method characterized by that.

Images