Product delivery method, delivery planning method, server, mobile body, and product delivery program

Abstract

A product delivery method according to the present disclosure includes acquiring waiting line information. The waiting line information is information about a waiting line. The waiting line includes a user. The product delivery method includes acquiring situation information. The situation information is information about the situation of the user. The product delivery method includes identifying, on the basis of the waiting line information and the situation information, one or more candidate locations where a product can be picked up in the waiting line. The product delivery method includes creating a delivery plan for delivering a product to a pickup location in response to a pickup request. The pickup request specifies, as the pickup location, a candidate location selected from among one or more candidate locations through the user's terminal. The product delivery method includes causing a mobile body carrying the product to travel in accordance with the delivery plan.

Description

Product delivery method, delivery planning method, server, mobile body, and product delivery program

[0001] The present disclosure relates to a product delivery method, a delivery planning method, a server, a mobile object, and a product delivery program.

[0002] For example, when a user uses a target facility such as an attraction at an amusement park, a waiting line may be formed in front of the target facility by multiple people, including the user. The person at the front of the waiting line uses the target facility, and the people after the front move forward accordingly. This process is repeated, and each of the multiple people forming the waiting line can use the target facility in order, starting with the person at the front.

[0003] Japanese Patent Application Laid-Open No. 2020-535549

[0004] Users waiting in line may request product delivery. For example, if the line is restricted by a barrier or other barrier and the users are waiting near the barrier, it may be difficult for the users to receive the delivered product. In this case, the convenience of the users waiting in line may be reduced.

[0005] The present disclosure provides a product delivery method, a delivery planning method, a server, a mobile object, and a product delivery program that can improve the convenience of users waiting in line.

[0006] A product delivery method according to the present disclosure includes acquiring queue information. The queue information is information about the queue. The queue includes a user. The product delivery method includes acquiring status information. The status information is information about the user's status. The product delivery method includes identifying one or more candidate locations where the product can be picked up in the queue based on the queue information and the status information. The product delivery method includes creating a delivery plan for delivering the product to the pickup location in response to a pickup request. The pickup request specifies a candidate location selected from the one or more candidate locations on a user's terminal as the pickup location. The product delivery method includes driving a mobile object carrying the product in accordance with the delivery plan.

[0007] 1 is a diagram showing a schematic configuration of a product delivery system in which a product delivery method according to an embodiment is implemented. 2 is a diagram showing a functional configuration of a product delivery system in which a product delivery method according to an embodiment is implemented. 3 is a diagram showing a hardware configuration of a product delivery system in which a product delivery method according to an embodiment is implemented. 4 is a flowchart showing a product delivery method according to an embodiment. 5 is a sequence diagram showing use cases of the product delivery method according to an embodiment. 6 is a diagram showing the operation of a display unit of a terminal in an embodiment. 7 is a flowchart showing a product delivery method according to a first modified example of an embodiment. 8 is a sequence diagram showing use cases of the product delivery method according to the first modified example of an embodiment. 9 is a flowchart showing a product delivery method according to a second modified example of an embodiment. 10 is a sequence diagram showing use cases of the product delivery method according to the second modified example of an embodiment. 11 is a diagram showing the operation of a display unit of a terminal in the second modified example of an embodiment. 12 is a diagram showing the functional configuration of a product delivery system in which a product delivery method according to a third modified example of an embodiment is implemented. 13 is a flowchart showing a product delivery method according to a fourth modified example of an embodiment. 14 is a sequence diagram showing use cases of the product delivery method according to the fourth modified example of an embodiment.

[0008] Hereinafter, an embodiment of a product delivery method according to the present disclosure will be described with reference to the drawings.

[0009] (Embodiment) In the product delivery method according to the embodiment, in response to a request for product delivery from a user waiting in a waiting line, a mobile vehicle carrying the product is driven to deliver the product to the user, and the method is devised to improve user convenience.

[0010] The product delivery method is executed in a product delivery system 1 as shown in Fig. 1. Fig. 1 is a diagram showing a schematic configuration of the product delivery system 1 in which the product delivery method is executed.

[0011] The product delivery system 1 receives a reservation request for product delivery from a user waiting in line LN. In response to the reservation request, the product delivery system 1 performs processing to deliver the product to the user U_1. The reservation request requests a reservation for an order of the product.

[0012] The waiting line LN is formed in front of the target facility AT by a plurality of people P_1 to P_n, including user U_1. n is any integer equal to or greater than 2, and represents the number of people in the waiting line LN. In FIG. 1, the first person in the waiting line LN is represented by P_1, and the last person is represented by P_n. FIG. 1 illustrates a case in which user U_1 is the sth person P_s from the front. s is an integer equal to or greater than 1 and equal to or less than n. The target facility AT may be, for example, a ride or attraction at an amusement park or theme park, or an ATM at a financial institution.

[0013] In the waiting line LN, the person P_1 at the front uses the target facility AT, and the people P_2 to P_n after the front move forward one person accordingly. This process is repeated, and each of the multiple people P_1 to P_n forming the waiting line LN can use the target facility AT in order, starting with the person P_1 at the front.

[0014] For example, the waiting line LN may be restricted by a restricting portion FN. The restricting portion FN restricts the waiting line LN, thereby defining the shape of the waiting line LN.

[0015] The product delivery system 1 can deliver a product GD to a user U_1 by running a mobile object 40. The mobile object 40 may be loaded with a plurality of products GD1 to GD4.

[0016] If user U_1 is lined up near the restrictor FN, even if the product delivery system 1 attempts to deliver the product GD, the restrictor FN may become an obstacle, making it difficult for user U_1 to receive the product GD. In the case of Figure 1, user U_1 is lined up near the fence FN4, and even if the product delivery system 1 drives the mobile object 40 close to user U_1, the fence FN4 becomes an obstacle, making it difficult for user U_1 to receive the product GD.

[0017] In response to this, the product delivery system 1 executes the following product delivery method. In this product delivery method, one or more candidate locations in the waiting line LN where the product can be received are identified and presented to the user U_1, and the product GD is delivered to a receiving location designated by the user U_1 from among the presented candidate locations. This allows the product GD to be handed over to the user U_1 waiting in the waiting line LN.

[0018] For example, in the product delivery method, waiting line information is acquired. The waiting line information is information about the waiting line LN. The waiting line LN includes a user U_1. In the product delivery method, status information is acquired. The status information is information about the status of the user U_1. In the product delivery method, one or more candidate locations in the waiting line LN where the product GD can be received are identified based on the waiting line information and the status information. In the product delivery method, one or more candidate locations are presented to the user, and one of the one or more candidate locations is selected by the user. In the product delivery method, a delivery plan is created to deliver the product GD to the receiving location in response to a receiving request that specifies the candidate location selected by the user as the receiving location. In the product delivery method, a mobile unit 40 carrying the product GD travels in accordance with the delivery plan. This allows the product GD to be handed over to the user U_1 waiting in the waiting line LN.

[0019] The product delivery system 1 receives the reservation request RQ0 and executes the product delivery method. As shown in Figures 1 and 2, the product delivery system 1 may include an operation management server 10, an area management server 20, a terminal 30, a mobile object 40, an image sensor 50, and a communication line 60 as a configuration for executing the product delivery method. Figure 2 is a diagram showing the functional configuration of the product delivery system 1.

[0020] The fleet management server 10, the area management server 20, the terminal 30, and the mobile object 40 are communicably connected to one another via a communication line 60. The image sensor 50 is communicably connected to the area management server 20.

[0021] The fleet management server 10 manages operations such as product delivery in an area near the target facility AT. The fleet management server 10 includes an acquisition unit 11, an acquisition unit 12, a candidate specification unit 13, a plan creation unit 14, and an instruction unit 15.

[0022] The acquisition unit 11 transmits an acquisition request RQ1 to the area management server 20 via the communication line 60. The acquisition request RQ1 requests acquisition of queue information.

[0023] The waiting queue information is information about the waiting queue LN. The waiting queue LN includes a user U_1. The waiting queue information includes a static configuration of the waiting queue LN. The static configuration of the waiting queue LN may include the placement of a restriction unit FN that restricts the waiting queue LN.

[0024] The restrictor FN may be a component arranged near the waiting line LN, or may be a group of people near the waiting line LN. Components arranged near the waiting line LN include components such as ropes, fences, partitions, and walls. Groups of people near the waiting line LN include groups of other waiting lines, multiple security guards, multiple venue staff, and the like. FIG. 1 illustrates a case in which the restrictor FN includes multiple fences FN1 to FN4 and a wall WL. FIG. 1 illustrates a waiting line LN defined in a serpentine shape by the multiple fences FN1 to FN4 and the wall WL.

[0025] The waiting line information may further include the dynamic configuration of the waiting line LN. The dynamic configuration of the waiting line LN may include the arrangement of multiple people in the waiting line LN. The waiting line information may include information about how many people are waiting in the waiting line LN. The waiting line information may include at least one of the position, length, and shape of the waiting line LN in the area near the target facility AT. The waiting line information may include information about the shape of the waiting line LN, such as the number of rows in the waiting line LN, the number of people in each row in the waiting line LN, and the shape of the waiting line LN. The information about the shape of the waiting line LN may include information about whether multiple people are lined up in a straight line or a bent line. The waiting line information may include information about locations in the waiting line LN where products can be received, or information about locations in the waiting line LN where products cannot be received.

[0026] The acquisition unit 11 receives the queue information from the area management server 20 via the communication line 60 as a response to the acquisition request RQ1. The acquisition unit 11 then acquires the queue information. The acquisition unit 11 then supplies the queue information to the candidate identification unit 13.

[0027] The acquisition unit 12 transmits the acquisition request RQ2 to the terminal 30 via the communication line 60. The acquisition request RQ2 requests acquisition of status information.

[0028] The status information is information about the status of the user U_1. The status information includes the position of the user U_1 in the waiting queue LN. The status information may further include the progress speed of the user U_1 in the waiting queue LN.

[0029] The acquisition unit 12 receives the status information from the terminal 30 as a response to the acquisition request RQ2 via the communication line 60. The acquisition unit 12 thereby acquires the status information. The acquisition unit 12 supplies the status information to the candidate identification unit 13.

[0030] In addition, in the fleet management server 10, the acquisition unit 11 and the acquisition unit 12 may not be functionally separate, but may be integrated.

[0031] The candidate identification unit 13 receives queue information from the acquisition unit 11 and status information from the acquisition unit 12. Based on the queue information and status information, the candidate identification unit 13 identifies one or more candidate locations in the queue LN where the product GD can be picked up. The candidate identification unit 13 transmits the one or more candidate locations to the terminal 30 via the communication line 60.

[0032] The plan creation unit 14 receives the pickup request RQ3 from the terminal 30 via the communication line 60. The pickup request RQ3 specifies, as the pickup location, a candidate location selected by the user U_1 from one or more candidate locations identified by the candidate identification unit 13. The plan creation unit 14 creates a delivery plan in response to the pickup request RQ3. The delivery plan includes delivering the product GD to the pickup location. The plan creation unit 14 provides the delivery plan to the instruction unit 15.

[0033] The instruction unit 15 receives a delivery plan from the plan creation unit 14 and generates driving instructions in accordance with the delivery plan. The driving instructions are instructions for driving the product GD to a pickup location. The driving instructions include a specification of a pickup location in accordance with the delivery plan, and may further include a specification of the product GD in accordance with the reservation request RQ0. The instruction unit 15 transmits the driving instructions to the mobile object 40 via the communication line 60.

