Mobile sales system and server device

Abstract

To provide a mobile sales system that enables a device loaded with an article to move to a location that a user specifies to sell the article, and a server device.SOLUTION: A mobile sales system according to an embodiment has a mobile sales device which comprises a loading part loaded with articles to be sold and a drive part which moves the device, and a terminal device which can specify a calling location of the mobile sales device. The terminal device comprises a transmission part which transmits location information specifying the calling location of the mobile sales device. The mobile sales device comprises an acquisition part which acquires the location information that the terminal device transmits, a drive control part which controls the drive part based upon the location information that the acquisition part acquires, and an accounting processing part which executes accounting processing based upon article information on an article taken out of the loading part.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a mobile sales system and a server device. [Background technology]

[0002] Conventionally, a system has been proposed that includes a robot (shopping support device) that moves around a store selling merchandise to assist customers in their shopping (for example, Patent Document 1). The robot in the system patrols the store, accepting purchased merchandise from customers and carrying it to the cash register, thereby assisting 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 that the present invention aims to solve is to provide a mobile sales system and a server device that enable a device loaded with products to move to a location specified by a user and sell the products. [Means for solving the problem]

[0005] The mobile sales system of the embodiment is a mobile sales system having a mobile sales device equipped with a mounting unit for mounting the goods to be sold and a driving unit for moving the device, and a terminal device capable of specifying a call location for the mobile sales device, wherein the terminal device has a transmitting unit for transmitting location information indicating the call location of the mobile sales device, and the mobile sales device has an acquiring unit for acquiring the location information transmitted by the terminal device, a driving control unit for controlling the driving unit based on the location information acquired by the acquiring unit, and an accounting processing unit for performing accounting processing based on the product information of the goods taken out from the mounting unit. The mobile sales device further includes a detection unit that detects merchandise removed from the mounting unit, an input unit into which trigger information that is a condition for starting sales is input, and an alarm unit that issues an alarm when it detects that a merchandise from the mounting unit is being removed without the trigger information being input into the input unit. [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 perspective view showing an example of the external configuration of the mobile vending device according to the embodiment. [Figure 3] FIG. 3 is a perspective view showing an example of the external configuration of the mobile vending device according to the embodiment. [Figure 4] FIG. 4 is a perspective view showing an example of the external configuration of the mobile vending device according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a hardware configuration of the mobile vending device according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of the product master according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of a stocked product table according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a hardware configuration of a user terminal according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a data configuration of a robot management table according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a data configuration of a product management table according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a data configuration of a user management table according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a data configuration of a call management table according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of the data configuration of the transaction management table. [Figure 15] FIG. 15 is a block diagram showing an example of the functional configuration of each device constituting the mobile sales system. [Figure 16]FIG. 16 is a diagram showing an example of a first display screen on the display unit of the user terminal. [Figure 17] FIG. 17 is a diagram showing an example of a second display screen on the display unit of the user terminal. [Figure 18] FIG. 18 is a diagram showing an example of a third display screen on the display unit of the user terminal. [Figure 19] FIG. 19 is a diagram showing an example of a fourth display screen on the display unit of the user terminal. [Figure 20] FIG. 20 is a diagram showing an example of a call location designation screen displayed on the display unit of the user terminal. [Figure 21] FIG. 21 is a diagram showing an example of a display screen displayed on the display unit of the user terminal when the mobile vending device arrives at the calling position. [Figure 22] FIG. 22 is a diagram showing another example of a display screen displayed on the display unit of the user terminal when the mobile vending device arrives at the calling position. [Figure 23] FIG. 23 is a diagram showing an example of a display screen displayed on the display unit of the user terminal when the purchase time limit has elapsed. [Figure 24] FIG. 24 is a sequence chart showing an example of the operation of the mobile sales system. [Figure 25] FIG. 25 is a flowchart showing an example of the flow of a call request acceptance process by the control unit of the server device. [Figure 26] FIG. 26 is a flowchart showing an example of the flow of transaction processing in the control unit of the mobile vending machine. [Figure 27] FIG. 27 is a flowchart showing an example of the flow of the payment process by the control unit of the server device. 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] Fig. 1 is a diagram showing an example of the configuration of a mobile sales system according to an embodiment. As shown in Fig. 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).

[0009] The mobile sales robot 10 is a self-propelled sales device that transports and sells merchandise without any human intervention, and is an example of a mobile sales device. For example, the mobile sales robot 10 travels within a predetermined area such as a shopping mall, selling 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 limited to the example shown in FIG. 1.

[0010] The external configuration of the mobile sales robot 10 will now be described with reference to Figures 2 to 4. Figures 2 to 4 are perspective views showing an example of the external configuration of the mobile sales robot 10.

[0011] 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 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 (the negative Y-axis side) will also be referred to as the front side of the mobile sales robot 10. The right side 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.

[0012] 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.

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

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

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

[0016] 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 the main body 11 may be open on one side (for example, the front side).

[0017] 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 products in the storage section 111 from falling out of the storage section 111 when the mobile sales robot 10 is moving, etc.

[0018] 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.

[0019] 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 under the control of a control unit 154 (described later) to indicate the operating status of the mobile sales robot 10. For example, the light emitting unit 114 emits light when the mobile sales robot 10 is moving, thereby indicating that the mobile sales robot 10 is moving.

[0020] The light emitted by the light emitting unit 114 is not limited to a single color. For example, the light emitting unit 114 may emit different colors or change light emission patterns depending on the operating state of the mobile sales robot 10. The light emitting unit 114 may be provided on the rear side of the main body 11, not necessarily on the front side.

[0021] The ranging sensor 115 is a sensor device for detecting objects present around the mobile sales robot 10 and detecting the distance to the objects. The sensing results of the ranging sensor 115 are output to the control unit 154 (described later) and are used for collision avoidance during movement, user detection, etc. The ranging sensor 115 can be realized by, for example, a sensor device that detects objects and measures distances using captured images or ultrasonic waves, or a sensor device such as 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. Furthermore, the imaging unit 134, 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 causing the mobile sales robot 10 (movement unit 12) to move forward, backward, or rotate.

[0026] 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.

[0027] 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 back side of the mobile sales robot 10. The third display unit 133 is a display device installed on the rear 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 the sale of the product C, etc., under the control of the control unit 154, which will be described later.

[0028] The imaging unit 134 is installed on the rear side of the mobile sales 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). The imaging unit 134 captures an image of a user using the mobile sales robot 10 to obtain an image of the user's face, etc.

[0029] The disinfection device 135 is a device for disinfecting a user of the mobile sales robot 10. In this embodiment, disinfection means killing (or removing) pathogenic bacteria, viruses, and other microorganisms present on an object to the extent that they are harmless. Disinfection can also be interpreted as sterilization, sterilization, or sterilization.

[0030] 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 a user operation.

[0031] The operating status of the sterilization device 135 may be configured to be electrically output to the control unit 154 described later. In this case, for example, the user interface unit 13 or the sterilization device 135 includes a sensor device (hereinafter also referred to as a sterilization operation detection unit) that detects the sterilization operation of the sterilization device 135. When the sterilization operation detection unit detects that the sterilization operation has been performed by the sterilization device 135, it outputs a detection signal to the control unit 154 described later.

