Information processing device, program, and method

Abstract

To provide an information processor capable of improving the convenience in storage service of luggage that is loaded on a vehicle and deposited in a locker.SOLUTION: The information processor includes a control unit configured so as to, when a piece of luggage remains in a locker even after the first preset date and time pass, accept settings from a user terminal concerning the handling of a piece of luggage that is loaded on a vehicle and deposited in a locker. The control unit creates a driving plan of the vehicle concerning a package that remains in the locker even after the first date and time has passed according to the settings concerning the package handling.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, a program, and a method. [Background technology]

[0002] A locker management system has been disclosed that determines which locker a user will use based on the user's locker usage request, and dispatches an autonomous vehicle equipped with the determined locker to the user (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-96201 A Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present disclosure is to provide an information processing device, a program, and a method that can improve the convenience of luggage storage services in lockers installed in vehicles. [Means for solving the problem]

[0005] One aspect of the present disclosure is a control unit that executes accepting, from the user terminal, settings for handling of a baggage that has been deposited in a locker mounted on a vehicle and that remains deposited in the locker even after a first date and time that has been set in advance; The information processing device includes:

[0006] Another aspect of the present disclosure is On the computer, Transmitting to a predetermined device settings for handling luggage left in a locker mounted on a vehicle when the luggage remains left in the locker after a first date and time set in advance. This is a program for executing the above.

[0007] Another aspect of the present disclosure is The computer receiving, from a user terminal, a setting for handling a baggage that has been deposited in a locker mounted on a vehicle and that remains deposited in the locker after a first date and time that has been set in advance; Creating a driving plan for the vehicle according to the contents of the setting; The present invention relates to an information processing method. Effect of the Invention

[0008] According to the present disclosure, it is possible to improve the convenience of luggage storage services in lockers installed in vehicles. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a system configuration of a movable locker system according to the first embodiment. [Diagram 2] FIG. 2 is an example of a hardware configuration of a center server and a user terminal. [Diagram 3] FIG. 3 is a diagram illustrating an example of a functional configuration of the center server and the user terminal. [Figure 4] FIG. 4 is an example of information stored in the locker information database. [Diagram 5] FIG. 5 is an example of information held in the service information database. [Figure 6] FIG. 6 is an example of information stored in the handling setting information database. [Figure 7] FIG. 7 is an example of information held in the schedule information database. [Figure 8] FIG. 8 shows an example of a locker use request screen on a user terminal. [Figure 9] FIG. 9 shows an example of a setting screen for handling forgotten packages on a user terminal. [Figure 10] FIG. 10 is an example of a flowchart of a process performed when the center server receives a locker use request from a user terminal. [Figure 11] FIG. 11 is an example of a flowchart of a process performed by the center server when a handling setting request is received from a user terminal. [Figure 12] FIG. 12 is an example of a flowchart of a parcel removal management process in the service by the center server. [Figure 13] FIG. 13 is an example of a flowchart of a parcel removal management process in the service by the center server. [Figure 14] FIG. 14 is a flowchart of a process performed when a user operation of a user terminal is input. [Figure 15] FIG. 15 is a flowchart of a process performed when a user operation is input to a user terminal. [Figure 16] FIG. 16 is a diagram showing an example of a processing sequence in the movable locker system. [Figure 17] FIG. 17 is a diagram showing an example of a processing sequence in the movable locker system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] There is a system that provides a temporary luggage storage service in which a vehicle carrying lockers moves around, allowing users to deposit and retrieve luggage at a location designated by the user. A locker that can be moved by being loaded onto a vehicle is hereinafter referred to as a mobile locker. A temporary luggage storage service using a mobile locker is hereinafter referred to as a mobile locker service.

[0011] When using the mobile locker service, the user specifies, for example, the location and date and time to deposit the luggage, and the location and date and time to retrieve the luggage. However, for example, the user may change or forget their plans, and may not be able to retrieve the luggage from the mobile locker at the specified location and date and time.

[0012] In one aspect of the present disclosure, the user can set how to handle luggage when the luggage cannot be retrieved from the mobile locker at the date and time specified by the user. Specifically, one aspect of the present disclosure is an information processing device including a control unit. The control unit executes accepting, from a user terminal, settings for handling luggage deposited in a locker loaded on a vehicle when the luggage remains deposited in the locker even after a first date and time set in advance.

[0013] The information processing device is, for example, a computer such as a server. The control unit is, for example, a processor such as a CPU (Central Processing Unit) provided in the computer. The terminals include, for example, smartphones, tablet terminals, and PCs (Personal Computers). The vehicle may be either a vehicle that is driven by a driver or an autonomous vehicle that can run without being driven by a driver. A locker mounted on a vehicle corresponds to a mobile locker.

[0014] If luggage left in a locker on board a vehicle is not retrieved by the first date and time, In this case, the handling of the package may be, for example, as follows: (1) Re-specify the second location and the second date and time for picking up the package. (2) Retrieve the package from the mobile locker and have it delivered to the second location. (3) Dispose of the package. In the case of delivery (2), the user may receive the package directly at the second location or may leave the package at the second location. The second location and the second date and time are specified by the user.

[0015] According to one aspect of the present disclosure, a user can set how to handle luggage that is left in a mobile locker when the user is unable to retrieve the luggage from the mobile locker at a predetermined date and time. This allows the user to retrieve, receive, or have the luggage disposed of at the user's convenience, even if the user forgets to retrieve the luggage from the mobile locker at the predetermined date and time. This improves the convenience of the mobile locker service.

[0016] When the second location and the second date and time for picking up the luggage in (1) are specified again, the control unit of the information processing device may transmit a message to the user terminal proposing picking up the luggage at a third location and a third date and time. The third location and the third date and time are candidates for the luggage pick-up location and pick-up date and time that reduce the cost related to the vehicle or the cost related to the user. The cost related to the vehicle is, for example, the energy source (electricity, gasoline, etc.) of the vehicle consumed when the mileage increases by driving the vehicle to arrive at the second location at the second date and time. The third location may be different from the second location, and the third date and time may also be different from the second date and time. Alternatively, the third location may be different from the second location, and the third date and time may be the same as the second date and time. Alternatively, the third location may be the same as the second location, and the third date and time may be different from the second date and time.

[0017] In the mobile locker service, a fee for using the mobile locker is charged to the user based on at least one of the length of time the luggage is kept and the relationship between the location where the luggage is left and the location where the luggage is picked up, etc. In addition, an additional fee may be charged depending on the settings for handling the luggage if the luggage cannot be picked up at the first date and time.

[0018] The cost related to the user is, for example, the usage fee of the mobile locker. A vehicle carrying a mobile locker does not stop at a fixed location. Therefore, for example, the vehicle is not necessarily traveling near the second location specified by the user at the second date and time specified by the user. In such a case, for example, the control unit may suggest to the user that the user pick up the luggage at the second location at the third date and time if the vehicle is scheduled to travel near the second location near the third date and time. For example, if the user agrees to pick up the luggage at the location and date and time proposed by the control unit, an additional fee may not be charged to the user.

[0019] The control unit may determine the additional charge according to the relationship between a first location, which is a location where the package is to be picked up and is specified together with the first date and time, and a second location, which is specified in the settings for handling the package in the case where the package is not picked up by the first date and time. For example, the control unit may not impose an additional charge due to an increase in travel distance if the first location and the second location are within a predetermined distance.

[0020] In one aspect of the present disclosure, the user can be charged according to the settings for handling the luggage when the luggage is not picked up by the first date and time, so that the increase in the cost of moving the vehicle can be compensated for. Also, the location or date and time for picking up the luggage can be suggested so that the additional fee does not increase, so that the user can also reduce costs.

[0021] In one aspect of the present disclosure, if the baggage remains in the locker after the first date and time, the control unit may transmit an inquiry about baggage handling settings to the user terminal and accept baggage handling settings from the user terminal. The unit may receive from the user terminal a request to use the locker as well as a setting for handling the luggage if the luggage is not picked up by the first date and time. According to one aspect of the present disclosure, the user can set the handling of the luggage if the luggage is not picked up by the first date and time at any time of his / her choice.

[0022] Another aspect of the present disclosure can be specified as a program or a non-transitory computer-readable recording medium having the program recorded thereon. The program causes a computer to transmit to a predetermined device settings for handling luggage left in a locker mounted on a vehicle when the luggage remains in the locker after a first preset date and time. The computer is, for example, a computer that operates as a user terminal.

[0023] In addition, as another aspect, the present disclosure can be specified as an information processing method executed by a computer. The information processing method includes receiving, from a user terminal, a setting for handling luggage left in a locker mounted on a vehicle when the luggage remains in the locker after a first date and time set in advance. The information processing method also includes creating a driving plan for the vehicle according to the content of the setting. The computer operates as the above-mentioned information processing device.

[0024] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The configurations of the following embodiments are merely examples, and the present disclosure is not limited to the configurations of the embodiments.

[0025] First Embodiment FIG. 1 is a diagram showing an example of the system configuration of a mobile locker system 100 according to the first embodiment. The mobile locker system 100 is a system that provides mobile coin lockers by loading coin lockers onto a vehicle and traveling. A user can deposit luggage in a locker at a designated location, have the luggage stored for a specified period of time, and retrieve the luggage from the locker at the designated location. The location where the luggage is deposited and the location where the luggage is retrieved may be different. A usage fee is charged to the user according to, for example, the length of time the luggage is deposited and the distance between the location where the luggage is deposited and the location where the luggage is retrieved.

[0026] The mobile locker system 100 includes a center server 1, lockers 4, a vehicle 3 that carries the lockers 4, and a user terminal 2 of a user who uses the service. Note that the mobile locker system 100 includes multiple lockers 4, vehicles 3, and user terminals 2, but for the sake of convenience, only one of each is shown in FIG.

[0027] The locker 4 has a plurality of storage compartments in one housing. Each storage compartment in the locker 4 can be locked and unlocked. In the first embodiment, each storage compartment in the locker 4 employs an electronic lock. For example, the electronic lock employed in the locker 4 may be locked by operating an input device such as a numeric keypad equipped in each storage compartment, and unlocked by inputting a PIN into the input device. Alternatively, the electronic lock employed in the locker 4 may be equipped with a receiver for a predetermined wireless signal, and may transmit a locking or unlocking signal together with authentication information from the user terminal 2, and lock or unlock when the authentication information held by the receiver matches the received authentication information. However, the lock employed in the locker 4 is not limited to an electronic lock, and may be locked or unlocked by a physical key. Hereinafter, the user's luggage is deposited in one of the storage compartments of the locker 4, but even when referring to one of the storage compartments of the locker 4, it may be simply written as "locker 4".