[0034] The imaging sensor 50 is disposed near the target facility AT. The imaging sensor 50 may be disposed on the ceiling above the target facility AT. The imaging sensor 50 is capable of capturing images of the area near the target facility AT. When the imaging sensor 50 acquires an image of the area near the target facility AT, it provides the image to the area management server 20.

[0035] The area management server 20 manages the area near the target facility AT and the waiting line LN formed therein. The area management server 20 stores waiting line information. The area management server 20 may manage the waiting line LN via images acquired by the imaging sensor 50. The area management server 20 has an information providing unit 21, a storage unit 22, and an information acquiring unit 23.

[0036] The information acquisition unit 23 acquires waiting line information. The information acquisition unit 23 may acquire the waiting line information by receiving an input from a manager of the target facility AT. The information acquisition unit 23 may acquire the waiting line information by receiving an image of the waiting line LN acquired by the image sensor 50 and generating waiting line information according to the image of the waiting line LN.

[0037] The information acquisition unit 23 stores the queue information in the storage unit 22. The storage unit 22 stores the queue information.

[0038] When the information providing unit 21 receives the acquisition request RQ1 from the fleet management server 10, it reads out the waiting queue information from the storage unit 22. The information providing unit 21 transmits the waiting queue information to the fleet management server 10 via the communication line 60 as a response to the acquisition request RQ1 from the fleet management server 10.

[0039] The terminal 30 is held by the user U_1 who is waiting in the waiting queue LN. In response to this, the terminal 30 holds status information.

[0040] The terminal 30 includes a position acquisition unit 31, a status acquisition unit 32, a notification unit 33, and a request generation unit .

[0041] The position acquisition unit 31 can acquire position information of the terminal 30. The position acquisition unit 31 may acquire the position information of the terminal 30 by receiving a GPS (Global Positioning System) signal. When the position acquisition unit 31 receives an acquisition request RQ2 from the fleet management server 10 via the communication line 60, the position acquisition unit 31 acquires the position information of the terminal 30 in response to the acquisition request RQ2. The position acquisition unit 31 may transmit the position information of the terminal 30 to the fleet management server 10 via the communication line 60 as status information.

[0042] The status acquisition unit 32 can accept input from the user U_1 regarding the status of the user U_1. When the status acquisition unit 32 receives an acquisition request RQ2 from the fleet management server 10 via the communication line 60, the status acquisition unit 32 prompts the user U_1 to input first text information indicating the user's current position in the waiting line LN in response to the acquisition request RQ2. When the status acquisition unit 32 accepts the first text information, the status acquisition unit 32 may transmit the first text information to the fleet management server 10 via the communication line 60 as status information. When the status acquisition unit 32 accepts the second text information, the status acquisition unit 32 may further transmit the second text information to the fleet management server 10 via the communication line 60 as status information.

[0043] The notification unit 33 can notify the user U_1 of predetermined information. When the notification unit 33 receives information about one or more candidate locations where the product GD can be picked up in the waiting line LN from the fleet management server 10 via the communication line 60, the notification unit 33 may notify the user U_1 of the one or more candidate locations by displaying the one or more candidate locations on a display screen.

[0044] The request generation unit 34 can receive input from the user U_1 and generate a predetermined request in response to the input. When the notification unit 33 displays one or more candidate locations on the display screen and the request generation unit 34 receives a selection instruction to select one candidate location from the one or more candidate locations, the request generation unit 34 generates a pickup request RQ3. The pickup request RQ3 specifies the candidate location selected by the user U_1 as the pickup location. The request generation unit 34 transmits the pickup request RQ3 to the fleet management server 10 via the communication line 60.

[0045] When the driving unit 41 receives a driving instruction from the fleet management server 10 via the communication line 60, the driving unit 41 accesses the position acquisition unit 42. The driving instruction includes a designation of a pickup location. The driving instruction may further include a designation of a product.

[0046] The position acquisition unit 42 can acquire position information of the mobile object 40. The position acquisition unit 42 may acquire the position information of the mobile object 40 by receiving a GPS signal.

[0047] The traveling unit 41 acquires the position information of the mobile object 40 from the position acquisition unit 42. The traveling unit 41 determines a traveling route according to the traveling instruction and the position information of the mobile object 40, and travels to the pick-up location along the traveling route. The traveling unit 41 may sequentially access the position acquisition unit 42 to acquire the position information of the mobile object 40, and travel to the pick-up location while adjusting the traveling route according to the traveling instruction and the position information of the mobile object 40. The traveling unit 41 notifies the providing unit 43 when the mobile object 40 arrives at the pick-up location.

[0048] The providing unit 43 provides the product GD to the user U_1. The providing unit 43 may provide the product GD specified in the driving instructions in response to notification that the pickup location has been reached. The providing unit 43 may provide the product GD by clearly indicating the receivable product GD to the user U_1. The providing unit 43 may clearly indicate the receivable product GD to the user U_1 by highlighting an area in which the receivable product GD is placed. The providing unit 43 may clearly indicate the receivable product GD to the user U_1 by moving the receivable product GD closer to the user U_1 than the other products GD.

[0049] This allows the product delivery system 1 to hand over the product GD to the user U_1 waiting in the waiting line LN.

[0050] Next, the hardware configuration of the product delivery system 1 will be described with reference to Fig. 3. Fig. 3 is a diagram showing the hardware configuration of the product delivery system 1.

[0051] The communication line 60 includes a wireless communication line and / or a wired communication line. In Fig. 3, the communication line 60 includes a wired communication line 61, a wired communication line 62, a wireless communication line 63, and a wireless communication line 64. The fleet management server 10 and the area management server 20 can be connected via the wired communication line 61 and the wired communication line 62. The fleet management server 10 and the terminal 30 can be connected via the wired communication line 61 and the wireless communication line 63. The fleet management server 10 and the mobile object 40 can be connected via the wired communication line 61 and the wireless communication line 64.

[0052] The wired communication lines 61 and 62 may each be the Internet, a LAN (Local Area Network), a telephone exchange network, or the like.

[0053] The wireless communication lines 63 and 64 may be communication lines using radio access technology (RAT: Radio Access Technology) such as LTE (Long Term Evolution), NR (New Radio), Wi-Fi, Bluetooth (registered trademark), etc.

[0054] The fleet management server 10 includes a control unit 10a, a communication interface (I / F) 10b, a nonvolatile storage unit 10c, a volatile storage unit 10d, and a bus 10e. The control unit 10a, the communication interface 10b, the nonvolatile storage unit 10c, and the volatile storage unit 10d are connected to each other via the bus 10e so as to be able to communicate with each other.

[0055] The control unit 10a performs overall control of each unit of the fleet management server 10. The control unit 10a may be a CPU (Central Processing Unit). The communication interface 10b is communicatively connected to the area management server 20, the terminal 30, and the mobile object 40 via a communication line 60. The nonvolatile memory unit 10c stores information in a nonvolatile manner. The nonvolatile memory unit 10c may be a nonvolatile memory such as a flash memory, or a nonvolatile disk medium such as a magnetic disk. The nonvolatile memory unit 10c may store a product delivery program 10c1. The volatile memory unit 10d temporarily stores information. The volatile memory unit 10d may be a volatile memory such as a DRAM (Dynamic Random Access Memory). The volatile memory unit 10d may store queue information 10d1, status information 10d3, and a delivery plan 10d4.

[0056] Each unit shown in FIG. 2 may be realized as software within the control unit 10a. For example, the control unit 10a may read and start the product delivery program 10c1 from the non-volatile storage unit 10c in response to a trigger such as power-on of the fleet management server 10, and may then load modules corresponding to each unit onto the volatile storage unit 10d either collectively at the time of compilation or sequentially as processing progresses. This allows each unit of the fleet management server 10 to be considered equivalently realized as software within the control unit 10a. Alternatively, each unit of the fleet management server 10 shown in FIG. 2 may be realized as hardware as a circuit configured within the control unit 10a. Alternatively, some of the units may be realized as software and the rest may be realized as hardware.

[0057] The area management server 20 includes a control unit 20 a, a communication interface (I / F) 20 b, a nonvolatile storage unit 20 c, a volatile storage unit 20 d, an imaging interface (I / F) 20 e, and a bus 20 f. The control unit 20 a, the communication interface 20 b, the nonvolatile storage unit 20 c, the volatile storage unit 20 d, and the imaging interface 20 e are connected to each other via the bus 20 f so as to be able to communicate with each other.

[0058] The control unit 20a performs overall control of each unit of the area management server 20. The control unit 20a may be a CPU. The communication interface 20b is communicatively connected to the fleet management server 10 via a communication line 60. The non-volatile memory unit 20c stores information in a non-volatile manner. The non-volatile memory unit 20c may be a non-volatile memory such as a flash memory, or a non-volatile disk medium such as a magnetic disk. The non-volatile memory unit 20c may store waiting queue information 22a. The volatile memory unit 20d temporarily stores information. The volatile memory unit 20d may be a volatile memory such as a DRAM. The imaging interface 20e is communicatively connected to the imaging sensor 50.

[0059] 2, the information providing unit 21 is realized by the control unit 20a and the communication interface 20b, the storage unit 22 is realized by the non-volatile storage unit 20c, and the information acquiring unit 23 is realized by the control unit 20a and the imaging interface 20e.

[0060] The terminal 30 includes a control unit 30a, a communication interface (I / F) 30b, a nonvolatile storage unit 30c, a volatile storage unit 30d, a display unit 30e, an input unit 30f, and a bus 30g. The control unit 20a, the communication interface 30b, the nonvolatile storage unit 30c, the volatile storage unit 30d, the display unit 30e, and the input unit 30f are connected to each other via the bus 30g so as to be able to communicate with each other.

[0061] The control unit 30a comprehensively controls each unit of the terminal 30. The control unit 30a may be a CPU. The communication interface 30b is communicatively connected to the fleet management server 10 via a communication line 60. The non-volatile memory unit 30c stores information in a non-volatile manner. The non-volatile memory unit 30c may be a non-volatile memory such as a flash memory, or a non-volatile disk medium such as a magnetic disk. The volatile memory unit 30d temporarily stores information. The volatile memory unit 20d may be a volatile memory such as a DRAM. The volatile memory unit 30d may store status information 30d1. The display unit 30e outputs predetermined information to the user by displaying it on a display screen. The display unit 30e may be a display such as an LCD or an organic EL. The input unit 30f accepts instructions from the user. The input unit 30f may include buttons, keys, a touch panel, a mouse, a touchpad, a voice input device, etc.

[0062] 2, the position acquisition unit 31 and the request generation unit 34 are realized by the control unit 30a and the communication interface 30b, respectively. The status acquisition unit 32 is realized by the communication interface 30b and the input unit 30f. The notification unit 33 is realized by the control unit 20a, the communication interface 30b, and the display unit 30e.

[0063] The mobile object 40 includes a control unit 40a, a communication interface (I / F) 40b, a nonvolatile memory unit 40c, a volatile memory unit 40d, a sensor 40e, a drive unit 40f, a traveling mechanism 40g, a drive unit 40h, a providing mechanism 40i, and a bus 40j. The control unit 40a, the communication interface 40b, the nonvolatile memory unit 40c, the volatile memory unit 40d, the sensor 40e, the drive unit 40f, and the drive unit 40h are connected to each other via a bus 20f so as to be able to communicate with each other.

