Unmanned vending machine

Abstract

To provide an unmanned vending device that can display a registration state of purchased articles and a progress state of payment processing in an easy-to-understand manner.SOLUTION: A mobile vending robot (unmanned vending device) according to the embodiment includes: an article identification unit that identifies an article taken out of or returned to a housing unit containing the article; an article registration unit that registers the article identified by the article identification unit as having been taken out of the housing unit; a display control unit (registration result display unit) that displays information pertaining to the articles registered by the article registration unit on a first display unit in an aligned manner; and a display control unit (payment processing support unit) that displays information pertaining to payment processing in a second display unit upon receiving an instruction that the article registration has been completed.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] FIELD OF THE INVENTION An embodiment of the present invention relates to an unmanned vending machine. [Background technology]

[0002] Conventionally, a system has been proposed that includes a robot (shopping support device) that moves around a store selling products and supports customers in their shopping (for example, Patent Document 1). The robot in the system patrols the store, accepting purchased products from customers and carrying them to the cash register, thereby supporting customers in their shopping.

[0003] As described above, conventional systems are limited to supporting customers' shopping within a store, and there is a demand for the construction of a more useful system for businesses that sell products. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide an unmanned sales device that can clearly display the registration status of purchased products and the progress of payment processing. [Means for solving the problem]

[0005] The unmanned vending machine of the embodiment includes: An unmanned vending machine having a storage unit for storing products to be sold and a drive unit for moving the machine, The device includes a product specification unit, a product registration unit, a registration result display unit, and a payment operation unit. Based on the change in weight of the container, The product registration unit registers the product that the product identification unit has identified as having been removed from the storage unit. The registration result display unit displays information related to the product that the product registration unit has registered. , provided on the side facing the storage section The payment processing support unit receives an instruction that product registration has been completed and displays the products in an aligned order on the first display unit. Rotate the display to a different orientation from the primary display. 2nd display facing the customer, and the second display unit Displays information related to payment processing. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a mobile sales system according to an embodiment. [Figure 2] FIG. 2 is a first perspective view showing an example of the external configuration of the mobile sales robot according to the embodiment. [Figure 3] FIG. 3 is a second perspective view showing an example of the external configuration of the mobile sales robot according to the embodiment. [Figure 4] FIG. 4 is a third perspective view showing an example of the external configuration of the mobile sales robot according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a hardware configuration of the mobile sales robot according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the data configuration of the product master. [Figure 7] FIG. 7 is a diagram illustrating an example of the data configuration of the stocked product table. [Figure 8] FIG. 8 is a diagram illustrating an example of the data structure of the product registration file. [Figure 9] FIG. 9 is a diagram illustrating an example of a hardware configuration of a user terminal according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the data configuration of the robot management table. [Figure 12] FIG. 12 is a diagram illustrating an example of the data configuration of the product management table. [Figure 13] FIG. 13 is a diagram illustrating an example of the data configuration of the user management table. [Figure 14] FIG. 14 is a diagram illustrating an example of the data configuration of the call management table. [Figure 15] FIG. 15 is a diagram illustrating an example of the data configuration of the transaction management table. [Figure 16] FIG. 16 is a functional block diagram illustrating an example of the functional configuration of the mobile sales robot according to the embodiment. [Figure 17]FIG. 17 is a functional block diagram illustrating an example of a functional configuration of a server device according to the embodiment. [Figure 18] FIG. 18 is a functional block diagram illustrating an example of a functional configuration of a user terminal according to the embodiment. [Figure 19] FIG. 19 is a diagram showing an example of a current position display screen displayed on the display unit of the user terminal. [Figure 20] FIG. 20 is a diagram showing an example of a call screen displayed on the display unit of the user terminal. [Figure 21] FIG. 21 is a diagram showing an example of the product registration screen. [Figure 22] FIG. 22 is a diagram showing an example of the authentication screen. [Figure 23] FIG. 23 is a diagram showing an example of a display form of the product registration screen when registering a product. [Figure 24] FIG. 24 is a first diagram showing an example of a display form of the product registration screen when product registration is canceled. [Figure 25] FIG. 25 is a second diagram showing an example of the display form of the product registration screen when product registration is canceled. [Figure 26] FIG. 26 is a diagram showing an example of screen transition of a screen displayed on the first display unit of the mobile sales robot according to the embodiment. [Figure 27] FIG. 27 is a sequence diagram showing an example of the flow of processing performed by the mobile sales system according to the embodiment. [Figure 28] FIG. 28 is a flowchart showing an example of the flow of the product registration process performed by the mobile sales robot according to the embodiment. [Figure 29] FIG. 29 is a flowchart showing an example of the flow of the payment process performed by the mobile sales system according to the embodiment. [Figure 30] FIG. 30 is a first diagram showing an example of another display format of merchandise registration information and information related to payment processing. [Figure 31] FIG. 31 is a second diagram showing an example of another display format of the product registration information and the information related to the payment process. [Figure 32]FIG. 32 is a third diagram showing an example of another display format of the product registration information and the information related to the payment process. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, embodiments will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiments described below.

[0008] (Mobile sales system configuration) The system configuration of a mobile sales system 1 according to an embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the configuration of a mobile sales system according to an embodiment.

[0009] 1, the mobile sales system 1 includes a mobile sales robot 10, a user terminal 20, and a server device 30. The mobile sales robot 10, the user terminal 20, and the server device 30 are connected to a network N such as a LAN (Local Area network).

[0010] The mobile sales robot 10 is a self-propelled unmanned vending machine that transports and sells merchandise. For example, the mobile sales robot 10 travels within a predetermined area such as a shopping mall and sells merchandise at each location it travels to. The mobile sales robot 10 performs patrol travel, traveling along a predetermined route, and call travel, traveling to a call location designated by a customer. The number of mobile sales robots 10 is not important. The mobile sales robot 10 is an example of an unmanned vending machine in the present disclosure.

[0011] (Outline of the mobile sales robot) The schematic configuration of the mobile sales robot 10 will be described with reference to Figs. 2 to 4. Fig. 2 is a first perspective view showing an example of the external configuration of the mobile sales robot according to the embodiment. Fig. 3 is a second perspective view showing an example of the external configuration of the mobile sales robot according to the embodiment. Fig. 4 is a third perspective view showing an example of the external configuration of the mobile sales robot according to the embodiment.

[0012] 2 to 4, the configuration of the mobile sales robot 10 will be described using three mutually perpendicular axial directions: the X-axis, the Y-axis, and the Z-axis. The X-axis runs through the mobile sales robot 10 from front to back, and extends from the rear to the front of the mobile sales robot 10. The Y-axis runs through the mobile sales robot 10 from left to right, and extends from the left side to the right side as viewed from the front of the mobile sales robot 10. The Z-axis runs through the mobile sales robot 10 from top to bottom, and extends from the bottom to the top of the mobile sales robot 10. Hereinafter, the left side of the mobile sales robot 10 as viewed from the front (the negative Y-axis side) will also be referred to as the front side of the mobile sales robot 10. Furthermore, the right side of the mobile sales robot 10 as viewed from the front of the mobile sales robot 10 (the positive Y-axis side) will also be referred to as the back side of the mobile sales robot 10.

[0013] The mobile sales robot 10 comprises a main body 11, a moving unit 12, and a user interface unit 13. The main body 11 is formed of a box-shaped housing with open front and back sides. A storage unit 111 is provided inside the main body 11.

[0014] The storage section 111 is a space for storing products M such as foodstuffs. In the storage section 111, a plurality of shelves 112 capable of displaying the products M are arranged in multiple vertical stages across the front-to-rear direction of the mobile sales robot 10. The products M are placed on the shelves 112 by a store clerk or the like managing the mobile sales robot 10. The products M stored in the storage section 111 are not limited to foodstuffs, and may be products of other categories such as medicines or leisure goods. Furthermore, the storage section 111 may store products M of multiple categories.

[0015] The shelf 112 may be divided into a plurality of areas, for example, to sort and place the same type of products M. In this case, the shelf 112 may be divided into a plurality of areas by using, for example, trays or the like.

[0016] Shelf labels 113 for displaying the name and price of the product M are provided on the front side of the shelves 112. The shelf labels 113 may be electronic shelf labels or digital signage that digitally display information. Each shelf 112 is also provided with a weight detection unit 159 (see FIG. 5) that can detect the weight of the product M placed on the shelf 112. The weight detection unit 159 detects a change in weight, thereby detecting that the product M placed on the shelf 112 has been removed from the shelf 112 or that the product M has been returned to the shelf 112. Details of the weight detection unit 159 will be described later.

[0017] In this embodiment, the shelf tags 113 are provided on the front side of the shelf 112, but the shelf tags 113 may also be provided on the back side of the shelf 112. Also, in this embodiment, both the front side and back side of the main body 11 (storage section 111) are open, but only one side (for example, only the front side) may be open.

[0018] Alternatively, a door made of a light-transmitting material such as glass may be attached to either or both of the front and back sides of the main body 11 (storage section 111) in an openable and closable manner, allowing access to the inside of the storage section 111 through the door. For example, a door may be attached to the front side of the main body 11, and the back side of the main body 11 may be covered with a wall. In this case, the wall on the back side may be made of a light-transmitting material such as glass. This prevents the products M in the storage section 111 from falling out of the storage section 111 when the mobile sales robot 10 is moving, etc.

[0019] Furthermore, the door may be configured to be lockable by providing an electronic lock or the like, which can prevent unauthorized removal of merchandise from the storage section 111, for example, when the mobile sales robot 10 is moving.

[0020] A light emitting unit 114 and a distance measuring sensor 115 are provided on the front side of the main body 11. The light emitting unit 114 has a light emitting element such as an LED (Light Emitting Diode) and emits light in accordance with control instructions from the control unit 154 (described later) to indicate the operating state of the mobile vending robot 10. For example, the light emitting unit 114 emits light when the mobile vending robot 10 is moving, thereby indicating that the mobile vending robot 10 is moving. Note that the light emitting color of the light emitting unit 114 is not limited to a single color. For example, the light emitting unit 114 may emit different light colors or change light emission patterns depending on the operating state of the mobile vending robot 10. Furthermore, the light emitting unit 114 is not limited to being provided on the front side of the main body 11, but may also be provided on the rear side.