[0028] In the mobile locker service, it is assumed that the user who deposits the luggage in the locker 4 and the user who retrieves the luggage from the locker 4 are the same person. A user who has deposited luggage in locker 4 can also hand over the authentication information or physical key of locker 4 to another user and request that the luggage be retrieved.

[0029] In the first embodiment, the vehicle 3 is an autonomous vehicle. However, the vehicle 3 may have a staff member on board to assist in depositing or retrieving the luggage, or to retrieve the luggage from the locker 4 and transport it from the vehicle 3 to the designated location. The luggage retrieved from the locker 4 may be transported from the vehicle 3 to the designated location by a drone or a small transport robot, for example, without being limited to a person. The vehicle 3 may be a vehicle driven by a driver. When the vehicle 3 is a vehicle driven by a driver, the staff member who supports the user or transports the luggage from the vehicle 3 to the designated location may be the same person as the driver. In the first embodiment, the vehicle 3 is assumed to be traveling in each assigned area. In addition, the vehicle 3 may be driven by an on-demand system in which the vehicle 3 is driven in response to the occurrence of a request for service use, or may be patrolling a predetermined route. In the first embodiment, the vehicle 3 is assumed to be driven by an on-demand system.

[0030] The user terminal 2 is a terminal used by a user who uses the services of the mobile locker system 100. The user terminal 2 is, for example, a smartphone, a tablet terminal, or a PC (Personal Computer). The application programs for using the service are installed.

[0031] The user terminal 2 and the vehicle 3 are connected to a network N1 and communicate with the center server 1 through the network N1. The network N1 is, for example, a public network such as the Internet. The vehicle 3 is, for example, equipped with a device having a communication function, and can connect to the network N1 and communicate with the center server 1 by using the device.

[0032] The center server 1 is a server that manages the mobile locker system 100. When a user uses the services of the mobile locker system 100, the user transmits a locker use request to the center server 1 through an application program on the user terminal 2. Together with the locker use request, information specified by the user on the location and date and time to deposit the luggage, and the location and date and time to pick up the luggage, is also transmitted to the center server 1. The date and time to pick up the luggage is an example of a "first date and time."

[0033] When the center server 1 receives a locker use request from the user terminal 2, it determines the vehicle 3 to be driven to the specified location at the specified date and time, and the storage section of the lockers 4 loaded on the vehicle 3 to store the luggage. In the first embodiment, since an electronic lock is adopted for the locker 4, the center server 1 notifies the user terminal 2 of the authentication information of the locker 4. Thereafter, the user meets the vehicle 3 at the specified location, gets into the vehicle 3, stores the luggage in the locker 4, and locks the locker 4 using the authentication information received from the center server 1. When retrieving the luggage, the user meets the vehicle 3 at a previously specified location, gets into the vehicle 3, unlocks the mobile locker 4 using the authentication information received from the center server 1, and retrieves the luggage from the locker 4.

[0034] Although a user specifies in advance the location and date and time for picking up the luggage, there are cases where the user forgets or an unforeseen event occurs and the luggage cannot be picked up at the specified date and time. In the first embodiment, the center server 1 accepts settings from the user regarding how to handle the luggage if the user does not allow the luggage to be picked up by the specified date and time. For example, the handling of the luggage if the luggage is not picked up by the specified date and time includes the following: (1) The location and date and time for picking up the luggage are specified again, and the luggage is left in the locker 4 until then. (2) The luggage is delivered to the specified location. (3) The luggage is discarded. Hereinafter, the state in which luggage remains in the locker 4 after the specified date and time has passed is referred to as "forgotten to pick up." Also, hereinafter, the specified date and time may be used to handle the luggage. Handling of luggage that remains in locker 4 after the date and time has passed is referred to as "handling of forgotten luggage." Depending on the settings for handling forgotten luggage, an additional fee will be added to the usage fee. (1) The location and date and time for re-specifying the luggage to be picked up are examples of a "second location" and a "second date and time," respectively.

[0035] The timing for setting the handling of forgotten baggage may be any timing of the user's choice. For example, the setting for the handling of forgotten baggage may be set together with the request to use the locker, or when baggage is forgotten to be picked up, the center server 1 may inquire of the user terminal 2 about the handling of the forgotten baggage.

[0036] According to the first embodiment, the center server 1 accepts settings for handling luggage left in a mobile locker when the luggage is forgotten to be picked up, and when the luggage is actually forgotten to be picked up, the center server 1 drives the vehicle 3 according to the settings for handling the forgotten luggage. This allows a user who uses the mobile locker service to pick up or receive the luggage at a convenient time or in a convenient manner, even if the user is unable to pick up the luggage by the specified date and time, thereby improving the convenience of the mobile locker service.

[0037] 2 is an example of the hardware configuration of the center server 1 and the user terminal 2. The center server 1 is, for example, a computer dedicated to the server or a general-purpose computer. The center server 1 includes, as its hardware configuration, a CPU 101, a memory 102, an external storage device 103, and a communication unit 104. The memory 102 and the external storage device 103 are computer-readable recording media. The center server 1 is an example of an "information processing device."

[0038] The external storage device 103 stores various programs and data used by the CPU 101 when executing each program. The external storage device 103 is, for example, an erasable programmable ROM (EPROM) or a hard disk drive. The programs held in the external storage device 103 include, for example, an operating system (OS), a control program for the mobile locker system 100, and various other application programs.

[0039] The memory 102 is a storage device that provides the CPU 101 with a storage area for loading a program stored in the external storage device 103 and a working area, and is used as a buffer. The memory 102 may be, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), or the like. This includes semiconductor memories such as IEEE 802.11b / g and IEEE 802.11b / g.

[0040] The CPU 101 executes various processes by loading the OS and various other application programs stored in the external storage device 103 into the memory 102 and executing them. The number of CPUs 101 is not limited to one, and multiple CPUs 101 may be provided. The CPU 101 is an example of a "control unit."

[0041] The communication unit 104 is, for example, a network interface card (NIC). The communication unit 104 is connected to an access network such as a local area network (LAN) by wire, and is connected to the network N1 through the access network. However, the communication unit 104 is not limited to a circuit that connects to a network by wire, and may be, for example, a wireless communication circuit that complies with a wireless communication method such as WiFi or a mobile communication method.

[0042] Next, the user terminal 2 is, for example, a smartphone, a tablet terminal, a wearable terminal, a PC, etc. The user terminal 2 has, as its hardware configuration, a CPU 201, a memory 202, an external storage device 203, a wireless communication unit 204, and a touch panel display. 2. However, in FIG. 2, the hardware components that perform the processing according to the first embodiment are extracted and illustrated as the hardware configuration of the user terminal 2, and the hardware components included in the user terminal 2 are not limited to the elements illustrated in FIG.

[0043] The CPU 201, memory 202, and external storage device 203 are similar to the CPU 101, memory 102, and external storage device 103, respectively. However, the storage device (storage) employed as the external storage device 203 is, for example, a flash memory. The external storage device 203 may also include a portable recording medium such as an SD card. In addition to an OS and the like, the external storage device 203 also stores application programs for utilizing the services of the mobile locker system 100.

[0044] The wireless communication unit 204 is a wireless communication unit that supports mobile communication methods such as 5G (5th Generation), 6G, 4G, and LTE (Long Term Evolution), WiMAX, and WiFi. The wireless communication unit 204 is a wireless communication circuit conforming to the standard. The wireless communication unit 204 connects to the network N1 via wireless communication, enabling communication with the center server 1.

[0045] The touch panel display 205 outputs images in accordance with instructions from the CPU 201 , and outputs signals input by the user to the CPU 201 .

[0046] 2 is an example, and the hardware configuration of the center server 1 and the user terminal 2 is not limited to that shown in FIG. 2. For example, the user terminal 2 may include a microphone, a speaker, a camera, and a position information device such as a global positioning system (GPS) in addition to the hardware components shown in FIG. Sensors and the like are also included in the hardware configuration.

[0047] 3 is a diagram showing an example of the functional configuration of the center server 1 and the user terminal 2. The center server 1 includes, as its functional configuration, a control unit 11, a schedule adjustment unit 16, a locker information DB 12, a schedule information DB 13, a reservation information DB 14, and a handling setting information DB 15. These functional components are achieved by, for example, the CPU 101 of the center server 1 executing a control program for the mobile locker system 100.

[0048] The control unit 11 manages the usage status of the lockers 4 and controls the traveling of the vehicle 3. Specifically, the control unit 11 receives, for example, a locker use request, a request to set up the handling of forgotten baggage, a deposit completion notification, and a retrieval completion notification from the user terminal 2. A locker use request is a request to use a mobile locker. A request to set up the handling of forgotten baggage is a request to set up the handling of baggage that remains deposited in the locker 4 even after the specified date and time. A deposit completion notification is a notification that the deposit of the baggage in the locker 4 has been completed. A retrieval completion notification is a notification that the baggage deposited in the locker 4 has been retrieved from the mobile locker 4.

[0049] When the control unit 11 receives a locker use request from the user terminal 2, it assigns a vehicle 3 and a mobile locker 4. Along with the locker use request, the user terminal 2 also transmits to the center server 1 the location and date and time for depositing the luggage, the location and date and time for picking up the luggage, and the user's identification information. Hereinafter, the location and date for depositing the luggage may be referred to as the deposit location and deposit date and time, respectively. Also, below, the location and date for picking up the luggage may be referred to as the pick-up location and pick-up date and time.

[0050] The control unit 11, for example, determines the vehicle 3 and the locker 4 to be assigned to the locker use request by referring to the schedule information DB 13 described later. For example, the vehicle 3 to be assigned to the locker use request is a vehicle that runs near the deposit location on the deposit date and time, and A vehicle 3 is a vehicle carrying a locker 4 having a storage section that is free of any scheduled items from the deposit date and time until at least the removal date and time. The locker 4 to be assigned in response to a locker use request is any of the storage sections of the lockers 4 loaded on the vehicle 3 that is free of any scheduled items from the deposit date and time until at least the removal date and time. The method of determining the vehicle 3 and locker 4 to be assigned may be any well-known method, and is not limited to a specific method.

[0051] The vehicle 3 and locker 4 in which the luggage is to be deposited may be specified by the user from, for example, the position information of the vehicle 3 on a map. In this case, the identification information of the vehicle 3 specified by the user is received from the user terminal 2 together with the locker use request. The control unit 11 also assigns, to the received locker use request, one of the storage units of the locker 4 loaded in the specified vehicle 3 that has no scheduled use from the deposit date and time to the removal date and time.