[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 those shown in the illustration. The user interface unit 13 may be configured without the disinfection device 135. Furthermore, the user interface unit 13 may 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 device used by a user of the mobile sales system 1, and is an example of a terminal device. 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 user requesting to call the mobile sales robot 10, and transmits the accepted call request to the server device 30. Note that the number of user terminals 20 is not limited to the example in FIG. 1.

[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 robots 10 and causes the mobile sales robots 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 robots 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] The hardware configuration and functional configuration of each device of the mobile sales system 1 will be described below.

[0036] First, we will explain the hardware configuration of the mobile sales robot 10. Fig. 5 is a diagram showing an example of the hardware configuration of the mobile sales robot 10. As shown in Fig. 5, the mobile sales robot 10 includes a CPU (Central Processing Unit) 151, a ROM (Read Only Memory) 152, and a RAM (Random Access Memory) 153.

[0037] The CPU 151 is an example of a processor, and performs overall control of each part of the mobile sales robot 10. The ROM 152 stores various programs. The RAM 153 is a workspace for developing programs and various data.

[0038] The CPU 151, ROM 152, and RAM 153 are connected via a bus or the like to form a computer-configured control unit 154. In the control unit 154, the CPU 151 operates in accordance with a program stored in the storage unit 162 and loaded into the RAM 153, thereby executing various processes.

[0039] The mobile sales robot 10 also includes the above-mentioned light-emitting unit 114, driving unit 123, and imaging unit 134. The mobile sales robot 10 also includes a display unit 155, an operation unit 156, a sound collection unit 157, a sensor unit 158, a weight detection unit 159, a positioning unit 160, a communication unit 161, and a memory unit 162.

[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 content of an operation received from a user 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 users who wish to purchase a product 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 measurement sensor 115, the disinfection operation detection unit, etc. 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.

[0045] Here, each shelf 112 is associated in advance with the weight detection unit 159 installed on that shelf 112, and when a weight change is detected by the weight detection unit 159, it is possible to identify the shelf 112 where the change occurred.

[0046] 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.

[0047] 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).

[0048] 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.

[0049] 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.

[0050] 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.

[0051] The storage unit 162 also stores map information 1621, a product master 1622, and a stocked product table 1623. The map information 1621 is information showing a map of the range in which the mobile sales robot 10 moves.

[0052] The product master 1622 is a data table that stores information about products for sale. Fig. 6 is a diagram showing an example of the data configuration of the product master 1622. 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, image data, etc.

[0053] The data configuration of the product master 1622 is not limited to the example shown in Fig. 6. For example, the product master 1622 may store image data representing the characteristics of the product in the product information.

[0054] 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 in the same way as in the configuration in which the product master 1622 is stored, by referring to the product master 3162 stored in the server device 30.

[0055] The stored product table 1623 is a data table for storing information about products stored in the storage section 111. Fig. 7 is a diagram showing an example of the data configuration of the stored product table 1623. 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.

[0056] 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.

[0057] Next, a description will be given of the hardware configuration of the user terminal 20. Fig. 8 is a diagram showing an example of the hardware configuration of the user terminal 20. As shown in Fig. 8, the user terminal 20 includes a CPU 211, a ROM 212, and a RAM 213.

[0058] The CPU 211 is an example of a processor, and performs overall control of each unit of the user terminal 20. The ROM 212 stores various programs. The RAM 213 is a workspace where programs and various data are developed.

[0059] The CPU 211, ROM 212, and RAM 213 are connected via a bus or the like to form a computer-configured control unit 214. In the control unit 214, the CPU 211 operates in accordance with a control program stored in the storage unit 220 and loaded into the RAM 213, thereby executing various processes.

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

[0061] 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 contents of an operation received from a user 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.

[0062] 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 the user who uses the user terminal 20, thereby acquiring an image of the user's face, etc.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] The storage unit 220 also stores map information 2201. Here, the map information 2201, like the map information 1621, is information showing a map of the area in which the mobile sales robot 10 moves.

[0067] Next, a description will be given of the hardware configuration of the server device 30. Fig. 9 is a diagram showing an example of the hardware configuration of the server device 30. As shown in Fig. 9, the server device 30 includes a CPU 311, a ROM 312, and a RAM 313.

[0068] The CPU 311 is an example of a processor, and performs overall control of each unit of the server device 30. The ROM 312 stores various programs. The RAM 313 is a workspace where programs and various data are developed.

[0069] The CPU 311, ROM 312, and RAM 313 are connected via a bus or the like to form a computer-configured control unit 314. In the control unit 314, the CPU 311 operates in accordance with a control program stored in the storage unit 316 and loaded into the RAM 313, thereby executing various processes.

[0070] The server device 30 also includes a communication unit 315 and a storage unit 316. The communication unit 315 is a wired or wireless communication interface connectable to a 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.

[0071] 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.

[0072] The storage unit 316 also 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 product master 3162 is a data table that stores information about products for sale. The data structure of the product master 3162 is the same as that of the product master 1622 described above.

[0073] 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.

[0074] The robot management table 3163 is a data table for managing the position and status of the mobile sales robot 10. Fig. 10 is a diagram showing an example of the data configuration of the robot management table 3163. As shown in Fig. 10, 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 and status information indicating the status of the mobile sales robot 10. The robot ID identifies the mobile sales robot 10 and is an example of mobile sales device identification information.

[0075] Here, the location information may be represented by coordinate values ​​such as longitude and latitude, etc. Alternatively, the location information may be represented by block numbers or the like obtained by dividing the area in which the mobile sales robot 10 can move into a plurality of blocks.

[0076] The state of the mobile sales robot 10 may be, for example, a "moving" state in which the mobile sales robot 10 moves to a call position designated by a user, a "waiting for transaction" state in which the mobile sales robot 10 has arrived at the call position and is waiting for an operation to start a transaction, a "transaction in progress" state in which a transaction has been started by a user operation, etc. In addition, the state of the mobile sales robot 10 may be a "waiting for call" state in which the mobile sales robot 10 can respond to a call from a user when the mobile sales robot 10 is patrolling, etc., or a "not selling" state in which the mobile sales robot 10 cannot sell due to replenishing products, etc.

[0077] The information stored in the robot management table 3163 is updated according to the movement and state of the mobile sales robot 10 under the control of the information management unit 3142 described later.

[0078] The product management table 3164 is a data table for managing products sold by each mobile sales robot 10. Fig. 11 is a diagram showing an example of the data configuration of the product management table 3164. As shown in Fig. 11, the product management table 3164 stores, in association with a robot ID, the product code of a product sold by the mobile sales robot 10 of that robot ID and the inventory quantity of that product.

[0079] The information stored in the product management table 3164 is updated according to the number of products in stock held by the mobile sales robot 10 under the control of the information management unit 3142 (to be described later).

[0080] The user management table 3165 is a data table for managing users who use the mobile sales system 1. Fig. 12 is a diagram showing an example of the data configuration of the user management table 3165. As shown in Fig. 12, the user management table 3165 associates each user with an identifiable user ID and stores user information about the user with that user ID.

[0081] The user information includes feature information indicating the user's facial features and payment information used for electronic payment. The feature information is, for example, a facial image of the user'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 user has previously signed up. Here, electronic payment services include code payment, electronic money payment, credit card payment, etc. Furthermore, if the electronic payment service is credit card payment, the payment information may be the number of a credit card owned by the user.

[0082] The user information is obtained from the user 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 user. 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 user's name, age, and address. The user information may also include the terminal ID of the terminal (user terminal 20) used by the user, the communication address of the terminal, etc.

[0083] The call management table 3166 is a data table for managing calls to the mobile sales robot 10 by the user terminal 20. Fig. 13 is a diagram showing an example of the data configuration of the call management table 3166. As shown in Fig. 13, 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 call location (hereinafter simply referred to as "call location"), authentication information used to authenticate the calling user, the robot ID of the mobile sales robot 10 corresponding to the call, and the date and time when the mobile sales robot 10 arrived at the call location (arrival date and time).

[0084] 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 user, a user ID, etc. In the former case, the pin code may be issued by the control unit 314 or may be specified by the user. In the latter case, the pin code may be a facial image or user ID transmitted from the user terminal 20 of the user 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, a form will be described in which the control unit 314 issues a pin code when accepting a call.

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

[0086] Next, a description will be given of the functional configuration of each device that constitutes the mobile sales system 1. Fig. 15 is a block diagram showing the functional configuration of each device that constitutes the mobile sales system 1. First, the user terminal 20 will be described.

[0087] The control unit 214 of the user terminal 20 functions as a transmission / reception unit 2141, an input reception unit 2142, a self-position identification unit 2143, and a display control unit 2144 by the CPU 211 operating in accordance with the control program stored in the ROM 212 or the storage unit 220. Note that each of these functions may be configured by hardware such as a dedicated circuit.

[0088] The transmitting / receiving unit 2141 transmits and receives various information to and from an external device such as the server device 30 via the communication unit 219. Note that the function and operation of the transmitting / receiving unit 2141 to "receive" information from the server device 30 or the like can also be rephrased as "acquiring" information.

[0089] For example, the transmitting / receiving unit 2141 receives information on the robot ID, current location, and status of the mobile sales robot 10 from the server device 30. The transmitting / receiving unit 2141 also transmits product information requests and call requests to the server device 30. A product information request specifies a 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.

[0090] 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 the call location. In addition, if the user 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 user may also be able to specify a desired call location on the user terminal 20.

[0091] The transmitting / receiving unit 2141 also receives product information transmitted by the server device 30 in response to the product information request. Furthermore, the transmitting / receiving unit 2141 receives a pin code issued by the server device 30 in association with the call request. The pin code is authentication information for authenticating (matching) the user who has called the mobile sales robot 10 with the user who is about to start shopping with the mobile sales robot.

[0092] Furthermore, the transmitting / receiving unit 2141 receives an arrival notification and a payment completion 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 completion notification indicates that payment for the purchase of the product stored in the mobile sales robot 10 has been completed.

[0093] 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.

[0094] 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 .

[0095] The display control unit 2144 displays various types of information on the display unit 215. Specifically, the display control unit 2144 displays various screens (GUI: Graphical User Interface) for supporting the purchase of products sold by the mobile sales robot 10 on the display unit 215. For example, the display control unit 2144 displays a display screen for supporting the calling of the mobile sales robot 10 on the display unit 215.

[0096] 16 and 17, examples of display screens displayed by the display control unit 2144 will be described. Fig. 16 is a diagram showing an example of a first display screen displayed on the display unit 215 of the user terminal 20. Fig. 17 is a diagram showing an example of a second display screen displayed on the display unit 215 of the user terminal 20.

[0097] The display control unit 2144 displays each mobile sales robot 10 on a map in a selectable manner in accordance with the location of the mobile sales robot 10, and then displays product information about the product carried by the selected mobile sales robot 10 along with a call button. Specifically, when a product information request menu is selected from a menu selection screen (not shown), the display control unit 2144 displays the first display screen shown in FIG. 16 on the display unit 215.

[0098] The first display screen has a map display area 2151. The display control unit 2144 displays a map of the range in which the mobile sales robot 10 can move in the map display area 2151 based on the map information 2201. Here, the display control unit 2144 may display a map of the vicinity of the location of the user terminal 20 based on the location information identified by the self-location identifying unit 2143, or may display a map of the vicinity of the location of the mobile sales robot 10 based on the location information of the mobile sales robot 10 provided by the server device 30. In addition, the display control unit 2144 changes the range of the map displayed in the map display area 2151 in response to an operation on the map (for example, a scroll operation, a zoom-in / zoom-out operation, etc.).

[0099] The display control unit 2144 also displays a robot mark 2152 representing the mobile sales robot 10, superimposed on the map in the map display area 2151. Specifically, the display control unit 2144 displays the robot mark 2152 at the position on the map where the mobile sales robot 10 is located. The robot mark 2152 also displays robot identification information such as a robot ID.

[0100] The user can select the corresponding mobile sales robot 10 by touching any of the robot marks 2152 displayed on the first display screen. When the input receiving unit 2142 receives the designation of the mobile sales robot 10, the transmitting / receiving unit 2141 transmits a product information request including the terminal ID of the user terminal 20 and the robot ID of the designated mobile sales robot 10 to the server device 30. The server device 30 that has received the product information request reads out product information of the product sold by the mobile sales robot 10 with the designated robot ID from the product management table 3164, as will be described later, and transmits the product information to the user terminal 20 that made the request.

[0101] When the transmitting / receiving unit 2141 receives the product information, the display control unit 2144 displays the product information in association with the robot mark 2152 of the selected mobile sales robot 10, as shown on the second display screen in Fig. 17. In other words, the second display screen is a screen that is displayed when any one of the robot marks 2152 displayed on the first display screen is touched.

[0102] 17, the second display screen has a map display area 2151 and a product information display area 2153. Like the map display area 2151 on the first display screen, the map display area 2151 is an area for displaying a map based on map information 2201. Note that the map display area 2151 is smaller than the map display area 2151 on the first display screen. The display control unit 2144 causes the robot mark 2152 touched on the first display screen and a map of its vicinity to be displayed in the map display area 2151.

[0103] The product information display area 2153 is an area for displaying product information of the products mounted on the selected mobile sales robot 10. The display control unit 2144 displays the product information transmitted from the server device 30 in response to the selection of the mobile sales robot 10 in the product information display area 2153. Specifically, the display control unit 2144 displays the product information for each product in a vertical arrangement. The displayed product information includes product images, product names, prices, etc. The product information display area 2153 can be scrolled vertically, and the display control unit 2144 updates the displayed product information in response to the scroll operation. This allows the product information display area 2153 to display product information for all products mounted on the mobile sales robot 10.

[0104] The second display screen also has a call button 2154 for calling the selected mobile sales robot 10. The user can check on the second display screen the products mounted on the mobile sales robot 10 selected on the first display screen, and if there is a product that the user wishes to purchase, the user can touch the call button 2154 to call the mobile sales robot 10. By calling the mobile sales robot 10 using the first display screen and the second display screen, the user can select the mobile sales robot 10 to be called while checking the location of the mobile sales robot 10, thereby efficiently calling the mobile sales robot 10, for example, by calling the mobile sales robot 10 closest to the user's location.

[0105] Specifically, when the input accepting unit 2142 accepts the operation of the call button 2154 on the second display screen, the transmitting / receiving unit 2141 transmits a call request including the terminal ID of the user terminal 20, the robot ID of the specified mobile sales robot 10, and the location information (call location) identified by the self-location identifying unit 2143 to the server device 30. The server device 30 that has received the call request causes the mobile sales robot 10 with the specified robot ID to travel to the specified call location, as will be described later. Furthermore, the server device 30 predicts the time it will take for the mobile sales robot 10 corresponding to the specified robot ID to arrive at the call location (hereinafter also referred to as arrival time) based on the current location and call location of the specified robot ID, the number of call requests for the robot ID registered in the call management table 3166, and the like, and transmits this to the user terminal 20 that made the request.

[0106] The second display screen also has an arrival time display area 2155 that displays the time it will take for the selected mobile sales robot 10 to arrive at the location of the user terminal 20. The display control unit 2144 displays the arrival time transmitted from the server device 30 in response to the selection of the mobile sales robot 10 in the arrival time display area 2155. The arrival display area 2155 may also display the robot ID, etc., of the mobile sales robot 10 that is scheduled to arrive.

[0107] The timing for displaying the arrival time is not limited to after the call button 2154 is operated. For example, the display control unit 2144 may display the arrival time when the mobile sales robot 10 is selected on the first display screen. In this case, the transmitting / receiving unit 2141 may acquire the arrival time from the server device 30 when the mobile sales robot 10 is selected by including the location information identified by the self-location identifying unit 2143 in the product information request and transmitting the request to the server device 30.

[0108] Furthermore, the second display screen identifiably displays the mobile sales robot 10 selected on the first display screen. Specifically, in the map display area 2151, a robot mark 2152 bearing the indication "Robot B," which is information for identifying the mobile sales robot 10 selected on the first display screen, is displayed together with a map of the surrounding area. This allows the user to check the location, identification information, product information of the products carried by the selected mobile sales robot 10, etc., on one screen. Note that the information for identifying the mobile sales robot 10 may be a unique number, name, etc., assigned to each mobile sales robot 10.

[0109] Furthermore, the method of displaying the information identifying the selected mobile sales robot 10 is not limited to the above. For example, the information identifying the mobile sales robot 10 may be displayed in association with the arrival time in the arrival display time display area 2155. Furthermore, the information identifying the mobile sales robot 10 may be displayed in the product information display area 2153.

[0110] The display screen for calling the mobile sales robot 10 is not limited to the examples shown in Figures 16 and 17. Other display screens will be described below with reference to Figures 18 and 19.

[0111] 18 is a diagram showing an example of the third display screen displayed on the display unit 215 of the user terminal 20. On the third display screen, it is possible to select a mobile sales robot 10, display product information of the products carried by the mobile sales robot 10, and call the mobile sales robot 10 on the same screen.

[0112] Specifically, the third display screen has a robot selection area 2156, a product information display area 2153, a call button 2154, and an arrival time display area 2155.

[0113] The robot selection area 2156 is an area for selectively displaying an image (robot mark) corresponding to each mobile sales robot 10. The product information display area 2153 is an area for displaying product information of a product sold by the mobile sales robot 10 with the robot mark selected in the robot selection area 2156.

[0114] Here, each image of a robot mark displayed in the robot selection area 2156 corresponds to each mobile sales robot 10 traveling within a predetermined area. The display control unit 2144 displays a robot mark corresponding to each robot ID in the robot selection area 2156 based on the robot ID transmitted from the server device 30, the position information corresponding to the robot ID, and the like. The robot selection area 2156 can be scrolled left and right, and the display control unit 2144 updates the displayed robot mark in response to a scroll operation. This allows the robot selection area 2156 to display all of the mobile sales robots 10.

[0115] The display control unit 2144 may also display the robot ID and the status of the corresponding mobile sales robot in association with each robot mark.

[0116] The user can select a mobile sales robot 10 by touching one of the robot marks displayed in the robot selection area 2156. When the mobile sales robot 10 is selected, the transmitter / receiver unit 2141 transmits a product information request specifying the robot ID of the selected mobile sales robot 10 to the server device 30 and acquires the product information from the server device 30. Then, the display control unit 2144 displays the product information of the product sold by the mobile sales robot 10 selected in the robot selection area 2156 in the product information display area 2153.

[0117] This allows the user to view product information about the products housed in the selected mobile sales robot 10 in the product information display area 2153. The user can also check the products carried by the mobile sales robot 10 selected in the robot selection area 2156 in the product information display area 2153, and if there is a product that the user wishes to purchase, the user can touch the call button 2154 to call the mobile sales robot 10. Therefore, the user can select a mobile sales robot 10, view product information about the products carried by the selected mobile sales robot 10, and call the mobile sales robot 10 without switching screens.

[0118] In addition, the arrival time display area 2155 displays the arrival time of the mobile sales robot 10 that has been called (or selected), as in the second display screen.

[0119] 19 is a diagram showing an example of the fourth display screen displayed on the display unit 215 of the user terminal 20. On the fourth display screen, instead of explicitly selecting a mobile sales robot 10, it is possible to select a product or a product genre (type) of the product, thereby selecting a mobile sales robot 10 equipped with the selected product or a product of the selected product genre. In this embodiment, it is possible to select a product genre.

[0120] Specifically, the fourth display screen has a product category selection area 2157, a product information display area 2153, a call button 2154, and an arrival time display area 2155.

[0121] The product category selection area 2157 is an area for displaying icons indicating the product categories of the products carried by the mobile sales robot 10. The display control unit 2144 causes the product category selection area 2157 to display selectable icons indicating the product categories of the products carried by the mobile sales robot 10. Here, the product categories to be displayed as icons may be determined in advance. Furthermore, the product categories to be displayed as icons may be determined based on the product categories (types) included in the product information of the products sold by each mobile sales robot 10, which is obtained from the server device 30 prior to displaying the fourth display screen.

[0122] When the user touches any of the icons displayed in the product category selection area 2157, the transmitter / receiver 2141 transmits to the server device 30 identification information and the like that identifies the product category corresponding to the icon. The server device 30 refers to the product management table 3164 and extracts the mobile sales robots 10 that carry products of the product category identified by the received identification information. In this example, the server device 30 is assumed to have a management table that associates product categories with products. The mobile sales robots 10 selected by the server device 30 include those that carry only products of the product category identified by the received identification information, and those that also carry products of other product categories.

[0123] The server device 30 then selects one of the extracted mobile sales robots 10, for example, the mobile sales robot 10 that is closest to the user's location (the location of the user terminal 20) that received the product category identification information. The server device 30 transmits product information about the product carried by the selected mobile sales robot 10 to the user terminal 20.

[0124] As a result, by touching one of the icons displayed in the product category selection area 2157, the user can select the mobile sales robot 10 carrying the product of the product category indicated by that icon. In addition, the user can view product information of the product stored in the selected mobile sales robot 10 in the product information display area 2153. The product information display area 2153 is the same as the product information display area 2153 of the second display screen shown in FIG. 17, so a duplicated description will be omitted.

[0125] Any of the above-described methods for calling the mobile sales robot 10 based on the first and second display screens, the method for calling the mobile sales robot 10 based on the third display screen, and the method for calling the mobile sales robot 10 based on the fourth display screen may be used. For example, the calling method may be switchable in response to the operation of a switching button or the like.

[0126] 16 to 19 may be used in combination. For example, the display control unit 2144 first displays the fourth display screen, and when a product category is selected on the fourth display screen, displays the first display screen on which a mobile sales robot 10 carrying a product of the selected product category can be selected. Then, the display control unit 2144 may display the second display screen based on the mobile sales robot 10 selected on the first display screen. In this case, the fourth display screen that is initially displayed may include only the product category selection area 2157.

[0127] As described above, the user terminal 20 transmits a product information request, receives and displays product information, and transmits a call request in response to user operations. At this time, the call location of the mobile sales robot 10 is the user's location. Note that the display control unit 2144 may display a call location specification screen on which the user can specify the call location of the mobile sales robot 10 before transmitting the call request to the server device 30.

[0128] 20 is a diagram showing an example of a call position designation screen displayed on the display unit 215 of the user terminal 20. The call position designation screen has, for example, a map display area 2151 similar to the first display screen. The display control unit 2144 displays a robot mark 2152 of the selected mobile sales robot 10 on the map in the map display area 2151. Furthermore, on the call position designation screen, the user can designate any position on the map as the call position of the mobile sales robot 10.

[0129] The display control unit 2144 displays a designated position mark 2158 at a call position on the map designated by the user. The designated position mark 2158 is set to the user's current position, that is, the current position of the user terminal 20, as a default. The user can move the designated position mark 2158 to a desired position, for example, by a drag-and-drop operation. Thereafter, when the user performs a predetermined operation, the transmitting / receiving unit 2141 transmits a call request including the designated call position to the server device 30. For example, when the user touches a call confirmation button (not shown) displayed on the map display area 2151, the user terminal 20 may transmit the call request to the server device 30.

[0130] After the transmitting / receiving unit 2141 transmits the call request, the display control unit 2144 displays the current location of the mobile sales robot 10 to be called on the map in the map display area 2151 using a robot mark 2152 or the like, based on the location information of the mobile sales robot 10 provided by the server device 30.

[0131] This allows the user to easily check the current location of the mobile sales robot 10 selected as the target to be called by looking at the map in the map display area 2151.

[0132] Furthermore, when the mobile sales robot 10 to be called moves to the call position, the display control unit 2144 causes the display unit 215 to display a display screen informing that the mobile sales robot 10 has arrived at the call position.

[0133] Hereinafter, the display screens that the display control unit 2144 causes the display unit 215 to display after the mobile sales robot 10 arrives at the calling position will be described with reference to FIGS.

[0134] 21 is a diagram showing an example of a display screen displayed by the display unit 215 when the mobile sales robot 10 arrives at the called position. When the mobile sales robot 10 arrives at the called position, a push notification is sent from the server device 30 to the user terminal 20. In response to the notification from the server device 30, the display control unit 2144 displays a pop-up message A on the display unit 215 to notify the user that the mobile sales robot 10 has arrived. Note that FIG. 21 shows an example in which the message A is displayed as a pop-up on the second display screen described above (the same applies to FIGS. 22 and 23).

[0135] In this way, the display control unit 2144 notifies the user using the display screen when the mobile sales robot 10 arrives at the called position. As a result, the user can easily recognize that the mobile sales robot 10 has arrived at the called position by looking at the display screen (message A). The method of notifying the user of the arrival is not limited to using the display screen. For example, the display control unit 2144 may notify the user that the mobile sales robot 10 has arrived at the called position by sound or vibration in cooperation with a notification unit such as a speaker or vibrator provided in the user terminal 20. The display control unit 2144 may also display the robot number or robot ID displayed on the arriving mobile sales robot 10 on a pop-up screen. This allows the user to more easily recognize the mobile sales robot 10 that he or she has called. The method of displaying the robot number, etc. on the mobile sales robot 10 is not limited.

[0136] In this embodiment, the arrival at the call position is notified in response to a notification from the server device 30. However, the present invention is not limited to this. The user terminal 20 may determine whether or not it has arrived by determining independently. In this case, for example, the control unit 214 of the user terminal 20 determines whether or not the position information of the mobile sales robot 10 to be called, provided by the server device 30, is within a predetermined range based on the position information (call position) of the designated position mark 2158. When the mobile sales robot 10 enters the predetermined range, the control unit 214 determines that the mobile sales robot 10 has arrived at the call position. In this case, the display control unit 2144, in response to the determination of the control unit 214, causes the display unit 215 to display a display screen notifying that the mobile sales robot 10 has arrived at the call position.

[0137] Furthermore, the display screen displayed when the mobile sales robot 10 arrives at the calling position is not limited to that shown in FIG. 21, and may include other information as shown in FIG. 22, for example.

[0138] 22 is a diagram showing another example of the display screen displayed by the display unit 215 when the mobile sales robot 10 arrives at the call location. The display screen in FIG. 22 is an example of a display in which a time limit is set for each user to purchase a product. Hereinafter, the time limit for purchasing a product will also be referred to as the "purchase time limit."

[0139] For example, assuming that there are many users who wish to use the mobile sales robot 10, it is desirable to set a purchase time limit for each user. This is because there may be users who call the mobile sales robot 10 out of curiosity even though they have no intention of purchasing a product. Note that the purchase time limit may not be set, or the setting may be switchable between enabled and disabled.

[0140] In this example, when the mobile sales robot 10 arrives at the called position, the display control unit 2144 pops up a message B on the display unit 215. The message B includes a message informing the user that the mobile sales robot 10 has arrived at the called position and a message informing the user of the purchase time limit. At this time, the transmitting / receiving unit 2141 notifies the server device 30 that the mobile sales robot 10 has arrived at the called position. The purchase time limit displayed in the pop-up may be the preset purchase time limit itself, or the remaining time of the purchase time limit. The remaining time of the purchase time limit can be calculated by the control unit 214 by subtracting the time (elapsed time) obtained by subtracting the time when the mobile sales robot 10 arrived at the called position from the preset purchase time limit.

[0141] This allows the user to recognize from message B that the mobile sales robot 10 has arrived at the called location and that there is a purchase time limit.

[0142] In this example, the display control unit 2144 may also display a time extension button C for extending the purchase time limit, as shown in Fig. 22. By touching the time extension button C, the user can extend the purchase time limit by a predetermined time.

[0143] For example, when the time extension button C is operated, the display control unit 2144 adds a preset extension time to the remaining time of the purchase time limit being displayed, correcting and displaying the remaining time of the purchase time limit. Then, the transmission / reception unit 2141 transmits an extension notification to the server device 30. The server device 30 recognizes the end time of the sale at the call location based on the arrival notification received from the mobile sales robot 10 when the mobile sales robot 10 arrives at the call location and the extension notification. Specifically, the server device 30 recognizes the end time of the sale as the time when the purchase time limit and the extension time have elapsed since the time when the arrival notification was received. The server device 30 can instruct the mobile sales robot 10 to move based on the recognized sales time, etc. Furthermore, for example, when the control unit 214 of the mobile sales robot 10 accepts the operation of the time extension button C, the control unit 214 may notify the server device 30 of the extension using status information by changing the status of the mobile sales robot 10 to a status in which the purchase time limit has been extended by a user operation (for example, "transaction extension in progress").

[0144] The method for restricting the purchase of goods by the mobile sales robot 10 when the purchase time limit has elapsed can be set arbitrarily. For example, it is possible to allow payment for goods registered within the purchase time limit, and not register goods removed after the purchase time limit has elapsed.

[0145] This makes it possible to avoid imposing any unnecessary time restrictions on users who purchase products.

[0146] In this example, if the purchase time limit has elapsed without any purchase being made, such as if no products have been taken out, the display control unit 2144 causes the display unit 215 to display a display screen informing the user of this. Fig. 23 shows a display screen that is displayed when the purchase time limit has elapsed without the user making any purchase. This display screen is displayed, for example, when no products have been taken out from the shelf 112 within the purchase time limit. If the purchase time limit has elapsed without the user making any purchase, the display control unit 2144 causes the display unit 215 to display a message D informing the user that the sale of products by the mobile sales robot 10 has been canceled.

[0147] This allows the user to recognize that the mobile sales robot 10 will move to the next call position or the like.

[0148] In this embodiment, the call request is sent to the server device 30 from the user terminal 20 carried by the user, but this is not limited to this. The call request may be sent to the server device 30 from a terminal device installed in the facility where the mobile sales robot 10 travels. In this case, it is desirable that the terminal device allows the user to set the call location to any location.

[0149] 15, the functional configuration of server device 30 will be described. Control unit 314 of server device 30 functions as a transmission / reception unit 3141, an information management unit 3142, a verification unit 3143, a payment processing unit 3144, and a robot management unit 3145 by CPU 311 operating in accordance with control programs stored in ROM 312 or storage unit 316. Note that each of these functions may be configured using hardware such as a dedicated circuit.

[0150] 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 indicating the location of each mobile vending robot 10 and status information indicating the status of the mobile vending robot 10 to the user terminal 20. Furthermore, the transmitting / receiving unit 3141 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.

[0151] 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.

[0152] 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.

[0153] 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 user to the mobile sales robot 10 from the mobile sales robot 10. 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 user who called the mobile sales robot 10 and the user who is about to start shopping with the mobile sales robot are the same.

[0154] Furthermore, the transmitting / receiving unit 3141 receives a payment request from the mobile sales robot 10, and when payment processing is completed in response to the payment request, transmits a payment completion notice to the mobile sales robot 10 and the user terminal 20. The payment request requests payment processing for the price of the product purchased by the user at the mobile sales robot 10. The payment request includes information necessary for the payment processing executed by the server device 30. In this embodiment, the information necessary for the payment processing is the user's facial image data. A user ID or the like may be used instead of the facial image data. 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.

[0155] The information management unit 3142 stores information in the storage unit 316 based on the information received by the transmission / reception unit 3141, and updates various pieces of information stored in the storage unit 316. Furthermore, the information management unit 3142 reads various pieces of information transmitted by the transmission / reception unit 3141 from the storage unit 316 as appropriate.

[0156] For example, the information management unit 3142 updates the robot management table 3163 based on the position information and status information received by the transmitting / receiving unit 3141 from the mobile sales robot 10. When the transmitting / receiving unit 3141 receives a product information request, the information management unit 3142 reads out the product code corresponding to the robot ID included in the product information request from the product management table 3164. Then, the information management unit 3142 refers to the product master 3162 and reads out the product information corresponding to the product code.

[0157] When the transmitting / receiving unit 3141 receives a call request or an arrival notification, the information management unit 3142 stores appropriate information in the call management table 3166. Furthermore, when the transmitting / receiving unit 3141 receives a payment request, the information management unit 3142 stores various information in the transaction management table 3167 and reads out payment information from the user management table 3165. Specifically, the information management unit 3142 reads out payment information from the user management table 3165 based on the facial image data included in the payment request. Furthermore, when the payment processing unit 3144 completes payment, the information management unit 3142 updates the payment flag in the transaction management table 3167.

[0158] The information management unit 3142 also manages the order in which the mobile sales robot 10 moves to the call position. 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 position specified in the call request in order from the call request with the earliest call date and time.

[0159] The collating unit 3143 collates whether or not the user who called the mobile sales robot 10 is the same as the user who is about to start shopping with 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.

[0160] The matching unit 3143 may also match the user who called the mobile sales robot 10 with the user who is about to start shopping with the mobile sales robot 10 by face authentication. In this case, the transmitting / receiving unit 3141 receives face image data from the mobile sales robot. Then, the matching unit 3143 refers to the user management table 3165 and matches the received face image data with the face feature of the calling user.

[0161] In the mobile sales system 1, it is not essential to verify the user who called the mobile sales robot 10 with the user who is about to start shopping with the mobile sales robot 10. In other words, the server device 30 does not need to have the function of the verification unit 3143.

[0162] The payment processing unit 3144 executes payment processing related to the payment request received by the transmitting / receiving unit 3141 from the mobile sales robot 10. In this embodiment, the payment processing unit 3144 executes electronic payment processing using facial recognition. Specifically, the payment processing unit 3144 executes payment with the payment service provider using payment information read by the information management unit 3142 based on facial image data. The payment processing unit 3144 executes payment processing by communicating with the payment server of the payment service provider. Note that the payment processing unit 3144 may execute electronic payment using credit card payment or two-dimensional code payment.

[0163] 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. For example, 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 with 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. Also, for example, 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 that corresponds to the call request from among the mobile sales robots 10 that are in the "waiting for call" state.

[0164] 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 arrival time of the selected mobile sales robot 10 at the call location, and sets the arrival time as the content of the message. The arrival time is calculated based on the number of call requests (unprocessed requests with no arrival date and time registered) for the mobile sales robot 10 registered in the call management table 3166, the preset purchase limit time for one transaction, the location information and status information of the mobile sales robot 10 registered in the robot management table 3163, etc.

[0165] In addition, the robot management unit 3145 refers to the product management table 3164 and sets the mobile sales robot 10 with a robot ID whose inventory of any or all of the products it carries has reached zero as the destination of the movement instruction, and sets the location where the products will be replenished as the movement destination.

[0166] 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, verification unit 3143, payment processing unit 3144, and robot management unit 3145. In this case, the user terminal 20 transmits and receives various information to and from the mobile sales robot 10.

[0167] Next, we will explain the functional configuration of the mobile sales robot 10. The control unit 154 of the mobile sales robot 10 functions as a transmitting / receiving unit 1541, an input receiving unit 1542, a self-location determining unit 1543, an information processing unit 1544, a drive control unit 1545, and a display control unit 1546, as a result of the CPU 151 operating in accordance with the control programs stored in the ROM 152 or the storage unit 162. Note that each of these functions may be configured using hardware such as a dedicated circuit.

[0168] 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 location information indicating the location of the device itself and status information indicating the status of the device itself to the server device 30 as needed.

[0169] Furthermore, the transmitting / receiving unit 1541 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 input to the input receiving unit 1542, and includes the pin code and robot ID received by the input receiving unit 1542. The authentication notification serves as trigger information for permitting processing related to the sale of a product, as will be described later. Therefore, the transmitting / receiving unit 1541 functions as an input unit into which trigger information is input. Furthermore, the transmitting / receiving unit 3141 transmits a payment request to the server device 30 and receives a payment completion notification from the server device 30.

[0170] The input receiving unit 1542 receives input information based on the operation of the operation unit 156. For example, the input receiving unit 1542 receives a pin code or a payment instruction input by the user's operation.

[0171] The self-position identifying unit 1543 identifies the position of the mobile sales robot 10 in the map information 2201 based on the output of the positioning unit 160 .

[0172] The information processing unit 1544 executes various processes based on various information input to the mobile sales robot 10.

[0173] For example, when the transmitting / receiving unit 1541 receives a movement instruction from the server device 30, the information processing unit 1544 determines a movement route to the called position based on the map information 1621.

[0174] Furthermore, when the weight detection unit 159 detects a weight change on the shelf 112, the information processing unit 1544 reads out, from the stored product table 1623, the product code corresponding to the shelf ID of the shelf 112 where the weight change occurred, and identifies the product that was removed from the shelf 112 or the product that was returned to the shelf 112. The information processing unit 1544 functions as a detection unit that detects the product that has been removed from the loading unit.

[0175] For example, if the weight change is a decrease in weight, the information processing unit 1544 reads out the product code stored in association with the shelf ID of the shelf 112 where the weight change occurred. Then, the information processing unit 1544 refers to the product master 1622 and identifies the product code corresponding to the decreased weight among the weights associated with the read product codes, thereby identifying the product taken out from the shelf 112. In this case, the information processing unit 1544 reads out product information corresponding to the identified product code from the product master 1622 and registers it in the RAM 153 (hereinafter also referred to as "product registration"). In other words, the information processing unit 1544 also functions as a registration unit that executes product registration. The information processing unit 1544 also subtracts the number of products taken out from the shelf 112 from the quantity of the identified product code stored in the stored product table 1623.

[0176] For example, if the weight change is an increase in weight, the information processing unit 1544 reads out the product code stored in association with the shelf ID of the shelf 112 where the weight change occurred. Then, the information processing unit 1544 refers to the product master 1622 and identifies the product code corresponding to the increased weight from among the weights associated with the read product codes, thereby identifying the product that has been returned to the shelf 112. In this case, the information processing unit 1544 deletes the product information corresponding to the identified product code that has been registered in the RAM 153. The information processing unit 1544 also increases the quantity of the identified product code stored in the stored product table 1623 by the number of products that have been returned to the shelf 112.

[0177] The registration of product information may be performed by server device 30. In particular, information processing unit 1544 causes server device 30 to transmit the product code of the product taken out from shelf 112 in the same manner as described above. Server device 30 then reads out and registers product information of the product corresponding to the received product code from product master 3162. In this case, information processing unit 1544 performs the function of registering product information in server device 30, and can be said to function as a registration unit that executes product registration.

[0178] The information processing unit 1544 executes a payment process when the input receiving unit 1542 receives a payment instruction. The payment process is part or all of the process for the user to pay for the purchase price of a product, and in this embodiment, includes calculating the purchase price of the registered product, obtaining facial image data, and sending a payment request.

[0179] When the mobile vending robot 10 performs the payment processing executed by the server device 30, the payment processing is included in the accounting processing executed by the information processing unit 1544. The mobile vending robot 10 may also be equipped with an automatic change dispenser or the like for cash payments, in which case the information processing unit 1544 controls the automatic change dispenser. In this way, the information processing unit 1544 functions as an accounting processing unit that executes the accounting processing that handles part or all of the processing related to the payment of the purchase price.

[0180] Furthermore, the information processing unit 1544 performs voice recognition on the sound picked up by the sound collection unit 157 from the surrounding area, and outputs a stop instruction to the drive control unit 1545 as necessary. For example, when the information processing unit 1544 recognizes a voice for stopping the mobile sales robot 10 through voice recognition, it outputs a stop instruction to the drive control unit 1545.

[0181] The information processing unit 1544 permits processing related to the sale of goods when the transmitting / receiving unit 1541 receives an authentication notification from the server device 30. That is, when the verifying unit 3143 of the server device 30 verifies the user who called the mobile sales robot 10 with the user who is about to start shopping, the information processing unit 1544 permits processing related to the sale of goods.

[0182] For example, the information processing unit 1544 cooperates with the display control unit 1546 to display an initial screen for starting shopping on the display unit 155, thereby permitting processing related to the sale of merchandise. In addition, if the storage unit 111 has a lockable door, the information processing unit 1544 permits processing related to the sale of merchandise by unlocking the door. The information processing unit 1544 functions as a permitting unit that permits processing related to the sale of merchandise when the user who called the mobile sales robot 10 is matched with the user who is about to start shopping.

[0183] In this embodiment, the trigger information for permitting a process related to the sale of a commodity at a call position is an authentication notification from the server device 30, but this trigger information is not set when the mobile sales robot 10 is patrolling. This is because when the mobile sales robot 10 is patrolling, the mobile sales robot 10 stops at a sales position in response to a user's voice, that is, a call request and a PIN code corresponding to the call request are not issued. For the sale of a commodity when the mobile sales robot 10 is patrolling, trigger information for permitting a process related to the sale of the commodity does not need to be set, and other information different from the authentication notification may be used as the trigger information.

[0184] For example, the trigger information may be information indicating that it has been detected that the user has made eye contact with the imaging unit 134, that the user has performed a predetermined action such as blinking in front of the imaging unit 134, or that the user has operated the disinfection device 135. Note that a user who purchases a commodity while the mobile sales robot 10 is traveling can purchase the commodity by paying by face authentication if the user has registered payment information in advance in the user management table 3165. In addition, if the mobile sales robot 10 is equipped with a payment device such as a card payment terminal or a change dispenser, the user can purchase a commodity regardless of whether payment information has been registered or not.

[0185] Furthermore, for the sale of a commodity at a designated call location, the trigger information for permitting the process related to the sale of the commodity may be the above-mentioned information instead of the authentication notification, or may be information indicating that the mobile sales robot 10 has arrived at the call location. Furthermore, the trigger information for permitting the process related to the sale of the commodity need not be set.

[0186] The information processing unit 1544 executes alarm processing to issue an alarm as necessary. For example, when it is detected that a product has been illegally removed from the shelf 112 while the mobile sales robot 10 is traveling or when a process related to the sale of the product is not permitted, the information processing unit 1544 executes alarm processing. The alarm processing involves causing the light emitting unit 114 to emit light to alert the surrounding area of ​​an abnormality, changing the color to a warning color, or emitting an alarm sound from a microphone (not shown).

[0187] The information processing unit 1544 may execute an alarm process when it detects that an item is being fraudulently removed. For example, the alarm process may be executed when it detects that a hand has been inserted into the storage unit 111 while the mobile sales robot 10 is moving or when a process related to selling items is not permitted. The information processing unit 1544 functions as an alarm unit that issues an alarm when it detects that an item is being fraudulently removed, in other words, when an item has been or is being fraudulently removed.

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

[0189] Furthermore, when it is detected that any or all of the products stored in the storage unit 111 are out of stock, the drive control unit 1545 moves the mobile sales robot 10, for example, to a back yard. This is to replenish the out-of-stock products. If the mobile sales robot 10 travels in a shopping mall or the like, the drive control unit 1545 may move the mobile sales robot 10 to a store selling the out-of-stock products.

[0190] The display control unit 1546 controls the display unit 155 to display various information on the display unit 155. The display control unit 1546 causes the first display unit 131, the second display unit 132, and the third display unit 133 to display content according to their respective installation positions. For example, the first display unit 131 displays information about a product taken out of the storage unit 111. The second display unit 132 displays information related to product promotion, such as information for advertising the product stored in the storage unit 111. The third display unit 133 displays information related to product payment, such as information to guide customers through product payment methods. Furthermore, if the shelf tag 113 is an electronic shelf tag, the display control unit 1546 also controls the display of the electronic shelf tag.

[0191] The operation of the mobile sales system 1 having the above-described devices will be described. Fig. 24 is a sequence chart showing an example of the operation of the mobile sales system 1. This sequence chart shows a case where a user checks the product information of a product mounted on the mobile sales robot 10, calls the mobile sales robot 10, and purchases the product from the mobile sales robot 10.

[0192] To call the mobile sales robot 10, the user 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 the first display screen shown in Fig. 16 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).