[0021] The ranging sensor 115 is a sensor that detects objects present around the mobile sales robot 10 and measures the position of the object and the distance to the object. The sensing results of the ranging sensor 115 are output to a control unit 154 (described later) and are used to avoid collisions when the mobile sales robot 10 moves. The ranging sensor 115 can be realized by, for example, a camera that captures images, a sensor device that detects objects and measures distances using ultrasonic waves, or a sensor device such as a LiDAR (Light Detection and Ranging) that detects objects using laser light.

[0022] The position where the distance measurement sensor 115 is provided is not limited to the front of the mobile sales robot 10. For example, the distance measurement sensor 115 may be provided at another position, such as the rear of the mobile sales robot 10. Also, the imaging unit 134 (see FIG. 3 ), which will be described later, may be used as the distance measurement sensor 115.

[0023] The moving unit 12 is provided below the main body unit 11 and movably supports the main body unit 11. Specifically, the moving unit 12 includes a non-drive wheel 121, a drive wheel 122, and a drive unit 123 that drives the drive wheel 122.

[0024] The non-drive wheels 121 are small wheels that can freely change direction in response to the direction of the force generated by the rotation of the drive wheels 122, thereby changing the traveling direction of the mobile sales robot 10 (movement unit 12).

[0025] The drive wheels 122 are rotationally driven by the drive unit 123, thereby moving the mobile sales robot 10 (movement unit 12) forward, backward, or rotated.

[0026] The driving unit 123 has a driving source such as a motor or a power supply. The driving unit 123 drives and rotates the driving wheels 122 in accordance with control instructions from the control unit 154, which will be described later, to move the mobile sales robot 10 (movement unit 12) in the direction and to the position instructed by the control unit 154.

[0027] The user interface unit 13 is provided on the upper part of the main body unit 11. The user interface unit 13 includes a first display unit 131, a second display unit 132, a third display unit 133, an imaging unit 134, a disinfection device 135, and the like.

[0028] The first display unit 131 is a display device installed on the front side of the mobile sales robot 10. The second display unit 132 is a display device installed on the rear side of the mobile sales robot 10. The third display unit 133 is a display device installed on the back side of the mobile sales robot 10. The first display unit 131, the second display unit 132, and the third display unit 133 display various information related to product registration processing and payment processing performed when selling the product M in accordance with control instructions from the control unit 154, which will be described later. Furthermore, the first display unit 131, the second display unit 132, and the third display unit 133 display various advertising screens in accordance with control instructions from the control unit 154, which will be described later. The various advertising screens include, for example, information for advertising the product M stored in the storage unit 111, information related to sales promotion of the product M, and corporate advertising.

[0029] The imaging unit 134 is installed on the rear side of the mobile vending robot 10. The imaging unit 134 is a digital camera having an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary MOS). When performing payment processing, the imaging unit 134 captures an image of the customer's face to obtain information necessary for facial authentication of the customer.

[0030] The disinfection device 135 is a device that disinfects customers who use the mobile sales robot 10. In this embodiment, disinfection means killing (or removing) pathogenic bacteria, viruses, and other microorganisms present on an object to make them harmless. Furthermore, disinfection can be interpreted as sterilization, sterilization, or sterilization.

[0031] The disinfection device 135 may have any configuration. For example, the disinfection device 135 may be a sprayer that sprays a disinfectant such as alcohol. Alternatively, the disinfection device 135 may be an ultraviolet disinfection device that irradiates ultraviolet rays. The disinfection device 135 performs a disinfection operation such as spraying a disinfectant or irradiating ultraviolet rays in response to an operation by a customer.

[0032] The configuration of the user interface unit 13 is not limited to the illustrated example. For example, the number and installation positions of the display devices included in the user interface unit 13 are not limited to the illustrated example. The user interface unit 13 may be configured without the disinfection device 135. The user interface unit 13 may also include a reader device that reads information stored in a code symbol such as a two-dimensional code, or a reader device that reads information from a card medium such as an IC card or a credit card.

[0033] Returning to FIG. 1, the user terminal 20 is a terminal device used by a user of the mobile sales system 1. The user terminal 20 is realized by a portable terminal device such as a smartphone or a tablet terminal. The user terminal 20 accepts a call request from a customer requesting to call the mobile sales robot 10, and transmits the accepted call request to the server device 30. The number of user terminals 20 is not important.

[0034] The server device 30 manages the mobile sales system 1. The server device 30 is realized by, for example, an information processing device such as a PC (Personal Computer). The server device 30 manages the products sold by each of the mobile sales robots 10. The server device 30 also manages the mobile sales robot 10 and causes the mobile sales robot 10 to travel to a call position specified in a call request received from the user terminal 20. For example, the server device 30 manages the current positions of the mobile sales robot 10 and the user terminal 20, and upon receiving a call request for the mobile sales robot 10 from the user terminal 20, causes the mobile sales robot 10 specified in the call request to travel toward the position of the user terminal 20.

[0035] (Mobile sales robot hardware configuration) The hardware configuration of the mobile sales robot 10 will be described using Fig. 5 to Fig. 8. Fig. 5 is a diagram showing an example of the hardware configuration of the mobile sales robot according to the embodiment. Fig. 6 is a diagram showing an example of the data configuration of the product master. Fig. 7 is a diagram showing an example of the data configuration of the stocked product table. Fig. 8 is a diagram showing an example of the data configuration of the product registration file.

[0036] As shown in FIG. 5, the mobile sales robot 10 includes a control unit 154 that controls the entire mobile sales robot 10, a storage unit 162, and various peripheral devices.

[0037] The control unit 154 includes a CPU (Central Processing Unit) 151, a ROM (Read Only Memory) 152, and a RAM (Random Access Memory) 153. The CPU 151 comprehensively controls each unit of the mobile sales robot 10. The ROM 152 stores various programs. The RAM 153 is a workspace where the programs and various data are expanded.

[0038] The CPU 151, the ROM 152, and the RAM 153 are connected via a bus, etc. The control unit 154 executes various processes by the CPU 151 operating in accordance with a program stored in the storage unit 162 and loaded into the RAM 153.

[0039] The mobile sales robot 10 includes various peripheral devices such as the light emitting unit 114, the driving unit 123, and the imaging unit 134. The mobile sales robot 10 also includes a display unit 155, an operation unit 156, a sound collecting unit 157, a sensor unit 158, a weight detecting unit 159, a positioning unit 160, a communication unit 161, etc.

[0040] The display unit 155 is a display device such as the first display unit 131, the second display unit 132, and the third display unit 133 described above. The display unit 155 is configured with an LCD (Liquid Crystal Display) or the like. The display unit 155 displays various information under the control of the CPU 151. Note that if the shelf tag 113 is an electronic shelf tag, the display unit 155 includes the electronic shelf tag.

[0041] Operation unit 156 is an input device such as a keyboard, a pointing device, etc. Operation unit 156 outputs the operation content received from the customer to CPU 151. Note that operation unit 156 may be a touch panel provided on the display screen of display unit 155.

[0042] The sound collection unit 157 collects sounds around the mobile sales robot 10 and outputs the audio signals of the collected sounds to the CPU 151. The sound collection unit 157 is realized by, for example, a sound collection device such as a microphone. For example, the sound collection unit 157 collects sounds from customers who wish to purchase products while the mobile sales robot 10 is traveling to stop the traveling.

[0043] The sensor unit 158 is a sensor device such as the distance measuring sensor 115. The sensor unit 158 outputs the detection result obtained by sensing to the CPU 151.

[0044] Weight detection unit 159 is a weight sensor that detects the weight of the product stored in storage unit 111. Specifically, weight detection unit 159 is provided on each shelf 112, and detects the weight and weight change of the product placed on shelf 112. Each shelf 112 and weight detection unit 159 provided on that shelf 112 are associated in advance, and when weight detection unit 159 detects a weight change, it is possible to identify the shelf 112 where the change occurred.

[0045] If the shelf 112 is divided into a plurality of areas, a weight detection unit 159 may be provided for each divided area. In this case, each divided area is associated with the weight detection unit 159 provided in that area.

[0046] The positioning unit 160 measures the position of the mobile sales robot 10. The positioning unit 160 can be realized by a positioning device using a positioning technology such as GPS (Global Positioning System).

[0047] The positioning unit 160 may be realized by a position measurement device that uses positioning technology such as beacon positioning, RFID (Radio Frequency Identifier) positioning, etc. In this case, by providing a terminal that supports positioning technology such as beacon positioning or RFID positioning at each position within the range in which the mobile sales robot 10 can move, the position of the mobile sales robot 10 can be measured (identified) by a positioning system formed by the terminal and the positioning unit 160.

[0048] The communication unit 161 is a wireless communication interface that can be connected to the network N. The communication unit 161 communicates with external devices such as the server device 30 via the network N.

[0049] The storage unit 162 has a storage medium such as a hard disk drive (HDD) or flash memory, and maintains the stored contents even when the power is cut off. The storage unit 162 stores programs that can be executed by the CPU 151 and various setting information.

[0050] The storage unit 162 also stores map information 1621, a product master 1622, a stocked product table 1623, and a product registration file 1624. The map information 1621 is information showing a map of the range in which the mobile sales robot 10 moves. The map information 1621 is information that associates the position identified by the positioning unit 160 with positions within the range in which the mobile sales robot 10 can move. The mobile sales robot 10 performs patrol travel and calling travel based on the identified position in the map information 1621. The format of the map information 1621 is not important.

[0051] The product master 1622 is a data table that stores information about products for sale. As shown in Fig. 6, the product master 1622 stores product information about a product corresponding to a product code, in association with the product code that identifies the product. The product information includes the product name, type, price, weight, product icon, etc.