[0064] The control unit 40a comprehensively controls each unit of the mobile object 40. The control unit 40a may be a CPU. The communication interface 40b is communicatively connected to the fleet management server 10 via a communication line 60. The nonvolatile storage unit 40c stores information in a nonvolatile manner. The nonvolatile storage unit 40c may be a nonvolatile memory such as a flash memory, or may be a nonvolatile disk medium such as a magnetic disk. The volatile storage unit 4d temporarily stores information. The volatile storage unit 40d may be a volatile memory such as a DRAM.

[0065] The sensor 40e is capable of detecting the surrounding environment of the mobile object 2. The sensor 40e may be, for example, an imaging sensor and may be capable of acquiring an image of the surroundings of the mobile object 40 as sensor information. The sensor 40e may be, for example, a distance measurement sensor and may be capable of acquiring the distance to an object in the surroundings of the mobile object 40 as sensor information.

[0066] The drive unit 40f includes a circuit and / or an actuator that drives the traveling mechanism 40g. The traveling mechanism 40g is a machine for traveling the mobile body 40 and may include wheels, axles, gears, etc. The drive unit 40f can drive the traveling mechanism 40g by supplying a signal to the traveling mechanism 40g or transmitting power to the traveling mechanism 40g in accordance with the control of the control unit 40a. For example, the control unit 40a may control the traveling mechanism 40g via the drive unit 40f in accordance with a traveling instruction so that the traveling mechanism 40g travels to a receiving location.

[0067] The drive unit 40h includes a circuit and / or an actuator that drives the provision mechanism 40i. The provision mechanism 40i is a machine for providing the product GD to the user U, and may include a table, lighting, gears, etc. The drive unit 40h can drive the provision mechanism 40i by supplying a signal to the provision mechanism 40i or transmitting power to the provision mechanism 40i in accordance with the control of the control unit 40a.

[0068] 2, the traveling unit 41 is realized by the control unit 40a, the communication interface 40b, the sensor 40e, the drive unit 40f, and the traveling mechanism 40g. The position acquisition unit 42 is realized by the control unit 40a and the communication interface 40b. The providing unit 43 is realized by the control unit 20a, the drive unit 40h, and the providing mechanism 40i.

[0069] Next, a product delivery method executed by the product delivery system 1 will be described with reference to Fig. 4. Fig. 4 is a flowchart showing the product delivery method.

[0070] The product delivery system 1 waits until it receives a reservation request RQ0 (No in S1). The reservation request RQ0 specifies the product that the user U_1 wants to receive.

[0071] When the product delivery system 1 receives the reservation request RQ0 (Yes in S1), it acquires waiting line information and status information (S2). The waiting line information is information about the waiting line LN, and may include the static configuration of the waiting line LN or may be stored in advance in the storage unit 22 (see FIG. 2). The product delivery system 1 can acquire the waiting line information by reading it from the storage unit 22. The status information is information about the status of user U_1, and may include the location of user U_1. The product delivery system 1 can acquire the status information by receiving an external signal (e.g., a GPS signal). The product delivery system 1 can acquire the status information by accepting input from user U_1.

[0072] The product delivery system 1 identifies one or more candidate locations in the waiting line LN where the product GD can be picked up based on the queue information and the status information (S3). The product delivery system 1 presents the one or more candidate locations to the user U_1 (S4) and waits until a pickup request RQ3 is received (No in S5). The pickup request RQ3 specifies a candidate location selected by the user U_1 from the one or more candidate locations as the pickup location.

[0073] When the product delivery system 1 receives the pickup request RQ3 (Yes in S5), it creates a delivery plan to deliver the product GD to the pickup location in accordance with the pickup request RQ3 (S6). The product delivery system 1 drives the mobile unit 40 carrying the product GD in accordance with the delivery plan (S7). The product delivery system 1 waits until it receives a completion notification indicating that pickup is complete (No in S8). When it receives the completion notification, the product delivery system 1 determines that pickup of the product GD is complete (Yes in S8) and ends the process.

[0074] In addition, the purchase settlement for product GD may be made when the reservation request RQ0 of S1 is received from user U_1, when the receipt request RQ3 of S5 is received from user U_1, or when the completion notification of S8 is received from user U_1.

[0075] Next, a use case of the product delivery method executed in the product delivery system 1 will be described with reference to Fig. 5. Fig. 5 is a sequence diagram showing a use case of the product delivery method.

[0076] In the product delivery system 1, the terminal 30 waits until it receives the reservation request RQ0 (No in S11).

[0077] When the terminal 30 receives the reservation request RQ0 (Yes in S11), the terminal 30 transmits the reservation request RQ0 to the fleet management server 10 and the area management server 20 via the communication line 60.

[0078] When the fleet management server 10 receives the reservation request RQ0 (S13), it transmits an acquisition request RG1 to the area management server 20 and transmits an acquisition request RQ2 to the terminal 30 (S15).

[0079] The area management server 20 receives the reservation request RQ0 from the terminal 30 (S14) and the acquisition request RG1 from the fleet management server 10 (S16), and then acquires the queue information (S17). The area management server 20 transmits the queue information to the fleet management server 10 (S18).

[0080] On the other hand, when the terminal 30 receives the acquisition request RQ2 from the fleet management server 10 (S19), the terminal 30 acquires the status information (S20), and transmits the status information to the fleet management server 10 (S21).

[0081] The fleet management server 10 receives the queue information from the area management server 20 and the status information from the terminal 30 (S23). Then, based on the queue information and the status information, the fleet management server 10 identifies one or more candidate locations in the queue LN where the product GD can be picked up (S24). The fleet management server 10 then sends a selection request RQ4 to the terminal 30 (S25). The selection request RQ4 requests that one of the one or more candidate locations be selected.

[0082] When the terminal 30 receives the selection request RQ4 from the fleet management server 10 (S26), it displays one or more candidate locations on its display screen.

[0083] For example, as shown in FIG. 6( a), the terminal 30 has a display screen 30e1 of the display unit 30e on the main surface of the housing 30g. The display unit 30e may display the configuration of the waiting line LN, the position of user U_1 in the waiting line LN, and one or more candidate locations in the waiting line LN on the display screen 30e1. FIG. 6( a) illustrates a case in which the display screen 30e1 displays the static and dynamic configuration of the waiting line LN, the position of user U_1, and two candidate locations RP1 and RP2 in the waiting line LN. In FIG. 6( a), the sth location from the beginning of the waiting line LN (see FIG. 1) is highlighted as the location of user U_1, and candidate locations RP1 near the k-1st to k+1st positions in the waiting line LN and candidate locations RP2 near the 1st and 2nd positions are displayed in frames. k is an integer between 4 and n-1, inclusive. s is an integer between k+1 and n, inclusive. The display unit 30e may display both of the two candidate locations RP1 and RP2 in a display form that indicates that they are not selected. In Fig. 6(a), the fact that both of the two candidate locations RP1 and RP2 are not selected is indicated by a dotted frame.

[0084] The terminal 30 selects one candidate location from one or more candidate locations in response to an instruction from the user U_1 (S27).

[0085] For example, in the terminal 30, the input unit 30f receives an instruction from the user U_1 to select the candidate location RP1 from two candidate locations RP1 and RP2. The input unit 30f may receive an instruction to select the candidate location RP1 from the user U_1 in response to a touch operation on the candidate location RP1 on the display screen 30e1. In response to this, the display unit 30e may display the candidate location RP1 in a display form indicating a selected state of the two candidate locations RP1 and RP2, and display the candidate location RP2 in a display form indicating a non-selected state, as shown in FIG. 6(b). In FIG. 6(b), the selected state of the candidate location RP1 is indicated by a solid-line frame, and the non-selected state of the candidate location RP2 is indicated by a dotted-line frame.

[0086] The terminal 30 generates a pickup request RQ3 that specifies the selected candidate location as the pickup location, and transmits the request to the fleet management server 10 (S28).

[0087] At this time, the display unit 30e may hide the candidate location RP2 on the display screen 30e1 as shown in Fig. 6(c). The display unit 30e may further display a display object 30e11 for confirming successful receipt on the display screen 30e1. Fig. 6(c) illustrates the display object 30e11 as a touch-operable button.

[0088] The fleet management server 10 waits until it receives the pickup request RQ3 (No in S29). When the fleet management server 10 receives the pickup request RQ3 (Yes in S29), it creates a delivery plan to deliver the product GD to the pickup location in accordance with the pickup request RQ3 (S30). The fleet management server 10 generates and transmits driving instructions to the mobile object 40 in accordance with the reservation request RQ0 received in S13 and the delivery plan created in S30 (S31). The driving instructions include a designation of the pickup location. The driving instructions may further include a designation of the product.

[0089] The mobile object 40 waits at the home position (S32) until it receives a travel instruction (No in S33). The home position may be preset in the mobile object 40 as a location where it should wait. When the mobile object 40 receives the travel instruction (Yes in S33), it acquires the position information of the mobile object 40, calculates a travel route from the home position to the pickup location based on the travel instruction and the position information of the mobile object 40, and travels to the pickup location along the travel route (S34). When the mobile object 40 arrives at the pickup location, it provides the product GD specified in the travel instruction (S35).

[0090] When the user U_1 arrives at a location near the pickup location, the user U_1 can pick up the product GD. The terminal 30 can accept an input indicating successful pickup.

[0091] For example, the input unit 30f of the terminal 30 receives an input of successful receipt from the user U_1. The input unit 30f may receive an input of successful receipt from the user U_1 in response to a touch operation on the display object 30e2.

[0092] In response to this, the terminal 30 transmits a completion notification indicating that the receipt has been completed to the fleet management server 10 (S28).

[0093] The fleet management server 10 waits until it receives a completion notification, assuming that the reception is incomplete (No in S37). Upon receiving the completion notification, the fleet management server 10 determines that the reception is complete (Yes in S37), generates a return instruction, and transmits it to the mobile unit 40 (S38).

[0094] When the mobile body 40 receives the return instruction, it acquires the position information of the mobile body 40, and based on the return instruction and the position information of the mobile body 40, it determines a return route from the current position to the home position, and returns to the home position according to the return route (S39).

[0095] As described above, in the embodiment, in the product delivery method, one or more candidate locations in the waiting line LN where the product can be received are identified and presented to the user U_1, and the product GD is delivered to a receiving location selected by the user U_1 from the candidate locations. This allows the product GD to be handed over to the user U_1 waiting in the waiting line LN. As a result, the convenience of the users waiting in the waiting line can be improved.

[0096] As a first modified example of the embodiment, in the product delivery method executed by the product delivery system 1, one or more candidate products may be presented to the user U_1 in addition to one or more candidate locations.

[0097] For example, the product delivery system 1 in the first modified example of the embodiment differs from the embodiment in the following respects.

[0098] The storage unit 22 of the area management server 20 shown in Fig. 2 may store product information 22b in addition to the queue information 22a. The product information 22b may be predetermined and stored in the storage unit 22.

[0099] Product information 22b is information about products corresponding to locations, and one or more locations are associated with one or more products. Product information 22b may also be information that can limit the types of products that can be provided depending on the location. For example, in the case of FIG. 1, mobile object 40 is loaded with products GD1 to GD3 classified as non-food products and product GD4 classified as food. The product information may, for example, associate third or subsequent positions in waiting line LN with any of products GD1 to GD4, and may associate first and second positions in waiting line LN with non-food products GD1 to GD3.