[0193] The server device 30 reads out product information from the storage unit 316 in response to the received product information request (step S3). Specifically, the server device 30 reads out a product code corresponding to the robot ID included in the product information request from the product management table 3164. Next, the server device 30 reads out product information corresponding to the read product code from the product master 3162. The server device 30 transmits the read 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.

[0194] The user terminal 20 displays the received product information on the display unit 215 (step S5). When the user checks the displayed product information and finds a product that the user wants to purchase, the user performs an operation to call the mobile sales robot carrying that 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).

[0195] When the server device 30 receives the call request, it executes a call request acceptance process (step S9). The details of the call request acceptance process will be described later. 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).

[0196] 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.

[0197] 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).

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

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

[0200] The server device 30 authenticates the pin code (step S19). Specifically, the server device 30 authenticates the pin code if the combination of the pin code and robot ID included in the received authentication request is stored in the call management table 3166. 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 sends an authentication notification to the mobile sales robot 10 (step S20).

[0201] When the mobile sales robot 10 receives the authentication notification, it permits processing related to the sale of the product. Then, when it detects that a product has been removed from the storage section 111 (step S21), it executes product registration for that product (step S22). The mobile sales robot 10 executes product registration every time a product is removed from the shelf 112, and cancels the product registration when the product is returned to the shelf 112. When a checkout instruction is input, the mobile sales robot 10 executes checkout processing (step S23). The details of the checkout processing will be described later. Then, the mobile sales robot 10 sends a payment request to the server device 30 based on the checkout processing (step S24).