[0052] The storage unit 162 may be configured not to store the product master 1622. In this case, the mobile sales robot 10 can handle the product master 3162 by referring to the product master 3162 (see FIG. 10) stored in the server device 30 in the same way as in the configuration in which the product master 1622 is stored.

[0053] The stored product table 1623 is a data table for storing information about products stored in the storage section 111. As shown in Fig. 7, the stored product table 1623 associates each shelf 112 provided in the storage section 111 with an identifiable shelf ID, and stores the product code of the product placed on the shelf 112 with the shelf ID and the quantity of the product placed.

[0054] The data configuration of the stored product table 1623 is not limited to the example in Fig. 7. For example, if the shelf 112 is divided into multiple areas, the stored product table 1623 may assign an identifier to each divided area and store the product code and quantity of the product placed in that area in association with each other.

[0055] The product registration file 1624 is a file that registers the product M that a customer has taken out from the shelf 112 of the mobile sales robot 10. As shown in Fig. 8, the product registration file 1624 stores the product code, quantity, and unit price of the product M that the customer with the user ID has taken out from the shelf 112 of the mobile sales robot 10, in association with the user ID that uniquely identifies the customer. The data configuration of the product registration file 1624 is not limited to the example shown in Fig. 8, and it is sufficient if it includes information that can identify the product M that the customer has taken out from the shelf 112 of the mobile sales robot 10.

[0056] Here, the user ID may be, for example, a pin code issued by the server device 30 when a customer calls the mobile sales robot 10, or a facial image or user ID sent from the user terminal 20 of the customer who called the mobile sales robot 10.

[0057] When a customer has finished removing all of the products M from the shelves 112, the mobile sales robot 10 transmits the product registration file 1624 to the server device 30. The server device 30 then performs payment processing based on the registered contents of the product registration file 1624. Note that each time a customer removes a product M from the shelves 112, the mobile sales robot 10 may transmit the product code of the removed product to the server device 30, and the server device 30 may perform both the product registration processing and the payment processing.

[0058] (User terminal hardware configuration) The user terminal 20 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the hardware configuration of the user terminal according to the embodiment.

[0059] As shown in FIG. 9, the user terminal 20 includes a control unit 214 that controls the entire user terminal 20, a storage unit 220, and various peripheral devices.

[0060] The control unit 214 includes a CPU 211, a ROM 212, and a RAM 213. The CPU 211 performs overall control of each unit of the user terminal 20. The ROM 212 stores various programs. The RAM 213 is a workspace where the programs and various data are expanded.

[0061] The CPU 211, the ROM 212, and the RAM 213 are connected via a bus, etc. The control unit 214 executes various processes by the CPU 211 operating in accordance with a program stored in the storage unit 220 and loaded in the RAM 213.

[0062] The user terminal 20 includes a display unit 215 , an operation unit 216 , an imaging unit 217 , a positioning unit 218 , a communication unit 219 , and a storage unit 220 .

[0063] The display unit 215 is a display device, and is configured, for example, with an LCD or the like. The display unit 215 displays various information under the control of the CPU 211. The operation unit 216 is an input device such as a keyboard or a pointing device. The operation unit 216 outputs the operation content received from the customer to the CPU 211. Note that the operation unit 216 may be a touch panel provided on the display screen of the display unit 215.

[0064] The imaging unit 217 is a digital camera having an imaging element such as a CCD or CMOS, etc. The imaging unit 217 captures an image of a customer using the user terminal 20, thereby obtaining an image of the customer's face, etc.

[0065] The positioning unit 218 measures the location of the user terminal 20. The positioning unit 218 can be realized by a positioning device using a positioning technique such as GPS. Alternatively, similar to the positioning unit 160 described above, the positioning unit 218 may be realized by a position measurement device using a positioning technique such as beacon positioning or RFID positioning.

[0066] The communication unit 219 is a wireless communication interface that can be connected to the network N. The communication unit 219 communicates with external devices such as the server device 30 via the network N.

[0067] The storage unit 220 has a storage medium such as a HDD or flash memory, and maintains its stored contents even when the power is turned off. The storage unit 220 stores programs that can be executed by the CPU 211 (including application programs related to the processing of the mobile sales system 1) and various setting information.

[0068] The storage unit 220 also stores map information 2201. The map information 2201 is information showing a map of the area in which the mobile sales robot 10 moves. The map information 2201 stores the same information as the map information 1621 provided in the mobile sales robot 10.

[0069] (Server hardware configuration) The hardware configuration of the server device 30 will be described using Fig. 10 to Fig. 15. Fig. 10 is a diagram showing an example of the hardware configuration of the server device according to the embodiment. Fig. 11 is a diagram showing an example of the data configuration of a robot management table. Fig. 12 is a diagram showing an example of the data configuration of a product management table. Fig. 13 is a diagram showing an example of the data configuration of a user management table. Fig. 14 is a diagram showing an example of the data configuration of a call management table. Fig. 15 is a diagram showing an example of the data configuration of a transaction management table.

[0070] As shown in FIG. 10, the server device 30 includes a control unit 314 that controls the entire server device 30, a communication unit 315, and a storage unit 316.

[0071] The control unit 314 includes a CPU 311, a ROM 312, and a RAM 313. The CPU 311 performs overall control of each unit of the server device 30. The ROM 312 stores various programs. The RAM 313 is a workspace where the programs and various data are expanded.

[0072] The CPU 311, ROM 312, and RAM 313 are connected via a bus, etc. The control unit 314 executes various processes by the CPU 311 operating in accordance with a program stored in the storage unit 316 and loaded into the RAM 313.

[0073] The communication unit 315 is a wired or wireless communication interface that can be connected to the network N. The communication unit 315 communicates with external devices such as the mobile sales robot 10 and the user terminal 20 via the network N.

[0074] The storage unit 316 has a storage medium such as an HDD or flash memory, and maintains the stored contents even when the power is cut off. The storage unit 316 stores programs that can be executed by the CPU 311 and various setting information.

[0075] The storage unit 316 stores map information 3161 and a product master 3162. The map information 3161 is information showing a map of the area in which the mobile sales robot 10 moves. The map information 3161 stores the same information as the map information 1621 provided in the mobile sales robot 10 and the map information 2201 provided in the user terminal 20. The product master 3162 is a data table that stores information about products for sale. The data configuration of the product master 3162 is the same as that of the product master 1622 described above.

[0076] The storage unit 316 also stores a robot management table 3163, a product management table 3164, a user management table 3165, a call management table 3166, a transaction management table 3167, and the like.

[0077] The robot management table 3163 is a data table for managing the position and status of the mobile sales robot 10. As shown in Fig. 11, the robot management table 3163 stores, in association with a robot ID, position information indicating the current position of the mobile sales robot 10 corresponding to the robot ID, status information indicating the status of the mobile sales robot 10, and the like.

[0078] The location information of the mobile sales robot 10 may be expressed by coordinate values such as longitude and latitude. Alternatively, the location information may be expressed by block numbers or the like obtained by dividing the range in which the mobile sales robot 10 can move into a plurality of blocks.

[0079] The status information of the mobile sales robot 10 may be, for example, a "moving" status in which the mobile sales robot 10 is moving to a customer's call destination, a "waiting for transaction" status in which the mobile sales robot 10 has arrived at the call destination and is waiting for an operation to start a transaction, a "transaction in progress" status in which a transaction has been started by a customer's operation, etc. The status information of the mobile sales robot 10 may also be a "waiting for call" status in which the mobile sales robot 10 is able to respond to a customer's call, such as when the mobile sales robot 10 is patrolling, or a "not selling" status in which the mobile sales robot 10 is unable to sell due to replenishing merchandise, etc.

[0080] The information stored in the robot management table 3163 is updated according to the position and state of the mobile sales robot 10 under the control of the server device 30.

[0081] The product management table 3164 is a data table for managing products sold by each mobile sales robot 10. As shown in Fig. 12, the product management table 3164 stores, in association with a robot ID, the product code of the product sold by the mobile sales robot 10 of that robot ID, the number of that product remaining on the shelf 112 of the mobile sales robot 10 (remaining number), and the like.

[0082] The information stored in the product management table 3164 is updated under the control of the server device 30 in accordance with the remaining number of products held by the mobile sales robot 10.

[0083] The user management table 3165 is a data table for managing customers who use the mobile sales system 1. As shown in Fig. 13, the user management table 3165 associates a customer with an identifiable user ID and stores user information about the customer with that user ID.

[0084] The user information includes feature information indicating the facial features of the customer and payment information used for electronic payment. The feature information is, for example, a facial image of the customer's face or feature quantities indicating facial features, and is used as matching data in the face authentication process described below. The payment information is information such as an account for using an electronic payment service with which the customer has previously signed up.

[0085] The user information is obtained from the customer by, for example, a known method such as member registration, and is registered in the user management table 3165. The user ID may be automatically assigned, or may use unique information entered by the customer. The user information is not limited to the above example, and may include other information. For example, the user information may include personal information such as the customer's name, age, and address. The user information may also include the terminal ID and address of the terminal (user terminal 20) used by the customer.

[0086] The call management table 3166 is a data table for managing calls to the mobile sales robot 10 by the user terminal 20. As shown in Fig. 14, the call management table 3166 stores, in association with each other, the terminal ID of the user terminal 20 that made the call, the date and time when the call was accepted (call date and time), location information indicating the location of the call destination (hereinafter simply referred to as "call location"), authentication information used to authenticate the customer who made the call, the robot ID of the mobile sales robot 10 that responded to the call, and the date and time when the mobile sales robot 10 arrived at the call destination (arrival date and time).

[0087] The authentication information may be, for example, a pin code consisting of a sequence of a predetermined number of digits, a facial image of the customer, or a user ID. In the former case, the pin code may be issued by the control unit 314 or may be specified by the customer. In the latter case, the pin code may be a facial image or user ID transmitted from the user terminal 20 of the customer who made the call, or a user ID identified by the control unit 314 from the user management table 3165 based on the transmitted facial image. In this embodiment, the control unit 314 issues a pin code when accepting a call, and when making payment for the product purchased by the customer, the control unit 314 performs authentication using the facial image of the customer.