[0100] The acquisition unit 11 of the fleet management server 10 receives, as a response to the acquisition request RQ1, the product information in addition to the waiting queue information from the area management server 20 via the communication line 60. The acquisition unit 11 supplies the waiting queue information and the product information to the candidate identification unit 13.

[0101] The candidate identification unit 13 identifies one or more candidate locations in the waiting line LN where the product GD can be picked up, based on the waiting line information, product information, and status information, and identifies one or more candidate products for each of the one or more candidate locations. That is, the candidate identification unit 13 identifies one or more sets of "candidate locations and one or more candidate products" based on the waiting line information, product information, and status information. The candidate identification unit 13 transmits one or more sets of "candidate locations and one or more candidate products" to the terminal 30 via the communication line 60.

[0102] When the notification unit 33 of the terminal 30 receives information on one or more sets of "candidate locations and one or more candidate products" from the operation management server 10 via the communication line 60, it may notify the user U_1 of the one or more sets of "candidate locations and one or more candidate products" by displaying the one or more sets of "candidate locations and one or more candidate products" on the display screen.

[0103] When the notification unit 33 displays one or more sets of "candidate locations and one or more candidate products" on the display screen and the request generation unit 34 receives a selection instruction to select one candidate location and one or more candidate products from the one or more sets of "candidate locations and one or more candidate products," the request generation unit 34 generates a pickup request RQ3. The pickup request RQ3 specifies the candidate location selected by the user U_1 as the pickup location and the candidate product selected by the user U_1 as the pickup product. The request generation unit 34 transmits the pickup request RQ3 to the fleet management server 10 via the communication line 60.

[0104] When the plan creation unit 14 of the fleet management server 10 receives the pickup request RQ3 from the terminal 30 via the communication line 60, it creates a delivery plan in response to the pickup request RQ3. The delivery plan includes delivering the pickup product GD to the pickup location. The plan creation unit 14 provides the delivery plan to the instruction unit 15.

[0105] The instruction unit 15 generates driving instructions in accordance with the delivery plan. The driving instructions include instructions for a pick-up location in accordance with the delivery plan, and further include designation of the product GD to be picked up in accordance with the delivery plan.

[0106] Furthermore, the product delivery method executed by the product delivery system 1 differs from the embodiment in the following respects, as shown in Fig. 7. Fig. 7 is a flowchart showing a product delivery method according to a first modified example of the embodiment.

[0107] The product delivery system 1 waits until it receives the reservation request RQ0 (No in S1), and upon receiving the reservation request RQ0 (Yes in S1), it acquires the queue information, product information, and status information (S102). The product delivery system 1 can acquire the product information by reading it from the storage unit 22.

[0108] The product delivery system 1 identifies one or more sets of "candidate locations and one or more candidate products" based on the queue information, product information, and status information (S103). The product delivery system 1 presents one or more sets of "candidate locations and one or more candidate products" to the user U_1 (S104) and waits until a pickup request RQ3 is received (No in S5). The pickup request RQ3 specifies a candidate location selected by the user from one or more candidate locations as the pickup location, and specifies a candidate product selected by the user from one or more candidate products as the pickup product.

[0109] When the product delivery system 1 receives the pick-up request RQ3 (Yes in S5), it creates a delivery plan for delivering the pick-up product GD to the pick-up location in response to the pick-up request RQ3 (S106).

[0110] After this, the same processing as in the embodiment can be performed.

[0111] Furthermore, a use case of the product delivery method executed in the product delivery system 1 differs from the embodiment in the following respects, as shown in Fig. 8. Fig. 8 is a sequence diagram showing a use case of the product delivery method according to a first modified example of the embodiment.

[0112] After steps S11 to S14 are performed in the same manner as in the embodiment, the fleet management server 10 transmits an acquisition request RG1 to the area management server 20 and transmits an acquisition request RQ2 to the terminal 30 (S115). The acquisition request RG1 includes a request to acquire waiting queue information and a request to acquire product information.

[0113] When the area management server 20 receives the acquisition request RG1 from the fleet management server 10 (S116), the area management server 20 acquires the waiting queue information and the product information (S117). The area management server 20 transmits the waiting queue information and the product information to the fleet management server 10 (S118).

[0114] On the other hand, steps S19 to S21 are carried out in the same manner as in the embodiment.

[0115] The operation management server 10 receives queue information and product information from the area management server 20 and status information from the terminal 30 (S123), and then identifies one or more sets of "candidate locations and one or more candidate products" based on the queue information, product information, and status information (S124).

[0116] For example, the product information may associate the third and subsequent positions in the waiting line LN with the products GD1 to GD4, and the first and second positions in the waiting line LN with the products GD1 to GD3. Candidate location RP1 is located near the k-1st to k+1st positions in the waiting line LN (see FIGS. 1 and 6(a)), and by referencing the product information, it may be identified as corresponding to the products GD1 to GD4. Candidate location RP2 is located near the first to second positions in the waiting line LN (see FIGS. 1 and 6(a)), and by referencing the product information, it may be identified as corresponding to the products GD1 to GD3. The fleet management server 10 may identify a set of candidate location RP1 (see FIG. 6(a)) and products GD1 to GD4, and a set of candidate location RP2 and products GD1 to GD3, based on the waiting line information and the product information.

[0117] The fleet management server 10 transmits a selection request RQ4 to the terminal 30 (S125). The selection request RQ4 requests the selection of one set of "candidate locations and one or more candidate products" from one or more sets of "candidate locations and one or more candidate products." The selection request RQ4 may further request the selection of at least one candidate product from one or more candidate products in the selected set of "candidate locations and one or more candidate products."

[0118] When the terminal 30 receives the selection request RQ4 from the fleet management server 10 (S126), it displays one or more sets of "candidate locations and one or more candidate products" on its display screen.

[0119] For example, in the terminal 30, the display unit 30e may display, on the display screen 30e1, a set of candidate location RP1 (see FIG. 6(a)) and products GD1 to GD4, and a set of candidate location RP2 and products GD1 to GD3. The display unit 30e may display, on the display screen 30e1, candidate location RP1 in a display form that associates products GD1 to GD4, and candidate location RP2 in a display form that associates products GD1 to GD3.

[0120] In response to an instruction from the user U_1, the terminal 30 selects one set of "candidate locations and one or more candidate products" from one or more sets of "candidate locations and one or more candidate products" (S127). The terminal 30 may further select at least one candidate product from the one or more candidate products in the selected set "candidate locations and one or more candidate products."

[0121] The terminal 30 generates a pickup request RQ3 that specifies the selected candidate location as the pickup location and the selected candidate product as the pickup product, and transmits the request to the fleet management server 10 (S128).

[0122] The fleet management server 10 waits until it receives the pickup request RQ3 (No in S29). When the fleet management server 10 receives the pickup request RQ3 (Yes in S29), it creates a delivery plan to deliver the pickup product GD to the pickup location in accordance with the pickup request RQ3 (S130). The fleet management server 10 generates and transmits driving instructions to the mobile object 40 in accordance with the delivery plan created in S130 (S131). The driving instructions include a designation of the pickup location and a designation of the pickup product.

[0123] After this, the same processing as in the embodiment is carried out.

[0124] In this way, in the product delivery method, one or more candidate locations in the waiting line LN where the product can be received and one or more candidate products corresponding to each candidate location are identified and presented to the user U_1. The product GD selected by the user U_1 from among the presented candidate locations is delivered to the receiving location selected by the user U_1 from among the presented candidate locations. This allows the product GD corresponding to the location to be handed over to the user U_1 waiting in the waiting line LN. As a result, the convenience of the users waiting in the waiting line can be further improved.

[0125] Note that product information 22b may be information that limits the quantity of products that can be provided depending on the location, instead of information that limits the type of product that can be provided depending on the location. For example, in the example shown in FIG. 1, a mobile object 40 is loaded with products GD1-GD3 with a small quantity and product GD4 with a large quantity. The product information may, for example, associate any of products GD1-GD4 with the third or subsequent positions in the waiting line LN, and associate the first and second positions in the waiting line LN with products GD1-GD3 with a small quantity. This type of product information 22b can also identify one or more candidate locations in the waiting line LN where products can be received, and one or more candidate products corresponding to each candidate location.

[0126] Alternatively, as a second modified example of the embodiment, the success or failure of receipt by the user may be determined in the product delivery method executed by the product delivery system 1 .

[0127] For example, the product delivery method executed by the product delivery system 1 differs from the embodiment in the following respects, as shown in Fig. 9. Fig. 9 is a flowchart showing a product delivery method according to a second modification of the embodiment.

[0128] After steps S1 to S7 are performed in the same manner as in the embodiment, the product delivery system 1 ends the process when it receives a completion notification indicating that the product has been received (Yes in S8).

[0129] If the product delivery system 1 does not receive a completion notification and the receipt is incomplete (No in S8), the product delivery system 1 waits until it determines that the receipt has failed (No in S201).

[0130] For example, the product delivery system 1 may determine that the receipt has failed by receiving a failure notification indicating that the receipt has failed in response to a user operation. This allows the product delivery system 1 to determine whether the receipt has been successful or not in response to the user operation.

[0131] Alternatively, the product delivery system 1 may determine that the receipt has failed (Yes in S201) if the receipt is not completed until the determination time has elapsed since the mobile object 40 arrived at the receiving location. The determination time includes a default time experimentally determined in advance as the time after which the user's receipt of the product is considered to have failed. This allows the product delivery system 1 to determine whether the receipt has been successful without relying on user operation, thereby reducing the number of user operations required to hand over the product GD.

[0132] Alternatively, the product delivery system 1 may identify the location and travel speed of the user U_1 based on the queue information and the situation information, and predict the stay time of the user U_1 at the pickup location upon arrival of the mobile object 2 based on the location, travel speed, and current time of the user U_1. If the predicted stay time is equal to or shorter than a predetermined time, the product delivery system 1 may determine that the pickup will fail (Yes in S201). This reduces the possibility that the progress of the queue LN will be impeded by the user waiting longer than necessary for the arrival of the mobile object 2.

[0133] When the product delivery system 1 determines that the receipt has failed or will be unsuccessful (Yes in S201), it reacquires the waiting queue information and the status information (S202).

[0134] The product delivery system 1 identifies one or more re-candidate locations where the product GD can be picked up in the waiting queue LN based on the waiting queue information and the status information (S203). If there are no re-candidate locations (No in S204), the product delivery system 1 cancels the reservation request R0 accepted in S1 and ends the process.

[0135] If there are re-candidate locations (Yes in S204), the product delivery system 1 presents one or more re-candidate locations to the user U_1 (S206) and waits until a re-receiving request RQ13 is received (No in S207). The re-receiving request RQ13 specifies a re-candidate location selected by the user from the one or more re-candidate locations as the re-receiving location.

[0136] When the product delivery system 1 receives the re-receive request RQ13 (Yes in S207), it creates a redelivery plan to deliver the product GD to the re-receive location in response to the re-receive request RQ13 (S208). The product delivery system 1 causes the mobile object 40 carrying the product GD to travel again in accordance with the redelivery plan (S209). The product delivery system 1 waits until it receives a completion notification indicating that the product GD has been received (No in S210). When the product delivery system 1 receives the completion notification, it considers that the product GD has been received (Yes in S210) and ends the process.

[0137] Furthermore, a use case of the product delivery method executed in the product delivery system 1 differs from the embodiment in the following respects, as shown in Fig. 10. Fig. 10 is a sequence diagram showing a use case of the product delivery method according to a second modified example of the embodiment.