[0202] The server device 30 executes the payment process based on the received payment request (step S25). The details of the payment process will be described later. 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 S26) and also to the user terminal 20 (step S27). When the user terminal 20 receives the payment completion notice, it displays information indicating that the payment has been completed on the display unit 215 (step S28).

[0203] Through the above operations, the mobile sales system 1 makes it possible for the mobile sales robot 10 carrying the product to move to a position designated by the user and sell the product.

[0204] Next, a description will be given of a call request acceptance process executed by the server device 30. Fig. 25 is a flowchart showing an example of the flow of the call request acceptance process by the control unit 314 of the server device 30.

[0205] The control unit 314 determines whether the transmitting / receiving unit 3141 has received a call request from the user terminal 20 (step S31), and if not (N in step S31), returns to the process of step S31 and waits. When the transmitting / receiving unit 3141 receives a call request (Y in step S31), the control unit 314 issues a PIN code associated with the call request (step S32).

[0206] The information management unit 3142 registers information related to the call request received by the transmitting / receiving unit 3141 in the call management table 3166 (step S33). Next, the transmitting / receiving unit 3141 transmits the issued PIN code to the user terminal 20 that is the source of the call request (step S34).

[0207] The robot management unit 3145 calculates the arrival time of the mobile sales robot 10 specified in the call request at the call position and transmits it to the user terminal 20 (step S35). The robot management unit 3145 refers to the robot management table 3163, and if the status of the specified mobile sales robot 10 is "waiting for a call" so that the mobile sales robot 10 can respond to a call from a user, calculates the arrival time based on the position of the mobile sales robot 10 and the call position.