[0088] The transaction management table 3167 is a data table for managing transactions via the mobile sales robot 10. As shown in Fig. 15, the transaction management table 3167 stores the robot ID of the mobile sales robot 10 that performed the transaction, the user ID of the customer performing the transaction, the product code of the product purchased by the customer, and a payment flag for determining whether payment has been made, in association with a transaction ID that identifies the transaction.

[0089] (Functional configuration of mobile sales robot) The functional configuration of the mobile sales robot 10 will be described with reference to Fig. 16. Fig. 16 is a functional block diagram showing an example of the functional configuration of the mobile sales robot according to the embodiment.

[0090] The control unit 154 of the mobile sales robot 10 loads a program into the RAM 153 and runs it, thereby realizing as functional units a transmission / reception unit 1541, a self-location identification unit 1542, a product identification unit 1543, a product registration unit 1544, a robot orientation control unit 1545, a user authentication unit 1546, a product registration information output unit 1547, a payment completion notification acquisition unit 1548, a display content control unit 1549, a drive control unit 1550, and a display control unit 1551, all of which are shown in Fig. 16. Note that each of these functions may be configured using hardware such as a dedicated circuit.

[0091] The transmitting / receiving unit 1541 transmits and receives various information to and from an external device such as the server device 30 via the communication unit 161. For example, the transmitting / receiving unit 1541 transmits position information and status information indicating the position of its own device to the server device 30 as needed.

[0092] The transmitting / receiving unit 1541 also transmits an authentication request to the server device 30 and receives an authentication notification from the server device 30. The authentication request requests authentication of the pin code acquired by the user authentication unit 1546, and includes the pin code and robot ID accepted by the user authentication unit 1546. The transmitting / receiving unit 1541 also transmits a payment request to the server device 30 and receives a payment completion notification from the server device 30.

[0093] The self-location identifying unit 1542 collates the output of the positioning unit 160 with the map information 1021 to identify the location of the mobile sales robot 10 .

[0094] The product identification unit 1543 detects that the product M has been removed from the storage unit 111 (shelf 112) that stores the products, and that the product M has been returned to the storage unit 111 (shelf 112) that stores the products. The product identification unit 1543 also identifies the product M that has been removed from the storage unit 111 (shelf 112) or the product M that has been returned to the storage unit 111 (shelf 112). Specifically, the product identification unit 1543 detects that the product M has been removed or returned based on the amount of change in weight detected by the weight detection unit 159. The product identification unit 1543 also identifies the product M by comparing the amount of change in weight detected by the weight detection unit 159 with the weight registered in the product master 1622.

[0095] The product registration unit 1544 registers the product M that the product identification unit 1543 identified as having been removed from the storage unit 111 in the product registration file 1624. In addition, the product registration unit 1544 deletes the product M that the product identification unit 1543 identified as having been returned to the storage unit 111 from the product registration file 1624.

[0096] The robot orientation control unit 1545 rotates the mobile sales robot 10 by 90° on the spot, provided that the registration of the product to be purchased by the customer is complete. As a result, the robot orientation control unit 1545 changes the display unit 155 facing the customer from the first display unit 131 to the second display unit 132. As will be described later, the first display unit 131 displays a product registration screen (see FIG. 21) showing the registered product details, and the second display unit 132 displays an authentication screen (see FIG. 22) that supports the payment process. Therefore, the customer is facing the screen showing the details of the process being performed at that time, and can easily and reliably check the status of the process being performed.

[0097] The user authentication unit 1546 accepts input information based on the operation of the operation unit 156. For example, the user authentication unit 1546 accepts a pin code entered by the customer's operation. The user authentication unit 1546 also transmits facial image data of the customer captured by the imaging unit 134 to the server device 30 for user authentication.

[0098] After all the registrations of the products to be purchased are completed, the product registration information output unit 1547 transmits the product registration file 1624 to the server device 30.

[0099] The payment completion notification acquisition unit 1548 acquires from the server device 30 a payment completion notification indicating that the payment process has been completed.

[0100] The display content control unit 1549 controls the display unit 155 to generate display content to be displayed on the first display unit 131, the second display unit 132, and the third display unit 133.

[0101] The drive control unit 1550 controls the drive unit 123 to move or stop the mobile sales robot 10. Under the control of the drive control unit 1550, the mobile sales robot 10 performs patrol travel along a predetermined route and call travel to a call location designated by a customer.

[0102] In addition, when the drive control unit 1550 detects that the remaining quantity of any or all of the products stored in the storage unit 111 has reached zero, it moves the mobile sales robot 10, for example, to the back yard, and causes it to replenish the products whose remaining quantity has reached zero.

[0103] The display control unit 1551 controls the display unit 155 to display the display content generated by the display content control unit 1549 on the display unit 155. For example, the display control unit 1551 causes information related to the products registered by the product registration unit 1544 to be aligned and displayed on the first display unit 131. Furthermore, the display control unit 1551 receives an instruction that product registration has been completed, and displays information related to payment processing on the second display unit 132. Furthermore, when the shelf tag 113 is an electronic shelf tag, the display control unit 1551 controls the display of the electronic shelf tag. The display control unit 1551 is an example of a registration result display unit and a payment processing support unit in the present disclosure.

[0104] (Functional configuration of server device) The functional configuration of the server device 30 will be described with reference to Fig. 17. Fig. 17 is a functional block diagram showing an example of the functional configuration of the server device according to the embodiment.

[0105] The control unit 314 of the server device 30 loads a program into the RAM 313 and runs it, thereby realizing a transmission / reception unit 3141, an information management unit 3142, a matching unit 3143, a payment processing unit 3144, and a robot management unit 3145 as functional units, as shown in Fig. 17. Note that each of these functions may be configured by hardware such as a dedicated circuit.

[0106] The transmitting / receiving unit 3141 transmits and receives various information to and from external devices such as the user terminal 20 and each mobile vending robot 10 via the communication unit 315. For example, the transmitting / receiving unit 3141 receives, from each mobile vending robot 10, location information indicating the location of the mobile vending robot 10 and status information indicating the status of the mobile vending robot 10. The transmitting / receiving unit 3141 also transmits the location information and status information of the mobile vending robot 10 to the user terminal 20. The transmitting / receiving unit 3141 also receives a product information request from the user terminal 20 and transmits product information corresponding to the product information request to the user terminal 20.

[0107] The transmitter / receiver unit 3141 also receives a call request from the user terminal 20 and transmits a movement instruction to the mobile sales robot 10 identified by the robot ID included in the call request. The movement instruction instructs the mobile sales robot 10 to move to the call location included in the call request from the user terminal 20. The movement instruction includes information such as the terminal ID of the user terminal 20 that transmitted the call request and the call location.

[0108] The transmitting / receiving unit 3141 also receives an arrival notification from the mobile sales robot 10 and transmits the arrival notification to the user terminal 20 that is the source of the call request for the mobile sales robot 10. The arrival notification indicates that the mobile sales robot 10 has arrived at the designated call position. The arrival notification includes information such as the robot ID of the mobile sales robot that has arrived at the call position.

[0109] In addition, the transmitting / receiving unit 3141 transmits a pin code (authentication information) to the user terminal 20 in response to the call request, and receives the pin code input by the customer to the mobile sales robot 10 from the mobile sales robot. When the comparing unit 3143 compares the pin code transmitted to the user terminal 20 with the pin code input to the mobile sales robot 10, the transmitting / receiving unit 3141 transmits an authentication notification to the mobile sales robot 10. The authentication notification indicates that the customer who called the mobile sales robot 10 and the customer who is about to start shopping with the mobile sales robot 10 are the same.

[0110] Furthermore, the transmitting / receiving unit 3141 receives a payment request from the mobile vending robot 10, and when payment processing is completed in response to the payment request, transmits a payment completion notice to the mobile vending robot 10. The transmitting / receiving unit 3141 also transmits payment information indicating the details of the payment to the user terminal 20. The payment request requests payment processing for the price of the product purchased by the customer at the mobile vending robot 10. The payment request includes information necessary for the payment processing executed by the server device 30. The information necessary for the payment processing is customer facial image data for authenticating the customer and the product registration file 1624 of the product purchased by the customer. The payment request may also include information related to the payment method, such as credit card payment or electronic money payment. The payment completion notice indicates that payment has been completed in response to the payment request. The payment completion notice includes information such as a transaction ID that identifies the settled transaction. The payment information is information indicating the details of the payment related to the purchase of the product stored in the mobile vending robot 10.

[0111] The information management unit 3142 manages the setting order of the destinations of the mobile sales robot 10. Specifically, for call requests whose arrival dates and times are not registered in the call management table 3166, the information management unit 3142 moves the mobile sales robot 10 to the call location in order from the call request with the earliest call date and time.

[0112] The collating unit 3143 collates whether or not the customer who called the mobile sales robot 10 is the same as the customer who is about to start shopping at the mobile sales robot 10. Specifically, when the transmitting / receiving unit 3141 receives a call request from the user terminal 20, the collating unit 3143 issues a pin code associated with the call request. Then, the collating unit 3143 collates whether or not the pin code received by the transmitting / receiving unit 3141 from the mobile sales robot 10 is the same as the issued pin code.

[0113] The matching unit 3143 may use facial recognition to match a customer who has called the mobile sales robot 10 with a customer who is about to start shopping with the mobile sales robot 10. In this case, the transmitting / receiving unit 3141 receives facial image data from the mobile sales robot 10. The matching unit 3143 then refers to the user management table 3165 and performs matching based on the feature values of the received facial image data and the feature values of the face of the customer who has called. In the mobile sales system 1, matching between a customer who has called the mobile sales robot 10 and a customer who is about to start shopping with the mobile sales robot 10 is not essential. In other words, the server device 30 may not have the function of the matching unit 3143. For example, a customer who has not made a call request may be able to stop a traveling mobile sales robot 10 and purchase a product.

