JP7577801B2 - Computer programs, management devices, unmanned operation devices and servers - Google Patents

Description

The present invention relates to a computer program, a management device, an unmanned driving device, and a server, and in particular to a technology that enables the transfer of goods between a user and a store via an unmanned driving device.

In recent years, advances in sensors and AI technology have led to the practical use of autonomously mobile vehicles, flying objects, and other devices. Such devices have a variety of uses, one of which is logistics. For example, in the system described in Non-Patent Document 1, autonomous vehicles are used to deliver goods from drugstores and supermarkets to consumers.

http://www.zmp.co.jp/products/carriro-delivery, (Retrieved September 15, 2017)

The application of autonomously mobile devices to logistics has only just begun, and various challenges arise when implementing the systems.

The present invention was made in consideration of these problems, and its purpose is to provide technology that solves the problems in a system that realizes the transfer of goods between a user and a store via an unmanned transport device, or to improve the system.

One aspect of the present invention relates to a computer program for a user terminal in a system for realizing the transfer of goods between a user and a store via an unmanned transportation device, the computer program causing the user terminal to realize a function of acquiring an image previously acquired by a server, the image corresponding to the current position of the unmanned transportation device obtained using a positioning means provided in the unmanned transportation device, and a function of displaying the acquired image on a display.

In addition, any combination of the above components, or mutual substitution of the components or expressions of the present invention between devices, methods, systems, recording media storing computer programs, etc., are also valid aspects of the present invention.

The present invention can solve problems in a system that realizes the transfer of goods between a user and a store via an unmanned transport device, or can improve the system.

FIG. 1 is a schematic diagram showing a configuration of a PDD system according to an embodiment. FIG. 2 is a block diagram showing an example of a hardware configuration of the mobile terminal of FIG. 1 . 1 is a chart showing a flow from ordering a product to completing delivery in the PDD system. FIG. 2 is a data structure diagram showing an example of a database in FIG. 1 . 2 is a block diagram showing the functions and configuration of a management server. FIG. 6 is a data structure diagram showing an example of a site information storage unit in FIG. 5 . FIG. 2 is a block diagram showing the functions and configuration of a mobile terminal. FIG. 13 is a representative screen diagram of an order confirmation screen displayed on a display. FIG. 13 is a representative screen diagram of a building designation screen displayed on a display. FIG. 4 is a representative screen diagram of a location and time display screen displayed on a display. FIG. 13 is a representative screen diagram of a meeting place narrowing down screen displayed on a display. FIG. 11 is a representative screen diagram of an optional selection screen displayed on a display. FIG. 13 is a typical screen diagram of a NG reason display screen displayed on a display. FIG. 13 is a representative screen diagram of a meeting place setting screen displayed on a display. 13 is a flowchart showing a series of processing steps in a PDD having a registration mode. FIG. 13 is a representative screen diagram of an order rejection screen displayed on a display. 2 is a block diagram showing the functions and configuration of a management server. FIG. 18 is a data structure diagram showing an example of the image storage unit of FIG. 17. 18 is a data structure diagram showing an example of the order control information storage unit of FIG. 17. FIG. 2 is a representative screen diagram of a top screen displayed on a display. FIG. 13 is a representative screen diagram of an approach notification screen displayed on a display. FIG. 11 is a representative screen diagram of a status notification screen displayed on a display. FIG. 13 is a representative screen diagram of a detailed text screen displayed on a display. FIG. 13 is a representative screen diagram of a reset inquiry screen displayed on a display. FIG. 13 is a representative screen diagram of a meeting place update screen displayed on the display. FIG. 13 is a representative screen diagram of a situation notification screen when it is determined that the distance between the PDD and the meeting place is below the first change threshold but is equal to or greater than the second change threshold. FIG. 13 is a representative screen diagram of a situation notification screen when it is determined that the distance between the PDD and the meeting place is below a second change threshold value. FIG. 13 is a representative screen diagram of a status notification screen when it is determined that the PDD has arrived at the meeting place. FIG. 13 is a representative screen diagram of a transaction completion screen displayed on a display. FIG. 4 is a representative screen diagram of a management screen displayed on a display. FIG. 13 is a representative screen diagram of an approach notification screen displayed on the display of the mobile terminal. 1 is a flowchart showing a series of processing steps in a PDD system. 13 is a flowchart showing the flow of a series of processes in a management server. 13 is a flowchart showing the flow of a series of processes in a management server. FIG. 4 is a representative screen diagram of a management screen displayed on a display of the management server. 2 is a block diagram showing the functions and configuration of a management server. FIG. 37 is a data structure diagram showing an example of a user information storage unit in FIG. 36. FIG. 13 is an explanatory diagram for explaining the identification process in the promotion target identification unit. FIG. 11 is a data structure diagram illustrating an example of a size matching table. FIG. 11 is a representative screen diagram of a recommendation screen displayed on the display of a mobile terminal. 13 is a flowchart showing the flow of a series of processes in a management server.

In the following, identical or equivalent components, parts, and processes shown in each drawing will be given the same reference numerals, and duplicate explanations will be omitted where appropriate. In addition, some parts that are not important for the explanation will be omitted in each drawing.

(Overall configuration and operation)
1 is a schematic diagram showing the configuration of a PDD (Personal Delivery Devices) system 10 according to an embodiment. The PDD system 10 is a system that realizes the delivery of a product 24 between a user 14 and a store 22 via a PDD. The PDD system 10 includes a management server 12 that manages the PDD system 10, a mobile terminal 16 of the user 14, a store 22 that sells the product 24, and a PDD 20 that transports the product 24 and receives packages from the user 14. The management server 12, the mobile terminal 16, the store 22, and the PDD 20 are each connected to a network 18 and configured to be able to communicate with each other.

The network 18 may include a wired network or a wireless network or a combination thereof, and may include the Internet, an intranet, a LAN, a WAN, WiFi, Bluetooth (registered trademark), a wireless telephone network, etc. For example, the mobile terminal 16 communicates with the management server 12 via a wireless telephone network. Furthermore, when the mobile terminal 16 is close to the PDD 20, it communicates with the PDD 20 via short-range wireless communication such as Bluetooth.

The store 22 may be a convenience store, drug store, supermarket, restaurant, department store, discount store, retail store, street stall, etc. In the store 22, a staff member of the store 22 can load products 24 onto the PDD 20, and can also collect luggage that the PDD 20 has entrusted to the user 14. The store 22 is equipped with a terminal (not shown) such as a Point Of Sale (POS) terminal, and the terminal is connected to the network 18. At least one PDD 20 is installed in the store 22, and the store 22 is one of the bases for the PDD 20. The store 22 may be a building on the store 22 side, such as a logistics warehouse or a factory.

The PDD 20 mediates the transfer of goods between the user 14 and the store 22. The PDD 20 is an unmanned transport device that stores goods such as goods 24 to be delivered from the store 22 to the user 14 and goods such as luggage to be handed over from the user 14 to the store 22, and automatically moves to a destination using position information from positioning means such as a GPS, gyro sensor, or acceleration sensor. The automatic movement of the PDD 20 may be achieved, for example, by using the automatic driving technology used in an automatically driving delivery robot described in Non-Patent Document 1. The PDD 20 may move automatically under the control of the management server 12, or may move standalone without such control. The PDD 20 has multiple storage spaces 26, each of which can store goods 24 or luggage.

In place of the PDD 20, an aerial transport device such as a drone or an unmanned vehicle such as an unmanned delivery vehicle that can travel on roads (rather than sidewalks) may be used.

The management server 12 is a server for managing the PDD system 10, and may be installed in a data center or in a store 22 depending on who the administrator is. The management server 12 acquires information about transactions carried out via the PDD 20 and stores the information in the database 40.

The mobile terminal 16 is a user terminal such as a smartphone, a mobile phone, a tablet, a laptop computer, or a smart watch. A user 14 of the mobile terminal 16 downloads and installs a PDD application program (hereinafter referred to as a PDD app) according to the embodiment from a download site to the mobile terminal 16 via a network 18. Alternatively, the PDD app may be pre-installed on the mobile terminal 16. The PDD app is provided by an administrator of the PDD system 10. When the PDD app is executed by the mobile terminal 16, the mobile terminal 16 communicates with the management server 12 via the network 18 and realizes various functions. Below, functions realized by the mobile terminal 16 (a processing unit such as a CPU) executing the PDD app are described as functions of the mobile terminal 16. These functions are actually functions that the PDD app causes the mobile terminal 16 to realize. Note that a stationary terminal such as a desktop computer may be used instead of the mobile terminal 16.

Figure 2 is a block diagram showing an example of the hardware configuration of the mobile terminal 16 in Figure 1. The mobile terminal 16 may be any terminal capable of installing and executing a PDD application, and may be, for example, a known mobile terminal. The mobile terminal 16 includes a memory 28, a processor 30, a communication interface 32, a display 34, and an input interface 36. Each of these elements is connected to a bus 38 and communicates with each other via the bus 38.

The memory 28 is a storage area for storing data and programs. The data and programs may be permanently or temporarily stored in the memory 28. In particular, the memory 28 stores a PDD application. The processor 30 may be a CPU that realizes various functions in the mobile terminal 16 by executing the programs stored in the memory 28, particularly the PDD application. The communication interface 32 is an interface for transmitting and receiving data to and from the network 18. The display 34 is a device for displaying various information, such as a liquid crystal display or an organic EL display. The input interface 36 is a device for receiving input from a user. The input interface 36 includes, for example, a touch panel provided on the display 34 and various input keys. The management server 12 and the POS may each have a hardware configuration similar to the hardware configuration shown in FIG. 2.

Figure 3 is a chart showing the flow from ordering a product 24 in the PDD system 10 to completing delivery. The user 14 uses the mobile terminal 16 to browse a list of products 24 that can be ordered from the store 22. The user 14 selects the desired product 24, specifies the meeting place for the PDD 20 (i.e., the destination of the PDD 20), and selects a payment method. The mobile terminal 16 accepts information on the selected product 24, information on the specified meeting place, and payment information regarding the payment (S302), generates order information including the information, and transmits it to the management server 12 via the network 18 (S304). The management server 12 receives the order information and performs a payment process using the payment information included in the order information (S306). For example, if the user 14 selects payment by credit card, the payment information includes the credit card number, and the payment process includes a process of obtaining approval from the credit card company.

When the payment process is completed, the management server 12 transmits a storage instruction to the POS of the store 22 via the network 18 to store the selected product 24 in the PDD 20 (S308). When the POS receives the storage instruction, it displays information indicating the selected product 24 and information specifying the PDD 20 (and the storage space 26) in which the product 24 should be stored on the POS display (S310). An employee of the store 22 checks the POS display and stores the selected product 24 in the specified PDD 20. Here, the POS may be a portable POS terminal, and the employee may read the barcode of the selected product 24 to change the status to one in which the selected product 24 has been stored in the PDD 20. Alternatively, the PDD may be equipped with a camera or barcode function, and the barcode of the selected product 24 may be read using the camera or barcode function to change the status in a similar manner.

Furthermore, when the payment process is completed, the management server 12 generates a travel route for the PDD 20, which includes the meeting place included in the order information as a destination, and transmits route information including the generated travel route to the PDD 20 via the network 18 (S312). The route information may include information specifying the storage space 26 where the item is to be stored.

When the PDD 20 receives the route information, it sets a route based on the route information (S314). The PDD 20 waits until an employee stores the product 24 in the storage space 26, and when the storage of the product 24 is confirmed (S316), it starts automatic driving to move along the set route to the destination. During automatic driving (S318), the PDD 20 measures its current location at any time and reports it to the management server 12 and the POS via the network 18 (S320). The reported current location may be used by the management server 12 to control automatic driving, or may be displayed on the display of the POS to inform the employee of the store 22 of the location of the PDD 20. The management server 12 may also provide the current location of the PDD 20 to the mobile terminal 16 via the network 18.

The PDD 20 arrives at the set meeting place and waits there (S322). While waiting, the PDD 20 broadcasts its own identification information to the surroundings by short-range wireless communication. The user 14 goes to the meeting place with the mobile terminal 16. The method of notifying the user 14 that the PDD 20 has arrived at the meeting place may be, for example, by displaying the current location of the PDD 20 on the display 34 of the mobile terminal 16, by displaying the expected arrival time of the PDD 20 or the remaining time until arrival on the display 34, or by the management server 12 receiving a report of the arrival from the PDD 20 notifying the mobile terminal 16 of the arrival of the PDD 20, or a combination of these.

The mobile terminal 16 detects the identification information of the PDD 20 via short-range wireless communication (S324). The mobile terminal 16 transmits authentication information of the user 14 to the PDD 20 via short-range wireless communication (S326). The PDD 20 receives the authentication information and performs user authentication using the received authentication information (S328). This user authentication may be performed by the PDD 20, or by the management server 12, or by communication between the two. Figure 3 shows an example in which user authentication is completed by the PDD 20. In this case, the route information that the PDD 20 receives from the management server 12 in step S312 includes the authentication information of the user 14.