[0208] Furthermore, if the status of the designated mobile sales robot 10 is not the above-mentioned "waiting for a call," the robot management unit 3145 calculates the arrival time taking into consideration other information. Here, the other information includes the number of call requests (unanswered requests with no arrival date and time registered) to the designated mobile sales robot 10 registered in the call management table 3166, a pre-set purchase time limit for one transaction, etc.

[0209] The robot management unit 3145 determines whether the status of the mobile sales robot 10 specified in the call request is "waiting for a call" (step S36). If it is "waiting for a call" (Y in step S36), the transmitting / receiving unit 3141 transmits a movement instruction including the terminal ID of the user terminal 20 and the call location to the specified mobile sales robot 10 (step S37). Then, the control unit 314 ends the call request acceptance process.

[0210] If the state of the designated mobile sales robot 10 is not "waiting for a call" (N in step S36), that is, if the mobile sales robot 10 cannot immediately start moving to the call position, the control unit 314 returns to the process of step S36.

[0211] By the above-described call request reception process, the server device 30 can manage the call requests from each user terminal 20 and move the designated mobile sales robot 10 to the call position in the order in which the call requests are received.

[0212] Next, a description will be given of the transaction process executed by the mobile sales robot 10. Fig. 26 is a flowchart showing an example of the flow of transaction process executed by the control unit 154 of the mobile sales robot.