[0052] Thereafter, the control unit 11 creates a schedule for the assigned vehicle 3 and locker 4 for the service of the received locker use request, and registers the created schedule in a schedule information DB 13 described below. In addition, the control unit 11 creates a driving plan for the vehicle 3 according to the schedule created for the assigned vehicle 3, so that the vehicle 3 arrives at a deposit location designated by the user at a deposit date and time designated by the user, and arrives at a pick-up location designated by the user at a pick-up date and time designated by the user. The created driving plan is transmitted to the vehicle 3. The driving plan includes, for example, a driving destination and arrival date and time, and route information to the destination.

[0053] The control unit 11 transmits to the user terminal 2 a response of acceptance to the locker use request, information about the assigned locker 4, the deposit location, and the deposit date and time. The information about the locker 4 includes, for example, identification information about the vehicle 3 and identification information about the storage unit of the locker 4. In the first embodiment, it is assumed that the locker 4 employs an electronic lock, so the information about the locker 4 also includes authentication information about the storage unit assigned to the user terminal 2. However, this is not limited to this, and since the storage unit assigned to the locker use request may be changed in relation to other locker use requests, the information about the locker 4 may be transmitted to the user terminal 2 separately from the response of acceptance to the locker use request. For example, when a predetermined time has passed since the deposit date and time, the information about the assigned locker 4 may be transmitted to the user terminal 2.

[0054] When the control unit 11 receives a setting request for handling of forgotten baggage from the user terminal 2, it determines whether the schedule between the locker 4 and the vehicle 3 can be secured based on the content of the setting request for handling of forgotten baggage. The setting request for handling of forgotten baggage may be received, for example, together with a request to use a locker, or may be received separately. In other words, the setting for handling of forgotten baggage may be made before the baggage is deposited in the locker 4, or may be made after the baggage is deposited in the locker 4, and the timing is arbitrary depending on the user.

[0055] Along with the setting request for handling forgotten parcels, information indicating, for example, the service identification information, the user identification information, and the setting contents for handling forgotten parcels designated by the user is also received from the user terminal 2. In the first embodiment, the types of handling forgotten parcels include (1) re-specifying the location and date and time for retrieving the parcel and leaving the parcel until then, (2) delivering the parcel to the designated location, and (3) discarding it. In addition, for delivering the parcel to the designated location in (2), there are two methods of handing over the parcel: (2-1) handing it over directly to the user, and (2-2) leaving the parcel at the designated location. The information indicating the type of handling forgotten parcels is, for example, a code, flag, or keyword indicating any of the above (1), (2-1), (2-2), and (3). Hereinafter, the setting request for handling forgotten parcels will be simply referred to as a handling setting request. Hereinafter, the above (1) ), (2-1), (2-2), and (3) will be written as (1) re-designation, (2-1) delivery, (2-2) leaving at door, and (3) disposal, respectively.

[0056] When the type of handling of the forgotten baggage designated by the user is (1) re-designation, information on the re-designated pick-up location and pick-up date and time is received together with the handling setting request from the user terminal 2. In this case, the control unit 11 refers to the schedule information DB 13 and determines whether the vehicle 3 carrying the locker 4 for storing the target baggage can arrive at the re-designated pick-up location by the pick-up date and time.

[0057] For example, assume that location #A is re-designated as the pick-up location and date and time #T1 is re-designated as the pick-up date and time. For example, if a schedule is set for vehicle 3 to travel to a location away from location #A at date and time #T1, control unit 11 determines that vehicle 3 cannot arrive at the re-designated pick-up location by the pick-up date and time. For example, if no schedule is set for vehicle 3 at date and time #T1 and a schedule is set for vehicle 3 to travel to a location that can reach location #A by date and time #T1, it is determined that vehicle 3 can arrive at the re-designated pick-up location by the pick-up date and time. Note that the method of determining whether vehicle 3 can arrive at the re-designated pick-up location by the pick-up date and time is not limited to a specific method.

[0058] When it is determined that the vehicle 3 cannot arrive at the re-designated pick-up location by the pick-up date and time, the control unit 11, for example, refers to the schedule information DB 13 to acquire a date and time at which the vehicle 3 can arrive at the re-designated pick-up location around the re-designated pick-up date and time. Alternatively, the control unit 11, for example, refers to the schedule information DB 13 to acquire a location around the re-designated pick-up location at which the vehicle 3 can arrive by the re-designated pick-up date and time. Alternatively, the control unit 11, for example, refers to the schedule information DB 13 to acquire a date and time and a location around the re-designated pick-up location around the re-designated pick-up date and time at which the vehicle 3 can arrive. The control unit 11 creates a proposal message proposing pick-up of the luggage at the acquired location, date and time, or the location and date and time, and transmits the proposal message to the user terminal 2.

[0059] Even if it is determined that vehicle 3 can arrive at the re-designated pick-up location by the pick-up date and time, there may be a better pick-up location or pick-up date and time due to the vehicle 3's driving route, etc. A better pick-up location or pick-up date and time is, for example, a pick-up location or pick-up date and time that can suppress an increase in the travel distance of vehicle 3 overall. If the travel distance of vehicle 3 does not increase by more than a predetermined value, (1) it may be possible to not impose an additional fee due to re-designation. In this case, a better pick-up location or pick-up date and time is a pick-up location or pick-up date and time for which no additional fee is incurred, which is beneficial for the user.

[0060] Therefore, even if it is determined that the vehicle 3 can arrive at the re-designated take-out location by the take-out date and time, the control unit 11 determines whether or not there is at least one of a take-out location or take-out date and time that is better than the re-designated take-out location and take-out date and time for the target vehicle 3. The determination is performed by referring to the schedule information DB 13. For example, when there is another locker use request in the schedule of the vehicle 3, in which the deposit location or take-out location is located near the re-designated take-out location, the control unit 11 acquires a date and time at which the re-designated take-out location can be passed near the deposit date and time or take-out date and time of the other locker use request. Alternatively, when there is another locker use request in the schedule of the vehicle 3, in which the deposit date and time or take-out date and time is located near the re-designated take-out date and time, the control unit 11 acquires a location and date and time at which the vehicle 3 can pass near the deposit location or take-out location of the other locker use request on the re-designated take-out date and time. Alternatively, the control unit 11 acquires, for example, a location and date and time at which the vehicle 3 can travel more efficiently than the re-designated take-out location and take-out date and time, in view of the schedule of the vehicle 3.

[0061] The location or date and time acquired may be different from the location or date and time re-specified by the user. It should be noted that the method of acquiring a better pick-up location or pick-up date and time than the re-specified pick-up location and pick-up date and time is not limited to a specific method. The control unit 11 creates a proposal message proposing pick-up of the package at the acquired location, date and time, or location and date and time, and transmits it to the user terminal 2. The pick-up location and pick-up date and time proposed by the proposal message are examples of the "third location" and "third date and time", respectively.

[0062] The control unit 11 receives a response indicating agreement or a response indicating refusal from the user terminal 2 in response to the proposal message. When the control unit 11 receives a response indicating agreement from the user terminal 2, the control unit 11 stores the retrieval of the package at the proposed location and / or date and time as the setting for handling the package left by the user in the handling setting information DB 15 described later. When the control unit 11 receives a response indicating refusal from the user terminal 2, the control unit 11 stores the retrieval of the package at the retrieval location and retrieval date and time received together with the handling setting request as the setting for handling the package left by the user in the handling setting information DB 15 described later. Alternatively, when the control unit 11 receives a response indicating refusal from the user terminal 2, the control unit 11 may create a proposal message proposing retrieval of the package at another location and date and time again, transmit it to the user terminal 2, and repeat this process until a response indicating agreement is obtained.

[0063] Next, if the setting for handling the forgotten parcel designated by the user is (2-1) pick-up or (2-2) drop-off, delivery destination information is also received from the user terminal 2 along with the handling setting request. If a delivery time slot is designated, information indicating the designated delivery time slot is also received. The control unit 11 registers the handling of the received forgotten parcel, for example (2-1) pick-up or (2-2) drop-off, and the delivery destination, in the handling setting information DB 15 described below.

[0064] If the setting for handling forgotten packages specified by the user is (3) Discard, the control unit 11 registers, for example, (3) Discard in the handling setting information DB 15 described below, the handling of the received forgotten packages.

[0065] The control unit 11 notifies the schedule adjustment unit 16 of the determined settings for handling forgotten baggage. The schedule adjustment unit 16 changes the schedule for the vehicle 3 and locker 4 for the target service according to the notified contents, and updates the schedule information DB 13. The settings for handling forgotten baggage may extend the usage period of the storage unit of the locker 4, which may conflict with the usage period of another service assigned to the storage unit. In such a case, the schedule adjustment unit 16 adjusts the schedule by changing the storage unit assigned to the other service, etc. The control unit 11 updates the driving plan of one or more vehicles 3 corresponding to the updated schedule according to the updated schedule, and transmits it to the relevant vehicles 3.

[0066] When the control unit 11 receives a deposit completion notification or a withdrawal completion notification from the user terminal 2, the control unit 11 may record it as an event history, for example, in a predetermined storage area of ​​the external storage device 103. Along with the deposit completion notification or the withdrawal completion notification, for example, service identification information and user identification information are also received. Furthermore, when the control unit 11 receives a withdrawal completion notification from the user terminal 2, the control unit 11 records it in the service information DB 14 described below.

[0067] The control unit 11 detects that a package has been left behind when the package pickup date and time has passed and a pickup completion notification has not been received from the user terminal 2. When a package has been left behind and a setting for handling the package has been set for the package, the control unit 11 inquires of the user terminal 2 as to whether or not the setting for handling the package has been implemented. Together with the inquiry, information indicating the setting for handling the package has also been sent to the user terminal 2.

[0068] When a response to the inquiry about whether or not the execution is permitted is received from the user terminal 2, the control unit 11 does not perform any particular process since a driving plan according to the settings for handling left-behind baggage has already been set in the vehicle 3. When a response to the inquiry about whether or not the execution is permitted is received from the user terminal 2, the control unit 11 sends a setting inquiry to the user terminal 2 inquiring about the settings for handling left-behind baggage. A handling setting request is received from the user terminal 2 as a response to the setting inquiry for handling left-behind baggage.

[0069] Furthermore, when a forgotten package is detected and handling settings for the forgotten package have not been made for the package, the control unit 11 transmits a setting inquiry to the user terminal 2 to inquire about settings for handling the forgotten package. A handling setting request is received from the user terminal 2 as a response to the setting inquiry for handling the forgotten package.