[0114] The payment processing unit 3144 executes payment processing related to the payment request received by the transmission / reception unit 3141 from the mobile sales robot 10. In this embodiment, the payment processing unit 3144 executes electronic payment processing using face authentication. The payment processing unit 3144 executes payment with the payment service provider based on the product registration file 1624 acquired by the transmission / reception unit 3141 from the mobile sales robot 10, on the condition that the facial image data of the customer received from the mobile sales robot 10 is authenticated by the verification unit 3143. The payment processing unit 3144 executes payment processing by communicating with the payment server of the payment service provider. The payment processing unit 3144 may execute electronic payment using credit card payment or two-dimensional code payment.

[0115] The mobile sales robot 10 may have some or all of the functions of the above-mentioned transmission / reception unit 3141, information management unit 3142, matching unit 3143, and payment processing unit 3144. In this case, the user terminal 20 transmits and receives various information to and from the mobile sales robot 10.

[0116] The robot management unit 3145 sets the destination and content of information to be sent by the transmission / reception unit 3141 based on a call request from the user terminal 20 and the location information and status information from each mobile sales robot 10. When the transmission / reception unit 3141 receives a call request from the user terminal 20, the robot management unit 3145 sets the mobile sales robot 10 corresponding to the robot ID included in the call request as the destination of the movement instruction and sets the call location included in the call request as the content of the transmission. In addition, the robot management unit 3145 checks the status information of each mobile sales robot 10 stored in the robot management table 3163 and selects the mobile sales robot 10 corresponding to the call request from among the mobile sales robots 10 in the "waiting for call" state.

[0117] In addition, the robot management unit 3145 sets the user terminal 20 that is the source of the call request as the destination, calculates the time required for the selected mobile sales robot 10 to arrive at the call location, and sets the estimated time as the content of the message to be sent. The estimated time is calculated based on the number of call requests (unanswered requests with no arrival date and time registered) for the mobile sales robot 10 registered in the call management table 3166, the preset purchase time limit for one transaction, and the location information and status information of the mobile sales robot 10 registered in the robot management table 3163.

[0118] In addition, the robot management unit 3145 refers to the product management table 3164 and sets the mobile sales robot 10 corresponding to the robot ID for which the remaining quantity of any or all of the products carried by it has reached zero as the destination of the movement instruction, and sets the location where the products will be replenished as the movement destination.

[0119] (User terminal functional configuration) The functional configuration of the user terminal 20 will be described with reference to Fig. 18. Fig. 18 is a functional block diagram showing an example of the functional configuration of the user terminal according to the embodiment.

[0120] The control unit 214 of the user terminal 20 deploys a program in the RAM 213 and runs it, thereby realizing a transmission / reception unit 2141, an input reception unit 2142, a self-position identification unit 2143, and a display control unit 2144 as functional units, as shown in Fig. 18. Note that each of these functions may be configured by hardware such as a dedicated circuit.

[0121] The transmitting / receiving unit 2141 transmits and receives various information to and from external devices such as the server device 30 via the communication unit 219. For example, the transmitting / receiving unit 2141 receives the robot ID, current location, status information, etc. of the mobile sales robot 10 from the server device 30. The transmitting / receiving unit 2141 also transmits product information requests, call requests, etc. to the server device 30.

[0122] The product information request specifies the mobile sales robot 10 and requests information on the products stored by the mobile sales robot 10, i.e., the products it sells. The product information request includes information such as the terminal ID of the user terminal 20 that made the request and the robot ID of the specified mobile sales robot 10. The call request specifies the mobile sales robot 10 and requests that the mobile sales robot 10 be called.

[0123] The call request specifies a mobile sales robot 10 and requests that the mobile sales robot 10 be called. The call request includes information such as the terminal ID of the user terminal 20 that made the request, the robot ID of the specified mobile sales robot 10, and location information (call location) indicating the location of the call destination. In addition, if the customer specifies authentication information, the call request further includes the specified authentication information. In this embodiment, the call location is the location where the user terminal 20 is located, i.e., the location determined by the positioning unit 218, but the customer may specify a desired call location on the user terminal 20.

[0124] The transmitting / receiving unit 2141 also receives the product information transmitted by the server device 30 in response to the product information request. Furthermore, the transmitting / receiving unit 2141 receives the pin code issued by the server device 30 in association with the call request. The pin code is authentication information used to authenticate (verify) whether the customer who called the mobile sales robot 10 is the same as the customer who is about to start shopping with the mobile sales robot 10.

[0125] Furthermore, the transmitting / receiving unit 2141 receives an arrival notification and a payment information notification from the server device 30. The arrival notification indicates that the mobile sales robot 10 has arrived at the call location specified in the call request. The payment information notification is information indicating the details of the payment for the purchase of the product stored in the mobile sales robot 10.

[0126] The input receiving unit 2142 receives input information based on the operation of the operation unit 216. For example, the input receiving unit 2142 receives a product information request or a call request from the operation unit 216.

[0127] The self-location identifying unit 2143 identifies the location of the user terminal 20 within the area represented by the map information 2201 based on the output of the positioning unit 218 .

[0128] The display control unit 2144 causes the display unit 215 to display various types of information. Specifically, the display control unit 2144 causes the display unit 215 to display various screens (GUI: Graphical User Interface) for supporting the purchase of products sold by the mobile sales robot 10. For example, the display control unit 2144 causes the display unit 215 to display a display screen for supporting the calling of the mobile sales robot 10. In addition, the display control unit 2144 causes the display unit 215 to display payment information indicating the payment details.

[0129] (Example of information displayed on a user device) An example of information display on the user terminal 20 will be described with reference to Fig. 19 and Fig. 20. Fig. 19 is a diagram showing an example of a current location display screen displayed on the display unit of the user terminal. Fig. 20 is a diagram showing an example of a call screen displayed on the display unit of the user terminal.

[0130] When a product information request menu is selected from a menu selection screen (not shown) on the user terminal 20, the display control unit 2144 displays a screen displaying the current position of the mobile sales robot 10 shown in Fig. 19. On the screen displaying the current position of the mobile sales robot 10, a robot mark 2152 indicating the current position of each mobile sales robot 10 in a map display area 2151 is displayed.

[0131] Each robot mark 2152 is drawn in a size that allows a customer to press it. A customer presses any of the robot marks 2152 to check the contents of the stored product.

[0132] 20 includes a list 2153 of products stored in the mobile sales robot 10 corresponding to the selected robot mark 2152, an estimated arrival time 2155, and a call button 2154. At the top of the call screen, an enlarged map display area 2151 near the selected robot mark 2152 is displayed.

[0133] The product list 2153 is a list showing product information of products carried by the mobile sales robot 10 corresponding to the selected robot mark 2152. The display control unit 2144 displays a list of product information transmitted from the server device 30 according to the selected mobile sales robot 10. Specifically, the display control unit 2144 displays the product information by arranging each product vertically. The displayed product information includes a product icon, product name, price, etc. The product list 2153 is scrollable vertically, and the display control unit 2144 updates the displayed product information in response to the customer's scrolling operation. This allows the product list 2153 to display product information of all products housed in the selected mobile sales robot 10.

[0134] The arrival time 2155 is the time required for the selected mobile sales robot 10 to arrive at the location of the user terminal 20 when the mobile sales robot 10 is called.

[0135] The required arrival time 2155 is estimated by the robot management unit 3145 of the server device 30 when the transmitting / receiving unit 2141 of the user terminal 20 transmits the location information identified by the self-location identification unit 2143 to the server device 30. Then, the transmitting / receiving unit 2141 obtains the estimated required time from the server device 30. Note that the required arrival time 2155 is estimated regardless of whether or not a call request has been made to the selected mobile sales robot 10.

[0136] The call button 2154 is a button for issuing a call request to the selected mobile sales robot 10. A customer can check the products stored in the mobile sales robot 10 selected on the current location display screen on the call screen, and if there is a product that the customer wishes to purchase, they can touch the call button 2154 to call the mobile sales robot 10.

[0137] Although detailed explanation will be omitted, the display unit 215 of the user terminal 20 also displays a screen displaying product information for the products stored by the mobile sales robot 10, a screen for selecting the mobile sales robot 10 based on the product name or product type, and the like.

[0138] (Screen displayed on the mobile sales robot) 21 and 22, the contents of the product registration screen 40 displayed on the first display unit 131 of the mobile sales robot 10 and the authentication screen 50 displayed on the second display unit 132 will be described. Fig. 21 is a diagram showing an example of the product registration screen. Fig. 22 is a diagram showing an example of the authentication screen.

[0139] As shown in FIG. 21, the product registration screen 40 displays information identifying the product M that the customer has taken out of the storage section 111, namely, a product icon 41, a product name 42, a registered number of items 43, and a subtotal 44, all aligned.

[0140] The product icon 41 is an image showing the product M.

[0141] Product name 42 is the name of product M.

[0142] The registered number 43 indicates the number of items M.

[0143] The subtotal 44 indicates the subtotal amount of each product M.

[0144] The display control unit 1551 arranges and displays the registered products in order from the top of the product registration screen 40. At this time, the product icon 41, product name 42, registered points 43, and subtotal 44 of the most recently registered product (product D in FIG. 21) are displayed with hatching. This allows the customer to immediately check the latest registered information. Furthermore, when the customer returns a product that was removed from the storage unit 111 to the storage unit 111, the display control unit 1551 deletes information related to that product from the product registration screen 40. The display form when the display control unit 1551 displays information related to registered products on the product registration screen 40 and the display form when the display control unit 1551 deletes information related to products that have been returned to the storage unit 111 from the product registration screen 40 will be described in detail later (see FIGS. 23, 24, and 25).

[0145] The display control unit 1551 identifies a product icon 41, a product name 42, a registered number of items 43, and a subtotal 44 based on the information related to the product M identified by the product identification unit 1543, and displays them on the display unit 155.

[0146] Furthermore, as shown in FIG. 21, the product registration screen 40 displays a total number of items 45, a total amount 46, and a registration completion button (checkout instruction button) 47.