If the user authentication is successful, the PDD 20 opens the storage space 26 in which the product 24 addressed to the user 14 is stored (S330). The user 14 takes out the product 24 from the opened storage space 26, and the product 24 is handed over. After taking out the product 24, the user 14 closes the lid of the storage space 26. When the PDD 20 detects that the lid has been closed, it starts automatic driving to move to the store 22 along the set route. During automatic driving (S332), the PDD 20 measures its current position at any time and reports it to the management server 12 and the POS via the network 18 (S334). The PDD 20 arrives at the store 22 and stops at a predetermined stopping position (S336). The PDD 20 transmits confirmation information to the management server 12 and the POS via the network 18 to confirm the completion of the transfer (S338). The confirmation information may be generated and transmitted when the PDD 20 is at the destination. When the management server 12 receives the confirmation information, it stores the transaction information related to this transaction in the database 40 (S340).

In the example of FIG. 3, an electronic prepayment method is described, but an electronic postpayment method may also be used, in which case the management server 12 may perform the settlement process after the completion of the transfer is confirmed. Alternatively, a method may be used in which the PDD 20 hands over the product 24 to the user 14, and in return receives payment for the product 24 from the user 14, who then takes it back to the store 22.

In the example of FIG. 3, a case where the user 14 orders a product 24 is described, but a similar process can be applied when the user 14 requests collection of a package. The main difference in this case from the example of FIG. 3 is that the storage space 26 is empty when the PDD 20 heads to the destination, and the storage space 26 holds the user 14's package when the PDD 20 returns from the destination to the store 22.

In the example of FIG. 3, the management server 12 transmits route information to the PDD 20 via the network 18, but this is not limited to the above. For example, the POS in the store 22 may obtain route information together with a storage instruction from the management server 12, and the POS may set the route information in the PDD 20 via, for example, short-range wireless communication or Wi-Fi.

Figure 4 is a data structure diagram showing an example of the database 40 in Figure 1. The database 40 holds, in association with each other, the attributes of the user 14 who performed the transaction, whether it was delivery or collection, the ordered product 24, the number of ordered products 24 or collected packages, the date and time when the order was confirmed, the location of the user 14's mobile terminal 16 when the order was confirmed, the date and time when the user 14 received the product 24 from the PDD 20, the location where the user 14 received the product 24 from the PDD 20 (= the designated meeting place), the PDD waiting time which is the time from when the PDD 20 arrives at the meeting place until the user 14 picks up the product 24, whether the meeting was successful or unsuccessful, and the weather.

According to the PDD system 10 of this embodiment, each time an order for a product 24 or a request for collection is made, information on the place where the transaction took place (meeting place) and information on the place where the order was made are accumulated in the database 40 of the management server 12. Since the meeting place is the place where the PDD 20 directly handed the product 24 to the user 14, it is highly accurate as to the place where the user 14 received the product 24. The administrator of the management server 12 can process the accumulated location information as big data to realize more effective product recommendations and marketing.

For example, by noting that meeting places are accumulated along with the success or failure of pickup attempts, the success rate of pickup can be calculated for each meeting place. Also, by noting that meeting places are accumulated along with the PDD waiting time, the time required for pickup can be calculated for each meeting place. Also, for each meeting place, an index of the ease of pickup for the user can be calculated based on the success rate of pickup and the time required for pickup. Based on this index, the management server 12 can suggest candidate meeting places to the user 14.

Alternatively, the location and time when an order is likely to be placed can be calculated from the accumulated meeting locations and order times. The management server 12 can recommend products 24 based on the calculated location and time. For example, if it is found that the frequency with which onigiri are handed out to users at the entrance of a certain office building between 11:30 a.m. and noon is higher than at other locations and other times of the day, it can be determined that it would be effective to electronically distribute coupons for onigiri to users in that office building between 11:00 a.m. and 11:30 a.m.

By noting that order dates and times are accumulated, it is possible to predict peak periods for orders. In this case, the number of PDDs 20 to be placed in the store 22 and their waiting locations can be adjusted for each time period based on the predicted peak periods.

The management server 12 may also perform an incentive process to give the user 14 an incentive to promptly pick up the PDD 20 when it arrives at the meeting place. The incentive process may be, for example, a process of giving a coupon to the user 14 who promptly picks up the PDD 20, or a process of preferentially recommending the user 14 as a good user.

After extensive research into the above-mentioned PDD system 10, the inventors have recognized that there are various issues in various phases of operation. Each issue and the means for solving it are described below.

(Example 1)
Phase: Order Reception Task: Identifying a Meeting Place As described in relation to step S302 in FIG. 2, when the user 14 orders the product 24, the user 14 specifies a meeting place where the user 14 will meet the PDD 20. As a user interface for accepting the designation of the meeting place, the PDD application may display an electronic map (hereinafter referred to as an electronic map) on the display 34 of the mobile terminal 16, and the user 14 may specify the meeting place on the electronic map. However, while the electronic map currently available allows a building to be designated, it does not allow a specific location (such as an entrance, back door, service entrance, rest area, smoking area, etc.) within the building's premises to be designated. Since an entrance is relatively suitable as a meeting place, it may be possible to implement a system in which the entrance is automatically designated as the meeting place when a building is designated. However, since the electronic map does not include information for identifying the location of the entrance, such implementation is difficult under the current circumstances. Therefore, it is necessary to devise a system in which the meeting place can be narrowed down to, for example, "in front of Hachiko" rather than "Shibuya Station".

Therefore, in this example, the electronic map and a map of the building site in the electronic map are associated with each other and registered in the management server 12. When the user 14 designates a building in the electronic map as a meeting place, the PDD app obtains a map of the building site from the management server 12, adds meeting place candidates to the obtained site map, and presents it to the user 14. This allows the user 14 to narrow down the meeting place to the level of a specific place within the building site, and increases the certainty of a meeting between the user 14 and the PDD 20.

Figure 5 is a block diagram showing the functions and configuration of the management server 12 according to Example 1. Each block shown in Figure 5 and other block diagrams can be realized in hardware terms by elements and mechanical devices such as a computer CPU, and in software terms by computer programs, etc., but here we have depicted functional blocks realized by the cooperation of these. Therefore, those skilled in the art who have read this specification will understand that these functional blocks can be realized in various ways by combining hardware and software.

The management server 12 includes an electronic map storage unit 42, a site information storage unit 44, a building designation reception unit 46, a building type determination unit 48, a meeting place designation reception unit 50, and a candidate update unit 52. The electronic map storage unit 42 stores an electronic map. The electronic map may be, for example, a wide-area/detailed map database ZMAP provided by Zenrin Co., Ltd., or Google Map provided by Google Inc. An API (Application Programming Interface) for acquiring an electronic map from another server may be used instead of the electronic map storage unit 42.

Fig. 6 is a data structure diagram showing an example of the site information storage unit 44 in Fig. 5. The site information storage unit 44 stores a building ID that identifies a building, a type of building, a map of the building site, coordinates of candidate meeting places, the number of times specified, a set of images, the range of the NG area, and the reason for NG, in association with each other.

The building ID is an identifier that identifies a building registered in the electronic map. The type of building may be, for example, an office building, an apartment, a house, an apartment, a school, a hospital, etc. The type of building may be updated each time a user registers a building, as described below. The map of the site is an image file in a bitmap format, a JPEG format, or the like. The candidate meeting place is (1) manually set by the administrator of the PDD system 10, or (2) a place where the user 14 and the PDD 20 have actually met is set, or (3) registered by the user 14 via the mobile terminal 16. The coordinates of the candidate meeting place are information that identifies the position of the candidate meeting place on the map of the site, for example, the coordinates of the candidate on the map of the site. The number of times the candidate meeting place has been designated is the number of times the candidate has been selected as a meeting place. The image of the candidate meeting place is an image of the surroundings of the candidate taken by the PDD 20 or the mobile terminal 16 of the user 14 at the candidate. The range of the NG area indicates information that identifies the range of the NG area when there is an NG area on the premises where a meeting between the user 14 and the PDD 20 is restricted or prohibited. The NG reason indicates reason information indicating why a meeting is restricted or prohibited in the NG area. In the example of Figure 6, it is shown that an NG area exists in the range "20<x<30, 50<y<55" on the premises of building ID "A11", and that this area is NG because it has stairs.

7 is a block diagram showing the functions and configuration of the mobile terminal 16 according to Example 1. The mobile terminal 16 includes a transmitting/receiving unit 54, an input receiving unit 56, and a display control unit 58.
The transmitting/receiving unit 54 exchanges information with the management server 12 via the network 18 .
The input acceptance unit 56 accepts input from the user 14 to the input interface 36. For example, when the user 14 taps an object displayed on the display 34, the input acceptance unit 56 acquires the position of the tap from a touch panel provided on the display 34, compares the acquired position with the display position of the object, and if the two match, accepts the tap as a designation of the object. The input acceptance unit 56 also accepts various instructions from the user 14 via the touch panel. The input acceptance unit 56 transmits information related to the instructions and designations by the user 14 to the management server 12 via the transmission/reception unit 54.
The display control unit 58 acquires screen information for generating a screen from the management server 12 via the transmission/reception unit 54, and causes the display 34 to display a predetermined screen in accordance with the acquired screen information.

The functions and configurations of the mobile terminals in the examples other than Example 1 described below are common to the functions and configurations of the mobile terminal 16 in Example 1 shown in FIG. 7. In Example 1, the mobile terminal 16 is basically responsible for inputting and outputting information, and information processing is performed by the management server 12, but this is not limited thereto, and in Example 1 and other examples, the PDD system 10 may be configured so that all or any part of the information processing in the management server 12 is performed by the mobile terminal 16.

Below, with reference to Figures 8 to 14, the narrowing down of meeting locations when accepting an order for a product from the user 14 will be described. Figure 8 is a representative screen diagram of an order confirmation screen 60 displayed on the display 34. When the input acceptance unit 56 of the mobile terminal 16 accepts the designation of a desired product from the user 14 on a product selection screen (not shown) or the like, it transmits information about the designated product to the management server 12 via the network 18. The management server 12 determines the content of the order confirmation screen 60 based on the designated product, generates order confirmation screen information that is screen information for generating the order confirmation screen 60, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the order confirmation screen information, and causes the display 34 to display the order confirmation screen 60 in accordance with the acquired order confirmation screen information.

The order confirmation screen 60 has an order details display area 62, a meeting place designation button 64, and a scheduled meeting time area 66. The order details display area 62 displays details such as the name, quantity, and price of the product designated by the user 14. The scheduled meeting time area 66 displays the scheduled time for the PDD 20 to arrive at the designated meeting place. Note that if the meeting place has not yet been determined, the scheduled meeting time area 66 displays a message indicating that the scheduled time will be displayed after the meeting place has been designated.

When the user 14 taps the meeting place designation button 64, the input reception unit 56 of the mobile terminal 16 accepts it as an instruction to designate a meeting place. The input reception unit 56 transmits the instruction to the management server 12 via the network 18. When the building designation reception unit 46 of the management server 12 receives the instruction, it acquires an electronic map of the surrounding area of the current position of the mobile terminal 16 from the electronic map storage unit 42, generates building designation screen information, which is screen information for generating a building designation screen 68, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the building designation screen information, and displays the building designation screen 68 on the display 34 according to the acquired building designation screen information.

9 is a representative screen diagram of the building designation screen 68 displayed on the display 34. The building designation screen 68 has an address input area 70, a building type designation area 72, an OK button 76, and a map designation area 74. The address input area 70 is an area for the user 14 to input the address of the building that the user 14 wants to designate as the meeting place. The building type designation area 72 is an area for the user 14 to designate or select the type of building that the user 14 wants to designate as the meeting place. The building type designation area 72 is configured in a pull-down format with options such as a single-family home, an office building, an apartment, a condominium, and a school. The options in the building type designation area 72 correspond to the type of building. For example, if the user 14 wants to hold a meeting in the office building where he or she works, the user 14 inputs the address of the office building in the address input area 70 and selects "office building" from the pull-down menu in the building type designation area 72. When the user 14 taps the OK button 76, the input acceptance unit 56 of the mobile terminal 16 accepts it as an instruction to designate the address and type of the building. The input reception unit 56 transmits the information entered in the address input area 70 and the type selected in the building type designation area 72 to the management server 12 via the network 18.