[0138] S11 to S33 (see Figure 5) are performed in the same manner as in the embodiment, and the mobile body 40 acquires the position information of the mobile body 40, determines a driving route from the home position to the pick-up location based on the driving instructions and the position information of the mobile body 40, and drives to the pick-up location according to the driving route (S34).

[0139] In this case, if the user U_1 passes a position in the waiting line LN near the pickup location before the mobile object 40 arrives at the pickup location, the user U_1 will not be able to pick up the product GD. The terminal 30 may be capable of accepting an input indicating failure to pick up the product GD.

[0140] For example, in S28 of Fig. 5, the display unit 30e may further display a display object 30e12 for confirming whether the item was received successfully on the display screen 30e1, in addition to a display object 30e11 for confirming whether the item was received successfully, as shown in Fig. 6(c) . Fig. 6(c) illustrates display objects 30e11 and 30e12 that are touch-operable buttons.

[0141] In S34 of FIG. 10 , as shown in FIG. 11( a), when the mobile object 40 arrives at the receiving location RP1 (see FIG. 6( c)), it is assumed that user U_1 is at the t-th position in the waiting line LN. t is an integer between 2 and k+1 (see FIG. 1). In this case, it is difficult for user U_1 to receive the product GD carried on the mobile object 40. In the terminal 30, the input unit 30f receives an input of a receiving failure from user U_1. The input unit 30f may receive an input of a receiving failure from user U_1 in response to a touch operation on the display object 30e12.

[0142] In response to this, the terminal 30 transmits a failure notification indicating failure in reception to the fleet management server 10 (S241).

[0143] On the other hand, if the fleet management server 10 receives a completion notification indicating that the reception is complete (Yes in S240), the fleet management server 10 ends the process.

[0144] If the fleet management server 10 does not receive a completion notification and reception is incomplete (No in S240), it waits until it receives a failure notification indicating failure of reception (No in S242). If the fleet management server 10 receives a failure notification, it determines that reception has failed (Yes in S242), and sends a reacquisition request RG11 to the area management server 20 and a reacquisition request RQ12 to the terminal 30 (S243).

[0145] When the area management server 20 receives the reacquisition request RG11 from the fleet management server 10 (S244), the area management server 20 reacquires the waiting queue information (S245), and transmits the waiting queue information to the fleet management server 10 (S246).

[0146] On the other hand, when the terminal 30 receives the reacquisition request RQ12 from the fleet management server 10 (S247), the terminal 30 reacquires the status information (S248), and transmits the status information to the fleet management server 10 (S249).

[0147] The fleet management server 10 receives the queue information from the area management server 20 and the status information from the terminal 30 (S250). Then, based on the queue information and the status information, the fleet management server 10 identifies one or more re-candidate locations in the queue LN where the product GD can be picked up (S251). The fleet management server 10 sends a reselection request RQ14 to the terminal 30 (S252). The reselection request RQ14 requests the selection of one of the one or more re-candidate locations.

[0148] When the terminal 30 receives the reselection request RQ14 from the fleet management server 10 (S253), it displays one or more re-candidate locations on its display screen.

[0149] For example, in the terminal 30, the display unit 30e may display the configuration of the waiting queue LN, the position of user U_1 in the waiting queue LN, and one or more re-candidate locations in the waiting queue LN on the display screen 30e1, as shown in FIG. 11(a). FIG. 11(a) illustrates a case in which the static and dynamic configurations of the waiting queue LN shown in FIG. 1 are displayed, the position of user U_1 is displayed, and one candidate location RP2 in the waiting queue LN is displayed. In FIG. 11(a), the tth position from the beginning of the waiting queue LN is highlighted as the position of user U_1, and the re-candidate locations RP2 near the first or second positions in the waiting queue LN are displayed in a frame. The display unit 30e may display the re-candidate location RP2 in a display form indicating a non-selected state. In FIG. 11(a), the non-selected state of the re-candidate location RP2 is indicated by a dotted frame.

[0150] The terminal 30 selects one re-candidate location from one or more re-candidate locations in response to an instruction from the user U_1 (S254).

[0151] For example, in the terminal 30, the input unit 30f receives an instruction to select the re-candidate location RP2 from the user U_1. The input unit 30f may receive the instruction to select the re-candidate location RP2 from the user U_1 in response to a touch operation on the re-candidate location RP2 on the display screen 30e1. In response to this, the display unit 30e may display the re-candidate location RP2 in a display form indicating a selected state, as shown in FIG. 11(b) . In FIG. 11(b) , the selected state of the re-candidate location RP2 is indicated by a solid-line frame.

[0152] The terminal 30 generates a re-pickup request RQ13 that specifies the selected one re-candidate location as the re-pickup location, and transmits it to the fleet management server 10 (S255).

[0153] At this time, the display unit 30e may further display a display object 30e13 on the display screen 30e1 to confirm whether the item has been received successfully, as shown in Fig. 11(c). The display unit 30e may further display a display object 30e14 on the display screen 30e1 to confirm whether the item has been received unsuccessfully. Fig. 11(c) illustrates display objects 30e13 and 30e14 as touch-operable buttons.

[0154] The fleet management server 10 waits until it receives a re-receive request RQ13 (No in S256). When the fleet management server 10 receives the re-receive request RQ13 (Yes in S256), it creates a redelivery plan to deliver the product GD to the pickup location in response to the re-receive request RQ13 (S257). The fleet management server 10 generates a re-travel instruction in response to the reservation request RQ0 received in S13 and the redelivery plan created in S257, and transmits it to the mobile object 40 (S258). The re-travel instruction includes a designation of a re-receive location. The re-travel instruction may further include a designation of a product.

[0155] The mobile object 40 waits at its current location (S259) until it receives a re-travel instruction (No in S260). When the mobile object 40 receives the re-travel instruction (Yes in S260), it acquires the location information of the mobile object 40, calculates a travel route from its current location to the re-receive location based on the travel instruction and the location information of the mobile object 40, and travels to the re-receive location along the travel route (S261). When the mobile object 40 arrives at the re-receive location, it provides the product GD specified in the re-travel instruction (S262).

[0156] When the user U_1 arrives at a location near the re-receiving location, the user U_1 can receive the product GD. The terminal 30 can accept an input indicating successful receipt.

[0157] For example, the input unit 30f of the terminal 30 receives an input of successful receipt from the user U_1. The input unit 30f may receive an input of successful receipt from the user U_1 in response to a touch operation on the display object 30e13.

[0158] In response to this, the terminal 30 transmits a completion notification indicating that the receipt has been completed to the fleet management server 10 (S263).

[0159] The fleet management server 10 waits until it receives a completion notification, assuming that the reception is incomplete (No in S264). Upon receiving the completion notification, the fleet management server 10 determines that the reception is complete (Yes in S264), generates a return instruction, and transmits it to the mobile unit 40 (S265).

[0160] When the mobile body 40 receives the return instruction, it acquires the position information of the mobile body 40, and based on the return instruction and the position information of the mobile body 40, it determines a return route from the current position to the home position, and returns to the home position according to the return route (S266).

[0161] In this way, in the product delivery method, if user U_1 fails to receive product GD at the receiving location, one or more re-candidate locations in the waiting line LN where the product can be received are identified and presented to user U_1, and the product GD is redelivered to the re-receiving location specified by user U_1 from among the presented re-candidate locations. This allows the product GD to be delivered to user U_1 even if delivery of the product GD to user U_1 waiting in the waiting line LN fails. As a result, the convenience of users waiting in line can be further improved.

[0162] Alternatively, as another modification of the embodiment, the following changes may be made to the product delivery method according to the embodiment.

[0163] In the product delivery method, the pickup location may be changeable in response to a change instruction from user U_1. For example, after S28 in FIG. 5 , when the terminal 30 receives an instruction from user U_1 to change the selection of a candidate location, it regenerates a pickup request RQ3 and resends it to the fleet management server 10 in response to the selection change instruction. The regenerated pickup request RQ3 specifies the candidate location specified in the selection change instruction as the pickup location. Then, the processing from S29 onward is redone. This allows for cases where user U_1 wants to change the pickup location for their own convenience.

[0164] In the product delivery method, the location of the mobile object 40 may be presented to the user U_1 in addition to one or more candidate locations where the product can be received. For example, in S24 of FIG. 5 , the fleet management server 10 identifies one or more candidate locations based on queue information and status information, and queries the mobile object 40 to obtain location information of the mobile object 40. In S25 of FIG. 5 , the fleet management server 10 transmits a selection request RQ4 including one or more candidate locations and the location of the mobile object 40 to the terminal 30. In S27 of FIG. 5 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 displays the one or more candidate locations and the location of the mobile object 40 on its display screen. This allows the location of the mobile object 40 to be presented to the user U_1 in addition to one or more candidate locations, allowing the user U_1 to prepare to receive the product GD.

[0165] In the product delivery method, the appearance of the mobile object 40 may be presented to the user U_1 in addition to one or more candidate locations where the product can be received. For example, in S24 of FIG. 5 , the fleet management server 10 identifies one or more candidate locations based on queue information and status information, and acquires information indicating the appearance of the mobile object 40. The information indicating the appearance of the mobile object 40 may be registered in advance in the fleet management server 10. In S25 of FIG. 5 , the fleet management server 10 transmits a selection request RQ4 including one or more candidate locations and the appearance of the mobile object 40 to the terminal 30. In S27 of FIG. 5 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 displays one or more candidate locations and the appearance of the mobile object 40 on its display screen. This allows the appearance of the mobile object 40 to be presented to the user U_1 in addition to one or more candidate locations, allowing the user U_1 to smoothly receive the product GD.

[0166] In the product delivery method, the user U_1 may be presented with the planned arrival location of the mobile object 40 in addition to one or more candidate locations where the product can be received. For example, in S24 of FIG. 5 , the fleet management server 10 identifies one or more candidate locations based on queue information and status information, and queries the mobile object 40 to obtain location information of the mobile object 40. The fleet management server 10 identifies the planned arrival location of the mobile object 40 based on the location information of the mobile object 40. In S25 of FIG. 5 , the fleet management server 10 transmits a selection request RQ4 including one or more candidate locations and the planned arrival location of the mobile object 40 to the terminal 30. In S27 of FIG. 5 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 displays the one or more candidate locations and the planned arrival location of the mobile object 40 on its display screen. This allows the planned arrival location of the mobile object 40 to be presented to the user U_1 in addition to one or more candidate locations, allowing the user U_1 to prepare for receiving the product GD before receiving the product GD.

[0167] In the product delivery method, the user U_1 may be presented with one or more candidate locations where the product can be received, as well as the required time until the product can be received. For example, in S24 of FIG. 5 , the fleet management server 10 identifies one or more candidate locations based on the queue information and the status information, and identifies the required time until the product can be received for each of the candidate locations. If the status information includes the user U_1's position in the queue LN and the user U_1's moving speed, the fleet management server 10 can obtain the required time by acquiring the current time and dividing the distance between the user U_1's position and the candidate locations by the user U_1's moving speed. In S25 of FIG. 5 , the fleet management server 10 transmits a selection request RQ4 to the terminal 30, including the required time for each of the one or more candidate locations. In S27 of FIG. 5 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 displays the one or more candidate locations and the required time for each of the candidate locations on its display screen. This allows the user U_1 to be presented with one or more candidate locations as well as the time required to receive the product, allowing the user U_1 to make preparations before receiving the product GD.