[0213] The control unit 154 determines whether the input receiving unit 1542 has received a payment instruction (step S41), and if not (N in step S41), returns to the process of step S41 and waits. When the input receiving unit 1542 receives a payment instruction (Y in step S41), the information processing unit 1544 reads out product information of the registered product (step S42).

[0214] The display control unit 1546 causes the first display unit 131 to display the product information read by the information processing unit 1544 (step S43). The information processing unit 1544 also calculates the transaction amount, i.e., the total price of the registered products, based on the read product information (step S44). The calculated transaction amount is temporarily stored in the RAM 153.

[0215] The control unit 154 determines whether the information processing unit 1544 has acquired face image data from the imaging unit 134 (step S45), and if not (N in step S45), returns to the processing of step S45 and waits. In other words, the control unit 154 determines whether the imaging unit 134 has captured an image of the face of the user who will purchase the product in order to perform payment by facial authentication.

[0216] When the information processing unit 1544 acquires the facial image data from the imaging unit 134 (Y in step S45), the transmitting / receiving unit 1541 transmits a payment request to the server device 30 (step S46). The payment request includes the facial image data, product information, the transaction amount, etc. Then, the control unit 154 ends the transaction process.

[0217] Through the above-mentioned accounting process, the mobile sales robot 10 can provide the server device 30 with the information necessary for the server device 30 to perform the payment process, and can work together with the server device 30 to complete the payment of the user's purchase price.