Alternatively, the user 14 may select a desired building from an electronic map of the surrounding area of the current location of the mobile terminal 16 shown in the map designation area 74. In the map designation area 74, buildings that the user 14 has previously designated as meeting places are highlighted (indicated by diagonal hatching in FIG. 9). When the user 14 taps a building on the electronic map, the input reception unit 56 of the mobile terminal 16 accepts it as an instruction to designate a building. The input reception unit 56 transmits the building ID of the designated building to the management server 12 via the network 18.

The building designation reception unit 46 of the management server 12 acquires (information entered in the address input area 70 and the type selected in the building type designation area 72) or (building ID) from the mobile terminal 16 via the network 18. If the acquired information is a building ID, the building designation reception unit 46 refers to the site information storage unit 44 and acquires the type of building corresponding to the building ID. The building type determination unit 48 determines whether the acquired type meets a criterion related to the size of the site. This criterion is, for example, whether the site is large or small. In the case of a single-family home or apartment, the site is small, so there is a high probability that the user 14 and the PDD 20 will be able to successfully meet without narrowing down the meeting place, whereas the site of an office building, condominium, or school is large, so narrowing down the meeting place is necessary. Therefore, the building type determination unit 48 classifies building types into large site groups (office buildings, condominiums, schools, stations, etc.) and small site groups (detached houses, apartments, etc.), and determines that the criteria are met if the acquired type falls into the large site group, and determines that the criteria are not met if the acquired type falls into the small site group.

If it is determined that the criteria are not met (i.e., the building site is small), the building type determination unit 48 calculates the scheduled meeting time based on the position of the building specified as the meeting location. The building type determination unit 48 generates location and time display screen information, which is screen information for generating a location and time display screen 78, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the location and time display screen information, and displays the location and time display screen 78 on the display 34 in accordance with the acquired location and time display screen information.

Figure 10 is a representative screen diagram of the location and time display screen 78 displayed on the display 34. The location and time display screen 78 has an order details display area 62, a confirmed meeting location display area 80, and a confirmed scheduled time display area 82. The confirmed meeting location display area 80 displays the meeting location and building type specified by the user 14 and confirmed by the management server 12. The confirmed scheduled time display area 82 displays the scheduled meeting time calculated by the management server 12.

When the building type determination unit 48 determines that the criteria are met (= when the building site is large), the meeting place designation reception unit 50 refers to the site information storage unit 44 and acquires a site map corresponding to the specified building, information on the candidate meeting places, and information on the NG areas. Based on the acquired information, the meeting place designation reception unit 50 generates meeting place narrowing down screen information, which is screen information for generating a meeting place narrowing down screen 84, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the meeting place narrowing down screen information, and displays the meeting place narrowing down screen 84 on the display 34 according to the acquired meeting place narrowing down screen information.

Figure 11 is a representative screen diagram of the meeting place narrowing down screen 84 displayed on the display 34. The meeting place narrowing down screen 84 has a site map display area 86, a candidate image display area 88, and a new setting button 90. The site map display area 86 displays a site map of the specified building. In the site map display area 86, a candidate mark 94 and a performance indicator 92 are displayed in association with each position of the meeting place candidate. The candidate mark 94 is an icon or graphical object indicating that the location can be specified as a meeting place. The performance indicator 92 corresponds to the number of times that the meeting place candidate has been specified as a meeting place, and is configured to display more black circles as the number of times increases. By looking at the site map display area 86, the user can at a glance grasp (1) which locations can be specified as meeting places, and (2) how frequently each meeting place candidate is selected.

The candidate image display area 88 displays images of the surroundings of the meeting place candidate specified by the temporary selection frame 96 in the site map display area 86. When the user 14 taps a candidate on the site map display area 86, the temporary selection frame 96 moves to the tapped candidate. By moving the temporary selection frame 96 between the candidates, the user 14 can see images of the surroundings of each candidate, thereby reducing the probability of specifying an incorrect meeting place. Note that in other embodiments, images of the surroundings of all the candidates displayed in the site map display area 86 may be displayed on one screen. In this case, viewability is improved.

When the user 14 double-tap a candidate on the site map display area 86, the input reception unit 56 of the mobile terminal 16 accepts it as an instruction to specify a meeting location. The input reception unit 56 transmits the specified candidate to the management server 12 via the network 18. The meeting location specification reception unit 50 of the management server 12 receives the specified candidate and acquires it as the meeting location. Additionally, the candidate update unit 52 accesses the site information storage unit 44 and updates (e.g., +1) the number of times the candidate has been specified for the specified candidate. The calculation of the scheduled meeting time and the display of the location and time display screen are as described in FIG. 10.

When the user 14 taps the new setting button 90 on the meeting place narrowing screen 84, the display control unit 58 of the mobile terminal 16 causes the display 34 to display an optional selection screen 98 that allows the user to select an optional meeting place.

Figure 12 is a representative screen diagram of the optional selection screen 98 displayed on the display 34. The optional selection screen 98 has a site map display area 100 and an OK button 104. The user 14 moves the designated marker 102 to a desired location in the site map display area 100 by a sliding operation or the like, and taps the OK button 104. The input reception unit 56 of the mobile terminal 16 accepts it as an instruction to specify a meeting place. The input reception unit 56 transmits the position of the designated marker 102 on the site map when the OK button 104 is tapped to the management server 12 via the network 18. The meeting place designation reception unit 50 receives the position of the designated marker 102 and compares the received position with the range of the NG area. If the received position does not fall within the range of the NG area, the meeting place designation reception unit 50 acquires the received position as the meeting place. In addition, the candidate update unit 52 registers the received position in the site information storage unit 44 as a new candidate corresponding to the site map. The calculation of the scheduled meeting time and the display of the location and time display screen are as described in Figure 10.

When the received location falls within the range of the NG area, the meeting place designation reception unit 50 refers to the site information storage unit 44 to obtain the NG reason. The meeting place designation reception unit 50 generates NG reason display screen information, which is screen information for generating the NG reason display screen 106, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 obtains the NG reason display screen information, and displays the NG reason display screen 106 on the display 34 according to the obtained NG reason display screen information.

Figure 13 is a representative screen diagram of the NG reason display screen 106 displayed on the display 34. The NG reason display screen 106 displays the reason why the designation of the meeting place selected on the optional selection screen 98 is restricted or prohibited. When the user 14 taps the back button 108, the mobile terminal 16 causes the optional selection screen 98 to be displayed again on the display 34.

In the examples of Figures 8 to 13, cases where a site map is available have been described, but for some buildings, the management server 12 does not store a site map. If the site map of the building specified on the building specification screen 68 shown in Figure 9 is not registered in the site information storage unit 44 of the management server 12, and if the building type determination unit 48 determines that the criteria are met, the meeting place specification acceptance unit 50 generates meeting place setting screen information, which is screen information for generating a meeting place setting screen 110 that allows arbitrary selection of a meeting place around the site, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the meeting place setting screen information, and displays the meeting place setting screen 110 on the display 34 according to the acquired meeting place setting screen information.

Figure 14 is a representative screen diagram of the meeting place setting screen 110 displayed on the display 34. The meeting place setting screen 110 has a map designation area 112 and an OK button 116. The map designation area 112 displays an electronic map (i.e., a map of the periphery of the site) of the designated building. In the map designation area 112, the designated building is highlighted (indicated by diagonal hatching in Figure 14). The user 14 moves the designated marker 114 to a desired location in the map designation area 112 by a slide operation or the like, and taps the OK button 116. The input reception unit 56 of the mobile terminal 16 accepts this as an instruction to designate the meeting place. The input reception unit 56 transmits the position of the designated marker 114 on the electronic map when the OK button 116 is tapped to the management server 12 via the network 18. The meeting place designation reception unit 50 receives the position of the designated marker 114 and acquires the received position as the meeting place. The calculation of the scheduled meeting time and the display of the location and time display screen are as described in Figure 10.

Alternatively, if the site map of the building specified on the building specification screen 68 shown in FIG. 9 is not registered in the site information storage unit 44 of the management server 12, the user 14 and the administrator of the PDD system 10 may directly communicate via voice communication or the like, and the administrator may manually set the meeting place.

In the examples of Figures 8 to 13, we have described a case where at least one candidate meeting place has already been registered in the site information storage unit 44, but there may be cases where a candidate meeting place has not yet been registered for a building or the like for which a site map has just been acquired. In relation to Figure 9, if a candidate meeting place for the building specified is not registered in the site information storage unit 44, the display control unit 58 of the mobile terminal 16 causes the display 34 to display the optional selection screen 98 shown in Figure 12 instead of the meeting place narrowing down screen 84 shown in Figure 11.

When calculating the scheduled meeting time in the examples of Figures 8 to 13, the time it takes for the PDD 20 to travel on public roads is calculated from an electronic map. The travel time within the building premises is calculated based on information about past movements within the premises. For example, an average travel time may be calculated and used as the travel time within the premises.

In the examples of Figures 8 to 14, the user 14 can set a new candidate meeting place on the display 34 of the mobile terminal 16, but this is not limited to the above. For example, when the PDD 20 meets with the user 14 at a building for the delivery of goods or the collection of luggage, the PDD 20 may accept the registration of a candidate meeting place by the user 14. The mode in which the PDD 20 accepts the registration of a candidate meeting place is called the registration mode.

Figure 15 is a flow chart showing a series of processing steps in the PDD 20 having the registration mode. The PDD 20, which has departed from the store 22, detects that it has arrived at the set meeting place (S102). The PDD 20 waits for the user 14 to specify the registration mode (S104). For example, the PDD 20 displays on a display unit (not shown) that the registration mode can be set. Alternatively, the PDD 20 may have a registration mode setting button (not shown). If the registration mode is not specified within a predetermined period after the PDD 20 arrives at the meeting place (N in S104), the PDD 20 departs for the next destination if there is one, and if not, starts returning to the store 22 (S118). If the registration mode is specified (Y in S104), the PDD 20 transitions to the registration mode and moves according to the guidance of the user 14 (S106). The PDD 20 checks whether the user 14 has instructed to set a candidate (S108), and if not, the process returns to step S106. Regarding the instruction to set the candidate, for example, the PDD 20 displays an area for receiving the instruction to set the candidate on a display unit (not shown). Alternatively, the PDD 20 may have a candidate setting button (not shown). When the instruction to set the candidate is received (Y in S108), the PDD 20 performs positioning using its own positioning means such as a GPS (S110) and takes an image using its own image capturing means such as a camera (S112). The PDD 20 transmits the position information obtained in step S110 and the image obtained in step S112 to the management server 12 via the network 18 as information identifying the meeting place candidate. The candidate update unit 52 of the management server 12 registers the received position information and image in the site information storage unit 44 as information of a new candidate. The PDD 20 releases the registration mode (S116). If there is a next destination, the PDD 20 departs for it, and if there is not, it starts returning to the store 22 (S118).

With this PDD 20, for example, it is possible to suggest to the user 14 that the meeting place be updated or changed in anticipation of the next delivery. In addition, in the registration mode, the PDD 20 acquires locations that the user 14 has been taken to as candidate meeting places, and has these locations registered in the management server 12. In this case, the location of the candidate meeting place can be directly identified by the positioning means of the PDD 20, so that the accuracy of the candidate location can be improved compared to when it is identified by the positioning means of the mobile terminal 16 of the user 14.

(Example 2)
Phase: Order Receipt Problem: Elimination of Unnatural Orders As shown in Fig. 9 of Example 1, the user 14 can basically specify any location as the meeting place. In this case, there is a risk that the user 14 may misunderstand something and specify a location that is quite far from the user 14's current location as the meeting place. This example provides a fail-safe mechanism for such a situation.

In this example, the mobile terminal 16 uses a positioning means such as GPS to determine its position, and transmits the current location obtained as a result of the positioning to the management server 12 together with the order information. The management server 12 extracts the current location of the mobile terminal 16 and the location of the specified meeting place from the received order information. If the two extracted locations are farther apart than a predetermined standard, the management server 12 generates order rejection screen information, which is screen information for generating an order rejection screen 118 indicating the rejection of the order (delivery of the product 24 or collection of the package), and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the order rejection screen information, and causes the display 34 to display the order rejection screen 118 in accordance with the acquired order rejection screen information.

Figure 16 is a representative screen diagram of the order rejection screen 118 displayed on the display 34. The order rejection screen 118 displays a message indicating that the order is rejected if, for example, the distance between the location of the meeting place specified on the building specification screen 68 shown in Figure 9 of Example 1 and the current location of the mobile device 16 is greater than a threshold value. When the user 14 taps the back button 120, the mobile device 16 causes the building specification screen 68 to be displayed again on the display 34.

The distance threshold may be a distance that a person cannot travel by normal transportation at the time of ordering. For example, if the current location indicates Osaka, a location in Tokyo is specified as the meeting place, the order time is 11:45, and the order is for rice balls, it will be virtually impossible for the user to arrive at the meeting place during lunch time that day, so the order will be rejected.