[0070] The schedule adjustment unit 16 adjusts the schedule of the specified vehicle 3 and locker 4 among the multiple services assigned to the vehicle 3 and locker 4 according to instructions from the control unit 11. Specifically, when the occupancy period of the assigned storage unit by the service is extended and may conflict with the occupancy period of other services assigned to the storage unit, the schedule adjustment unit 16 adjusts the schedule. The extension of the occupancy period of the storage unit by the service occurs, for example, when a new setting for handling forgotten baggage is made or when baggage is forgotten to be taken out. In the schedule adjustment, for example, the storage unit assigned to the other service is changed. Note that the method of adjusting the schedule is not limited to a specific method. The schedule adjustment unit 16 notifies the control unit 11 of the change in the schedule. In response to the changed schedule, the control unit 11 changes, for example, the driving plan of the vehicle 3 assigned to the corresponding service, or notifies the user terminal 2 of the change in the storage unit assigned to the corresponding service.

[0071] The locker information DB 12, schedule information DB 13, service information DB 14, and handling setting information DB 15 are created, for example, in a memory area of ​​the external storage device 103 of the center server 1. The locker information DB 12 holds information about the lockers 4. The schedule information DB 13 holds schedules for the lockers 4. The service information DB 14 holds service information for the use of mobile lockers. The service information is information about the mobile locker service provided in response to a request to use one locker. The handling setting information DB 15 holds information about the handling settings for luggage that is left behind. Details of the information held in the locker information DB 12, schedule information DB 13, service information DB 14, and handling setting information DB 15 will be described later.

[0072] The user terminal 2 includes a control unit 21 as a functional configuration. The processing of the control unit 21 is achieved by the CPU 202 of the user terminal 2 executing the application program of the mobile locker system 100 held in the external storage device 203. The control unit 21 transmits, to the center server 1, for example, a locker use request, a handling setting request, a deposit completion notification, a removal completion notification, and responses to various inquiries from the center server 1 in response to an input from the user to the touch panel display 205. The control unit 21 also receives, from the center server 1, for example, responses to the locker use request and the handling setting request, and information associated therewith. The control unit 21 also transitions the screen in response to a user operation, and outputs a message received from the center server 1 to the touch panel display 205. Note that the functional configuration of the center server 1 and the user terminal 2 is merely an example, and is not limited to that shown in FIG. 3.

[0073] FIG. 4 is an example of information stored in the locker information DB 12. The locker information DB 12 stores information about the lockers 4. The information in the locker information DB 12 shown in FIG. One record indicates information about one storage section of the locker 4. One record of the locker information DB 12 shown in Fig. 4 includes fields for a locker ID, a vehicle ID, and authentication information.

[0074] The locker ID field stores identification information for a storage section of the locker 4. For example, the identification information for a storage section of a locker 4 is a string of a predetermined number of alphanumeric characters, and is composed of an upper part that indicates the locker 4 and a lower part that indicates the storage section. Between multiple storage sections included in the same locker 4, the upper part of the identification information that indicates the locker 4 has the same value.

[0075] The vehicle ID field stores identification information of the vehicle 3 on which the locker 4 including the storage unit is loaded. The authentication information field stores authentication information of the electronic lock provided in the storage unit. The authentication information of the storage unit may be fixed or variable. Note that the information stored in the locker information DB 12 shown in FIG. 4 is an example, and the information stored in the locker information DB 12 is not limited to that shown in FIG. 4.

[0076] Fig. 5 is an example of information stored in the service information DB 14. The service information DB 14 stores service information. One record in the service information DB 14 shown in Fig. 5 is service information for a service provided in response to one locker use request. One record in the service information DB 14 shown in Fig. 5 includes fields for a service ID, a user ID, a locker ID, a deposit date and time, a deposit location, a removal date and time, a removal location, whether or not handling settings are set, and a removal completion notification.

[0077] The service ID field stores the identification information of the service. The service identification information is assigned by the control unit 11 when the provision of the service is established for the received locker use request. The user ID field stores the identification information of the user. The user identification information is assigned by the control unit 11 when registering the user in the mobile locker system 100. User registration in the mobile locker system 100 is performed through a client application of the mobile locker system 100. The locker ID field stores the identification information of the storage section of the locker 4 assigned to the service.

[0078] The fields of deposit date and time, deposit location, take-out date and time, and take-out location store information indicating the deposit date and time, deposit location, take-out date and time, and take-out location, respectively. Information indicating the deposit location and take-out location is, for example, an address, latitude and longitude, and a landmark name. The deposit date and time and take-out date and time are indicated, for example, by year, month, day, hour, and minute.

[0079] The handling setting availability field stores information indicating whether or not there is a setting for handling left-behind parcels for the corresponding service. The information indicating whether or not there is a setting for handling left-behind parcels is, for example, a flag, a keyword, or a code. In the example shown in FIG. 5, "yes" and "no" are used to indicate whether or not there is a setting for handling left-behind parcels.

[0080] The field of the removal completion notification stores information indicating whether or not a removal completion notification has been received, which indicates that the luggage has been removed from the locker 4 assigned to the corresponding service. The information indicating whether or not a removal completion notification has been received is, for example, a flag, a code, or a keyword.

[0081] The control unit 11 receives a locker use request from the user terminal 2, and when the provision of the service is established, adds a record to the service information DB 14. When the record is added, the control unit 11 assigns identification information to the established service and adds an ID to the service ID field. The control unit 11 stores the user's identification information, deposit date and time, deposit location, removal date and time, and removal location, which are received from the user terminal 2 together with the locker use request, in the fields of user ID, deposit date and time, deposit location, removal date and time, and removal location, respectively.

[0082] The initial value of the handling setting presence / absence field is information indicating that there is no setting for handling left-behind parcels. The handling setting presence / absence field is updated by the control unit 11 to information indicating that there is a setting when a handling setting request is received from the user terminal 2 and the setting for handling left-behind parcels is established.

[0083] The initial value of the extraction completion notification field is information indicating that the extraction completion notification has not been received. When the extraction completion notification is received from the user terminal 2, the extraction completion notification field is updated by the control unit 11 to information indicating that the extraction completion notification has been received. Note that the information held in the service information DB 14 is not limited to the information shown in FIG.

[0084] FIG. 6 is an example of information stored in the handling setting information DB 15. The handling setting information DB 15 stores setting information for handling left-behind baggage. One record in the handling setting information DB 15 shown in FIG. 6 is setting information for handling left-behind baggage as a service provided for one locker use request. A record in the handling setting information DB 15 is created by the control unit 11 when a handling setting request is received from the user terminal 2 and the settings for handling left-behind baggage are confirmed. One record in the handling setting information DB 15 shown in FIG. 6 includes fields for service ID, user ID, handling, designated date and time, designated location, and additional fee.

[0085] The service ID field stores identification information of the service. The value of the service ID field is used to link with a record in the service information DB 14. The user ID field stores identification information of the user. The handling field stores information indicating the type of handling of the forgotten package specified by the user. The types of handling of the forgotten package include (1) re-designation, (2-1) delivery, (2-2) drop-off, and (3) disposal. The information indicating the type of handling of the forgotten package may be, for example, a flag, a code, or a keyword.

[0086] The designated date and time and designated location fields store information indicating the date and time and location at which the handling of the forgotten package is performed, as specified by the user. For example, when the handling of the forgotten package specified by the user is (1) re-designation, the designated date and time and designated location fields store information indicating the date and time of pick-up and the location at which the package is picked up, as specified by the user. For example, when the handling of the forgotten package specified by the user is (2-1) delivery and (2-2) drop-off, the designated location field stores information indicating the delivery destination specified by the user. In addition, when (2-1) delivery or (2-2) drop-off is specified and a desired delivery time zone is specified, the designated date and time field stores information indicating the desired delivery time zone. For example, when the handling of the forgotten package specified by the user is (3) disposal, the designated date and time and designated location fields are blank or null.

[0087] The additional fee field stores the amount of the additional fee according to the type of handling of the forgotten package. The additional fee may be set to a flat rate depending on the type of handling of the forgotten package, or may be set according to the location indicated in the designated location field. For example, in the cases of (1) re-designation, (2-1) delivery, and (2-2) drop-off, the additional fee is set based on the pickup location received together with the locker use request and the location indicated in the designated location field. The additional fee may be higher as the value of the specified location field increases. For example, in the case of (1) re-designation, (2-1) delivery, and (2-2) drop-off, a flat amount may be added when the distance between the pick-up location received together with the locker use request and the location indicated by the value of the specified location field is greater than a predetermined distance. For example, in the case of (1) re-designation, when the pick-up date and time and pick-up location proposed by the control unit 11 are adopted by the user, the additional fee may be lower than usual or may not be charged. When the additional fee is variable, for example, it is determined by the control unit 11 when the handling setting of the forgotten package is confirmed. Note that the information held in the handling setting information DB 15 is not limited to the information shown in FIG. 6.

[0088] Fig. 7 is an example of information held in the schedule information DB 13. The schedule information DB 13 stores schedules for each locker 4 and vehicle 3. The example shown in Fig. 7 shows a schedule for one vehicle 3 and each storage section of the lockers 4 loaded on the vehicle 3 during business hours on a certain day.

[0089] In the example shown in FIG. 7, the storage unit with locker ID:001 is assigned to the service with service ID:001, and is reserved from 8:15 to 17:00. For the service with service ID:001, the deposit date and time is set to 8:15, and the retrieval date and time is set to 14:00. The reservation from 14:00 to 17:00 is for handling baggage that was left behind. For example, for the service with service ID:001, (1) re-designation is set as the handling of baggage that was left behind, and (1) the re-designated retrieval date and time is set to 17:00.

[0090] 7, the schedule of vehicle 3 is set according to the reservations of each storage unit. Item #100, item #101, item #200, item #201, item #300, and item #301 are set as schedule items of vehicle 3 corresponding to the service of service ID:001 assigned to the storage unit of locker ID:001.

[0091] Item #100 and item #101 are schedule items corresponding to the deposit of luggage for the service of service ID:001. Item #100 is an item for a driving event of vehicle 3. In item #100, the deposit location of service ID:001 is set as the destination of the drive, and the deposit date and time of service ID:001 -α is set as the arrival date and time. Item #101 is an item for an event in which vehicle 3 stops. The event of vehicle 3 stopping in item #101 is an event for a user to deposit luggage in locker 4. A series of actions for a user to deposit luggage in locker 4 includes getting on vehicle 3, storing luggage in the storage unit, locking the storage unit, and getting off vehicle 3. Vehicle 3 needs to stop for a sufficient time to perform these series of actions. Therefore, in item #101, the date and time of deposit date and time of service ID:001 -α is set as the start date and time of the stop, and the date and time of deposit date and time of service ID:001 +α is set as the end date and time of the stop.

[0092] The driving plan set for vehicle 3 corresponding to item #100 and item #101 is a driving plan that indicates driving to the deposit location at deposit date and time -α and stopping at the deposit location from deposit date and time -α to deposit date and time +α.