[0168] In the product delivery method, the user U_1 may be presented with one or more candidate locations where the product can be received, as well as a predicted time for receiving the product. For example, in S24 of FIG. 5 , the fleet management server 10 identifies one or more candidate locations based on queue information and status information, and identifies a predicted time for receiving the product for each of the candidate locations. If the status information includes the user U_1's position in the queue LN and the user U_1's moving speed, the fleet management server 10 acquires the current time, divides the distance between the user U_1's position and the candidate locations by the user U_1's moving speed to determine the required time, and adds the determined required time to the current time to determine the predicted time for receiving the product. In S25 of FIG. 5 , the fleet management server 10 transmits a selection request RQ4 to the terminal 30, including the predicted time for receiving the product for each of the one or more candidate locations. In S27 of FIG. 5 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 displays the one or more candidate locations and the predicted time for receiving the product on its display screen. This allows the user U_1 to be presented with one or more candidate locations as well as a predicted time for receiving the product, allowing the user U_1 to make preparations before receiving the product GD.

[0169] In the product delivery method, the user U_1 may be notified of the arrival of the mobile object 40. For example, in S24 of FIG. 5, the fleet management server 10 identifies one or more candidate locations based on queue information and status information, and identifies a predicted pickup time for each of the candidate locations. If the status information includes the user U_1's position in the queue LN and the user U_1's traveling speed, the fleet management server 10 obtains the current time, divides the distance between the user U_1's position and the candidate location by the user U_1's traveling speed to determine the required time, and adds the determined required time to the current time to determine the predicted pickup time. After S31 of FIG. 5, the fleet management server 10 transmits an arrival notification to the terminal 30 a predetermined time before the predicted pickup time, notifying the user U_1 of the arrival of the mobile object 40. Upon receiving the arrival notification, the terminal 30 visually and / or audibly notifies the user U_1 of the predicted arrival of the mobile object 40. The visual notification may be a message displayed on the display screen 30e1 of the terminal 30. The auditory means may be a voice message output from the terminal 30. This allows the user U_1 to be notified in advance of the arrival of the moving object 40, and allows the user U_1 to prepare for receiving the product GD.

[0170] In the product delivery method, the delivery plan may be created taking into account a time margin so that user U_1 can receive the product GD with ample time to spare even if the user U_1's traveling speed in the waiting line LN increases or decreases. For example, in S30 of FIG. 5 , the fleet management server 10 creates a delivery plan based on the pickup request RQ3, the waiting line information, and the status information. If the status information includes the user U_1's position in the waiting line LN and the user U_1's traveling speed, the fleet management server 10 obtains the current time, divides the distance between the user U_1's position and the candidate location by the user U_1's traveling speed, and adds the obtained time to the current time to calculate the predicted pickup time. The fleet management server 10 subtracts the time margin from the predicted pickup time to calculate the target arrival time. The fleet management server 10 queries the mobile unit 40 to obtain the mobile unit 40's current location, divides the distance from the mobile unit 40's current location to the pickup location by the time from the current time to the target arrival time to calculate the target traveling speed, and includes the obtained target traveling speed in the delivery plan. In S31 of FIG. 5, the fleet management server 10 generates and transmits driving instructions to the mobile object 40 in accordance with the reservation request RQ0 and the delivery plan. At this time, the driving instructions include a target travel speed in addition to a specified pickup location. In response to this, in S34 of FIG. 5, the mobile object 40 drives to the pickup location along the travel route while controlling its travel speed to approach the target travel speed in accordance with the driving instructions. This increases the likelihood that user U_1 will successfully receive the product.

[0171] The time margin for allowing sufficient time for receiving the product GD may be updated sequentially using the difference between the predicted time for receiving the product when it was delivered in the past and the actual time for receiving the product, thereby taking past performance into consideration and further increasing the possibility that the user U_1 will successfully receive the product.

[0172] In the product delivery method, the predicted time for user U_1 to receive the product may be determined using status information for another user U_2. For example, in S23 of FIG. 5 , the fleet management server 10 receives status information for user U_1 from terminal 30 and determines that a product GD has also been provided to another user U_2 who is waiting in the same queue LN between now and a predetermined time ago. In this case, since users U_1 and U_2 in the same queue LN are assumed to be moving at similar speeds, the fleet management server 10 can determine the predicted time for user U_1 to receive the product using the difference between the predicted time for user U_2 to receive the product and the actual time of receipt. This also allows the past performance of another user U_2 who is waiting in the same queue LN to be taken into consideration, further increasing the likelihood that user U_1 will successfully receive the product.

[0173] In the product delivery method, location information of the mobile unit 40 may be acquired, and candidate locations where the mobile unit 40 can pick up the product may be calculated taking into account the time until the mobile unit 40 arrives. For example, in S15 of FIG. 5 , the fleet management server 10 sends an acquisition request RG1 to the area management server 20, an acquisition request RQ2 to the terminal 30, and an acquisition request RQ21 to the mobile unit 40. When the mobile unit 40 receives the acquisition request RQ21 from the fleet management server 10 (S19b), it acquires status information (S20b). The status information includes the location of the mobile unit 40. The mobile unit 40 transmits the status information to the fleet management server 10 (S21b). The fleet management server 10 receives queue information from the area management server 20, status information from the terminal 30, and status information from the mobile object 40 (S23 in FIG. 5), and then identifies one or more candidate locations in the queue LN where the product GD can be picked up, based on the queue information, the status information from the terminal 30, and the status information from the mobile object 40 (S24 in FIG. 5). This makes it possible to increase the number of candidate locations for product pick-up that can be presented to the user when the mobile object 40 can arrive at the pick-up location quickly.

[0174] In the product delivery method, locations where user U_1 is expected to pass after leaving the waiting line LN (for example, the exit side of the attraction AT) may also be presented to user U_1 as possible locations for receiving the product.

[0175] In the product delivery method, if another mobile body 40a is located closer to the pickup location than the mobile body 40, the other mobile body 40a may be driven to the pickup location instead of the mobile body 40. For example, after S30 of FIG. 5 , the fleet management server 10 transmits a status information acquisition request to one or more mobile bodies, including the mobile body 40. The fleet management server 10 receives status information from the one or more mobile bodies. The status information includes the location of the mobile body. The fleet management server 10 references the status information of the one or more mobile bodies and determines whether another mobile body is located closer to the pickup location than the mobile body 40. If the other mobile body 40a is located closer to the pickup location than the mobile body 40, the fleet management server 10 generates and transmits driving instructions to the other mobile body 40a in accordance with the reservation request RQ0 received in S13 and the delivery plan created in S30 (S31 of FIG. 5 ). This allows the other mobile body 40a to arrive at the pickup location more quickly, further increasing the likelihood that the user U_1 will successfully receive the product.

[0176] In the product delivery method, if the product is a rental product, a delivery plan may be created that includes delivery and collection. For example, in S30 of FIG. 5, the fleet management server 10 creates a delivery plan in response to a pickup request RQ3, in which the fleet management server 10 delivers the product GD to a pickup location, waits at the pickup location, collects the product GD at the pickup location, and returns. The fleet management server 10 generates and transmits driving instructions to the mobile unit 40 in response to the reservation request RQ0 received in S13 and the delivery plan created in S30 (S31 of FIG. 5). The driving instructions include a pickup location designation, a waiting designation, and a collection designation. The driving instructions may also include a product designation. In response to this, in S34 of FIG. 5, the mobile unit 40 travels to the pickup location along the driving route (S34 of FIG. 5), provides the product GD to the user U_1 (S35 of FIG. 5), waits at the pickup location, and, once the product GD is returned by the user U_1, returns to the home location (S39 of FIG. 5). This allows the delivery and collection of the product to be carried out together when the product is a rental product, thereby improving convenience for the user U_1.

[0177] In the product delivery method, the moving object 40 may provide the product GD to the user U_1 while moving, depending on the direction and speed of travel of the waiting line LN. This allows the product GD to be smoothly handed over to the user U_1, improving convenience for the user U_1.

[0178] In the product delivery method, one or more candidate locations where the product GD can be received may be presented to the user U_1 in two patterns: when the user U_1 is in the waiting line LN and when the user U_1 is outside the waiting line LN. For example, the user U_1 may be in the vicinity of the waiting line LN rather than in the waiting line LN. In S23 of FIG. 5, if the accuracy of the user U_1 included in the status information received from the terminal 30 is relatively low, the fleet management server 10 may have difficulty determining whether the user U_1 is in the waiting line LN even by referring to the status information. Therefore, in S24 of FIG. 5, the fleet management server 10 identifies one or more candidate locations in the waiting line LN where the product GD can be received, based on the waiting line information and the status information, in two patterns: when the user U_1 is in the waiting line LN and when the user U_1 is outside the waiting line LN. 5, the terminal 30 selects one of the two patterns in response to an instruction from the user U_1 that takes into account the user's actual location, and selects one of the one or more candidate locations in the selected pattern (S27). This allows the terminal 30 to present the user U_1 with suitable candidate pick-up locations for both the case where the user U_1 is inside the waiting queue LN and the case where the user U_1 is outside the waiting queue LN.

[0179] In the product delivery method, when reservation requests are made within a predetermined time period from multiple users in the same waiting line LN, the reservation requests may be processed in order of earliest timing, or the reservation requests may be processed in order of the users' line-up in the waiting line LN. This allows reservation requests from multiple users to be processed without any omissions, and prevents users from missing out on receiving products.

[0180] In the product delivery method, if reservation requests are received from multiple users in the same waiting line LN within a predetermined time period, the reservation requests from the multiple users may be processed in parallel. For example, let person P_s in FIG. 1 be user U_1, and person P_t be user U_2. The product delivery system 1 may perform the processes S1 to S8 in FIG. 4 for user U_1 and the processes S1 to S8 in FIG. 4 for user U_2 in parallel. The product GD' specified in the reservation request RQ0' in S1 for user U_2 may be different from the product GD specified in the reservation request RQ0 in S1 for user U_1. The status information acquired by the product delivery system 1 in S2 for user U_2 is information regarding the status of user U_2 and may include the location of user U_2. The one or more candidate locations identified in S3 for user U_2 and presented in S4 may be the same as the one or more candidate locations identified in S3 for user U_1 and presented in S4, or may be different from the one or more candidate locations identified in S3 for user U_1 and presented in S4. The pickup request RQ3' for user U_2, the acceptance of which is determined in S5, may be different from the pickup request RQ3 for user U_1, the acceptance of which is determined in S5. The delivery plan created in S6 for user U_2 is a plan for delivering product GD' to the pickup location corresponding to pickup request RQ3'.

[0181] In the product delivery method, when multiple product reservation requests are made by users in the same waiting line LN within a predetermined time period, the reservation requests for the multiple products may be processed in parallel. For example, suppose there are reservation requests for products GD1 and GD2 shown in FIG. 1 . The product delivery system 1 may process S1 to S8 of FIG. 4 for product GD1 in parallel with S1 to S8 of FIG. 4 for product GD2. Product GD1 is specified by a reservation request RQ0 in S1 for product GD1, and product GD2 is specified by a reservation request RQ0' in S1 for product GD2. The one or more candidate locations identified in S3 and presented in S4 for product GD2 may be the same as the one or more candidate locations identified in S3 and presented in S4 for product GD1, or may be different from the one or more candidate locations identified in S3 and presented in S4 for product GD1. The pickup location specified in the pickup request RQ3' for product GD2, the acceptance of which is determined in S5, may be the same as the pickup location specified in the pickup request RQ3 for product GD1, the acceptance of which is determined in S5, or may be different from the pickup location specified in the pickup request RQ3 for product GD1, the acceptance of which is determined in S5. The delivery plan created in S6 for product GD1 is a plan for delivering product GD1 to the pickup location specified in the pickup request RQ3. The delivery plan created in S6 for product GD2 is a plan for delivering product GD2 to the pickup location specified in the pickup request RQ3'. The mobile object on which product GD1 is loaded in S7 for product GD2 may be the same as the mobile object on which product GD1 is loaded in S7 for product GD1, or may be different from the mobile object on which product GD1 is loaded in S7 for product GD1.