(Example 3)
Phase: Delivering goods/Waiting at destination Issue: Notifying the status of the PDD As described in relation to steps S318, S320, and S322 in Fig. 2, while the PDD 20 is performing automatic driving to move to the destination along the set route, it measures its current location at any time and reports it to the management server 12 via the network 18. When the PDD 20 arrives at the set meeting place, it waits there. Here, it would be helpful if the user 14 could be notified of the approach of the PDD 20 and also of where the PDD 20 is actually located. By doing so, it is possible to encourage the user 14 to arrive at the meeting place on time, and the waiting time of the PDD 20 at the meeting place can be reduced.

Figure 17 is a block diagram showing the functions and configuration of the management server 12 according to Example 3. The management server 12 includes an image storage unit 138, an electronic map storage unit 42, an order control information storage unit 152, an image acquisition unit 198, a privacy processing unit 200, a cancellation processing unit 190, a PDD position acquisition unit 124, a distance determination unit 126, a notification control unit 128, a status notification screen generation unit 136, and a meeting place change processing unit 182.

The PDD 20 acquires images of the surroundings from time to time as it departs from the store 22, arrives at the meeting place, and returns to the store 22, and transmits the acquired images and current location to the management server 12 via the network 18. The image acquisition unit 198 acquires the images and current location sent from the PDD 20 via the network 18, and registers them in the image storage unit 138.

The privacy processing unit 200 reads an image from the image storage unit 138, performs a predetermined privacy processing on the read image, and registers the processed image in the image storage unit 138. The privacy processing is a process for protecting privacy, and may be, for example, a process that makes the whole or part of a person (e.g., the head) unidentifiable when it is recognized that the person is in the image (e.g., blurring, blacking out, mosaic, etc.). Alternatively, it may be a process that makes an object that can identify an individual, such as a house nameplate or license plate, unidentifiable when it is recognized that the object is in the image.

18 is a data structure diagram showing an example of the image storage unit 138. The image storage unit 138 stores a position (coordinates), an original PDD image obtained by the PDD 20 capturing the surroundings at that position, the acquisition date and time of the original PDD image, an other source image obtained from another image source for that position, a processed image obtained by performing privacy processing on the original PDD image, and the processing date and time of the privacy processing in association with each other. The original PDD image is the image itself received from the PDD 20. The other image source may be, for example, Google Street View. The image acquisition unit 198 acquires images from other image sources and registers them in the image storage unit 138 as other source images. For example, the image acquisition unit 198 may periodically refer to the image storage unit 138, and acquire and register other source images corresponding to positions where there is no original PDD image from other image sources.

FIG. 19 is a data structure diagram showing an example of the order control information storage unit 152. The order control information storage unit 152 stores an order ID that identifies an order, an order time when the order was accepted, an ID of the user 14 who made the order, an ID of the PDD 20 that will transport the ordered product 24, an ID of the store 22 that will load the ordered product 24 onto the PDD 20, a meeting place that is the destination of the PDD 20, an approach threshold, a set of meeting place change candidates and change thresholds, a scheduled arrival time of the PDD 20, a scheduled route of the PDD 20, the ordered product and its quantity, and a cancellation threshold, in association with each other. The set of meeting place change candidates and change thresholds may be dynamically set for each order, or may be set in advance in association with the meeting place. In the latter case, when the meeting place for the order is set, a change candidate corresponding to the meeting place for the order may be determined by referring to a meeting place-change candidate database (not shown).

The user interface provided to the mobile terminal 16 of the user 14 while the PDD 20 is automatically traveling and waiting at the meeting place will be described below with reference to Figures 20 to 29. After the PDD 20 leaves the store 22, until it approaches the meeting place, the display control unit 58 of the mobile terminal 16 basically displays the top screen 122 on the display 34.

Figure 20 is a representative screen diagram of the top screen 122 displayed on the display 34. The top screen 122 does not include information on the current location of the PDD 20 described below, nor an image related to the current location. The PDD location acquisition unit 124 of the management server 12 acquires the current location of the PDD 20 from the PDD 20 via the network 18. The distance determination unit 126 determines whether the current location of the PDD 20 is within a predetermined range based on the meeting place of the PDD 20. Specifically, the distance determination unit 126 refers to the order control information storage unit 152 and acquires an approach threshold, a change threshold corresponding to a change candidate, and a cancellation threshold. The distance determination unit 126 calculates the distance (straight line distance or distance) between the acquired current location of the PDD 20 and the location of the meeting place, and compares the calculated distance with each acquired threshold. In this example, the approach threshold>change threshold, and the approach threshold>cancellation threshold.

The notification control unit 128 does not notify the approach of the PDD 20 while it is determined that the distance calculated by the distance determination unit 126 is equal to or greater than the approach threshold value. In this case, the display control unit 58 of the mobile terminal 16 causes the top screen 122 to be displayed on the display 34. Normally, there is no need for the user 14 to see images of the position of the PDD 20 or the surrounding area when the PDD 20 is near the store 22. Also, from the perspective of privacy protection, it is preferable to limit the presentation of unnecessary images.

When it is determined that the distance calculated by the distance determination unit 126 falls below the approach threshold, the notification control unit 128 generates approach notification screen information, which is screen information for generating an approach notification screen 130 that notifies the user 14 of the approach of the PDD 20, and transmits the information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the approach notification screen information, and displays the approach notification screen 130 on the display 34 in accordance with the acquired approach notification screen information.

Figure 21 is a representative screen diagram of the approach notification screen 130 displayed on the display 34. The approach notification screen 130 includes a message 132 for informing the user 14 of the approach of the PDD 20. When the user 14 taps the display button 134, the input reception unit 56 of the mobile terminal 16 sends a display instruction to the management server 12 via the network 18. The notification control unit 128 of the management server 12 receives the display instruction.

When the display instruction is received, the status notification screen generating unit 136 of the management server 12 refers to the image storage unit 138 and acquires a processed image corresponding to the current position of the PDD 20 acquired by the PDD position acquiring unit 124. The processed image acquired in this way is not a current image corresponding to the current position, but a past image corresponding to the current position. In other words, the acquired processed image is not an image currently acquired by the PDD 20 delivering the product 24 to the user 14 for the order, but an image acquired by processing another PDD 20 or the PDD 20 during operation for another past order, etc. If a processed image corresponding to the current position is not registered, the status notification screen generating unit 136 may acquire other source images if there are other source images. If there is neither a processed image corresponding to the current position nor another source image, the status notification screen generating unit 136 may acquire an original PDD image corresponding to the current position and use it after performing privacy processing. If there is no original PDD image, processed image, or other source image corresponding to the current location, the status notification screen generating unit 136 may not acquire an image, or may instruct the PDD 20 to capture and send an image of the surroundings.

The status notification screen generation unit 136 refers to the electronic map storage unit 42 and obtains a portion of the electronic map large enough to include both the current location of the PDD 20 and the meeting place. The status notification screen generation unit 136 obtains the current location of the PDD 20 from the PDD position acquisition unit 124. The status notification screen generation unit 136 refers to the order control information storage unit 152 and obtains the ID of the PDD 20, the planned route, the meeting place, the product, the quantity, the expected arrival time, and possible changes to the meeting place.

The status notification screen generating unit 136 generates status notification screen information, which is screen information for generating the status notification screen 140, based on the information acquired as described above. The status notification screen generating unit 136 transmits the status notification screen information to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the status notification screen information, and displays the status notification screen 140 on the display 34 in accordance with the acquired status notification screen information.

Figure 22 is a representative screen diagram of the status notification screen 140 displayed on the display 34. The status notification screen 140 has an image display area 142 and a position display area 144. The image display area 142 displays a processed image corresponding to the current position of the PDD 20. The position display area 144 displays a meeting place 146, a planned route 148 for the PDD 20, the current position 150 of the PDD 20, possible changes to the meeting place 156, 158, and a cancel button 154 in accordance with the above-mentioned electronic map portion. The meeting place 146 and the possible changes 156, 158 are displayed in different ways in the position display area 144.

By looking at the status notification screen 140, the user 14 can get a detailed understanding of where the nearby PDD 20 actually is, and by looking at the image display area 142 in particular, the user 14 can get a sense of where the PDD 20 is currently located. In addition, because the image displayed in the image display area 142 is a processed image, privacy issues are also reduced or eliminated.

When the user 14 taps the cancel button 154 on the status notification screen 140, the input reception unit 56 of the mobile terminal 16 accepts it as an instruction to cancel the order. The input reception unit 56 transmits the instruction to the management server 12 via the network 18. When the cancellation processing unit 190 of the management server 12 receives the instruction, it executes the cancellation process without incurring a cancellation fee.

When the user 14 taps the image display area 142 on the status notification screen 140, the display control unit 58 of the mobile terminal 16 causes the display 34 to display a detailed text screen 160 that displays the order details in text.

Figure 23 is a representative screen diagram of the detailed text screen 160 displayed on the display 34. The detailed text screen 160 has a text display area 162 and a position display area 144. The text display area 162 is displayed in place of the image display area 142, and displays in text the ID of the PDD 20, the product name and quantity related to the order, the meeting place (destination), and the estimated time of arrival. The detailed text screen 160 allows the user 14 to check the contents of their order with a single tap, i.e., with a minimal amount of operation.

When the user 14 taps the first change candidate 156 on the status notification screen 140, the display control unit 58 of the mobile terminal 16 displays on the display 34 a reset inquiry screen 164 that inquires whether it is OK to reset the meeting location. The same process is also performed when the second change candidate 158 is tapped.

24 is a representative screen diagram of the reset inquiry screen 164 displayed on the display 34. The reset inquiry screen 164 has an image display area 142, a position display area 144, and a reset inquiry area 166 superimposed on the position display area 144. The reset inquiry area 166 displays text 168 inquiring whether the tapped first change candidate 156 may be set as a new meeting place, a YES button 170, and a NO button 172. When the user 14 taps the NO button 172, the screen transitions back to the status notification screen 140. When the user 14 taps the YES button 170, the display control unit 58 of the mobile terminal 16 causes the display 34 to display a meeting place update screen 174 indicating that the first change candidate 156 has been set as the new meeting place.

25 is a representative screen diagram of the meeting place update screen 174 displayed on the display 34. The meeting place update screen 174 has an image display area 142 and a position display area 144. In the position display area 144, the display of the first change candidate 156 is updated to the meeting place 176, and the planned route 178 is also changed accordingly. A message 180 indicating that the meeting place has been changed is superimposed on the position display area 144. In conjunction with displaying the meeting place update screen 174 on the display 34, the input reception unit 56 of the mobile terminal 16 receives a tap on the YES button 170 as an instruction to change the meeting place. The input reception unit 56 transmits an instruction to change the meeting place to the first change candidate 156 to the management server 12 via the network 18. Upon receiving the instruction, the meeting place change processing unit 182 of the management server 12 updates the order control information storage unit 152. That is, the meeting place change processing unit 182 replaces the meeting place of the corresponding order in the order control information storage unit 152 with the new meeting place (first change candidate 156) included in the instruction, replaces the planned route with a new planned route with the new meeting place as the destination, and replaces the scheduled arrival time with a new scheduled arrival time corresponding to the new meeting place. The meeting place change processing unit 182 transmits the new meeting place and the new planned route to the PDD 20 via the network 18. The PDD 20 continues automatic driving toward the received new meeting place according to the received new planned route.

Returning to FIG. 22, the status notification screen generation unit 136 of the management server 12 periodically generates and transmits the status notification screen 140, for example at a predetermined time interval (such as one second, ten second, or one minute). When generating the status notification screen 140 for the second or subsequent times, the status notification screen generation unit 136 updates only the display of the current location 150 on the status notification screen 140 shown in FIG. 22 while it is determined that the distance calculated by the distance determination unit 126 is equal to or greater than the change threshold value. The display control unit 58 of the mobile terminal 16 causes the display 34 to display the updated current location 150.

In the example of FIG. 22, the first change candidate 156 and the second change candidate 158 correspond to the first change threshold and the second change threshold, respectively, and the first change threshold is greater than the second change threshold. While it is determined that the distance calculated by the distance determination unit 126 is greater than or equal to the first change threshold, both the first change candidate 156 and the second change candidate 158 can be specified as new meeting places on the situation notification screen 140.

Assume that the PDD 20 approaches the meeting place 146 from the state shown in FIG. 22, and it is determined that the distance calculated by the distance determination unit 126 falls below the first change threshold. In this case, the situation notification screen generation unit 136 restricts or prohibits re-designation of the meeting place on the situation notification screen 140. If the situation notification screen generation unit 136 determines that the distance calculated by the distance determination unit 126 falls below the first change threshold but is equal to or greater than the second change threshold, it updates the situation notification screen 140 to prohibit designation of the first change candidate 156. The display control unit 58 of the mobile terminal 16 causes the display 34 to display the situation notification screen 140 thus updated.