[0147] The total points 45 is the total points of the registered products. The total points 45 is the sum of the registered points 43 of each product.

[0148] The total price 46 is the total price of the registered products. The total price 46 is the sum of the subtotals 44 of each product.

[0149] The registration completion button 47 is pressed by the customer when he or she has removed all of the products to be purchased from the storage unit 111. When the product registration unit 1544 detects that the registration completion button 47 has been pressed, it ends the product registration process. The registration completion button 47 is also pressed to instruct the customer to proceed to the payment process.

[0150] As shown in FIG. 22, authentication screens 50, 51, and 52 displayed on second display unit 132 display information according to the progress of the payment process.

[0151] When the product registration is complete, the display control unit 1551 displays information indicating the total amount, information indicating that payment is in progress, and a photographing frame 53 on the authentication screen 50. The photographing frame 53 indicates the area in which the customer's face captured by the imaging unit 134 should appear when the server device 30 performs face authentication of the customer before making a payment.

[0152] The display control unit 1551 displays the authentication screen 51 on which the image 54 of the customer captured by the imaging unit 134 is superimposed. The customer adjusts the position of their face on the authentication screen 51 so that their face is positioned inside the photographing frame 53.

[0153] The mobile sales robot 10 transmits the captured facial image of the customer to the server device 30. The server device 30 performs facial authentication on the facial image acquired from the mobile sales robot 10. If the facial authentication is successful, the server device 30 performs payment processing. Then, the server device 30 transmits a payment completion notice to the mobile sales robot 10, indicating that the payment has been completed. When the mobile sales robot 10 receives the payment completion notice from the server device 30, the display control unit 1551 displays an authentication screen 52 on which a message 55 indicating that the payment has been completed is displayed.

[0154] (Display format of product registration screen when registering a product) The display form of the product registration screen 40 displayed when the mobile sales robot 10 performs product registration processing will be described with reference to Fig. 23. Fig. 23 is a diagram showing an example of the display form of the product registration screen when registering a product.

[0155] A case will be described where a customer takes out product D from the storage unit 111 of the mobile sales robot 10. At this time, the product identification unit 1543 identifies that product D has been taken out from the shelf 112 of the storage unit 111. Then, the display control unit 1551 adds product D to the product registration screen 40.

[0156] At this time, the display control unit 1551 wipes in the information related to the product D from the bottom edge of the product registration screen 40. That is, the display control unit 1551 makes the information related to the product D appear from the bottom edge of the product registration screen 40 in the direction of the arrow Ra, as shown at time t=ta in FIG.

[0157] After that, at time t=tb (tb>ta), the display control unit 1551 moves the information related to the product D on the product registration screen 40 in the direction of the arrow Ra.

[0158] Furthermore, at time t=tc (tc>tb), the information related to product D is completely arranged on the product registration screen 40. At this time, the display control unit 1551 updates the total number of items and the total price of the product displayed at the bottom of the product registration screen 40 to values to which the information related to product D has been added. Note that the total number of items and the total price of the product are fixed when product D is removed from the shelf 112 of the storage unit 111. However, by updating the total number of items and the total price of the product when the information related to product D is wiped in on the product registration screen 40 and the arrangement is completed, it is possible to reliably notify the customer that the total number of items and the total price of the product have been updated. Of course, the total number of items and the total price of the product may also be updated when product D is removed from the shelf 112 of the storage unit 111.

[0159] It is desirable that the direction in which the information related to the product D is wiped in be a direction that corresponds to the positional relationship between the storage unit 111 and the product registration screen 40. In the present embodiment, since the product registration screen 40 is located above the storage unit 111, in order to accurately depict the state in which the product D taken out from below is added to the product registration screen 40 at the top, the information related to the product D is wiped in from the bottom edge of the product registration screen 40 upward. Similarly, if the product registration screen 40 is located to the left of the storage unit 111, it is desirable that the information related to the taken-out product D is wiped in from the right edge of the product registration screen 40 to the left. Furthermore, if the product registration screen 40 is located to the right of the storage unit 111, it is desirable that the information related to the taken-out product D is wiped in from the left edge of the product registration screen 40 to the right.

[0160] Furthermore, since the customer may bend down to remove the product from the storage unit 111, the customer may not be able to see the product registration screen 40 at the moment of removing the product D. Therefore, the display control unit 1551 may wipe in information related to the removed product D onto the product registration screen 40 after a predetermined time has elapsed since the product D was removed from the storage unit 111.

[0161] (Product registration screen display when product registration is canceled) 24 and 25, the display form of the product registration screen 40 when a customer cancels a product that has been registered will be described. Fig. 24 is a first diagram showing an example of the display form of the product registration screen when product registration is canceled. Fig. 25 is a second diagram showing an example of the display form of the product registration screen when product registration is canceled.

[0162] First, with reference to Fig. 24, a case will be described in which a customer returns product D, which was once registered, to the storage unit 111 of the mobile sales robot 10. At this time, the product identification unit 1543 identifies that product D has been returned to the shelf 112 of the storage unit 111. Then, the display control unit 1551 deletes product D from the product registration screen 40.

[0163] At this time, the display control unit 1551 wipes out the information related to the product D from the bottom edge of the product registration screen 40. That is, as shown at time t=tb (tb>ta) in FIG. 24, the display control unit 1551 moves the information related to the product D from the display position at time t=ta in the direction of arrow Rb.

[0164] Furthermore, at time t=tc (tc>tb), the information related to product D is wiped out from the bottom of the product registration screen 40. At this time, the display control unit 1551 updates the total points and total price of the products displayed at the bottom of the product registration screen 40 to values obtained by subtracting the information related to product D. The display control unit 1551 also deletes the information related to product D and hatches the information related to product C displayed at the bottom of the product registration list. Note that the total points and total price of the products are finalized when product D is returned to the shelf 112 of the storage unit 111. However, by updating the total points and total price of the products when the information related to product D is wiped out from the product registration screen 40, it is possible to reliably notify the customer that the total points and total price of the products have been updated. Of course, the total points and total price of the products may also be updated when product D is returned to the shelf 112 of the storage unit 111.

[0165] The direction in which the information related to the product D is wiped out is preferably determined according to the relative positions of the storage unit 111 and the product registration screen 40. In this embodiment, since the product registration screen 40 is located above the storage unit 111, the information related to the product D is wiped out downward from the bottom edge of the product registration screen 40 to accurately represent the state in which the product D registered in the upper product registration screen 40 is being returned to the storage unit 111 below. Similarly, if the product registration screen 40 is located to the left of the storage unit 111, the information related to the product D returned to the storage unit 111 is preferably wiped out from the right edge of the product registration screen 40 to the right. Furthermore, if the product registration screen 40 is located to the right of the storage unit 111, the information related to the product D returned to the storage unit 111 is preferably wiped in from the left edge of the product registration screen 40 to the left.

[0166] Furthermore, since the customer may bend down to return the product to the storage unit 111, the customer may not be able to see the product registration screen 40 at the moment of returning the product D. Therefore, the display control unit 1551 may wipe out information related to the returned product D from the product registration screen 40 after a predetermined time has elapsed since the product D was returned to the storage unit 111.

[0167] Next, with reference to Fig. 25, a case will be described in which a customer returns product B, which has been registered once, to the storage unit 111 of the mobile sales robot 10, i.e., a product that is in the middle of the product registration list. At this time, the product identification unit 1543 identifies that product B has been returned to the shelf 112 of the storage unit 111. Then, the display control unit 1551 deletes product B from the product registration screen 40.

[0168] At this time, the display control unit 1551 wipes out the information related to product B from the bottom edge of the product registration screen 40. That is, as shown at time t=tb (tb>ta) in Fig. 25 , the display control unit 1551 moves the information related to product B in the direction of arrow Rc from the display position at time t=ta. At this time, the information related to product B moves in the direction of arrow Rc so as to hide behind the information related to product C and the information related to product D that have already been registered.

[0169] Furthermore, at time t=tc (tc>tb), the information related to product B is wiped out from the bottom of the product registration screen 40. Then, as shown at time t=tc in FIG. 25 , the display control unit 1551 moves the information related to product C and the information related to product D in the direction of arrow Rd to fill in the blanks left blank by the wiping out of the information related to product B. At this time, the display control unit 1551 updates the total points and total price of the products displayed at the bottom of the product registration screen 40 to values obtained by subtracting the information related to product B. Note that the total points and total price of the products are fixed when product B is returned to the shelf 112 of the storage unit 111. However, by updating the total points and total price of the products when the information related to product B is wiped out from the product registration screen 40, it is possible to reliably notify the customer that the total points and total price of the products have been updated. Of course, the total points and total price of the products may also be updated when product B is returned to the shelf 112 of the storage unit 111.

[0170] As described above, it is desirable that the direction in which the information related to product B is wiped out be a direction according to the positional relationship between the storage unit 111 and the product registration screen 40. Furthermore, the display control unit 1551 may wipe out the information related to the returned product B from the product registration screen 40 after a predetermined time has elapsed since the product B was returned to the storage unit 111.

[0171] (Product registration screen transition) The transition of the screen displayed on the first display unit 131 of the mobile sales robot 10 will be described with reference to Fig. 26. Fig. 26 is a diagram showing an example of the transition of the screen displayed on the first display unit of the mobile sales robot according to the embodiment.

[0172] The screen 61 is displayed when the mobile sales robot 10 arrives at the location of the customer who made the call request. The screen 61 announces to the customer that they can start shopping.

[0173] Screens 62 and 63 are displayed when a customer takes out product M from the storage section 111 of the mobile sales robot 10. Screen 64 is displayed when a customer returns product M that he or she has taken out to the storage section 111 of the mobile sales robot 10.

[0174] Screen 65 is a screen that is displayed when a customer presses the registration completion button 47 (see FIG. 21). Screen 65 shows that the mobile sales robot 10 turns around on the spot, and the second display unit 132, which shows the progress of the payment process, faces the customer instead of the first display unit 131 that had faced the customer until then.