[0093] Item #200 and item #201 are schedule items corresponding to the pick-up of luggage for the service with service ID:001. Item #200 is an item for a driving event of vehicle 3. Item #200 is set with the pick-up location of service ID:001 as the driving destination, and the pick-up date and time of service ID:001 - α as the arrival date and time. Item #201 is an item for an event where vehicle 3 stops. Item #2 The stop event of vehicle 3 of 01 is an event for the user to take out luggage from locker 4. The series of actions for the user to take out luggage from locker 4 includes getting into vehicle 3, unlocking the storage unit, taking out the luggage from the storage unit, and getting off vehicle 3. Therefore, for item #201, the take-out date and time of service ID:001 -α is set as the stop start date and time, and the take-out date and time of service ID:001 +α is set as the stop end date and time.

[0094] The driving plan set for vehicle 3 corresponding to item #200 and item #201 indicates that the vehicle will travel to the pick-up location at pick-up date and time -α and stay at the pick-up location from pick-up date and time -α to pick-up date and time +α.

[0095] Item #300 and item #301 are schedule items corresponding to (1) the handling of re-specified forgotten baggage, which is set for the service of service ID:001. Item #300 is an item for a driving event of vehicle 3. Item #300 has the specified location of service ID:001 set as the driving destination, and the specified date and time of service ID:001 -α set as the arrival date and time. Item #301 is an item for an event in which vehicle 3 stops. The event of vehicle 3 stopping for item #301 is an event for the user to take out luggage from locker 4. Item #301 has the specified date and time of service ID:001 -α set as the stop start date and time, and the specified date and time of service ID:001 +α set as the stop end date and time.

[0096] The driving plan set for vehicle 3 corresponding to item #300 and item #301 is a driving plan indicating that the vehicle will travel to a specified location at specified date and time -α and stop at the specified location from specified date and time -α to specified date and time +α.

[0097] For example, if a user corresponding to the service of service ID:001 retrieves luggage from locker 4 on the retrieval date and time, the schedule for handling the forgotten luggage becomes unnecessary. Therefore, when the control unit 11 receives a retrieval completion notification from the user terminal 2 on the retrieval date and time for the service of service ID:001, it deletes the schedule set after the retrieval date and time from the schedule information DB 13. The schedule to be deleted for locker 4 is the reservation schedule from the retrieval date and time of the storage unit of locker ID:001 assigned to the service of service ID:001, 14:00 to the specified date and time 17:00. The schedule to be deleted for vehicle 3 is item #300 and item #301 linked to service ID:001 from the retrieval date and time of the service of service ID:001 onward, 14:00.

[0098] During a blank period in the schedule of the vehicle 3, for example, the control unit 11 drives the vehicle 3 along a route that matches the schedule before and after that time. The control unit 11 refers to the schedule information DB 13 to assign lockers 4 and suggest pick-up locations and pick-up dates and times. The information stored in the schedule information DB 13 is not limited to that shown in FIG.

[0099] <Example of user device screen> 8 and 9 are examples of the screen of the user terminal 2 by the client application of the mobile locker system 100. Fig. 8 is an example of a locker use request screen of the user terminal 2. The locker use request screen is a screen for making a request to use the mobile locker service. The locker use request screen is displayed, for example, when a locker use request is selected from the menu of the client application of the mobile locker system 100.

[0100] The locker use request screen shown in FIG. 8 includes input fields for the deposit location, deposit date and time, pick-up location and pick-up date and time, and a check box for specifying whether or not to set up the handling of forgotten baggage. The buttons for requesting to use a locker and for requesting to use a locker are included. The input fields for the deposit location and retrieval location each have radio buttons for selecting the designation method: search by keyword, selection from a map, or selection from a registered address. When "search by keyword" is selected, the search results for the entered keyword are displayed, and the deposit location or retrieval location can be selected from the search results. Keyword search results may include, for example, place names, station names, building names, and addresses.

[0101] When "Select from map" is selected, the screen transitions to a map display screen, where the deposit location or withdrawal location can be set on the map. When "Select from registered address" is selected, a list of registered addresses is displayed, and the deposit location or withdrawal location can be selected from the list.

[0102] The deposit date and time and the withdrawal date and time may be set, for example, in 5-minute increments, 10-minute increments, 15-minute increments, or 30-minute increments.

[0103] When the "Start request" button is selected, the control unit 21 accepts the user's operation to request to use a locker, and transmits the request to use a locker to the center server 1. Along with the locker use request, the deposit location and deposit date and time, pick-up location and pick-up date and time, and user identification information entered on the locker use request screen are also transmitted. If the "Set handling of forgotten baggage" check button is checked, the transmission of the locker use request to the center server 1 is put on hold, and the screen transitions to the setting screen for handling forgotten baggage shown in FIG. 9. Note that the configuration of the locker use request screen is not limited to the example shown in FIG. 8.

[0104] Fig. 9 is an example of a setting screen for handling forgotten baggage on the user terminal 2. The setting screen for handling forgotten baggage is displayed, for example, when a check box for specifying whether or not to set up handling of forgotten baggage is checked on the locker use request screen shown in Fig. 9 and the "Start request" button is selected. Alternatively, the setting screen for handling forgotten baggage is displayed, for example, when setting up handling of forgotten baggage is selected from the menu of the client application of the mobile locker system 100.

[0105] The handling setting screen for forgotten packages shown in Fig. 9 includes radio buttons for re-specifying the pick-up location and date and time, delivery, and disposal, and a "Request handling settings" button. The radio button for re-specifying the pick-up location and date and time is accompanied by input fields for the pick-up location and pick-up date and time. The input fields for the pick-up location and pick-up date and time have the same structure as the input fields for the pick-up location and pick-up date and time shown in Fig. 9.

[0106] The radio button for delivery is accompanied by radio buttons for "Pick up" and "Leave at door", and input fields for the delivery destination and desired delivery date and time. The input field for the delivery destination has the same structure as the input fields for the drop-off location and pick-up location shown in Figure 9. In the input field for the desired delivery date and time, the desired delivery date and desired delivery time zone can be set.

[0107] When the "Request handling settings" button is selected, the control unit 21 accepts the user's operation for the handling settings request and transmits a locker use request to the center server 1. Along with the handling settings request, information indicating the type of handling of the forgotten parcel entered on the handling settings screen for the forgotten parcel and user identification information are also transmitted. Depending on the type of handling of the forgotten parcel, the pick-up location and pick-up date and time (in the case of (1) re-designation) or the delivery destination (in the case of (2-1) pick-up or (2-2) drop-off) are also transmitted. As an option, the service identification information and the desired delivery date and time are also transmitted (in the case of (2-1) pick-up or (2-2) drop-off). In addition, if the handling settings screen for the forgotten parcel is displayed by transitioning from the locker use request screen, the pending locker use request is also transmitted along with the handling settings request. The configuration of the setting screen for handling left-behind parcels is not limited to the example shown in FIG.

[0108] <Processing flow> Fig. 10 to Fig. 13 are examples of flowcharts of processing executed by the center server 1. Fig. 14 and Fig. 15 are examples of flowcharts of processing executed by the user terminal 2. The processing shown in Fig. 10 to Fig. 13 is executed by the CPU 101 of the center server 1, but for convenience, the processing will be described mainly by functional components. The processing shown in Fig. 14 and Fig. 15 is executed by the CPU 201 of the user terminal 2, but for convenience, the processing will be described mainly by functional components.

[0109] Fig. 10 is an example of a flowchart of the process when the center server 1 receives a locker use request from the user terminal 2. The process shown in Fig. 10 is repeatedly executed at a predetermined cycle.

[0110] In OP101, the control unit 11 determines whether or not a locker use request has been received from the user terminal 2. If a locker use request has been received from the user terminal 2 (OP101: YES), the process proceeds to OP102. If a locker use request has not been received from the user terminal 2 (OP101: NO), the process shown in Fig. 10 ends.

[0111] In OP102, the control unit 11 refers to the schedule information DB 13 and determines whether or not there is a locker 4 that can be assigned to the received locker use request. For example, the control unit 11 determines whether or not there is a storage unit that has no schedule set from the deposit date and time to at least the removal date and time, and is loaded on a vehicle 3 that exists or is scheduled to exist in a position that can arrive at the deposit location at the deposit date and time. If there is a locker 4 that can be assigned to the received locker use request (OP102: YES), it is agreed to provide a service for the received locker use request, and the process proceeds to OP103. If there is no locker 4 that can be assigned to the received locker use request (OP102: NO), the control unit 11 transmits a response indicating that the locker use request is not possible, and the process shown in FIG. 10 ends.

[0112] In OP103, the control unit 11 determines a storage unit and a vehicle 3 to be assigned to the locker use request from among the lockers 4 that can be assigned to the locker use request. The vehicle 3 to be assigned to the locker use request is selected from a vehicle 3 that is loaded with a locker 4 having a storage unit for which no schedule is set from the deposit date and time to at least the retrieval date and time, and that is present or scheduled to be present in a position that allows it to arrive at the deposit location on the deposit date and time. The storage unit to be assigned to the locker use request is selected from among the lockers 4 loaded on the vehicle 3 assigned to the locker use request, a storage unit for which no schedule is set from the deposit date and time to at least the retrieval date and time.

[0113] In OP104, the control unit 11 registers service information corresponding to the received locker use request in the service information DB 14. In addition, the control unit 11 registers a service item corresponding to the locker use request in the schedule of the assigned vehicle 3 and locker 4.

[0114] In OP105, the control unit 11 transmits a response of approval to the locker use request to the user terminal 2. Together with the response of approval, authentication information of the storage unit of the assigned locker 4 is also transmitted. In OP106, the control unit 11 creates a driving plan corresponding to the registered schedule for the assigned vehicle 3, and transmits it to the vehicle 3. Thereafter, the process shown in FIG. 10 ends.

[0115] Fig. 11 is an example of a flowchart of the processing of the center server 1 when a handling setting request is received from the user terminal 2. The processing shown in Fig. 11 is executed repeatedly at a predetermined cycle. The handling setting request may be received together with a locker use request, or may be received alone. When a handling setting request is received together with a locker use request, the processing for the locker use request (Fig. 9) is executed first, and then the handling setting request is processed.

[0116] In OP201, the control unit 11 determines whether or not a handling setting request has been received from the user terminal 2. If a handling setting request has been received from the user terminal 2 (OP201: YES), the process proceeds to OP202. If a handling setting request has not been received from the user terminal 2 (OP201: NO), the process shown in FIG. 11 ends.