Figure 26 is a representative screen image of the status notification screen 140 when it is determined that the distance between the PDD 20 and the meeting place is less than the first change threshold but is equal to or greater than the second change threshold. The current position 150 of the PDD 20 is closer to the meeting place 146 than that in Figure 22, and therefore the first change candidate 184 cannot be specified. In order to indicate that the first change candidate 184 cannot be specified, for example, the first change candidate 184 may be displayed in a manner different from both the meeting place 146 and the second change candidate 158. Alternatively, the display of the first change candidate 184 may simply be stopped.

Let us assume that the PDD 20 approaches the meeting place 146 from the state shown in FIG. 26, and the distance calculated by the distance determination unit 126 is determined to be below the second change threshold. In this case, the status notification screen generation unit 136 updates the status notification screen 140 so as to prohibit the designation of the second change candidate 158. The display control unit 58 of the mobile terminal 16 causes the display 34 to display the status notification screen 140 thus updated.

Figure 27 is a representative screen image of the situation notification screen 140 when it is determined that the distance between the PDD 20 and the meeting place is below the second change threshold. The current position 150 of the PDD 20 is closer to the meeting place 146 than that in Figure 26, and therefore the second change candidate 186 as well as the first change candidate 184 cannot be specified.

In the status notification screen 140 of FIG. 22, the current location 150 of the PDD 20 is far from the meeting place 146, so the cancellation process related to the cancel button 154 is free. In contrast, in the status notification screen 140 of FIG. 27, the current location 150 of the PDD 20 is close to the meeting place 146, so cancellation is subject to a fee. Accordingly, in the status notification screen 140 shown in FIG. 27, the cancel button 154 is replaced with a fee-based cancel button 188.

When the distance calculated by the distance determination unit 126 is determined to be below the cancellation threshold, the status notification screen generation unit 136 updates the status notification screen 140 to replace the cancel button 154 with a paid cancel button 188. When the user 14 taps the paid cancel button 188 on the updated status notification screen 140, the input acceptance unit 56 of the mobile terminal 16 accepts this as an instruction to cancel the order. The input acceptance unit 56 transmits the instruction to the management server 12 via the network 18. Upon receiving the instruction, the cancellation processing unit 190 of the management server 12 executes cancellation processing in which a cancellation fee is charged.

Let us assume that the PDD 20 approaches the meeting place 146 from the state shown in FIG. 27 and it is determined that the PDD 20 has arrived at the meeting place 146. In this case, the status notification screen generating unit 136 updates the status notification screen 140 to notify the arrival of the PDD 20 at the meeting place 146. The display control unit 58 of the mobile terminal 16 causes the display 34 to display the status notification screen 140 thus updated.

Figure 28 is a representative screen diagram of the status notification screen 140 when it is determined that the PDD 20 has arrived at the meeting place 146. In the position display area 144 of this status notification screen 140, a decorative display 192 for emphasizing the arrival of the PDD 20 and a message 194 informing of the arrival are displayed. The message 194 also displays the waiting time of the PDD 20 at the meeting place 146.

The user 14 can be informed of the arrival of the PDD 20 by the status notification screen 140 shown in FIG. 28, and can more accurately determine where the meeting location is by looking at the image display area 142.

When the management server 12 receives a signal indicating the completion of the delivery of the product 24 from the PDD 20 or the mobile terminal 16 of the user 14 via the network 18, it generates transaction completion screen information, which is screen information for generating a transaction completion screen 196, and transmits it to the mobile terminal 16 via the network 18. The display control unit 58 of the mobile terminal 16 acquires the transaction completion screen information, stops the display of the status notification screen 140, and displays the transaction completion screen 196 on the display 34 in accordance with the transaction completion screen information.

Figure 29 is a representative screen diagram of a transaction completion screen 196 displayed on the display 34. With the transaction completion screen 196, the user 14 can no longer see images associated with the location of the PDD 20, but this is fine since the user 14 typically does not care about the return journey of the PDD 20. Also, from the perspective of privacy protection, it is desirable to limit the presentation of unnecessary images.

In this example, a case has been described in which a past privacy-processed image corresponding to the current location of the PDD 20 is used as the image to be displayed in the image display area 142, but this is not limited to the above. For example, the status notification screen generating unit 136 may obtain an image of the surroundings from the PDD 20 via a network, and perform privacy processing on the obtained image of the surroundings in real time. In this case, the image display area 142 displays an image that has been privacy-processed and is currently obtained by the PDD 20 that is delivering the product 24 to the user 14 for the order.

In this example, the case where the status notification screen 140 is displayed on the display 34 using the PDD app has been described, but this is not limited to the above. For example, if the user 14 has registered an email address with the management server 12, the notification control unit 128 may send an email including a URL to the email address of the user 14 related to the order when it is determined that the PDD 20 is approaching the meeting place. The URL identifies the web page that displays the status notification screen 140. In this case, the user 14 can be notified of the approach of the PDD 20 even if the user 14 has not launched the PDD app.

(Example 4)
Phase: Product delivery in progress Task: Cooperation with delivery truck As described in relation to steps S318, S320, and S322 in FIG. 2, while the PDD 20 is autonomously traveling to the destination along a set route, it measures its current location at any time and reports it to the management server 12 via the network 18. In addition, in this example, the management server 12 also obtains the current location of a delivery truck carrying inventory via the network 18. The delivery truck is usually used to transport the product 24 between a warehouse and a store 22, or between the stores 22. The delivery truck is configured to be able to deliver the product 24 to the PDD 20 manually or automatically.

The management server 12 has a display 202, on which a management screen 204 including an electronic map and the operation status of the PDD 20 and the delivery truck is displayed. The manager manages the operation of the PDD 20 and the delivery truck by looking at the management screen 204 displayed on the display 202.

Figure 30 is a representative screen diagram of the management screen 204 displayed on the display 202. The management server 12 displays on an electronic map the operating status of the PDD 20 and the operating status of the delivery truck based on the acquired current position of the PDD 20 and the acquired current position of the delivery truck. The management server 12 accepts, on the management screen 204, the specification of the location where the PDD 20 and the delivery truck are scheduled to meet.

The management screen 204 has an electronic map display area 206 and a detail display area 208. In the electronic map display area 206, the current position 210 of the PDD 20, the planned route 212 of the PDD 20, the destination (meeting place) 214 of the PDD 20, the store 216 to which the PDD 20 will return, the current position 218 of the delivery truck, the planned route 222 of the delivery truck, and a candidate meeting place 220 for the PDD 20 and the delivery truck are displayed together with the electronic map. The detail display area 208 has a PDD information display area 224 that displays the ID and status of the PDD 20 displayed in the electronic map display area 206, a truck information display area 226 that displays the ID and status of the delivery truck displayed in the electronic map display area 206, and a PDD detail display area 228 that displays in text the ID of the PDD 20 selected in the PDD information display area 224, the product name and quantity related to the order, the destination, and the expected arrival time. The truck information display area 226 includes a link to a screen showing the inventory of delivery trucks. The candidates 220 may be determined by the management server 12 based on the current location and planned route of the PDD 20 and the current location and planned route of the delivery truck.

By looking at the management screen 204 shown in FIG. 30, the manager determines whether it is beneficial to have the PDD 20 and the delivery truck meet. If it is beneficial, the manager determines the location where the PDD 20 and the delivery truck will meet, and performs processing to guide both of them to the determined location. For example, the management server 12 may transmit instructions to the target PDD 20 via the network 18 to set a new destination (= determined location). The management server 12 may also transmit similar information to the delivery truck via the network 18, or the manager may directly give instructions to the driver of the delivery truck by telephone, etc. When these instructions are completed, the management server 12 accepts the designation of the location where the PDD 20 and the delivery truck are scheduled to meet, and updates the display of the electronic map display area 206.

Alternatively, the administrator may specify a candidate 220 displayed in the electronic map display area 206 with a mouse or the like. In this case, the management server 12 accepts the specified candidate 220 as the location where the PDD 20 and the delivery truck are scheduled to meet. The process for guiding the target PDD 20 and delivery truck to the specified location is the same as described above.

In this example, the administrator can direct the delivery truck loaded with the stocked items to a specified point depending on the order status. As a result, the items 24 can be loaded onto the PDD 20 at the relay point, enabling faster delivery.

In this example, the case where the management screen 204 is displayed on the display 202 of the management server 12 has been described, but this is not limited thereto. For example, the management screen 204 may be displayed on a POS in the store 22, or on the display 34 of the mobile terminal 16 of the user 14.

(Example 5)
Phase: Waiting at destination Task: Identifying the PDD at the time of delivery As described in relation to step S322 in FIG. 2, when the PDD 20 arrives at the set meeting place, it waits there. Here, when multiple PDDs 20 are to meet the user 14 at the same meeting place and the same time period, a situation may occur in which the user 14 cannot identify his/her own PDD 20. Therefore, in this example, the color (paint) of the PDD 20 itself and the color of light emitted by the light-emitting means such as LEDs provided in the PDD 20 are used as identification information of the PDD 20. For example, when multiple PDDs 20 are to wait at the same meeting place at the same time period, the color of light emitted by each PDD 20 is adjusted so as not to overlap within a predetermined range (for example, a range of a radius of 100 m).

Figure 31 is a representative screen diagram of an approach notification screen 230 displayed on the display 34 of the mobile terminal 16. The approach notification screen 230 corresponds to the approach notification screen 130 shown in Figure 21. The approach notification screen 230 displays a message 132 to inform the user 14 of the approach of a PDD 20, and a message 232 to inform the user 14 of the color of light emitted by the PDD 20 corresponding to the user 14. By referring to the information shown on the approach notification screen 230, the user 14 can easily identify his/her own PDD 20 even if multiple PDDs 20 are waiting at the meeting place. In the example of Figure 31, the user 14 recognizes the PDD 20 emitting red light at the meeting place as his/her own PDD 20. Here, the color of the light-emitting means is used as the identification method, but the type of blinking timing may also be used for identification.

Note that other information that can be perceived by humans, such as sound or shape, may be used as the identification information.
Alternatively, a plurality of PDDs 20 may recognize the distance between each other at the meeting place and park a predetermined distance apart, making it easier for the user 14 to identify the PDDs 20. In this case, when it is determined that the PDD 20 has arrived at the destination, the PDD 20 has a means for performing a process for waiting at a position that avoids the waiting positions of other PDDs 20 at the destination. For example, the PDD 20 has a means for performing peer-to-peer communication such as Bluetooth (registered trademark) or infrared communication. The PDD 20 cooperates with other PDDs 20 through peer-to-peer communication to determine its own waiting position.

Alternatively, if a situation may arise in which multiple PDDs 20 arrive at the same meeting place at the same time, the arrival time of the PDD 20 with the later order time may be shifted.

(Example 6)
Phase: Waiting at destination Problem: User does not come to pick up As described in relation to step S322 in Fig. 2, when the PDD 20 arrives at the set meeting place, it waits there. Here, it may happen that the user 14 who placed the order does not come to the meeting place due to some circumstances. In this example, the action taken by the PDD system 10 in such a case will be described.

Figure 32 is a flowchart showing a series of processing steps in the PDD system 10. The PDD 20 arrives at the meeting place (S402). The PDD 20 times the waiting time at the meeting place. If the PDD 20 and the user 14 meet before the waiting time exceeds the first threshold (N in S404), a normal product 24 handover process (e.g., steps S328 and S330 in Figure 3) occurs. If the waiting time exceeds the first threshold without a meeting (Y in S404), the PDD 20 sends a confirmation message addressed to the user 14 via the management server 12 over the network 18 (S406). If the PDD 20 and the user 14 meet before the waiting time exceeds the second threshold (>first threshold) ("Meeting" in S408), a normal product 24 handover process occurs. If the user 14 responds to the confirmation message before the waiting time exceeds the second threshold ("Response" in S408), the PDD 20 or the management server 12 determines whether the response indicates that the user 14 will not be able to make the appointment in time (S410). If the user 14 will be able to make the appointment in time (N in S410), the PDD 20 continues to wait and meets the user 14. If the user 14 will not be able to make the appointment in time (Y in S410), the PDD 20 or the management server 12 performs a process to reset the meeting place and meeting time (S412). Alternatively, the PDD 20 or the management server 12 may cancel the order instead of such a reset process. The reset process may be, for example, a process to reset the planned route of the PDD 20 so that if the PDD 20 has another delivery destination, it will first visit that destination and then visit the destination again on the way back, or a process to deliver the same product at the same or a different meeting place on a different date and time.