[0218] Next, the payment process executed by the server device will be described. Figure 27 is a flowchart showing an example of the flow of the payment process by the control unit 314 of the server device.

[0219] The control unit 314 determines whether the transmitting / receiving unit 3141 has received a payment request from the mobile sales robot 10 (step S51), and if not (N in step S51), returns to the processing of step S51 and waits.

[0220] When the transmitting / receiving unit 3141 receives a payment request (Y in step S51), the payment processing unit 3144 determines whether the user ID can be identified from the facial image data included in the payment request (step S52). Specifically, the payment processing unit 3144 refers to the user management table 3165 and searches whether the received facial image data or the feature amount of the facial image data is registered as feature information.

[0221] If the user ID is identified (Y in step S52), the payment processing unit 3144 reads out payment information from the user management table 3165 and transmits the payment information to a payment server (not shown) of the payment service provider (step S53). Subsequently, the payment processing unit 3144 determines whether the payment is completed or not depending on whether information indicating that the payment is completed is received from the payment server (step S54).

[0222] When the payment is completed (Y in step S54), the payment processing unit 3144 updates the transaction management table 3167 (step S55). Specifically, the payment processing unit 3144 registers information indicating the payment completion in the payment flag of the transaction management table 3167. Next, the transmitting and receiving unit 3141 transmits a transaction completion notification to the user terminal 20 and the mobile sales robot 10 (step S56). The transmitting and receiving unit 3141 selects, from the terminal IDs corresponding to the robot ID of the mobile sales robot 10 that sold the product in the call management table 3166, the terminal ID corresponding to the arrival date and time closest to the time when the payment request was received, and transmits a payment completion notification to the user terminal 20 of that terminal ID. Then, the control unit 314 ends the payment processing.