[0182] Alternatively, the following modifications may be made to the product delivery method according to the second modified example of the embodiment.

[0183] In the product delivery method, when multiple reservation requests for products are made by users in the same waiting line LN within a predetermined time period, the reservation requests for the multiple products may be processed in parallel. For example, suppose that reservation requests are made for products GD1 and GD2 shown in FIG. 1 . The product delivery system 1 may process S1 to S201 of FIG. 9 for product GD1 in parallel with S1 to S201 of FIG. 9 for product GD2. Product GD1 is specified by a reservation request RQ0 in S1 for product GD1, and product GD2 is specified by a reservation request RQ0' in S1 for product GD2. The one or more candidate locations identified in S3 for product GD2 and presented in S4 may be different from the one or more candidate locations identified in S3 for product GD1 and presented in S4. The pickup location specified in a pickup request RQ3' for product GD2, the acceptance of which is determined in S5, may be different from the pickup location specified in a pickup request RQ3 for product GD1, the acceptance of which is determined in S5. The delivery plan created in S6 for product GD1 is a plan for delivering product GD1 to a pickup location in accordance with pickup request RQ3. The delivery plan created in S6 for product GD2 is a plan for delivering product GD2 to a pickup location in accordance with pickup request RQ3'. The mobile body on which product GD1 is loaded in S7 for product GD2 may be the same mobile body on which product GD1 is loaded in S7 for product GD1.

[0184] In this case, the product delivery system 1 may determine that the receipt of each of product GD1 and product GD2 has failed (Yes in S201) if the receipt is not completed until the determination time has elapsed since the mobile object 40 arrived at the receiving location. For example, if the mobile object 2 arrives to receive product GD1 and then product GD2, the determination time for product GD1 may be shorter than a default time experimentally determined in advance as the time at which the user's receipt of the product is considered to have failed. The determination time for product GD1 may be shorter than the determination time for product GD2. This reduces the chance of the user failing to receive each of the multiple products GD1 and GD2.

[0185] Alternatively, as a third modified example of the embodiment, in the product delivery system 101 , the situation information regarding the situation of the user U may be acquired by the area management server 120 using the image sensor 50 .

[0186] For example, the product delivery system 101 in the third modified example of the embodiment differs from the embodiment in the following respects, as shown in Fig. 12. Fig. 12 is a diagram showing the functional configuration of the product delivery system 101 in which the product delivery method according to the third modified example of the embodiment is executed.

[0187] A user characteristic image indicating the characteristics of the user U may be registered in advance in the area management server 120. The area management server 120 may manage situation information via the user characteristic image and the image acquired by the image sensor 50.

[0188] In the area management server 120, the information acquisition unit 123 may acquire status information in addition to the waiting line information. The information acquisition unit 123 may acquire status information in addition to the waiting line information by receiving input from the manager of the target facility AT, and store the status information in the memory unit 122. As a result, the memory unit 122 stores status information 22d in addition to waiting line information 22a.

[0189] Alternatively, the information acquisition unit 123 may perform image recognition on the image of the waiting line LN acquired by the image sensor 50 to acquire status information in addition to the waiting line information and store the acquired status information in the storage unit 122.

[0190] For example, the terminal 130 has an image acquisition unit 135 instead of the situation acquisition unit 32 (see FIG. 2 ), and the position acquisition unit 31 is omitted. The terminal 130 may further have an imaging sensor 30f in addition to the hardware configuration shown in FIG. 3 . The image acquisition unit 135 shown in FIG. 7 may be realized by the imaging sensor 30f and the communication I / F 30b. The image acquisition unit 135 receives an imaging request from the user U, acquires a user characteristic image in response to the imaging request, and transmits the user characteristic image to the area management server 20 via the communication line 60.

[0191] The area management server 120 receives the user characteristic image via the communication line 60 and stores it in the storage unit 122. As a result, the storage unit 122 stores the user characteristic image 22c in advance.

[0192] The information acquisition unit 123 receives the image of the waiting queue LN acquired by the image sensor 50, generates waiting queue information according to the image of the waiting queue LN, and stores it in the storage unit 122. At the same time, the information acquisition unit 123 may read the user characteristic image 22c from the storage unit 122, perform pattern matching of the user characteristic image 22c with the image of the waiting queue LN, generate situation information such as the position of the user U in the waiting queue LN, and store it in the storage unit 122. As a result, the storage unit 122 stores situation information 22d in addition to the waiting queue information 22a.

[0193] At this time, in the fleet management server 110, the acquisition unit 112 may transmit an acquisition request RQ2 requesting acquisition of status information to the area management server 120 instead of the terminal 130.

[0194] When the information providing unit 121 receives the acquisition request RQ1 and the acquisition request RQ2 from the fleet management server 110, the information providing unit 121 reads out the waiting queue information 22a and the status information 22d from the storage unit 122. As a response to the acquisition request RQ1 from the fleet management server 110, the information providing unit 121 transmits the waiting queue information to the fleet management server 110 via the communication line 60. At the same time, as a response to the acquisition request RQ2, the information providing unit 121 transmits the status information to the fleet management server 110 via the communication line 60.

[0195] According to this product delivery system 101, one or more candidate locations are identified and presented to the user U using status information acquired by input on the area management server 120 or image recognition, and the product GD is delivered to a pickup location designated by the user U from among the presented candidate locations. This allows the user U to hand over the product GD to the user U waiting in the waiting line LN without having to input status information into the terminal 130. As a result, convenience for the users waiting in the waiting line can be further improved.

[0196] Furthermore, with this product delivery system 101, the location of the user U can be identified more accurately than when using input from the user U. This allows, for example, the predicted product receipt time to be calculated accurately when calculating the predicted product receipt time based on the location of the user U.

[0197] Alternatively, as a fourth modified example of the embodiment, in the product delivery system 101, as shown in Fig. 13, the candidate locations where the product can be received may be dynamically changed without a request from the user U. Fig. 13 is a flowchart showing a product delivery method according to the fourth modified example of the embodiment.

[0198] The product delivery system 101 waits until it receives a reservation request RQ0 (No in S1), and upon receiving the reservation request RQ0 (Yes in S1), it acquires queue information and status information (S301). The queue information and status information may be stored in advance in the storage unit 122 (see FIG. 12). The product delivery system 1 can acquire the queue information and status information by reading them from the storage unit 122.

[0199] The product delivery system 1 identifies one or more candidate locations in the waiting line LN where the product GD can be received, based on the waiting line information and the status information (S3).

[0200] The product delivery system 101 performs the processes of S4 to S303 and S304 to S307 in parallel.

[0201] In the processes of S304 to S307, the product delivery system 101 waits until it is time to acquire the queue information and the status information (No in S304). The timing to acquire the queue information and the status information may be when the product delivery system 101 detects a change in the surrounding situation, or when a predetermined time has elapsed since the start of S304.

[0202] When it is time to acquire the queue information and the status information (Yes in S304), the product delivery system 101 acquires the queue information and the status information (S305).

[0203] The product delivery system 101 identifies one or more candidate locations in the waiting line LN where the product GD can be picked up, based on the waiting line information and the status information (S306).

[0204] The product delivery system 101 repeats the processes of S304 to S306 until the moving object 2 arrives at the destination (No in S307).

[0205] In the processing of S4 to S303, the product delivery system 101 performs S4 to S7 in the same manner as in the embodiment, and determines whether or not one or more candidate locations in the waiting line LN where the product GD can be received should be changed (S302).

[0206] If the one or more candidate locations identified in the previous S306 differ from the one or more candidate locations presented to user U_1 in S4, the product delivery system 101 determines that the one or more candidate locations should be changed (Yes in S302), and changes the one or more candidate locations by, for example, replacing the one or more candidate locations with the one or more candidate locations identified in the previous S306. The product delivery system 101 changes the delivery plan to deliver the product GD to a pickup location corresponding to the one or more changed candidate locations (S6). The product delivery system 101 drives the mobile unit 40 carrying the product GD toward the changed destination according to the changed delivery plan (S7).

[0207] If the one or more candidate locations identified in the previous S306 are the same as the one or more candidate locations presented to user U_1 in S4, the product delivery system 101 determines that the one or more candidate locations should not be changed (No in S302), and repeats the processes of S7 to S302 until the mobile object 2 arrives at the destination (No in S303).

[0208] When the mobile object 2 arrives at the destination (Yes in S303, Yes in S307), the product delivery system 101 completes the processes of S4 to S302 and S303 to S306, and waits until it receives a completion notification indicating that the product has been received (No in S8). When it receives the completion notification, the product delivery system 101 determines that the product GD has been received (Yes in S8) and ends the process.

[0209] Furthermore, the use case of the product delivery method executed in the product delivery system 101 differs from the embodiment in the following respects, as shown in Fig. 14. Fig. 14 is a sequence diagram showing a use case of the product delivery method according to the fourth modified example of the embodiment.

[0210] After steps S11 to S16 are performed in the same manner as in the embodiment, the area management server 120 acquires the waiting queue information and the status information (S311). The area management server 120 transmits the waiting queue information and the status information to the fleet management server 110 (S312).

[0211] When the fleet management server 110 receives the queue information and the status information from the area management server 120 (S313), steps S24 to S33 are performed in the same manner as in the embodiment, and the moving object 40 starts traveling (S34).

[0212] When a change in the surrounding situation is detected (or when a predetermined time has passed since the previous acquisition), the area management server 120 reacquires the waiting queue information and the status information (S314).The area management server 120 retransmits the waiting queue information and the status information to the fleet management server 110 (S315).

[0213] When the fleet management server 110 receives the queue information and status information from the area management server 120 again (S316), it identifies one or more candidate locations in the queue LN where the product GD can be picked up, based on the queue information and status information. If the identified candidate locations differ from the candidate locations identified in S24, the fleet management server 110 changes the candidate locations to be used in the delivery plan, for example by replacing the candidate locations with the identified candidate locations (S317). The fleet management server 110 selects one of the candidate locations after the change and recreates the delivery plan based on the selected candidate location (S318). The fleet management server 110 generates and transmits revised driving instructions to the vehicle 40 based on the reservation request RQ0 received in S13 and the delivery plan recreated in S318 (S319).

[0214] When the mobile body 40 receives the changed driving instruction, it acquires the position information of the mobile body 40, determines a driving route from the current position to the changed pick-up location according to the changed driving instruction and the position information of the mobile body 40, and drives to the changed pick-up location according to the driving route (S320).

[0215] When a change in the surrounding conditions is detected again (or when a predetermined time has passed since the previous acquisition), the area management server 120 reacquires the waiting queue information and the status information (S321).The area management server 120 retransmits the waiting queue information and the status information to the fleet management server 110 (S322).