If the waiting time exceeds the second threshold without a response or meeting in step S408 (Y in S408), the PDD 20 sends a reconfirmation message addressed to the user 14 via the management server 12 over the network 18 (S414). If the PDD 20 and the user 14 meet before the waiting time exceeds the third threshold (>second threshold) ("Meeting" in S416), a normal product 24 handover process occurs. If the user 14 responds to the reconfirmation message before the waiting time exceeds the third threshold ("Response" in S416), the PDD 20 or management server 12 determines whether the response indicates that the user will not be able to make the meeting on time (S410).

If the waiting time exceeds the third threshold without a response or meeting in step S416 (Y in S416), the PDD 20 or the management server 12 automatically calls the mobile terminal 16 of the user 14 (S418). If there is a response to the call (N in S420), the process proceeds to step S410. If there is no response to the call (Y in S420), the PDD 20 stops waiting at the meeting place and starts automatically moving to the next destination if there is one, or starts returning to the store 22 if there is no destination (S422). The management server 12 executes a penalty process to impose a monetary or procedural penalty on the user 14 (S424). The penalty process may be, for example, a cancellation fee for cancellation without prior notice, or a process to refuse future orders by registering the user on a blacklist.

In step S420, if there is no response to the automated call, manual confirmation may be triggered by inquiring of the administrator. In this case, the administrator checks the order status, etc. to determine whether the PDD 20 has returned, and calls the mobile terminal 16 as necessary.

(Example 7)
Phase: Order Reception Issue: Notifying the Recipient When the Gift is Delivered by the PDD As described in relation to step S302 in FIG. 2, when the user 14 orders the product 24, the user 14 specifies a meeting place to meet the PDD 20. Here, as in the case of gift delivery, the orderer and the recipient of the product 24 may be different. In this case, the recipient may not necessarily know that the delivery will be made by the PDD 20. Therefore, a mechanism is needed to inform the recipient, who is different from the orderer, that the delivery will be made by the PDD 20.

In this example, when the management server 12 receives an order in which the orderer and the recipient are different, it inquires of the recipient, and if consent to delivery by the PDD 20 is obtained, delivery is performed by the PDD 20. If consent is not obtained, normal delivery is performed.

Figure 33 is a flowchart showing a series of processing steps in the management server 12. The management server 12 receives order information specifying a recipient different from the orderer from the terminal of the orderer via the network 18 (S502). When the order is confirmed by completing the payment process, the management server 12 transmits an agreement confirmation message to the terminal of the recipient via the network to inquire whether the recipient agrees to receive the item (S504). As a method for identifying the terminal of the recipient, for example, if the recipient has already been registered in the PDD system 10, the terminal of the recipient may be identified by the registration information. If the terminal of the recipient is online, the management server 12 may transmit the agreement confirmation message to the terminal of the recipient. If the email address of the terminal of the recipient is registered, the management server 12 may transmit the agreement confirmation message to the address. Alternatively, if the recipient is not registered in the PDD system 10, the management server 12 may inquire about the email address of the recipient from the terminal of the orderer. Alternatively, when obtaining the order information from the orderer, the management server 12 may have the orderer input information for identifying the terminal of the recipient.

The management server 12 receives a response to the consent confirmation message from the recipient's terminal via the network 18. If the response indicates non-consent (N in S506), or if a response to the consent confirmation message is not received within a predetermined period of time, the management server 12 executes processing to perform normal delivery (S508). The normal delivery may be any delivery method other than delivery using the PDD 20.

If the response to the consent confirmation message indicates consent (Y in S508), the management server 12 starts processing to direct the PDD 20 to the destination corresponding to the recipient. The management server 12 judges whether the recipient is already registered in the PDD system 10, i.e., whether the recipient has received delivery by the PDD system 10 (S510). For example, since the order control information storage unit 152 shown in FIG. 19 stores the order history, the management server 12 judges whether the ID of the recipient is registered in the order control information storage unit 152. If the recipient is already registered (Y in S510), the management server 12 executes processing to perform delivery by the PDD 20 using the registered recipient's information (S512). If the recipient is not registered (N in S510), the management server 12 performs delivery verification (S514). Then, the process proceeds to step S512.

(Example 8)
Phase: When the PDD breaks down Issue: Repair/recovery of the PDD, and delivery of the goods in the broken PDD Since the PDD 20 runs automatically without a human driver, what to do when it breaks down during delivery or on the way back to the base is a problem. There are two issues: the first is how to recover the broken PDD 20, and the second is how to deliver the goods 24 loaded on the broken PDD 20.

The PDD 20 in this example monitors itself, and when a fault is detected, generates fault information indicating the location and nature of the detected fault, and transmits this information to the management server 12 via the network 18.

Figure 34 is a flowchart showing a series of processing steps in the management server 12. The management server 12 receives failure information from the PDD 20 via the network 18 (S602). The management server 12 has a failure response storage unit (not shown) that previously stores failure information in association with a failure level. The failure levels are expressed, for example, as four levels, from level 1 to level 4. Level 1 is "business continuity possible," level 2 is "return to base possible," level 3 is "on-site evacuation possible," and level 4 is "power cut off soon." The administrator assigns one of levels 1 to 4 to the expected type and location of the failure, and registers it in the failure response storage unit.

The management server 12 refers to the failure response storage unit and acquires the failure level corresponding to the received failure information (S604). The management server 12 judges whether the broken PDD 20 is self-propelled or not based on the acquired failure level (S606). For example, if the failure level is level 1 or level 2, the management server 12 judges that the broken PDD 20 is self-propelled. If the failure level is level 3 or level 4, the management server 12 judges that the broken PDD 20 is not self-propelled. If the management server 12 judges that the broken PDD 20 is self-propelled (Y in S606), it transmits a return instruction to the broken PDD 20 via the network 18 (S608). If the management server 12 judges that the broken PDD 20 is not self-propelled (N in S606), it performs a recovery process to recover the broken PDD 20 by another PDD 20 or a recovery means such as a delivery truck (S610). For example, the management server 12 transmits a recovery instruction including the location of the broken PDD 20 to another PDD 20 waiting at the store 22 via the network 18. Upon receiving the collection instruction, the PDD 20 automatically travels to the specified location, connects the broken PDD 20 (by connecting wires, etc.), and takes it back to the store 22.

Alternatively, the management server 12 transmits a collection instruction including the location of the broken PDD 20 to a nearby delivery truck via the network 18. The delivery truck that receives the collection instruction indicates the location of the broken PDD 20 to the driver using a navigation system or the like. The driver heads to the indicated location and loads the broken PDD 20 onto the delivery truck.

The management server 12 performs an alternative delivery process to deliver the product 24 loaded on the broken PDD 20 to the user 14 (S612). For example, the management server 12 transmits an instruction to the store 22 via the network 18 to load the same product 24 as loaded on the broken PDD 20 onto another PDD 20. The management server 12 also transmits the meeting location of the broken PDD 20 to the other PDD 20 via the network 18. A staff member at the store 22 loads the product 24 onto the other PDD 20, and the other PDD 20 starts automatic driving to the specified meeting location.

Alternatively, the management server 12 transmits alternative delivery instructions, including the location of the broken PDD 20 and the meeting place of the broken PDD 20, via the network 18 to other PDDs 20 waiting in the store 22. The PDDs 20 that receive the alternative delivery instructions automatically travel to the location of the broken PDD 20, receive and store the product 24 from the broken PDD 20, and automatically travel to the designated meeting place in place of the broken PDD 20. This is particularly effective when the product 24 loaded on the broken PDD 20 is an out-of-stock product or a unique product.

In this example, the failure level is determined by the management server 12, but this is not limited to the above. The failure level may be determined by the PDD 20, and the PDD 20 may then report the failure level to the management server 12.

(Example 9)
Phase: During product delivery or during return to base Issue: Product handover between PDDs As mentioned in Example 8, handover of products 24 between PDDs 20 is advantageous in various situations. For example, when a returning PDD 20 having empty storage spaces 26 passes another PDD 20 heading to a meeting place with products 24 loaded in all storage spaces 26, if the latter PDD 20 can hand over some of the products 24 to the former PDD 20, delivery efficiency will improve.

Example 8 describes a case where PDDs 20 automatically transfer products 24 to each other. This requires that the PDDs 20 be equipped with a dedicated transfer mechanism, which creates a trade-off with costs. In this example, a case is described where products 24 are transferred between PDDs 20 by a person in a place where people are present, such as a convenience store. This limits the places where transfers can be made, but alleviates the cost issue.

Figure 35 is a representative screen diagram of the management screen 234 displayed on the display 202 of the management server 12. The management screen 234 corresponds to the management screen 204 shown in Figure 30. The management screen 234 has an electronic map display area 236 and a detailed display area 238. In the electronic map display area 236, together with the electronic map, a current position 240 of the PDD 20, a planned route 242 of the PDD 20, a destination (meeting place) 244 of the PDD 20, a store 246 to which the PDD 20 will return, a candidate meeting place 248 for the PDDs 20, and a delivery store 254 associated with the candidate 248 are displayed. The details display area 238 has a PDD information display area 250 that displays the ID and status of the PDD 20 displayed in the electronic map display area 236, and a PDD details display area 252 that displays in text the ID of the PDD 20 selected in the PDD information display area 250, the product name and quantity related to the order, the destination, and the estimated arrival time.

The management server 12 has a transferable location holding unit (not shown) that holds the locations of multiple delivery stores 254 where the product 24 can be delivered between the PDDs 20. The management server 12 receives the current locations of both the PDD 20 (No. 63) in delivery and the PDD 20 (No. 52) returning to base via the network 18. The management server 12 selects a location where the two PDDs 20 should meet from among the multiple locations held in the transferable location holding unit based on the acquired current locations. For example, the management server 12 selects the location of the delivery store 254 that is closest to one of the two received current locations from among the locations held in the transferable location holding unit. The management server 12 selects the location of the delivery store 254 that is closest to the other of the two received current locations from among the locations held in the transferable location holding unit. The management server 12 displays the two selected locations in the electronic map display area 236 as candidates 248 for the meeting location between the PDDs 20.

When one of the two displayed location candidates 248 is specified, the management server 12 transmits instructions to the PDD 20 (No. 63) in delivery and the PDD 20 (No. 52) returning to the designated candidate 248 via the network 18. When the two PDDs 20 meet at the designated candidate 248, the management server 12 transmits instructions including information specifying the product to be handed over to the POS of the delivery store 254 via the network 18. When the POS receives the instructions, it displays a screen on the display prompting the delivery of the product. The clerk of the delivery store 254 looks at the screen and executes the delivery of the product 24 between the two PDDs 20. Here, the POS may be a portable POS terminal, and the status of the selected product 24 may be changed to the status that the selected product 24 has been stored in the delivery destination PDD 20 by an employee reading the barcode of the selected product 24. Alternatively, the PDD may be equipped with a camera or barcode function, and the barcode of the selected product 24 may be read using the camera or barcode function to change the status in a similar manner.

(Example 10)
Phase: Product Delivery/Waiting at Destination Problem: Effective Sales Promotion The PDD 20 has a plurality of storage spaces 26 each capable of storing a product 24 or luggage. When a user 14 places an order and heads to a designated meeting place, it is wasteful to leave the storage spaces 26 other than the storage space 26 that stores the ordered product 24 empty. In this example, a product that matches the empty storage space 26 or a product derived from the target user's past order history is proposed to a user who can deliver on the determined route. Note that the following describes a case where the product 24 related to the recommendation is loaded into the empty storage space 26, but this is not limited thereto, and the user may be suggested to pick up the product and the luggage from the user may be loaded into the empty storage space 26.

Figure 36 is a block diagram showing the functions and configuration of the management server 12 according to Example 10. The management server 12 includes a user information storage unit 256, an order control information storage unit 152, a destination/route determination unit 258, a promotion target identification unit 260, a recommendation generation unit 262, and a recommendation distribution unit 264.

Figure 37 is a data structure diagram showing an example of the user information storage unit 256 of Figure 36. The user information storage unit 256 stores, in association with each other, the user ID of the user 14, a terminal ID that identifies the mobile terminal 16 of the user 14, the email address of the user 14, the latest location of the mobile terminal 16 received from the mobile terminal 16 of the user 14, a previous meeting place that is the meeting place in the previous order of the user 14, a frequent meeting place that is the meeting place most frequently specified in the orders of the user 14, and an order ID that identifies an order placed in the past by the user 14. The previous meeting place and frequent meeting places are added and updated as appropriate by an order information analysis unit (not shown) analyzing the order control information storage unit 152.

Returning to FIG. 36, the destination/route determination unit 258 receives order information, including information on the product 24 selected by the user 14 and information on the specified meeting place, from the mobile terminal 16 via the network 18. The destination/route determination unit 258 extracts the meeting place information from the received order information and sets it as the destination of the PDD 20. The destination/route determination unit 258 uses a predetermined navigation algorithm to determine a route between the store 22 where the PDD 20 is waiting and the specified meeting place.