[0117] In OP202, the control unit 11 determines whether the type of handling of the forgotten package specified by the user, received together with the handling setting request, is (1) re-designation. If the type of handling of the forgotten package specified by the user is (1) re-designation (OP202: YES), the process proceeds to OP203. If the type of handling of the forgotten package specified by the user is not (1) re-designation, that is, if it is (2-1) delivery, (2-2) drop-off, or (3) disposal, the process proceeds to OP205.

[0118] In OP203, the control unit 11 refers to the schedule information DB 13 to determine whether there is a better pick-up location and / or pick-up date and time than the re-designated pick-up location and / or pick-up date and time received together with the handling setting request. The better pick-up location and / or pick-up date and time is, for example, a pick-up location and pick-up date and time for which there is less or no additional charge or the travel distance of the vehicle 3 is shorter than when the vehicle 3 travels at the re-designated pick-up location and pick-up date and time. Alternatively, while the schedule of the vehicle 3 does not allow the vehicle 3 to arrive at the re-designated pick-up location by the re-designated pick-up date and time, the better pick-up location and / or pick-up date and time allows the vehicle 3 to arrive at the pick-up location by the pick-up time.

[0119] If there is a pick-up location and / or pick-up date and time that is better than the re-designated pick-up location and / or pick-up date and time (OP203: YES), the process proceeds to OP207. If there is no pick-up location and / or pick-up date and time that is better than the re-designated pick-up location and / or pick-up date and time (OP203: NO), the process proceeds to OP204.

[0120] In OP204, the control unit 11 refers to the schedule information DB 13 and determines whether or not the vehicle 3 can arrive at the re-designated pick-up location by the re-designated pick-up date and time according to the schedule of the vehicle 3. If the vehicle 3 can arrive at the re-designated pick-up location by the re-designated pick-up date and time (OP204: YES), the process proceeds to OP205. If the vehicle 3 cannot arrive at the re-designated pick-up location by the re-designated pick-up date and time (OP205: NO), the process proceeds to OP206.

[0121] In OP205, the control unit 11 registers information on the contents of the received handling setting request in the handling setting information DB 15 for the received handling setting request. The control unit 11 also updates the service information corresponding to the received handling setting request, which is held in the service information DB 14, by adding that there is a handling setting. The control unit 11 also creates a schedule item for the vehicle 3 and locker 4 linked to the service corresponding to the handling setting request for the request contents of the handling setting request, and updates the schedule of the corresponding vehicle 3 and locker 4 in the schedule information DB 13. The control unit 11 also creates a driving plan for the vehicle 3 in response to the update of the schedule for the vehicle 3 linked to the service corresponding to the received handling setting request, and transmits it to the vehicle 3.

[0122] In OP206, the control unit 11 determines whether the vehicle 3 is to be transported to the re-designated pick-up location by the re-designated pick-up date and time. Since the package cannot arrive and there is no better pick-up location and / or pick-up date and time, an error response is sent to the user terminal 2. When the error response is received, the user terminal 2 outputs an error. The user who receives the error may, for example, select a different type of handling for the forgotten package, or change the pick-up location and / or pick-up date and time, and then input a handling setting request again to the user terminal 2. Alternatively, the user may abort the setting for handling the forgotten package. After that, the processing shown in FIG. 11 ends.

[0123] In OP207, a proposal message proposing a better retrieval location and retrieval date and time than the re-designated retrieval location and retrieval date and time is transmitted to the user terminal 2. One or both of the retrieval location and retrieval date and time proposed in the proposal message are different from the re-designated retrieval location and retrieval date and time. Note that there may be multiple retrieval locations and retrieval dates and times proposed in the proposal message.

[0124] In OP208, the control unit 11 determines whether or not an agreement response to the proposal message has been received. If an agreement response to the proposal message has been received (OP208: YES), the process proceeds to OP209. If a rejection response to the proposal message has been received (OP208: NO), the process proceeds to OP204.

[0125] In OP209, the control unit 11 registers information in the handling setting information DB 15 for the received handling setting request, such that the type of handling of the forgotten baggage is (1) re-designated, and the pick-up location and pick-up date and time proposed in the proposal message. The control unit 11 also updates the service information corresponding to the received handling setting request, which is held in the service information DB 14, by adding that there is a handling setting. The control unit 11 also creates a schedule item for the vehicle 3 and locker 4 linked to the service corresponding to the received handling setting request for picking up the baggage at the proposed pick-up location and pick-up date and time ((1) re-designation), and updates the schedule of the corresponding vehicle 3 and locker 4 in the schedule information DB 13. The control unit 11 also creates a driving plan for the vehicle 3 in response to the update of the schedule for the vehicle 3 linked to the service corresponding to the received handling setting request, and transmits it to the vehicle 3.

[0126] In OP210, the control unit 11 transmits a response of acceptance to the handling setting request to the user terminal 2. Together with the response of acceptance, the confirmed setting contents of handling of forgotten packages (registered in the handling setting information DB 15) are also transmitted to the user terminal 2. After that, the process shown in FIG. 11 ends.

[0127] In addition, depending on the settings of the handling of forgotten baggage confirmed in OP205 and OP209, for example, the occupancy period of the storage unit of the locker 4 assigned to the corresponding service may be extended and may conflict with the occupancy period of another service assigned to the storage unit. Therefore, when a schedule item of the storage unit of the locker 4 is updated for one service and the period of the updated schedule item conflicts with the period of the schedule item of another service assigned to the storage unit, the schedule adjustment unit 16 may reallocate another storage unit of the same locker 4 to the other service. The schedule item of the storage unit of the locker 4 is that the storage unit is used after baggage is deposited.

[0128] Fig. 12 and Fig. 13 are examples of a flowchart of parcel removal management processing in a service by the center server 1. The processing shown in Fig. 12 and Fig. 13 is executed repeatedly at a predetermined cycle. The processing in Fig. 12 is executed, for example, for each record stored in the service information DB 14 in which the value of the removal completion notification field stores information indicating that a removal completion notification has not been received (see Fig. 5).

[0129] In OP301, the control unit 11 determines whether or not a take-out completion notification for the target service has been received from the user terminal 2. If a take-out completion notification has been received from the user terminal 2 (OP301: YES), the process proceeds to OP302. If a take-out completion notification has not been received from the user terminal 2 (OP301: NO), the process proceeds to OP308.

[0130] The process from OP302 to OP307 is carried out when a removal completion notification is received. In OP302, the control unit 11 judges whether or not there is a setting for handling left-behind parcels for the target service. If there is a setting for handling left-behind parcels for the target service (OP302: YES), the process proceeds to OP303. If there is no setting for handling left-behind parcels (OP302: NO), the process proceeds to OP305.

[0131] In OP303, the control unit 11 determines whether or not the process for handling the forgotten package has not yet been executed for the target service. If the value of the "designated date and time" field in the record for the target service of 15 indicates a date and time after the current time, a positive determination is made, and if the value indicates a date and time before the current time, a negative determination is made (see FIG. 6). If the process for handling forgotten packages has not yet been executed for the target service (OP303: YES), the process proceeds to OP304. If the process for handling forgotten packages has already been executed for the target service (OP303: NO), the process proceeds to OP305.

[0132] In OP304, the control unit 11 deletes the schedule event related to the handling of forgotten baggage for the target service from the schedule of the corresponding vehicle 3 and locker 4 in the schedule information DB 13, and updates the service information DB 14. This is because the retrieval completion notification was received before the processing of handling the forgotten baggage for the target service was executed, so the processing of handling the forgotten baggage does not need to be executed. Also, in OP304, the control unit 11 cancels the driving plan of the vehicle 3 corresponding to the deleted schedule, re-creates the driving plan of the vehicle 3, and transmits the re-created driving plan to the vehicle 3.

[0133] In OP305, the control unit 11 updates, for example, the field of "notification of removal completion" of the record of the target service in the service information DB 14 to information indicating that the removal completion notification has been received, and records that the removal completion notification has been received from the user terminal 2. In OP306, the control unit 11 calculates a fee for the target service. The fee is calculated, for example, based on the length of time from the deposit date and time to the removal date and time or the specified date and time, and / or the distance between the deposit location and the removal location. For example, the longer the length of time from the deposit date and time to the removal date and time or the specified date and time, the higher the fee. For example, the longer the distance between the deposit location and the removal location, the higher the fee. In addition, when a process for handling a forgotten package is being executed, a fee is added according to the type of package. In OP307, the control unit 11 transmits a response to the user terminal 2. For example, the service usage fee is also transmitted together with the response. Thereafter, the control unit 11 may execute a payment process. The payment process may be performed, for example, using credit card information registered in advance, or a bill may be sent to a specified address of the user. After that, the process shown in FIG. 12 ends.

[0134] In OP308, the control unit 11 refers to the service information DB 14 and determines whether or not the current time is the retrieval date and time of the target service. If the current time is the retrieval date and time of the target service (OP308: YES), the process proceeds to OP401 in Fig. 13. If the current time is not the retrieval date and time of the target service (OP308: NO), the process proceeds to OP309.

[0135] In OP309, the control unit 11 determines whether or not the current time is a time when a predetermined time has passed since the pick-up date and time of the target service. If the current time is a time when a predetermined time has passed since the pick-up date and time of the target service (OP309: YES), the process proceeds to OP401 in Fig. 13. The predetermined time in OP309 is set arbitrarily by the administrator of the mobile locker system 100 within the range of, for example, 5 minutes to 12 hours. If the current time is not a time when a predetermined time has passed since the pick-up date and time of the target service (OP309: NO), the process shown in Fig. 12 ends.

[0136] The process shown in FIG. 13 is executed when the take-out date and time arrives without a take-out completion notification being received for the target service, and when a predetermined time has passed since the take-out date and time without a take-out completion notification being received for the target service.

[0137] In OP401, the control unit 11 determines whether or not there is a setting for handling left-behind parcels for the target service. If there is a setting for handling left-behind parcels for the target service (OP401: YES), the process proceeds to OP402. If there is no setting for handling left-behind parcels (OP401: NO), the process proceeds to OP405.

[0138] In OP402, the control unit 11 transmits an inquiry to the user terminal 2 as to whether or not the set process for handling the forgotten baggage can be executed. In OP403, the control unit 11 determines whether or not an approval response to the inquiry as to whether or not the set process for handling the forgotten baggage can be executed is received from the user terminal 2. If an approval response is received (OP403: YES), the schedule and driving plan of the vehicle 3 for the process for handling the forgotten baggage that has already been set, and thereafter, the process shown in FIG. 13 ends.

[0139] If a rejection response is received (OP403: NO), the process proceeds to OP404. In OP404, the control unit 11 deletes the record of the target service in the handling setting information DB 15, the schedule item of the vehicle 3 for that process in the schedule information DB 13, and notifies the vehicle 3 of the cancellation of the driving plan corresponding to the deleted schedule. This is because the currently set process for handling the forgotten baggage is not executed due to the reception of the rejection response.