[0175] Screen 66 is an example of a screen displayed on first display unit 131 during payment processing. At this time, various advertisement screens are displayed in the upper part of the screen of first display unit 131.

[0176] The screens 67 and 68 are examples of various advertisements that are displayed on the first display unit 131 or the third display unit 133 when the mobile sales robot 10 finishes selling a product to a customer who has received a call request and moves to a fixed location, for example. The advertisements include an advertisement related to the mobile sales robot 10 (screen 67), an advertisement related to an event being held (screen 68), and a company advertisement (not shown). When and what type of advertisement is displayed is determined, for example, by the display content control unit 1549 of the mobile sales robot 10 based on the date and time, the location of the movement, the details of the store event, etc.

[0177] (Processing flow of the mobile sales system) The flow of processing performed by the mobile sales system 1 will be described with reference to Fig. 27. Fig. 27 is a sequence diagram showing an example of the flow of processing performed by the mobile sales system according to the embodiment. The sequence diagram in Fig. 27 shows a case where a customer checks the product information of the product M stored in the mobile sales robot 10, calls the mobile sales robot 10, and purchases the product M.

[0178] To call the mobile sales robot 10, a customer starts the application program of the mobile sales system 1 installed in the user terminal 20. When the product information request menu is selected, the user terminal 20 displays a screen showing the current location of the mobile sales robot 10 as shown in Fig. 19 and accepts the selection of the mobile sales robot 10 (step S1). The user terminal 20 transmits a product information request including the robot ID of the selected mobile sales robot 10 and the terminal ID of the user terminal 20 to the server device 30 (step S2).

[0179] The server device 30 reads out the product information from the storage unit 316 in response to the received product information request (step S3). Next, the server device 30 transmits the read out product information to the user terminal 20 (step S4). The communication address of the user terminal 20 may be registered in advance in the user management table 3165, or may be included in the product information request.

[0180] The user terminal 20 displays the received product information on the display unit 215 (step S5). When the customer checks the displayed product information and finds a product they want to purchase, they perform an operation to call the mobile sales robot 10 that stores the product. This inputs a call request to the user terminal 20 (step S6). The user terminal 20 acquires location information of the location where the user terminal 20 is located (step S7), and transmits a call request to the server device 30 with the acquired location information as the call location (step S8).

[0181] When the server device 30 receives the call request, it executes a call request acceptance process (step S9). The server device 30 transmits the PIN code issued in the call request acceptance process to the user terminal 20 (step S10). The server device 30 also transmits a movement instruction including a call position to the mobile sales robot 10 specified in the call request (step S11).

[0182] The mobile sales robot 10 controls the driving unit 123 to move to the call position specified in the movement instruction (step S12). When the mobile sales robot 10 arrives at the call position, the mobile sales robot 10 transmits an arrival notification to the server device 30 (step S13). Note that the mobile sales robot 10 may transmit only location information indicating its own location to the server device 30, and the server device 30 may determine whether the mobile sales robot 10 has arrived at the call position.

[0183] The server device 30 updates the call management table 3166 based on the received arrival notification (step S14). Specifically, the server device 30 registers the arrival date and time of the corresponding call request in the call management table 3166. Next, the server device 30 transmits the arrival notification to the user terminal 20 that is the source of the call request (step S15).

[0184] When the user terminal 20 receives the arrival notification, the display unit 215 displays information indicating that the called mobile sales robot 10 has arrived (step S16). This allows the customer to recognize the arrival of the mobile sales robot 10 and enters the pin code received from the server device 30 into the operation unit 156 of the mobile sales robot 10 (step S17).

[0185] When the mobile sales robot 10 receives the input of the pin code, it transmits an authentication request including the input pin code and robot ID to the server device 30 (step S18).

[0186] The server device 30 authenticates the pin code (step S19). If the server device 30 authenticates the pin code and determines that the user who made the call request matches the user who is about to start shopping, it transmits an authentication notification to the mobile sales robot 10 (step S20).

[0187] When the mobile sales robot 10 receives the authentication notification, it permits the process related to the sale of the product. Then, when it detects that the product has been removed from the storage unit 111, it executes product registration for the product (step S22). Furthermore, when the mobile sales robot 10 returns the removed product to the shelf 112, it cancels the product registration (step S23).

[0188] When the mobile sales robot 10 detects that the registration completion button 47 has been pressed, it determines that the product registration has been completed (step S24). Next, the mobile sales robot 10 rotates 90° on the spot and turns the second display unit 132 toward the customer (step S25). Then, the mobile sales robot 10 captures an image of the customer's face to authenticate the customer (step S26), and transmits the captured image of the customer's face to the server device 30 to request authentication (step S27).

[0189] The server device 30 performs face authentication (step S28), and if the authentication is successful, transmits an authentication notification to the mobile sales robot 10 (step S29).

[0190] Upon receiving the authentication notification, the mobile sales robot 10 transmits the product registration file 1624 to the server device 30 to request payment (step S30).

[0191] The server device 30 executes the payment process based on the received payment request (step S31). When the payment is successfully completed in the payment process, the server device 30 transmits a payment completion notice to the mobile sales robot 10 (step S32). In addition, the server device 30 transmits payment information indicating the payment details to the user terminal 20 (step S33).

[0192] When the mobile sales robot 10 receives the payment completion notice, it displays information indicating that the payment has been completed on the second display unit 132 (step S34).

[0193] When the user terminal 20 receives the payment information, it displays information indicating the payment details on the display unit 215 (step S35).

[0194] Through the above operations, the mobile sales system 1 moves the mobile sales robot 10 storing the merchandise to a position designated by the user, and enables the mobile sales robot 10 to sell the merchandise.

[0195] (Product registration process flow performed by a mobile sales robot) The flow of the product registration process performed by the mobile sales robot 10 will be described with reference to Fig. 28. Fig. 28 is a flowchart showing an example of the flow of the product registration process performed by the mobile sales robot according to the embodiment. The flowchart shown in Fig. 28 shows in detail the flow of the process performed from step S21 to step S24 in Fig. 27.

[0196] The product identification unit 1543 determines whether the product M has been removed from the shelf 112 of the storage unit 111 (step S41). If it is determined that the product M has been removed (step S41: Yes), the process proceeds to step S42. On the other hand, if it is not determined that the product M has been removed (step S41: No), the process proceeds to step S45.

[0197] If it is determined in step S41 that the product M has been taken out, the product identification unit 1543 identifies the taken-out product M (step S42).

[0198] The product registration unit 1544 updates the product registration file 1624 by adding the information related to the product M identified in step S42 to the product registration file 1624 (step S43).

[0199] The display control unit 1551 updates the product registration screen 40 displayed on the first display unit 131 of the mobile sales robot 10 by adding information related to the product M identified in step S42 to the product registration screen 40 (step S44).

[0200] In step S41, if it is determined that the product M has not been removed, or following step S44, the product identification unit 1543 determines whether the product M has been returned to the shelf 112 of the storage unit 111 (step S45). If it is determined that the product M has been returned (step S45: Yes), the process proceeds to step S46. On the other hand, if it is not determined that the product M has been returned (step S45: No), the process proceeds to step S49.

[0201] If it is determined in step S45 that the product M has been returned, the product identification unit 1543 identifies the returned product M (step S46).

[0202] The product registration unit 1544 updates the product registration file 1624 by deleting the information related to the product M identified in step S46 from the product registration file 1624 (step S47).

[0203] The display control unit 1551 updates the product registration screen 40 displayed on the first display unit 131 of the mobile sales robot 10 by deleting information related to the product M identified in step S46 from the product registration screen 40 (step S48).

[0204] The product registration unit 1544 determines whether the registration of all products to be purchased by the customer has been completed (step S49). If it is determined that the registration of all products to be purchased by the customer has been completed (step S49: Yes), the mobile sales robot 10 ends the processing of FIG. 28. On the other hand, if it is determined that the registration of all products to be purchased by the customer has not been completed (step S49: No), the processing returns to step S41. Whether the registration of all products to be purchased by the customer has been completed is determined by detecting that the customer has pressed the registration completion button 47.

[0205] (Payment processing flow performed by the mobile sales system) The flow of the payment process performed by the mobile sales system 1 will be described using Figure 29. Figure 29 is a flowchart showing an example of the flow of the payment process performed by the mobile sales system according to the embodiment. Below, the flow of the payment process performed by the mobile sales robot 10, the flow of the payment process performed by the server device 30, and the flow of the payment process performed by the user terminal 20 will be described in order.

[0206] (Payment processing flow performed by a mobile sales robot) Steps S61 to S69 in FIG. 29 show in detail the flow of the processing performed by the mobile sales robot 10 in steps S25, S26, S27, S29, S30, S32, and S34 in FIG.

[0207] The display control unit 1551 causes the second display unit 132 to display the authentication screen 50 (step S61).

[0208] The robot direction control unit 1545 rotates the direction of the mobile sales robot 10 by 90 degrees so that the second display unit 132 faces the customer (step S62).

[0209] The user authentication unit 1546 causes the imaging unit 134 to capture image data (step S63).

[0210] The display control unit 1551 displays the image data captured by the imaging unit 134 on the authentication screen 50 (step S64).

[0211] The user authentication unit 1546 outputs the image data to the server device 30 (step S65).

[0212] The user authentication unit 1546 determines whether an authentication notification has been received from the server device 30 (step S66). If it is determined that an authentication notification has been received (step S66: Yes), the process proceeds to step S67. On the other hand, if it is not determined that an authentication notification has been received (step S66: No), the process returns to step S63.

[0213] If it is determined in step S66 that the authentication notification has been acquired, the product registration information output unit 1547 outputs the product registration file 1624 to the server device 30 (step S67).

[0214] The payment completion notification acquisition unit 1548 determines whether a payment completion notification has been acquired from the server device 30 (step S68). If it is determined that a payment completion notification has been acquired (step S68: Yes), the process proceeds to step S69. On the other hand, if it is not determined that a payment completion notification has been acquired (step S68: No), step S68 is repeated.