The promotion target identification unit 260 refers to the user information storage unit 256 and identifies users (hereinafter referred to as promotion target users) who can meet with the PDD 20 based on at least one of the destination and route locations determined by the destination/route determination unit 258.

Figure 38 is an explanatory diagram for explaining the specification process in the promotional target specification unit 260. Assume that the destination/route determination unit 258 sets the destination 268 and the planned route 270. The promotional target specification unit 260 sets a predetermined area based on the destination 268. In the example of Figure 38, the promotional target specification unit 260 sets a circular area 272 centered on the destination 268. The promotional target specification unit 260 sets a predetermined area based on the planned route 270. In the example of Figure 38, the promotional target specification unit 260 sets a band area 274 centered on the planned route 270. The promotional target specification unit 260 refers to the user information storage unit 256 and acquires the latest location of the user. If the latest location is unavailable, the promotional target specification unit 260 acquires the previous meeting place. If the previous meeting place is unavailable, the promotional target specification unit 260 acquires the frequent meeting place. In Figure 38, both the open circle and the filled circle indicate the user's location acquired as described above. The promotional target identification unit 260 compares the acquired user position with the circular area 272 and the band area 274. If the user position falls within both the circular area 272 and the band area 274, the promotional target identification unit 260 identifies the user as a promotional target user. If not, the promotional target identification unit 260 does not identify the user as a promotional target user. In the example of FIG. 38, the user corresponding to the position indicated by the black circle is identified as a promotional target user.

The promotion target identification unit 260 may identify a user as a promotion target user if the user's position falls within at least one of the circular area 272 and the band area 274. Alternatively, the promotion target user may be identified based on an inclusion relationship with respect to the circular area 272 without setting the band area 274. The promotion target user may be identified based on an inclusion relationship with respect to the band area 274 without setting the circular area 272.

36, the recommendation generation unit 262 generates recommendation information related to the sale of the product 24. In this example, the following two criteria are adopted as recommendation criteria.
(1) Matching with the size of the empty storage space 26 (2) Matching with the order history of the promotion target user

(1) Regarding matching with the size of the empty storage space 26, the recommendation generation unit 262 generates a size matching table 276 that summarizes, for each storage space 26 and for each product, whether the product 24 can fit into the empty storage space 26.

39 is a data structure diagram showing an example of the size matching table 276. In the example of FIG. 39, there are five storage spaces, and the product 24 is stored in storage space "2". The remaining storage spaces "1", "3", "4", and "5" are empty. The recommendation generation unit 262 compares the size of each empty storage space with the size of the product, and if the former is larger than the latter including the margin, it registers that it can be stored ("○"), and if not, it registers that it cannot be stored ("×"). In the example of FIG. 39, the product "1" is small and can be stored in all of storage spaces "1", "3", "4", and "5", while the product "11" is large and can only be stored in storage space "5", which is the largest of storage spaces "1", "3", "4", and "5". The recommendation generation unit 262 refers to the size matching table 276 and identifies products that can be stored as candidates for products to be promoted.

(2) Matching with the order history of the promotion target user: The recommendation generation unit 262 acquires the past order history of the promotion target user identified by the promotion target identification unit 260 from the order control information storage unit 152. The recommendation generation unit 262 analyzes the acquired order history. Based on the analysis result, the recommendation generation unit 262 identifies a promotion target product that matches the promotion target user from among the candidates for the promotion target products identified above. For example, the recommendation generation unit 262 identifies a product that is likely to be purchased by the promotion target user by the scheduled delivery time of the product 24 stored in the storage space "2" from the order history. If the product identified in this way is a candidate for the promotion target product, the recommendation generation unit 262 identifies the candidate as the promotion target product. As a result, the identified promotion target product is one that can be stored in the empty storage space 26 and is in line with the preferences of the promotion target user.

The recommendation generation unit 262 includes information on the identified promotional product in the recommendation information. The recommendation generation unit 262 calculates multiple different scheduled delivery times for the promotional product based on the destination and route determined by the destination/route determination unit 258. The destination/route determination unit 258 determines a delivery fee for each of the calculated multiple scheduled delivery times. The recommendation generation unit 262 includes the calculated multiple scheduled delivery times and the determined delivery fee in the recommendation information.

The recommendation distribution unit 264 transmits the recommendation information generated by the recommendation generation unit 262 to the mobile terminal of the promotion target user identified by the promotion target identification unit 260 via the network 18. If the mobile terminal of the promotion target user is running a PDD app, the recommendation distribution unit 264 may transmit the recommendation information using the terminal ID registered in the user information storage unit 256. Alternatively, the recommendation distribution unit 264 may transmit an email including the recommendation information to an email address registered in the user information storage unit 256.

Figure 40 is a representative screen diagram of the recommendation screen 278 displayed on the display 34 of the mobile terminal 16. The transmission/reception unit 54 of the mobile terminal 16 receives the recommendation information via the network 18. The display control unit 58 displays the recommendation screen 278 on the display 34 based on the received recommendation information. The recommendation screen 278 has a message display area 280 that displays a message recommending ordering a product, a product image display area 282 that displays an image of the product being promoted, a product information display area 284 that displays product information such as the price and name of the product being promoted, a delivery information display area 286 that displays candidates for the scheduled delivery time and delivery fee, and a other user information display area 288. The candidates displayed in the delivery information display area 286 correspond to multiple scheduled delivery times and delivery fees obtained in the recommendation generation unit 262. The other user information display area 288 shows the number of other users who are referring to the recommendation screen 278 in response to the recommendation information. This lets users know that the promotion is limited in quantity and for a limited time.

Figure 41 is a flowchart showing the flow of a series of processes in the management server 12. The management server 12 determines the destination and route related to the order (S702). The management server 12 identifies the promotion target user based on the determined destination and route (S704). The management server 12 checks the free storage space 26 of the PDD 20 to which the ordered product 24 is delivered (S706). If there is free storage space 26 (Y in S708), the management server 12 selects products that match the size of the confirmed free storage space 26 as candidates for the promotion target product (S710). The management server 12 narrows down the candidates obtained in step S710 by analyzing the order history of the promotion target user (S712). The management server 12 generates recommendation information including information on the promotion target product obtained as a result of the narrowing down in step S712, and transmits it to the mobile terminal of the promotion target user (S714). The management server 12 receives the order according to the recommendation information (S716). The process returns to step S706, and the management server 12 checks again the free storage space 26 of the PDD 20. If there is free storage space 26, the above process is repeated, and if there is not (N in S708), the process ends.

In this example, in accordance with the product order by user 14, effective sales promotion can be implemented for other users in the vicinity of the meeting place or planned route. In particular, products that are likely to be in line with the intentions of other users are promoted, which increases the probability of receiving an order. In addition, the administrator can reduce the amount of free storage space 26 on the PDD 20.

In this example, since promoting every PDD delivery schedule can be cumbersome, a basic number of times may be determined. Alternatively, the user may access and use the service independently.

In addition, in this example, the management server 12 transmits the recommendation information to the mobile terminal 16 before the PDD 20 departs from the store 22, but the present invention is not limited to this. For example, the management server 12 may transmit the recommendation information to the mobile terminal of the promotion target user via the network 18 after the PDD 20 departs. In this case, the PDD 20 can be departed without waiting for a response to the recommendation information, so that the operation of the PDD 20 can be expedited. In this modified example, the PDD 20 is loaded with products that have not yet been requested but are likely to be purchased by the promotion target user, and the PDD 20 departs. After departure, a promotion is made to the promotion target user, such as, "Your Mizuyokan will arrive in 5 minutes. It is 100 yen after discount. Delivery is free. Would you like some?"

In this example, a case where a recommendation is made to the user 14 when there is free space in the storage space 26 has been described, but the form of the recommendation is not limited to this. For example, the management server 12 may obtain information on the weather around the user 14, and if it is raining or snowing, may suggest a meeting place closer to the current location of the user 14 along with a higher delivery fee. Alternatively, if the product ordered by the user 14 is heavier than a standard, the management server 12 may suggest a meeting place closer to the user 14 along with a higher delivery fee than if the product is light. Alternatively, the management server 12 may predict, from the analysis results of the order control information storage unit 152, a product that is likely to be ordered by a specific user 14 based on the current location and current time of the user 14. The management server 12 may recommend the predicted product before an order is made by the user 14. For example, if the analysis of the order control information storage unit 152 reveals that the user 14 tends to order rice balls at around 11:30 every day, the management server 12 transmits a recommendation to purchase rice balls to the mobile terminal 16 of the user 14 at around 11:25. Also, if the analysis of the order control information storage unit 152 reveals that the user 14 tends to purchase stationery in bulk at the end of each month, the management server 12 may distribute stationery coupons to the user 14 starting a few days before the end of the month.

In this example, the case where a recommendation is made to a promotion target user has been described, but this is not limited thereto. For example, the management server 12 may make a group recommendation to the same department of a company. In this case, the management server 12 may be configured so that a specific person in the group, for example, a new employee, can receive the product. The management server 12 accepts the order and transmits information for receiving the product (meeting place, time) to the terminal of the specified recipient (new employee). In this case, the product can be delivered in bulk, improving efficiency. Here, even if a recommendation is made to a group, the order and payment are made by each group member, and only the method of receiving the product is determined by the group: one of the group members, one of the group members who placed the order this time, or a specific group member. Determining by the group means, for example, that the recipient set by the first person who placed the order can be changed by the second person who placed the order, and similarly, subsequent orderers can change the recipient setting. When changing the recipient setting, a process of confirming in advance the person set as the recipient may be performed.

In the above-described embodiment, examples of the storage unit are a hard disk and a semiconductor memory. Furthermore, based on the description in this specification, it will be understood by those skilled in the art who have read this specification that each unit can be realized by a CPU (not shown), an installed application program module, a system program module, a semiconductor memory that temporarily stores the contents of data read from a hard disk, and the like.

The configuration and operation of the PDD system 10 according to the embodiment have been described above. This embodiment is merely an example, and it will be understood by those skilled in the art that various modifications are possible in the combination of each component and each process, and that such modifications are also within the scope of the present invention.

The embodiment may be expressed by the following items.
(PDD basic operation 0 (identifying the meeting place), <operation at the time of receiving a request>)
(Item 1)
A computer program for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A function of acquiring a designation of a type of destination of the unmanned transportation device from a user;
A computer program for causing the terminal to realize a function of displaying on the display a screen for the user to specify a location where the user and the unmanned transportation device will meet, if the specified type satisfies a criterion regarding the size of the lot.
(Item 2)
2. The computer program product of claim 1, wherein the display includes a map of a site at a destination for the unmanned vehicle and at least one potential meeting location displayed in association with the map.
(Item 3)
3. The computer program product of claim 2, wherein the screen includes, associated with the candidate, an indication of the number of times the candidate has been designated as a meeting location.
(Item 4)
4. The computer program according to claim 2 or 3, wherein the screen includes an image of the surroundings of the candidate in association with the candidate.
(Item 5)
2. The computer program of claim 1, wherein if the specified type meets a criterion regarding site size and a map of the site of the destination of the unmanned vehicle is not available, the screen includes a map of the surroundings of the site.
(Item 6)
The screen is configured to allow any location on the premises to be designated as a meeting location,
The computer program further comprises:
6. The computer program according to claim 1, which causes the terminal to realize a function of rejecting a location designated by a user on the screen if the location satisfies a criterion for rejecting the designation.
(Item 7)
An unmanned transport device that mediates the delivery of goods between a user and a store,
A moving means for realizing automatic movement to a destination using location information from the positioning means;
A reception means for receiving a registration mode designated by a user;
The unmanned transportation device includes an acquisition means for acquiring, in a registration mode, information specifying a location where the user has arrived following guidance from the user as information specifying a candidate location where the user and the unmanned transportation device will meet.
(Item 8)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
An acquisition means for acquiring a designation of a destination type of the unmanned transportation device from a user's terminal via a network;
A determination means for determining whether or not the designated type satisfies a criterion regarding the size of the lot;
A server comprising: a transmission means for transmitting screen information to the terminal via the network when it is determined that the conditions are met, to generate a screen for the user to specify a location where the user and the unmanned transportation device will meet.
(Item 9)
A terminal related to a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device,
An acquisition means for acquiring a designation of a type of destination of the unmanned transportation device from a user;
and a display control means for displaying on a display a screen for the user to specify a location where the user and the unmanned transportation device will meet, if the specified type satisfies a criterion regarding the size of the site.