[0140] In OP405, the control unit 11 transmits a setting inquiry for the handling of the forgotten package to the user terminal 2. Thereafter, the processing shown in Fig. 13 ends. When the user terminal 2 receives the setting inquiry for the handling of the forgotten package, for example, the user inputs a user operation for a handling setting request from the handling setting screen, and the user terminal 2 transmits the handling setting request to the center server 1. In this case, the control unit 11 receives the handling setting request from the user terminal 2, and performs the processing of Fig. 11.

[0141] Figures 14 and 15 are flowcharts of the process when a user operation is input to the user terminal 2. The process shown in Figures 14 and 15 is repeatedly executed in the user terminal 2 while the client application of the movable locker system 100 is running.

[0142] In OP501, the control unit 21 determines whether or not a user operation to complete the deposit has been input. The user operation to complete the deposit is input to the user terminal 2 when the deposit of the luggage in the locker 4 is completed. If a user operation to complete the deposit has been input (OP501: YES), the process proceeds to OP502. In OP502, the control unit 21 transmits a deposit completion notification to the center server 1. If a user operation to complete the deposit has not been input (OP501: NO), the process proceeds to OP503.

[0143] In OP503, the control unit 21 determines whether or not a user operation for completing removal has been input. The user operation to complete removal is input to the user terminal 2 when the baggage deposited in the locker 4 is removed from the locker 4 or received. If the user operation to complete removal is input (OP503: YES), the process proceeds to OP504. In OP504, the control unit 21 transmits a removal completion notification to the center server 1. If the user operation to complete removal is not input (OP503: NO), the process proceeds to OP601 in FIG. 15.

[0144] In OP505, the control unit 21 determines whether or not a response has been received from the center server 1. If a response has been received from the center server 1 (OP505: YES), the process shown in Fig. 14 ends. The control unit 21 remains in a standby state until a response is received from the center server 1 (OP505: NO).

[0145] In OP601 of Fig. 15, the control unit 21 determines whether or not a user operation for requesting to use a locker has been input. If a user operation for requesting to use a locker has been input (OP601: YES), the process proceeds to OP601. If a user operation for requesting to use a locker has not been input (OP601: NO), the process proceeds to OP605.

[0146] In OP602, the control unit 21 judges whether or not a user operation for requesting settings for handling forgotten baggage has been input. For example, when the check box for "Set handling of forgotten baggage" is checked on the locker use request screen (see FIG. 8), and then the screen transitions to the setting screen for handling forgotten baggage (see FIG. 9) and the handling setting request button is selected, OP602 is judged as positive. For example, when the check box for "Set handling of forgotten baggage" is not checked on the locker use request screen (see FIG. 8), and the locker use request button is selected, OP602 is judged as negative.

[0147] If a user operation to request settings for handling forgotten baggage has not been input (OP602: NO), the process proceeds to OP603. In OP603, the control unit 21 transmits a locker use request to the center server 1. If a user operation to request settings for handling forgotten baggage has been input (OP602: YES), the process proceeds to OP604. In OP604, the control unit 21 transmits a locker use request and a handling setting request to the center server 1.

[0148] In OP605, the control unit 21 determines whether or not a user operation for requesting settings for handling left-behind baggage has been input. OP605 is a process performed when the setting screen for handling left-behind baggage (see FIG. 9) is displayed without going through the locker use request screen (see FIG. 8) and the handling setting request button is selected. For example, OP605 is determined to be positive when settings for handling left-behind baggage are made at any time after a locker use request is made and in response to a setting inquiry for handling left-behind baggage from the center server 1.

[0149] When a user operation for requesting settings for handling forgotten packages has been input (OP605: YES), the process proceeds to OP606. In OP606, the control unit 21 transmits a handling setting request to the center server 1. When a user operation for requesting settings for handling forgotten packages has not been input (OP605: NO), no user operation has been input to the user terminal 2, and therefore the process shown in FIG. 15 ends.

[0150] In OP607, the control unit 21 determines whether or not a suggestion message has been received from the center server 1. In the handling setting request transmitted to the center server 1 in OP604 or OP606, when the type of handling of forgotten parcels to be set is (1) re-designation, a suggestion message may be received from the center server 1. In the handling setting request transmitted to the center server 1 in 06, if the type of handling of forgotten baggage to be set is other than (1) re-designation, OP607 results in a negative determination. If a proposal message is received from the center server 1 (OP607: YES), the process proceeds to OP608. If a proposal message is not received from the center server 1 (OP607: NO), the process proceeds to OP611.

[0151] In OP608, the control unit 21 determines whether or not a user operation indicating agreement with the proposal message has been input. If a user operation indicating agreement with the proposal message has been input (OP608: YES), the process proceeds to OP609. In OP609, the control unit 21 transmits a response indicating agreement to the center server 1. If a user operation indicating rejection with respect to the proposal message has been input (OP608: NO), the process proceeds to OP610. In OP610, the control unit 21 transmits a response indicating rejection to the center server 1. Note that, in the case where the proposal message proposes multiple pick-up locations and pick-up dates and times, the pick-up location and pick-up date and time selected by the user are also transmitted to the center server 1 together with the response indicating agreement.

[0152] In OP611, the control unit 21 determines whether or not a response to the locker use request and / or the handling setting request has been received from the center server 1. If a response to the locker use request and / or the handling setting request has been received (OP611: YES), the process shown in Fig. 15 ends. The control unit 21 remains in a standby state until a response to the locker use request and / or the handling setting request is received (OP611: NO).

[0153] 10 to 15 are merely examples, and the processes of the center server 1 and the user terminal 2 are not limited to these. The processes of the center server 1 and the user terminal 2 can be appropriately changed depending on the embodiment.

[0154] <Example of processing sequence> 16 and 17 are diagrams showing an example of a processing sequence in the mobile locker system 100. The example shown in Fig. 16 is an example of a processing sequence when a request to use a locker is made together with a request to set up the handling of forgotten baggage.

[0155] In S11, the user terminal 2 accepts the user's input of a locker use request and a handling setting request, and transmits them to the center server 1 (FIG. 15, OP601: YES, OP602: YES, OP604). In S11, it is assumed that the type of handling of the forgotten baggage selected by the user is (1) re-designation. Therefore, in S11, the user terminal 2 transmits the user's identification information, (1) information indicating re-designation, the pick-up location, and the pick-up date and time together with the handling setting request to the center server 1.

[0156] In S12, the center server 1 receives a locker use request and a handling setting request from the user terminal 2 (OP101: YES in FIG. 10, OP201: YES in FIG. 11), and assigns either the vehicle 3 or the locker 4 to the locker use request (OP103 in FIG. 10). In the example shown in FIG. 16, there is no pick-up location and pick-up date and time better than the pick-up location and pick-up date and time received from the user terminal 2 together with the handling setting request in S12 (OP203: NO in FIG. 11), and the vehicle 3 can arrive at the pick-up location at the received pick-up date and time (OP204 in FIG. 11: YES). Therefore, in S12, as the handling setting for the forgotten baggage, (1) re-designation is set to the pick-up location and pick-up date and time received from the user terminal 2 together with the handling setting request (OP205 in FIG. 11).

[0157] In S13, the center server 1 transmits to the user terminal 2 a response indicating approval for the locker use request and a response indicating approval for the handling setting request (OP105 in FIG. 10, OP210 in FIG. 11). In S14, the center server 1 transmits a driving plan to the vehicle 3 (OP105 in FIG. 10). 11). The driving plan transmitted to the vehicle 3 in S14 includes, for example, driving to arrive at the deposit location at deposit date and time-α, staying at the deposit location until deposit date and time+α, driving to arrive at the take-out location at removal date and time-α, staying at the take-out location until take-out date and time+α, driving to arrive at the designated location at designated date and time-α, and staying at the designated location until designated date and time+α. The designated location and designated date and time are, respectively, the take-out location and take-out date and time in (1) re-designation.

[0158] In S15, the vehicle 3 drives according to the driving plan so as to arrive at the pick-up location on the pick-up date and time. In S16, the user of the user terminal 2 deposits the luggage in the locker 4 loaded on the vehicle 3. In S17, the user terminal 2 accepts an input of a user operation indicating completion of the deposit from the user (OP501 in FIG. 14: YES), and transmits a deposit completion notification to the center server 1 (OP502 in FIG. 14). In S18, the center server 1 receives the deposit completion notification from the user terminal 2, and transmits a response to the user terminal 2.

[0159] In S21, time passes, and the center server 1 does not receive a notification of completion of retrieval from the user terminal 2 even when the retrieval date and time arrives (OP301: YES, OP308: YES in FIG. 12), so it detects that the luggage has been left behind. In S22, since the handling of the forgotten luggage is set for the service (OP401: YES in FIG. 13), the center server 1 transmits an inquiry to the user terminal 2 as to whether or not the processing of the handling type of the forgotten luggage that has been set can be executed (OP402 in FIG. 13). In S23, the user terminal 2 accepts the input of a user operation that permits the execution of the processing of the handling type of the forgotten luggage that has been set, and transmits a permission response to the center server 1. The center server 1 receives the permission response from the user terminal 2 (OP403: YES in FIG. 13), and thus, the processing of the handling type of the forgotten luggage that has been set by the user is executed without changing the driving plan transmitted in S14.

[0160] In S31, as time passes, the vehicle 3 executes the process (1) re-designation of the handling of the forgotten baggage set by the user. The vehicle 3 travels so as to arrive at the pick-up location (indicated as "designated location" in FIG. 16) at (1) re-designated pick-up date and time-α. Note that (1) re-designated pick-up date and time-α is assumed to be a time before a predetermined time has passed since the pick-up date and time.

[0161] In S32, (1) at the re-designated pick-up location, the user of the user terminal 2 picks up the luggage from the storage section of the locker 4. In S33, the user terminal 2 accepts a user operation input indicating completion of pick-up (OP503 in FIG. 14: YES), and transmits a pick-up completion notice to the center server 1 (OP504 in FIG. 14). In S34, the center server 1 receives the pick-up completion notice from the user terminal 2 (OP301 in FIG. 12: YES), calculates the fee (OP306 in FIG. 12), and transmits a response to the user terminal 2 (OP307 in FIG. 12).

[0162] The example shown in Figure 17 is an example of a processing sequence in which no request is made to set up the handling of forgotten luggage when a request to use a locker is made, and a request is made to set up the handling of forgotten luggage when a luggage is forgotten to be picked up.