[0216] When the fleet management server 110 receives the queue information and status information from the area management server 120 again (S323), it identifies one or more candidate locations in the queue LN where the product GD can be picked up, based on the queue information and status information. If the identified candidate locations differ from the candidate locations selected in S317, the fleet management server 110 changes the one or more candidate locations to be used in the delivery plan, for example by replacing them with the identified candidate locations (S324). The fleet management server 110 selects one of the one or more candidate locations after the change and recreates the delivery plan based on the selected candidate location (S325). The fleet management server 110 generates and transmits revised driving instructions to the mobile unit 40 based on the reservation request RQ0 received in S13 and the delivery plan recreated in S325 (S326).

[0217] When the mobile body 40 receives the changed driving instructions, it acquires the position information of the mobile body 40, and determines a driving route from the current position to the changed pick-up location according to the changed driving instructions and the position information of the mobile body 40, and drives to the changed pick-up location according to the driving route (S327).

[0218] Thereafter, steps S35 to S39 are carried out in the same manner as in the embodiment.

[0219] In this way, in the product delivery method, the candidate locations where the product can be received are dynamically changed without a request from the user U, and the product GD is delivered to a receiving location corresponding to the changed candidate location. This eliminates the need for the user U to input situation information into the terminal 130, and allows the candidate locations to be flexibly changed in response to changes in the surrounding circumstances, allowing the product GD to be handed over to the user U_1. As a result, the convenience of users waiting in line can be further improved.

[0220] Alternatively, the following modifications may be made to the product delivery method according to the fourth modified example of the embodiment.

[0221] In the product delivery method, the selection of candidate locations to be used in the delivery plan may be performed by the fleet management server 110. For example, in the product delivery method shown in FIG. 14, steps S25 to S29 may be omitted. In this case, in step S30 of FIG. 14, the fleet management server 110 selects one candidate location from the one or more candidate locations identified in step S24, and creates a delivery plan based on the selected candidate location. This eliminates the need for the user U to input situation information into the terminal 130 and the user U to select and input a candidate location into the terminal 130.

[0222] In the product delivery method, when selecting candidate locations to be used in the delivery plan, candidate locations with a high degree of service provision suitability may be preferentially selected. For example, in the product delivery method shown in FIG. 14, steps S25 to S29 may be omitted. In this case, in step S30 of FIG. 14, the fleet management server 110 may preferentially select candidate locations with a high degree of service provision suitability from among one or more candidate locations. This allows for the generation of driving instructions that include a pickup location to which the mobile object 40 can appropriately travel.

[0223] For example, the fleet management server 110 may select, from among one or more candidate locations, a candidate location where the route along which the mobile object 40 travels to the pickup location is unlikely to be impassable due to a waiting queue LN or the like, as a candidate location with a high degree of service provision appropriateness. This increases the likelihood that the mobile object 40 will arrive at the pickup location by the specified time.

[0224] Alternatively, the fleet management server 110 may select, from among one or more candidate locations, a candidate location where it is easy to provide the product GD as a candidate location with a high degree of service provision suitability. The fleet management server 110 may select, from among one or more candidate locations, a candidate location where a larger space can be secured for providing the product GD as a candidate location with a high degree of service provision suitability. This allows the product GD to be smoothly handed over to the user U when providing the product GD.

[0225] In the product delivery method, when the selection request RQ4 is transmitted from the fleet management server 110 to the terminal 30, the selection request RQ4 may include reference information for candidate locations with a high degree of service provision suitability. For example, in S24 of FIG. 14 , the fleet management server 110 may identify one or more candidate locations in the queue LN where the product GD can be received based on the queue information and the situation information. Then, the fleet management server 110 may generate reference information for candidate locations with a high degree of service provision suitability among the one or more candidate locations. The reference information includes information identifying the candidate locations. In this case, in S26 of FIG. 14 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 may display one or more candidate locations included in the selection request RQ4 on its display screen and may also display the reference information included in the selection request RQ4 in association with the candidate locations. This allows reference information to be provided when the user U selects one of the one or more candidate locations, improving the user U's convenience.

[0226] For example, the fleet management server 110 may determine, among one or more candidate locations, a candidate location whose service provision suitability is equal to or greater than a predetermined value as a recommended candidate location and generate reference information indicating this. In response, when displaying one or more candidate locations on its display screen, the terminal 30 may display the candidate location according to the reference information in a display format (e.g., highlighted display) that indicates that the candidate location according to the reference information is recommended. This allows the user U to be presented with reference information for selecting a candidate location and assist the user U in selecting a candidate location.

[0227] While the above-described embodiment and its modified examples illustrate a product delivery method in which a product is delivered to a user by a mobile object, the scope of application of the present disclosure is not limited thereto. For example, the present disclosure may be applied to a service provision method in which any service is provided to a user by a mobile object. The services include mobile vending machine provision and luggage storage / return, in addition to product delivery. The mobile vending machine provision is a service in which a mobile vending machine is moved to a location where the user can operate it, encouraging the user to operate it. The mobile vending machine provision may be a service in which the vending machine can be relocated to a location where the user can operate it, or a service in which the vending machine can be relocated to match the shape of a queue to maximize sales. The luggage storage service may be a service in which a mobile locker robot is used to store and return luggage for users waiting to check in or check out of a lodging facility.

[0228] For example, in the service provision method, one or more candidate service provision locations in the waiting queue LN where service can be provided are identified and presented to the user U, and a service vehicle is moved to a service provision location specified by the user U from among the presented candidate service provision locations. This allows the service to be provided by the service vehicle to the users U waiting in the waiting queue LN. As a result, convenience for the users waiting in the waiting queue can be improved.

[0229] In the product delivery method, a method for receiving the service from a mobile object may be presented to the user in addition to one or more candidate service locations where the service can be received. For example, in S24 of FIG. 5 , the fleet management server 10 identifies one or more candidate locations based on queue information and status information, and acquires information indicating a method for receiving the service from the mobile object 40. In S25 of FIG. 5 , the fleet management server 10 transmits a selection request RQ4 including one or more candidate locations and a method for receiving the service from the mobile object 40 to the terminal 30. In S27 of FIG. 5 , upon receiving the selection request RQ4 from the fleet management server 10, the terminal 30 displays the one or more candidate locations and the method for receiving the service from the mobile object 40 on its display screen. This allows the user U_1 to be presented with the method for receiving the service in addition to one or more candidate locations, allowing the user U_1 to smoothly receive the service.

[0230] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention described in the claims and their equivalents.

[0231] REFERENCE SIGNS LIST 1 Product delivery system 10 Traffic management server 11 Acquisition unit 12 Acquisition unit 13 Candidate identification unit 14 Plan creation unit 15 Instruction unit 20 Area management server 21 Information provision unit 22 Storage unit 23 Information acquisition unit 30 Terminal 31 Position acquisition unit 32 Status acquisition unit 33 Notification unit 34 Request generation unit 40 Mobile body 41 Travel unit 42 Position acquisition unit 43 Provision unit 50 Imaging sensor

Claims

1. Obtaining queue information regarding a queue including a user, obtaining status information regarding the status of the user, identifying one or more candidate locations where a product in the queue can be received based on the queue information and the status information, creating a delivery plan for delivering the product to the received location in response to a receiving request designating the candidate location selected by the user as the receiving location among the one or more candidate locations, and causing a moving body on which the product is mounted to travel according to the delivery plan. A product delivery method including the above steps.

2. The product delivery method according to claim 1, wherein the status information includes the position of the user in the queue.

3. The product delivery method according to claim 2, wherein the status information further includes the moving speed of the user in the queue.

4. The product delivery method according to claim 1, wherein the queue information includes the static configuration of the queue.

5. The product delivery method according to claim 4, wherein the queue information further includes the dynamic configuration of the queue.

6. The product delivery method according to claim 4, wherein the static configuration of the queue includes the arrangement of a regulating unit that regulates the queue.

7. The product delivery method according to claim 5, wherein the dynamic configuration of the queue includes the arrangement of a plurality of people included in the queue.

8. The queue further includes a second user, and the product delivery method further includes obtaining second status information regarding the status of the second user, identifying one or more second candidate locations where a product in the queue can be received based on the queue information and the second status information, creating a second delivery plan for delivering the product to the second received location in response to a second receiving request designating the second candidate location selected by the second user as the second receiving location among the one or more second candidate locations, and causing a moving body on which the product is mounted to travel according to the second delivery plan. The product delivery method according to claim 1.

9. In response to a second receiving request for designating, as a second receiving location, a second candidate location selected by the user from among the one or more candidate locations, creating a second delivery plan for delivering a second product to the second receiving location; and causing a moving body on which the second product is mounted to travel according to the second delivery plan. The product delivery method according to claim 1, further comprising the above.

10. In response to the receiving request, creating a second delivery plan for delivering a second product to the receiving location; and causing a second moving body on which the second product is mounted to travel according to the second delivery plan. The product delivery method according to claim 1, further comprising the above.

11. When the user fails to receive the product at the receiving location, reacquiring the queue information and the situation information respectively; identifying one or more re-candidate locations where the product in the queue can be received again based on the queue information and the situation information; in response to a re-receiving request for designating, as a re-receiving location, a re-candidate location selected by the user from among the one or more re-candidate locations, creating a re-delivery plan for re-delivering the product to the re-receiving location; and causing the moving body on which the product is mounted to travel according to the re-delivery plan. The product delivery method according to claim 1, further comprising the above.

12. Obtaining product information regarding products according to locations; identifying one or more candidate products that can be received at each of the one or more candidate locations based on the product information; and the creation of the delivery plan includes creating the delivery plan for moving the received product to the receiving location in response to the receiving request for designating, as the receiving location, a candidate location selected by the user from among the one or more candidate locations and designating, as the received product, a candidate product selected by the user from among the one or more candidate products. The product delivery method according to claim 1, further comprising the above.

13. A delivery planning method including: obtaining queue information regarding a queue including a user; obtaining situation information regarding the situation of the user; identifying one or more service-providing candidate locations where services can be provided in the queue based on the queue information and the situation information; determining a destination for a service vehicle among the one or more candidate locations; and moving the service vehicle to the determined destination.

14. A server comprising: a first obtaining unit that obtains queue information regarding a queue including a user; a second obtaining unit that obtains situation information regarding the situation of the user; a specifying unit that specifies one or more candidate locations where goods can be received in the queue based on the queue information and the situation information; a creating unit that creates a delivery plan for delivering goods to the receiving location in response to a receiving request that designates, as the receiving location, a candidate location selected by the user among the one or more candidate locations; and an instructing unit that instructs a moving body on which the goods are mounted to travel according to the delivery plan.

15. A mobile body comprising: a traveling mechanism; a communication interface connectable to a server; and a control unit capable of controlling the traveling mechanism and the communication interface, wherein when a traveling instruction to the receiving location according to a delivery plan created in response to a receiving request that designates, as the receiving location, a candidate location selected by the user among one or more candidate locations where goods can be received in the queue based on queue information regarding a queue including a user and situation information regarding the situation of the user is received by the communication interface, the control unit controls the traveling mechanism to travel to the receiving location.

16. A product delivery program that causes a management device to acquire queue information regarding a queue including a user, acquire status information regarding the status of the user, identify one or more candidate locations where a product in the queue can be received based on the queue information and the status information, create a delivery plan for delivering the product to the receiving location in response to a receiving request designating, as the receiving location, a candidate location selected by the user from among the one or more candidate locations, and cause a moving body on which the product is mounted to travel according to the delivery plan.

Images