[0215] If it is determined in step S68 that a payment completion notice has been acquired, the display control unit 1551 displays a payment completion message on the authentication screen 50 to indicate that the payment has been completed (step S69). After that, the mobile sales robot 10 ends the payment process.

[0216] (Flow of payment processing performed by the server device) Steps S71 to S78 in FIG. 29 show in detail the flow of the processing performed by the server device 30 in steps S27, S28, S29, S30, S31, S32, and S33 in FIG.

[0217] The transmitting / receiving unit 3141 determines whether image data has been acquired from the mobile sales robot 10 (step S71). If it is determined that image data has been acquired from the mobile sales robot 10 (step S71: Yes), the process proceeds to step S72. On the other hand, if it is not determined that image data has been acquired from the mobile sales robot 10 (step S71: No), step S71 is repeated.

[0218] When it is determined in step S71 that image data has been acquired from the mobile sales robot 10, the matching unit 3143 performs face authentication (step S72).

[0219] The matching unit 3143 determines whether the face authentication has been successful (step S73). If it is determined that the face authentication has been successful (step S73: Yes), the process proceeds to step S74. On the other hand, if it is determined that the face authentication has not been successful (step S73: No), the process returns to step S71.

[0220] If it is determined in step S73 that the face authentication has been successful, the transmitting / receiving unit 3141 transmits an authentication notification to the mobile sales robot 10 that transmitted the image data (step S74).

[0221] The transmitting / receiving unit 3141 determines whether the product registration file 1624 has been acquired from the mobile sales robot 10 that transmitted the authentication notification in step S74 (step S75). If it is determined that the product registration file 1624 has been acquired (step S75: Yes), the process proceeds to step S76. On the other hand, if it is not determined that the product registration file 1624 has been acquired (step S75: No), step S75 is repeated.

[0222] If it is determined in step S75 that the product registration file 1624 has been acquired from the mobile sales robot 10 that sent the authentication notification, the settlement processing unit 3144 performs settlement processing based on the product registration file 1624 (step S76).

[0223] The transmitting / receiving unit 3141 transmits a settlement completion notice to the mobile sales robot 10 (step S77).

[0224] Furthermore, the transmitting / receiving unit 3141 transmits payment information indicating the content of the payment process to the user terminal 20 (step S78). After that, the server device 30 ends the payment process.

[0225] (Payment process flow performed by user terminal) Steps S81 to S82 in FIG. 29 show in detail the flow of the processing performed by the user terminal 20 in steps S33 and S35 in FIG.

[0226] The transmitting / receiving unit 2141 determines whether payment information has been acquired from the server device 30 (step S81). If it is determined that payment information has been acquired (step S81: Yes), the process proceeds to step S82. On the other hand, if it is not determined that payment information has been acquired (step S81: No), step S81 is repeated.

[0227] If it is determined in step S81 that the payment information has been acquired, the display control unit 2144 displays the payment information on the display unit 215 (step S82). After that, the user terminal 20 ends the payment process.

[0228] (Effects of the embodiment) As described above, the mobile vending robot 10 (unmanned vending machine) of the embodiment includes a product identification unit 1543 that identifies the product M taken out of the storage unit 111 that stores the product M or the product M returned to the storage unit 111, a product registration unit 1544 that registers the product M identified by the product identification unit 1543 as having been taken out of the storage unit 111, a display control unit 1551 (registration result display unit) that aligns and displays information related to the product M registered by the product registration unit 1544 on the first display unit 131, and a display control unit 1551 (payment processing support unit) that receives an instruction that product registration has been completed and displays information related to payment processing on the second display unit 132. Therefore, the registration status of the purchased product and the progress of payment processing can be displayed in an easy-to-understand manner.

[0229] Furthermore, in the mobile sales robot 10 (unmanned sales device) of the embodiment, the display control unit 1551 (registration result display unit) wipes in information related to the product M identified as having been taken out from the storage unit 111 onto the first display unit 131 in a direction from the storage unit 111 toward the first display unit 131. Therefore, it is possible to inform the customer in an easy-to-understand manner that the purchased product has been registered.

[0230] Furthermore, in the mobile sales robot 10 (unmanned sales device) of the embodiment, the display control unit 1551 (registration result display unit) causes the first display unit 131 to wipe out information related to the product M that has been returned to the storage unit 111 after registration in a direction from the first display unit 131 toward the storage unit 111. Therefore, it is possible to inform the customer in an easy-to-understand manner that the product that was once registered has been canceled.

[0231] In the mobile sales robot 10 (unmanned sales device) of the embodiment, the first display unit 131 and the second display unit 132 are provided on different sides of the mobile sales robot 10. Therefore, the content of the process being executed by the mobile sales robot 10 is displayed on the screen facing the customer, so that the operating status of the mobile sales robot 10 can be communicated to the customer in an easy-to-understand manner.

[0232] (Modification of the embodiment) In the above-described embodiment, the first display unit 131 that displays registration information and the second display unit 132 that displays information related to payment processing are installed on different surfaces of the mobile sales robot 10, but the positional relationship between the first display unit 131 and the second display unit 132 is not limited to this.

[0233] Another embodiment of the positional relationship between first display unit 131 and second display unit 132 will be described below with reference to Figures 30, 31, and 32. Figure 30 is a first diagram showing an example of another display format for product registration information and information related to payment processing. Figure 31 is a second diagram showing an example of another display format for product registration information and information related to payment processing. Figure 32 is a third diagram showing an example of another display format for product registration information and information related to payment processing.

[0234] FIG. 30 shows an example in which the product registration screen 40 and the authentication screen 51 are displayed on the same first display unit 131. In this way, by displaying the information related to the payment process that was displayed on the second display unit 132 in a part of the first display unit 131 that displays the product registration screen 40, the customer can easily and reliably recognize the operating status of the mobile sales robot 10. Note that, according to the configuration of FIG. 30, the second display unit 132 is unnecessary. Moreover, since only the display location of the authentication screen 51 changes, the flow of the product registration process (FIG. 28) and the flow of the payment process (FIG. 29) described above remain unchanged.

[0235] 31 shows an example in which a first display unit 131 displaying the product registration screen 40 and a second display unit 132 displaying the authentication screen 51 related to the payment process are installed adjacent to each other on the same face of the mobile sales robot 10. By adopting such a display format, customers can easily and reliably recognize the operating status of the mobile sales robot 10. Note that since only the display position of the authentication screen 51 changes, the flow of the product registration process (FIG. 28) and the flow of the payment process (FIG. 29) described above remain unchanged.

[0236] 32 shows an example in which the product registration screen 40 and the authentication screen 51 are switched between for display. That is, when the mobile sales robot 10 detects that product registration has been completed, it erases the product registration screen 40 that was displayed on the first display unit 131 and displays the authentication screen 51 on the first display unit 131. Even with this display format, customers can easily and reliably recognize the operating status of the mobile sales robot 10. Note that since only the display position of the authentication screen 51 changes, the flow of the product registration process (FIG. 28) and the flow of the payment process (FIG. 29) described above remain unchanged.

[0237] (Operations and Effects of Modified Embodiments) As described above, in the mobile sales robot 10 (unmanned sales device) according to the modified embodiment, the information displayed on the second display unit 132 is displayed on a part of the first display unit 131. Therefore, customers can easily and reliably recognize the operating status of the mobile sales robot 10.

[0238] In the mobile sales robot 10 (unmanned sales device) according to the modified embodiment, the first display unit 131 and the second display unit 132 are provided adjacent to each other. Therefore, customers can easily and reliably recognize the operating state of the mobile sales robot 10.

[0239] Although the embodiments of the present invention have been described above, these embodiments are merely examples and are not intended to limit the scope of the invention. This novel embodiment can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0240] 1 Mobile sales system 10 Mobile sales robot (unmanned vending machine) 11 Main body 12 Moving section 13 User Interface Section 111 Storage unit 112 Shelves 131 1st display section 132 2nd display section 133 Third display section 134 Imaging unit 154 Control Unit 1541 Transmitter / Receiver 1542 Self-location part 1543 Product Specification Department 1544 Product Registration Department 1545 Robot Orientation Control Unit 1546 User Authentication Unit 1547 Product registration information output unit 1548 Payment completion notification acquisition unit 1549 Display content control unit 1550 Drive control unit 1551 Display control unit (registration result display unit, payment processing support unit) 159 Weight detection unit 20 User terminal 214 Control Unit 2141 Transmitter / Receiver 2142 Input reception section 2143 Self-location part 2144 Display control unit 30 Server device 314 Control Unit 3141 Transmitter / Receiver 3142 Information Management Department 3143 Collation Unit 3144 Payment processing unit 3145 Robot Management Department 40 Product registration screen 50, 51, 52 Authentication screen M product [Prior art documents] [Patent documents]

[0241] [Patent Document 1] Japanese Patent Application Laid-Open No. 2008-87892

Claims

1. An unmanned vending machine having a storage unit for storing products to be sold and a drive unit for moving the machine, a product identification unit that identifies a product removed from the storage unit or a product returned to the storage unit based on a change in weight of the storage unit; a product registration unit that registers the product identified by the product identification unit as having been removed from the storage unit; a registration result display unit that displays information about the products registered by the product registration unit in a line on a first display unit provided on a side facing the storage unit; a payment processing support unit that receives an instruction that product registration has been completed, rotates its own orientation, faces a second display unit that is installed in a different orientation from the first display unit, and displays information related to payment processing on the second display unit. Unmanned vending machine.

2. the registration result display unit wipes in information related to the product identified as having been removed from the storage unit onto the first display unit in a direction from the storage unit toward the first display unit. The unmanned vending machine according to claim 1.

3. the registration result display unit wipes out information about the product that has been registered and returned to the storage unit onto the first display unit in a direction from the first display unit toward the storage unit. The unmanned vending machine according to claim 1 or 2.

4. The first display unit and the second display unit are provided on different surfaces of the unmanned vending machine. The unmanned vending machine according to any one of claims 1 to 3.

Images