[0163] In S111, the user terminal 2 accepts the user's input of a locker use request and transmits it to the center server 1 (FIG. 15, OP601: YES, OP602: NO, OP603). In S112, the center server 1 receives the locker use request from the user terminal 2 (OP101: YES in FIG. 10) and assigns either the vehicle 3 or the storage section of the locker 4 to the locker use request (OP103 in FIG. 10). In S113, the center server 1 transmits a response to the user terminal 2 indicating acceptance of the locker use request (OP105 in FIG. 10).

[0164] In S114, the center server 1 transmits a driving plan to the vehicle 3 (OP106 in FIG. 10, OP205 in FIG. 11). The driving plan transmitted to the vehicle 3 in S114 includes, for example, driving to arrive at the deposit location at deposit date and time-α, staying at the deposit location until deposit date and time+α, driving to arrive at the pick-up location at pick-up date and time-α, and staying at the pick-up location until pick-up date and time+α.

[0165] In S115, the vehicle 3 drives according to the driving plan so as to arrive at the pick-up location on the pick-up date and time. In S116, the user of the user terminal 2 deposits the luggage in the locker 4 loaded on the vehicle 3. In S117, the user terminal 2 accepts an input of a user operation indicating completion of the deposit from the user (OP501 in FIG. 14: YES), and transmits a deposit completion notification to the center server 1 (OP502 in FIG. 14). In S118, the center server 1 receives the deposit completion notification from the user terminal 2, and transmits a response to the user terminal 2.

[0166] In S121, time passes and the center server 1 detects that a parcel has been left behind since it has not received a parcel completion notification from the user terminal 2 even though the parcel pickup date and time has arrived (OP301: YES in FIG. 12, OP308: YES), and in S122, the center server 1 transmits a setting inquiry for handling of forgotten parcels to the user terminal 2 since the setting for handling forgotten parcels has not been configured for the service (OP401: NO in FIG. 13).

[0167] In S123, the user terminal 2 accepts the user's input of a handling setting request, and transmits the handling setting request to the center server 1. In S123, it is assumed that the type of handling of the forgotten package selected by the user is (2-2) re-designation. Therefore, in S123, the user terminal 2 transmits the user's identification information, (1) information indicating re-designation, pick-up location, and pick-up date and time together with the handling setting request to the center server 1.

[0168] In S124, the center server 1 receives a handling setting request from the user terminal 2 (OP201: YES in FIG. 11), detects a pick-up location and pick-up date and time that are better than the pick-up location and pick-up date and time received from the user terminal 2 together with the handling setting request, and transmits a proposal message to the user terminal 2 (OP202: YES, OP203: YES, OP207 in FIG. 11). It is assumed that the pick-up location and pick-up date and time proposed to the user of the user terminal 2 in S124 are ones that do not incur an additional fee.

[0169] In S125, the user terminal 2 receives the proposed message from the center server 1 (OP607 in FIG. 15: YES), displays it on the touch panel display 205, accepts a user operation input agreeing with the better pick-up location and pick-up date and time in the proposed message (OP608 in FIG. 15), and transmits an agreement response to the center server 1 (OP609 in FIG. 15). In S126, the center server 1 receives the agreement response from the user terminal 2 (OP208 in FIG. 11: YES), sets the handling of forgotten parcels of the service in accordance with the better pick-up location and pick-up date and time in the proposed message (OP209 in FIG. 11), and transmits a response to the handling setting to the user terminal 2 (OP210 in FIG. 11).

[0170] In S131, time passes, and the vehicle 3 executes the process (1) re-designation of the handling of the forgotten baggage set by the user. The vehicle 3 travels so as to arrive at the pick-up location (indicated as "designated location" in FIG. 17) at (1) re-designated pick-up date and time -α. Note that the (1) re-designated pick-up date and time and pick-up location in S131 are the pick-up date and time and pick-up location proposed in the proposal message.

[0171] In S132, (1) the user of the user terminal 2 accesses the locker 4 at the re-designated pick-up location. The user terminal 2 removes the luggage from the storage section. In S133, the user terminal 2 accepts the user's input of a removal completion operation (OP503 in FIG. 14: YES), and transmits a removal completion notification to the center server 1 (OP504 in FIG. 14). In S134, the center server 1 receives the removal completion notification from the user terminal 2 (OP301 in FIG. 12: YES), calculates the fee (OP306 in FIG. 12), and transmits a response to the user terminal 2 (OP307 in FIG. 12). In the example shown in FIG. 17, the removal location and removal date and time proposed by the center server 1 are adopted, so no additional fee is charged for executing the re-designation of the process (1) for handling the forgotten luggage set by the user.

[0172] <Effects of the First Embodiment> In the first embodiment, the user can select and set how to handle luggage left in a mobile locker when the user forgets to take it out. This allows the luggage left in the mobile locker to be handled according to the user's convenience, improving the convenience of the mobile locker service.

[0173] When (1) re-designation is set for the forgotten baggage, the user can re-designate the pick-up location and pick-up date and time according to his / her own convenience. For example, if there is a pick-up location and pick-up date and time that is more efficient for the running of the vehicle 3 or does not incur an additional fee, the center server 1 transmits a suggestion message to the user terminal 2. This allows the user or the vehicle 3 to re-designate the pick-up location and pick-up date and time that are advantageous to the user or the vehicle 3.

[0174] When (2-1) pick-up or (2-2) drop-off is set for the luggage left behind, the user does not have to carry the luggage left in the mobile locker from the vehicle 3 to the designated location, improving convenience. When (3) disposal is set for the luggage left behind, for example, if the luggage left in the mobile locker is food and has spoiled due to forgetting to take it out, the mobile locker service will dispose of it, saving the user time. Note that the luggage is disposed of by taking it out of the locker 4 in the garage of the vehicle 3, for example.

[0175] <Other embodiments> The above-described embodiment is merely an example, and the present disclosure can be modified and implemented as appropriate without departing from the spirit and scope of the present disclosure.

[0176] In the first embodiment, when a user makes a request to use a locker, the user sets the pick-up location and pick-up date and time in addition to the deposit location and deposit date and time. This is not limited to the above, and the pick-up location and pick-up date and time may not be specified, and the user may pick up the luggage by calling the vehicle 3 to a specified location when he or she wants to pick up the luggage. In such a case, for example, the center server 1 may set the pick-up date and time by default to a date and time a specified time after the deposit date and time, and send a setting inquiry about the handling of the forgotten luggage to the user terminal 2 when the default pick-up date and time arrives without the luggage being picked up.

[0177] In addition, if the luggage is not picked up even when the (1) re-designation process is executed as the process for handling the forgotten luggage set by the user, the center server 1 may, for example, send a setting inquiry for handling the forgotten luggage to the user terminal 2, thereby prompting the user to set the handling of the forgotten luggage again.

[0178] Furthermore, the terminal that transmits the locker use request is not limited to the user terminal 2. For example, if the vehicle 3 is equipped with a terminal, the locker use request may be transmitted using that terminal. For example, if a user finds a parked vehicle 3 and wants to leave his / her luggage in the vehicle 3, If a locker 4 is found to be in the vehicle 3, the user operates the terminal installed in the vehicle 3 to transmit a locker use request for the locker 4 loaded on the vehicle 3. In this case, the user must be registered in the mobile locker system 100, and inputs the user's identification information on the locker use request screen of the terminal installed in the vehicle 3.

[0179] The processes and means described in this disclosure can be freely combined and implemented as long as no technical contradiction occurs.

[0180] Furthermore, a process described as being performed by one device may be shared and executed by multiple devices. Alternatively, a process described as being performed by different devices may be executed by one device. In a computer system, the hardware configuration (server configuration) by which each function is realized can be flexibly changed.

[0181] The present disclosure can also be realized by supplying a computer program implementing the functions described in the above embodiments to a computer, and having one or more processors of the computer read and execute the program. Such a computer program may be provided to the computer by a non-transitory computer-readable storage medium connectable to the system bus of the computer, or may be provided to the computer via a network. Non-transitory computer-readable storage media include, for example, any type of disk, such as a magnetic disk (floppy disk, hard disk drive (HDD), etc.), an optical disk (CD-ROM, DVD disk, Blu-ray disk, etc.), a read-only memory (ROM), a random access memory (RAM), an EPROM, an EEPROM, a magnetic card, a flash memory, an optical card, and any type of medium suitable for storing electronic instructions. [Explanation of symbols]

[0182] 1. Center server 2. User terminal 3. Vehicle 4. Lockers 11 Control section 12. Locker information database 13. Schedule information database 14. Service Information Database 15. Handling settings information database 16. Schedule Coordination Department 21 Control section 100··Mobile Locker System 101, 201··CPU 102, 202...Memory 103, 203...External storage device 104 Communications Department 204 Wireless communication unit 205··Touch panel display

Claims

1. From a user terminal, accepting a first specification including a first location and a first date and time for retrieving luggage deposited in a locker carried by the vehicle; accepting a second designation including a second location and a second date and time for picking up the package as a handling method in the case where the package has not been picked up even after the first date and time has passed; A control unit that executes the control unit, when retrieving the luggage at a third location and the third date and time results in a lower travel cost for the vehicle than retrieving the luggage at the second location and the second date and time, transmits to the user terminal a message proposing retrieval of the luggage at the third location and the third date and time instead of at the second location and the second date and time; Information processing device.

2. The control unit further executes creating a driving plan for the vehicle in accordance with the first designation and the second designation. The information processing device according to claim 1 .

3. The control unit is if the baggage remains deposited in the locker even after the first date and time has passed, accept the second designation from the user terminal; 3. The information processing device according to claim 1 or 2.

4. The control unit is accepting the second specification when accepting a reservation for use of the locker from the user terminal; The information processing device according to claim 1 .

5. An information processing method executed by an information processing device, comprising: From the user terminal, A first location and a first date for retrieving luggage deposited in a locker mounted on a vehicle. accepting a first specification including a time; accepting a second designation including a second location and a second date and time for picking up the package as a handling method in the case where the package has not been picked up even after the first date and time has passed; sending to the user terminal a message proposing retrieval of the luggage at the third location and the third date and time, instead of the second location and the second date and time, when retrieving the luggage at a third location and the third date and time results in a lower travel cost for the vehicle than retrieving the luggage at the second location and the second date and time; An information processing method comprising:

6. The method further includes creating a driving plan for the vehicle according to the first designation and the second designation. The information processing method according to claim 5.

7. If the baggage remains deposited in the locker after the first date and time, the second designation is accepted from the user terminal.

7. The information processing method according to claim 5 or 6.

8. When accepting a reservation for use of the locker from the user terminal, the second designation is accepted. The information processing method according to any one of claims 5 to 7.

9. A program for causing a computer to execute the information processing method described in any one of claims 5 to 8.

Images