(PDD basic operation 1 (PDD current location display), <operation upon request acceptance>)
(Item 1)
A computer program for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A function to obtain the current location of the user's device;
A function for receiving a destination designation for the unmanned transportation device;
A computer program for causing the terminal to realize a function of displaying a screen indicating a refusal of a request for delivery of an item on a display if the acquired current location and the specified destination are farther apart than a predetermined standard.
(Item 2)
A terminal related to a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device,
An acquisition means for acquiring a current location of the user's terminal;
A reception means for receiving a designation of a destination of the unmanned transportation device;
The terminal is provided with a display control means for displaying on a display a screen indicating a refusal of a request for delivery of an item when the acquired current position and the specified destination are farther apart than a predetermined standard.
(Item 3)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
an acquisition means for acquiring a current location of the user's terminal from the terminal via a network;
a receiving means for receiving a destination specification of the unmanned transportation device from the terminal via the network;
a determination means for determining whether the acquired current position and the designated destination are farther apart than a predetermined criterion;
a transmitting means for transmitting information for refusing a request for delivery of an item to said terminal via said network when it is determined that said terminal is far away.

(PDD basic operation 1 (PDD current position display), <operation during transportation/waiting for destination>)
(Item 1)
A computer program for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A function of acquiring an image corresponding to a current position of the unmanned transportation device obtained by using a positioning means provided in the unmanned transportation device;
A function for displaying the acquired image on a display, and a computer program for enabling the terminal to do this.
(Item 2)
The display function may include displaying the image on the display in association with an electronic map including at least one of a route of the unmanned vehicle, a current location of the unmanned vehicle, and a destination of the unmanned vehicle. 2. The computer program according to claim 1,
(Item 3)
3. The computer program according to item 1 or 2, wherein the image is displayed under one of the conditions that the current position of the unmanned transportation device is within a predetermined range based on the destination of the unmanned transportation device.
(Item 4)
4. The computer program according to any one of claims 1 to 3, further comprising a function of causing the terminal to stop displaying the image when the transfer of the item between the user and the unmanned transport device is completed.
(Item 5)
The image according to any one of items 1 to 4, wherein the image is obtained by performing a privacy protection process on an image obtained by an unmanned transportation device capturing an image of the surroundings at the current position. The computer program product described herein.
(Item 6)
5. The computer program product of claim 1, wherein the image is a past image corresponding to a current position of the unmanned vehicle.
(Item 7)
A terminal related to a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device,
an acquisition means for acquiring an image corresponding to a current position of the unmanned transportation device obtained by using a positioning means provided in the unmanned transportation device;
A terminal equipped with a display control means for displaying the acquired image on a display.
(Item 8)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A first acquisition means for acquiring information relating to a current position of the unmanned transportation device from the unmanned transportation device via a network;
a second acquisition means for acquiring an image that has been subjected to processing for protecting privacy and that corresponds to a current position of the unmanned vehicle;
A server comprising: a transmitting means for transmitting the acquired image to a user's terminal via a network.
(Item 9)
A computer program for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
When the current position of the unmanned transportation device obtained by using the positioning means provided in the unmanned transportation device is farther from the destination of the unmanned transportation device than a predetermined criterion, A function that provides an interface that allows re-specification;
and a computer program for causing the terminal to realize a function of acquiring a new destination specified via the interface.
(Item 10)
The interface presents candidates of destinations that can be specified;
10. The computer program according to item 9, wherein the acquiring function includes a function of acquiring a candidate designated by a user as a new destination.
(Item 11)
Item 9 or 10, further realizing a function in the terminal to restrict or prohibit re-designation of the destination in the interface when the current position of the unmanned transportation device and the destination of the unmanned transportation device become closer than the predetermined criterion. The computer program according to claim 1,
(Item 12)
A terminal related to a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device,
When the current position of the unmanned transportation device obtained by using the positioning means provided in the unmanned transportation device is farther from the destination of the unmanned transportation device than a predetermined criterion, providing means for providing an interface enabling re-designation;
and an acquisition means for acquiring a new destination specified via the interface.
(Item 13)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
a determination means for determining whether or not a current position of the unmanned transportation device, obtained using a positioning means provided in the unmanned transportation device, is farther away from a destination of the unmanned transportation device than a predetermined criterion;
a transmitting means for transmitting information for providing an interface that enables a user to re-designate the destination of the unmanned transportation device to the user's terminal via a network when it is determined that the user is away from the unmanned transportation device;
and an acquisition means for acquiring the new destination specified via the interface from the terminal via a network.

(PDD Basic Operation 2 (Linkage with Delivery Trucks), <Management Device>)
(Item 1)
A management device for managing a system for realizing delivery and receipt of an article between a user and a store via an unmanned transportation device,
A first acquisition means for acquiring a current position of the unmanned transportation device from the unmanned transportation device via a network;
A second acquisition means for acquiring a current location of a delivery vehicle capable of receiving and delivering an item from the unmanned transportation device from the delivery vehicle via a network;
a display control means for displaying on an electronic map the operation status of the unmanned transportation device and the operation status of the delivery vehicle together based on the acquired current position of the unmanned transportation device and the acquired current position of the delivery vehicle;
The management device is provided with a reception means for receiving a designation of a location where the unmanned transportation device and the delivery vehicle are to meet.
(Item 2)
A management device for managing a system for realizing delivery and receipt of an article between a user and a store via an unmanned transport device,
A function of acquiring a current position of the unmanned transportation device from the unmanned transportation device via a network;
A function of acquiring a current location of a delivery vehicle capable of receiving and delivering an item from the unmanned transportation device from the delivery vehicle via a network;
A function of displaying on an electronic map the operation status of the unmanned transportation device and the operation status of the delivery vehicle based on the acquired current position of the unmanned transportation device and the acquired current position of the delivery vehicle;
A computer program for realizing a function of accepting a designation of a location where the unmanned transportation device and the delivery vehicle are to meet.

(PDD basic operation 3 (PDD handover problem), <Handover waiting operation>)
(Item 1)
A computer program for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A function of acquiring information regarding the operation status of the unmanned transportation device via a network;
a computer program for causing the terminal to realize a function of providing the user with identification information of the unmanned transportation device corresponding to the user in accordance with the acquired information;
(Item 2)
An unmanned transport device that mediates the delivery of goods between a user and a store,
A moving means for realizing automatic movement to a destination using location information from the positioning means;
The unmanned transportation device is provided with a waiting means for carrying out processing to make the unmanned transportation device wait at a position avoiding waiting positions of other unmanned transportation devices at the destination when it is determined that the unmanned transportation device has arrived at the destination.
(Item 3)
A terminal related to a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device,
A means for acquiring information regarding the operation status of the unmanned transportation device via a network;
and means for providing a user with identification information of an unmanned transportation device corresponding to the user in accordance with the acquired information.

(PDD Basic Operation 4 (Problem of Absence When Receiving PDD) <Waiting for Delivery>)
(Item 1)
An unmanned transport device that mediates the delivery of goods between a user and a store,
A moving means for realizing automatic movement to a destination using location information from the positioning means;
A timing means for timing a waiting time at a destination;
and a confirmation means for performing a process to confirm with a user when the waiting time exceeds a threshold value.
(Item 2)
2. The unmanned driving device according to item 1, further comprising a waiting stop means for performing processing to stop waiting at the destination when it is determined that confirmation has not been obtained from the user.
(Item 3)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
An acquisition means for acquiring a waiting time of the unmanned transportation device at a destination;
and a confirmation means for performing a process for confirming with a user when the acquired waiting time exceeds a threshold value.
(Item 4)
4. The server according to item 3, further comprising a penalty means for carrying out a process for imposing a penalty on the user when it is determined that confirmation has not been obtained from the user.
(Item 5)
The server according to item 3 or 4, further comprising a change means for changing the route of the unmanned driving device so as to revisit the destination when a response to the confirmation from the user is received.

(PDD Basic Operation 5 (PDD Delivery of Gifts) <Operation at the Time of Accepting a Request>)
(Item 1)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A receiving means for receiving a request for delivery of an item to a receiving user from a terminal of the requesting user via a network;
a transmission means for transmitting a message to a receiving user's terminal via a network in response to the receipt of the request, the message inquiring whether or not the receiving user agrees to receive the request;
and processing means for performing processing to direct the unmanned vehicle to a destination corresponding to the recipient user if the response to the sent message is affirmative.
(Item 2)
The server according to item 1, further comprising a means for performing processing to deliver an item using a predetermined delivery method other than delivery using an unmanned transport device when it is determined that there is no response to the sent message or when the response to the sent message is a disagreement.
(Item 3)
A storage means for storing a delivery history is further provided,
3. The server according to claim 1 or 2, wherein the processing means performs delivery verification if the recipient user is not registered in the storage means.

(PDD Basic Operation 6 (Operation in the Event of a Failure))
(Item 1)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
a receiving means for receiving information indicating a fault in the unmanned transportation device detected by the unmanned transportation device from the unmanned transportation device via a network;
an acquisition means for acquiring a level indicating a degree of the failure based on the received information;
A server comprising: a determination means for determining whether or not a failure response process is necessary according to the acquired level.
(Item 2)
2. The server according to claim 1, wherein the failure response process includes a process for transporting an item equivalent to an item loaded on the unmanned transportation device in which the failure was detected, by another unmanned transportation device.
(Item 3)
2. The server according to claim 1, wherein the failure response process includes a process for transferring items loaded on the unmanned transportation device in which the failure was detected to another unmanned transportation device for transportation.

(PDD Basic Operation 7 (Transfer between PDDs))
(Item 1)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
A holding means for holding a plurality of predetermined locations where an article can be transferred between the unmanned transport devices;
An acquisition means for acquiring current positions of two or more unmanned transportation devices via a network;
A server comprising: a selection means for selecting a location where the two or more unmanned vehicles should meet from among a plurality of locations held in the holding means based on the acquired current location.

(PDD Basic Operation 8 (Sales Promotion on PDD Delivery Decision Route) <Operation during transportation/waiting at destination>)
(Item 1)
A server for a system for realizing delivery of goods between a user and a store via an unmanned transport device,
a determining means for determining a destination and a route for the unmanned vehicle;
An identification means for identifying a user available to meet with the unmanned vehicle based on at least one of the determined destination and route locations;
A server comprising: a transmission means for transmitting recommendation information relating to the sale of an item or the collection of an item to a terminal of the identified user via a network.
(Item 2)
The unmanned transportation device has a plurality of storage spaces each capable of storing an item;
2. The server according to item 1, further comprising a means for including in the recommendation information, as an item for sale, an item that can be stored in an empty storage space among a plurality of storage spaces of the unmanned transportation device.
(Item 3)
A means for calculating a plurality of different scheduled delivery times for the items for sale based on at least one of the determined destination and route;
3. The server according to item 1 or 2, further comprising: a means for including the calculated multiple estimated delivery times in recommendation information.
(Item 4)
A means for determining a delivery fee for each of the calculated plurality of scheduled delivery times;
4. The server according to item 3, further comprising: a means for including the determined delivery fee in the recommendation information.
(Item 5)
a retention means for retaining a delivery history;
5. The server according to any one of items 1 to 4, further comprising: a means for identifying an item for sale corresponding to the identified user based on the history stored in the storage means.
(Item 6)
The server described in item 5, wherein the transmission means transmits recommendation information related to the identified item for sale to the identified user's terminal via a network after the unmanned transportation device containing the item departs.

10 PDD system, 12 management server, 14 user, 16 mobile terminal, 18 network, 20 PDD, 22 store.

Claims (7)

A computer program for a user terminal in a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device, comprising:
A function of acquiring an image previously acquired in a server, the image corresponding to the current position of the unmanned transportation device obtained by using a positioning means provided in the unmanned transportation device;
A computer program for causing the user's terminal to realize a function of displaying the acquired image on a display. The computer program according to claim 1, wherein the display function includes a function for displaying the image on the display in association with an electronic map including at least one of the route of the unmanned transportation device, the current position of the unmanned transportation device, and the destination of the unmanned transportation device. The computer program according to claim 1 or 2, wherein the image is displayed under one of the conditions that the current position of the unmanned transport device is within a predetermined range based on the destination of the unmanned transport device. 4. The computer program according to claim 1, further comprising a function of stopping the display of the image on the user's terminal when the transfer of the article between the user and the unmanned transport device is completed. The computer program according to claim 1 , wherein the image previously acquired in the server is an image obtained by an unmanned transportation device capturing an image of the surroundings in advance in association with a position of the unmanned transportation device. The computer program according to claim 1 , wherein the image previously acquired in the server is an image obtained by performing a process for protecting privacy on the acquired image. A user terminal in a system for realizing delivery and receipt of goods between a user and a store via an unmanned transport device,
an acquisition means for acquiring an image previously acquired in a server, the image corresponding to a current position of the unmanned transportation device obtained by using a positioning means provided in the unmanned transportation device;
A terminal equipped with a display control means for displaying the acquired image on a display.

Images