[0223] If the user ID cannot be identified in the process of step S52 (N in step S52), that is, if the facial image data included in the payment request or the feature values ​​of the facial image data are not registered in the user management table 3165, the transmitting / receiving unit 3141 transmits error information to the mobile sales robot 10 indicating that payment cannot be made (step S57). Then, the control unit 314 ends the payment process.

[0224] Furthermore, in the process of step S54, if the payment is not completed (N in step S54), the control unit 314 proceeds to the process of step S57. If the payment by the payment service provider is not completed, the transmitting / receiving unit 3141 also transmits error information to the mobile sales robot 10.

[0225] Through the above-described payment process, the server device 30 executes the payment process in response to a payment request from the mobile sales robot 10. This allows the user to pay for the purchase without having to go to a separate cash register or the like.

[0226] As described above, the mobile sales system 1 of the above embodiment is a mobile sales system 1 having a mobile sales robot 10 equipped with a storage unit 111 for storing goods to be sold and a drive unit 123 for moving the device, and a user terminal 20 that can specify a call location for the mobile sales robot 10, wherein the user terminal 20 has a transmission / reception unit 2141 that transmits location information indicating the call location for the mobile sales robot 10, and the mobile sales robot 10 has a transmission / reception unit 1541 that acquires the location information transmitted by the user terminal 20, a drive control unit 1545 that controls the drive unit 123 based on the location information acquired by the transmission / reception unit 1541, and an accounting processing unit (information processing unit 1544) that performs accounting processing based on the product information of the goods taken out from the storage unit 111.

[0227] As a result, the mobile sales system 1 enables the mobile sales robot 10 loaded with merchandise to move to a location specified by a user and sell the merchandise. By adopting the mobile sales system 1, businesses that sell merchandise can expand their sales formats.

[0228] In addition, the user terminal 20 in the mobile sales system 1 of the above embodiment is a terminal device that can be carried by the user, and further includes a self-location determination unit 2143 that determines its own location, and the transmission / reception unit 2141 transmits location information indicating the location determined by the self-location determination unit 2143 as location information indicating the call location.

[0229] This allows the user to call the mobile sales robot 10 without performing any operation to input the call location of the mobile sales robot 10. Therefore, the mobile sales system 1 can improve user convenience.

[0230] Furthermore, the user terminal 20 in the mobile sales system 1 of the above embodiment further includes a transmission / reception unit 2141 that receives product information of the products carried by the mobile sales robot 10, and a display control unit 2144 that displays the product information received by the transmission / reception unit 2141 on the display unit 215.

[0231] This allows the user to check the products carried by the mobile sales robot 10 before calling the mobile sales robot 10. Therefore, the mobile sales system 1 can improve user convenience in this respect as well.

[0232] In addition, the mobile sales robot 10 in the mobile sales system 1 of the above embodiment further includes a detection unit (information processing unit 1544) that detects merchandise taken out of the storage unit 111, and the accounting processing unit (information processing unit 1544) performs accounting processing for the merchandise detected by the detection unit.

[0233] This eliminates the need for the user to perform any operation to read the product information of the product to be purchased, and therefore allows the user to easily pay for the purchase.

[0234] In addition, the mobile sales robot 10 in the mobile sales system 1 of the above embodiment further includes an input unit (transmitting / receiving unit 1541) into which trigger information (authentication notification) that is a condition for starting sales is input, and an alarm unit (information processing unit 1544) that issues an alarm when it is detected that a product is being removed from the storage unit 111 while the input unit has not accepted the input of the trigger information.

[0235] This allows the mobile sales robot 10 to issue an alarm when a commodity is or is about to be illegally removed from the storage section 111. This improves the security of the mobile sales system 1.

[0236] In the above embodiment, the control programs executed by the mobile sales robot 10, the user terminal 20, and the server device 30 may be provided by being recorded on a computer-readable recording medium such as a CD-ROM. Also, the control programs executed by the above devices may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or may be provided via a network such as the Internet.

[0237] Although the embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. The above embodiments 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 set forth in the claims. [Explanation of symbols]

[0238] 1 Mobile sales system 10 Mobile sales robot (mobile sales device) 20 User terminal (terminal device) 30 Server device 111 Storage unit (mounting unit) 215 Display section 123 Drive unit 1541 Transmitting / receiving unit (acquisition unit, input unit) 1544 Information processing unit (accounting processing unit, detection unit, alarm unit) 1545 Drive control unit 2141 Transmitter / Receiver 2143 Self-location part 2144 Display control unit 3141 Transmitter / Receiver [Prior art documents] [Patent documents]

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

Claims

1. A mobile sales system having a mobile sales device equipped with a mounting unit for mounting products to be sold and a driving unit for moving the device, and a terminal device capable of designating a call position for the mobile sales device, The terminal device a transmitting unit that transmits location information indicating a calling location of the mobile vending device; The mobile sales device is an acquisition unit that acquires location information transmitted by the terminal device; a drive control unit that controls the drive unit based on the position information acquired by the acquisition unit; a transaction processing unit that executes transaction processing based on product information of the product removed from the loading unit; Equipped with The mobile sales device is a detection unit that detects the product removed from the loading unit; an input unit for inputting trigger information that is a condition for starting sales; an alarm unit that issues an alarm when it is detected that the product is being removed from the loading unit while the trigger information is not being input to the input unit; The mobile sales system further comprises:

2. The terminal device A terminal device portable by a user, further comprising a self-location determining unit that determines a self-location, the transmitting unit transmits, as the location information indicating the call location, location information indicating the location identified by the self-location identifying unit. The mobile sales system according to claim 1.

3. The terminal device a receiving unit that receives product information of the products carried by the mobile sales device; a display control unit that causes the product information received by the receiving unit to be displayed on a display unit; The mobile sales system according to claim 1 or 2, further comprising:

4. The accounting processing unit performs accounting processing for the product detected by the detection unit.

4. The mobile sales system according to claim 1.

Images