Title of invention: article accommodating system, server, article accommodating method, program and information processing apparatus
Technical field
[0001]
　The present invention relates to a technique for managing the accommodation of goods.
Background technology
[0002]
　When delivering goods such as goods and luggage to a specific user, the user may go to a storage place such as a store or an agency to receive the goods, or a trader may deliver the goods to his / her home or office.
Prior art literature
Patent documents
[0003]
Patent Document 1: International Publication No. 2018/042668
Patent Document 2: Japanese Patent Application Laid-Open No. 2011-022791
Outline of the invention
Problems to be solved by the invention
[0004]
　However, it is laborious for the user to go to the storage destination. In addition, the method of delivering goods to home or work also places a heavy burden on the trader.
[0005]
　The present invention is an invention completed based on the above-mentioned problem recognition, and its main purpose is to enable easy delivery of goods.
Means to solve problems
[0006]
　The article accommodating system according to an aspect of the present invention is an article accommodating system including a storage body for accommodating articles and a server connected to the storage body, in which the server provides a user interface for inquiring articles by a user. The storage body includes an interface providing unit, which provides an operation unit for delivering an article in the storage body to a user.
[0007]
　The article accommodating system according to another aspect of the present invention is an article accommodating system including a storage body for accommodating articles and an information processing device connected to the storage body, wherein the storage body is an article picked up by a user. , A first notification unit that notifies the information processing device of the information associated with the user who has picked up the article, and the information processing device records the user's pick-up of the article from the storage body based on the linked information. It is equipped with a recording unit.
The invention's effect
[0008]
　According to the present invention, the delivery of goods can be easily performed.
A brief description of the drawing
[0009]
[Fig. 1] Fig. 1 is a configuration diagram of a storage device.
[Fig. 2] Fig. 2 is a diagram showing an example of a photographed image of a storage device.
[Fig. 3] Fig. 3 is a functional block diagram of a computer included in a storage device.
[Fig. 4] Fig. 4 is a flowchart showing an operation process of a storage device.
[Fig. 5] Fig. 5 is a layout diagram of a storage device.
[Fig. 6] It is a network configuration diagram.
[Fig. 7] Fig. 7 is a schematic diagram showing a pre-purchase method for products in storage.
[Fig. 8] Fig. 8 is a functional block diagram of a user terminal.
[Fig. 9] It is a functional block diagram of a server.
[Fig. 10] This is an example of the storage layout screen.
[Fig. 11] This is an example of the storage confirmation screen.
[Fig. 12] This is an example of a product purchase screen.
[Fig. 13] This is an example of the route navigation screen.
[Fig. 14] It is a data structure diagram of the product list in storage.
[Fig. 15] It is a data structure diagram of a ticket table.
[Fig. 16] It is a data structure diagram of a sales table.
[Fig. 17] It is a functional block diagram of a clerk terminal.
[Fig. 18] Fig. 18 is a sequence diagram when a store clerk stores a product in a storage device.
[Fig. 19] Fig. 19 is a sequence diagram when a user accesses a server site from a user terminal and purchases a product in a storage device.
FIG. 20 is a sequence diagram when a user accesses a server site from a user terminal and purchases a product in a storage device.
FIG. 21 is a sequence diagram when a user takes out a product purchased from a storage device.
[Fig. 22] Fig. 22 is a schematic diagram showing a reservation purchase method for products in storage.
[Fig. 23] Fig. 23 is a schematic diagram showing a method of voluntarily purchasing products in storage.
[Fig. 24] Fig. 24 is a layout diagram of a storage device.
[Fig. 25] Fig. 25 is a schematic diagram showing a pre-purchase method for products in store inventory.
[Fig. 26] It is a functional block diagram of a store terminal.
[Fig. 27] Fig. 27 is a sequence diagram when a user accesses a server site from a user terminal and purchases a product in a store.
[Fig. 28] It is a schematic diagram which shows the reservation purchase method of the store inventory product.
[Fig. 29] FIG. 29 is a schematic diagram showing a prepaid payment method using a paper ticket.
[Fig. 30] Fig. 30 is a functional block diagram of a cash register.
[Fig. 31] It is a sequence diagram about the exchange at the cash register.
[Fig. 32] Fig. 32 is a sequence diagram for taking out products.
[Fig. 33] Fig. 33 is a schematic diagram showing a post-payment method using a paper ticket.
FIG. 34 is a sequence diagram relating to the issuance of a paper ticket.
[Fig. 35] Fig. 35 is a sequence diagram related to product retrieval and settlement.
FIG. 36 is a schematic diagram showing a reservation purchase method for store products.
[Fig. 37] Fig. 37 is a sequence diagram when a user accesses a server site from a user terminal and reserves a product (hot snack) in a store.
[Fig. 38] Fig. 38 is a sequence diagram when a user takes out a product purchased from a storage device.
FIG. 39 is a schematic diagram showing a pre-purchase method for store products.
Embodiment for carrying out the invention
[0010]
　In this embodiment, a storage device is used for delivery of goods. The storage device is about the same size as a vending machine or refrigerator, so it can be installed in a small space.
[0011]
　FIG. 1 is a configuration diagram of a storage device 100.
　The storage device 100 includes a hinged door type door 102, and stores the product 104 on a plurality of shelves. The open / closed state of the door 102 is detected by the open / close sensor 106. Further, the door 102 is locked by the lock mechanism 108. The product 104 installed on the shelf is photographed by the camera 110. The captured image identifies the contained goods 104. The storage device 100 includes a temperature adjusting device 112, and can adjust the internal temperature and humidity. Further, the storage device 100 includes a ticket reader 114. The ticket reader 114 reads the electronic ticket presented by the operator. The electronic ticket is a graphic code such as a QR code (registered trademark) or a barcode, a contact / non-contact type IC card, or the like. Hereinafter, the electronic ticket will be described as assuming that it is a QR code. The storage device 100 is connected to the server via a network and communicates with the server. Further, the storage device 100 includes a speaker 116 that emits an operation guide, a warning message, and a warning sound.
[0012]
　The storage device 100 stores a list of electronic tickets granted to an operator authorized to use the storage device 100, and any of the electronic tickets read by the ticket reader 114 is included in the ticket list. When it matches the electronic ticket, the lock is released and the door 102 is controlled to be opened. There are two types of electronic tickets, one that allows only one use and the other that can be used repeatedly. Further, the storage device 100 has a computer 200 for control.
　The type, number, position, arrangement, additional functions, etc. of the camera 110 can be appropriately set. As an additional function, a sensor for improving accuracy (improving recognition accuracy after adding weight by a weight sensor) can be appropriately adopted. In addition, the camera includes not only still images but also those capable of shooting moving images.
[0013]
　FIG. 2 is a diagram showing an example of a captured image of the storage device 100.
　A label on which the product barcode 118 is printed is affixed to the surface of the product 104. By reading the product barcode 118 from the captured image, the stored product 104 can be identified. The product 104 in this example is a side dish pack such as a lunch box, a sandwich, a salad, or a drink. However, it may be a product 104 of a type other than these.
　In the present embodiment, the description will proceed on the premise that the product 104 is identified by the product barcode 118, but in the present invention, the product barcode 118 is not essential, and the shape and the like of the product 104 are directly read from the photographed image. May identify the contained goods 104.
[0014]
　FIG. 3 is a functional block diagram of the computer 200 included in the storage device 100.
　Each component of the computer 200 is stored in a storage device and hardware including a CPU (Central Processing Unit), a computing unit such as various coprocessors, a storage device such as a memory and a storage device, and a wired or wireless communication line connecting them. It is realized by software that supplies processing instructions to the arithmetic unit. A computer program may be composed of a device driver, an operating system, various application programs located on the upper layer thereof, and a library that provides common functions to these programs. Each of the illustrated blocks shows a block of functional units, not a configuration of hardware units. The same applies to the user terminal, the server, the clerk terminal, the store terminal, and the cash register, which will be described later.
[0015]
　The computer 200 includes a user interface processing unit 210, a data processing unit 240, a communication unit 250, and a data storage unit 280. The user interface processing unit 210 is in charge of user interface processing via the ticket reader 114, the speaker 116, and the like. The communication unit 250 is in charge of communication processing via the network. The data storage unit 280 stores various data. The data processing unit 240 executes various processes based on the data acquired by the communication unit 250 and the data stored in the data storage unit 280. The data processing unit 240 also functions as an interface for the user interface processing unit 210, the communication unit 250, and the data storage unit 280.
[0016]
　The user interface processing unit 210 includes an input unit 220 that accepts operation input by the operator and an output unit 230 that presents information of the operator.
　The input unit 220 includes a ticket reading unit 222 for reading a ticket. The output unit 230 includes a warning output unit 232 that outputs a warning message or a warning sound from the speaker 116. The operator referred to here corresponds to a user who purchases a product or a store clerk who manages the storage device 100 in the example described later.
[0017]
　The data processing unit 240 includes a ticket authentication unit 242, a product detection unit 244, a lock control unit 246, an open / close detection unit 248, and a ticket list management unit 252. The ticket authentication unit 242 authenticates the read electronic ticket. The product detection unit 244 detects the product 104 stored or the product 104 taken out while the door 102 is opened and closed. Specifically, it is determined that the product 104 that has increased when the door 102 is closed is the stored product 104, and the product 104 that has also decreased is the product 104 that has been taken out. The lock control unit 246 controls the lock mechanism 108. The open / close detection unit 248 detects the open / close of the door 102 of the storage device 100 by using the open / close sensor 106. The ticket list management unit 252 manages the ticket list.
[0018]
　The communication unit 250 includes a transmission unit 260 for transmitting data and a reception unit 270 for receiving data.
　The transmission unit 260 includes a storage notification transmission unit 262 and a take-out notification transmission unit 264. The storage notification transmission unit 262 transmits a storage notification. The storage notification will be described later in relation to FIG. The take-out notification transmission unit 264 transmits a take-out notice. The withdrawal notification will be described later in relation to FIG. The receiving unit 270 includes a ticket receiving unit 272 and a approval / disapproval notification receiving unit 274. The ticket receiving unit 272 receives the electronic ticket. The approval / rejection notification receiving unit 274 receives the approval / rejection notification. The approval / disapproval notification will be described later in relation to FIG.
[0019]
　The data storage unit 280 includes a ticket list storage unit 282. The ticket list storage unit 282 stores the ticket list. The electronic ticket data received from the server is registered in the ticket list. In the case of a modification using a paper ticket, the data converted into the QR code (hereinafter referred to as "paper ticket data") is registered in the ticket list.
[0020]
　FIG. 4 is a flowchart showing the operation process of the storage device.
　When the ticket reading unit 222 detects the reading of the electronic ticket by the ticket reader 114 (S10), the ticket authentication unit 242 authenticates the read ticket (S12). If the electronic ticket read by the ticket reader 114 matches any of the electronic tickets contained in the ticket list, the authentication is successful. On the other hand, if the read electronic ticket does not match any of the electronic tickets included in the ticket list, authentication fails. If authentication fails, no further processing is performed. If the authentication fails, the warning output unit 232 may output a warning message or a warning sound such as "This ticket cannot be used."
[0021]
　If the authentication is successful, the product detection unit 244 detects the product 104 currently housed inside (S14). Then, the lock control unit 246 controls the lock mechanism 108 to unlock the door 102 (S16). As a result, the operator can open the door 102 of the storage device 100.
[0022]
　When the door 102 of the storage device 100 is opened, the open / close detection unit 248 detects the door open by using the open / close sensor 106 (S18). If the user purchases the product 104, the product 104 is taken out from the shelf. If the store clerk visits to install the product 104, the product 104 is stored on the shelf. Then, when the operator closes the door 102 of the storage device 100, the open / close detection unit 248 detects the door close using the open / close sensor 106 (S20).
[0023]
　The product detection unit 244 detects the product 104 housed inside when the door 102 of the storage device 100 is closed. Then, the product detection unit 244 calculates the difference from the product 104 detected in S14. When the product 104 is taken out from the shelf, the product detection unit 244 determines that the reduced product 104 is the product 104 taken out. When the product 104 is stored on the shelf, the product detection unit 244 determines that the increased product 104 is the stored product 104 (S22).
[0024]
　When the product 104 is taken out, the take-out notification transmission unit 264 transmits the take-out notice to the server 400. The withdrawal notification includes the data of the product barcode 118 of the retrieved product 104 and the electronic ticket used. When the product 104 is stored, the storage notification transmission unit 262 transmits the storage notification to the server 400 (S24). The storage notification includes the data of the product barcode 118 of the stored product 104 and the electronic ticket used.
[0025]
　When the server 400 receives the take-out notification or the storage notification from the storage device 100, it determines whether the taken-out product 104 or the stored product 104 is valid in relation to the operator specified by the electronic ticket. do. If it is valid, a notification indicating approval is sent to the storage device 100. If it is not valid, a notification indicating denial is sent to the storage device 100. For example, if a clerk stores an unscheduled product 104, a notification indicating denial is sent. Alternatively, if the user takes out the product 104 that has not been purchased, a notification indicating denial is sent. A notice indicating approval or denial is called a denial notice.
[0026]
　The approval / rejection notification receiving unit 274 of the storage device 100 receives the approval / rejection notification from the server 400 (S26). When the approval / rejection notification indicates rejection, the warning output unit 232 outputs a warning (S30). If the removed product 104 is not valid, for example, a warning message or a warning sound such as "The wrong product has been taken out. Please take it again." Is emitted. If the stored product 104 is not valid, for example, a warning message or sound such as "The correct product has not been inserted. Please reinsert it." Is emitted. Then, the process returns to S18.
[0027]
　On the other hand, when the received approval / disapproval notification indicates approval, the lock control unit 246 locks by the lock mechanism 108 (S32). When an electronic ticket of a type that allows only one use is used, the used electronic ticket is deleted from the ticket list (S34).
[0028]
　In the following, it is assumed that a user working in an office district purchases a side dish pack such as a lunch box, a sandwich, a salad, or a drink at lunch. However, when the other product 104 is purchased for another purpose, it can be operated in the same manner. An example of arranging the storage device as a prerequisite will be described.
[0029]
　FIG. 5 is a layout diagram of the storage device.
　The storage device 100a is installed on the 4th floor of the office building A where the office where the user 122 works is located, and the storage device 100b is also installed on the 1st floor. Further, the storage device 100c is installed on the third floor of the office building B next to the office building A, and the storage device 100d is also installed on the first floor.
[0030]
　Furthermore, there is a store on the first floor of office building C next to office building B. This store sells lunch boxes, sandwiches, salads and other delicatessen packs and drinks. The storage devices 100a to 100d are managed by this store. That is, the product 104 housed in the storage devices 100a to 100d is supplied by this store. In addition to the sales floor in the store, the product 104 can be sold in the storage devices 100a to 100d, so that the sales of the store are expected to increase. In addition, it can be expected that the unsold product 104 will be eliminated.
[0031]
　At the store, side dish packs such as lunch boxes, sandwiches, and salads and drinks are provided to nearby consumers in the storage devices 100a to 100d, and the consumers purchase these. By delivering the products distributed to the storage devices 100a to 100d, the congestion in the store is eliminated and the purchase can be smoothly performed. The store clerk 120 patrols the storage devices 100a to 100d to replenish the product 104. In the following, it is assumed that the clerk 120 stores the product 104 in the storage devices 100a to 100d, and the user 122 purchases the product 104 housed in the storage devices 100a to 100d.
[0032]
　In this example, only one store is shown, but a plurality of stores may be in charge of the storage device 100 in the same manner. The store may be a chain store such as a convenience store or a family restaurant, or may be a department store, a supermarket, a member's store belonging to a union in a shopping district, a distribution center, a distribution center, or the like.
　In addition, the store itself may be eliminated and the product may be sent directly from the manufacturer.
[0033]
　FIG. 6 is a network configuration diagram.
　The storage devices 100a to 100d are connected to the server 400 via a network (for example, the Internet or a dedicated line). Further, the user terminals 300a to 300c (for example, a smartphone, a mobile terminal or a personal computer) used by the user 122 can be connected to the server 400 via the Internet. When the user terminals 300a to 300c and the like are collectively referred to, or when there is no particular distinction, they are collectively referred to as "user terminal 300".
[0034]
　The server 400 is connected to a store information system (hereinafter referred to as "store system") via a network (for example, the Internet or a dedicated line). The store system 500 includes a store clerk terminal 600 (for example, a smartphone, a mobile terminal or a personal computer), a store terminal 700, a cash register 800 and a storage device 100e. Further, the cash register 800 and the storage device 100e are connected to the store terminal 700 via, for example, a LAN (Local Area Network). The cash register 800 and the storage device 100e are used in a modification described later.
[0035]
　The site of the server 400 provides information about the store, the storage device 100, and the product 104. The user terminal 300 has an application program that accesses the server 400, downloads various data, displays a screen, and uploads various data input by the user operation to the server 400. That is, it is assumed that the application program of the user terminal 300 controls the operation of the user terminal 300 as a native application method. However, a method of a Web application that controls the operation of the user terminal 300 by a script included in the Web page may be adopted. In the method of the Web application, the user terminal 300 performs the same processing as in the case of the native application by executing the script included in the Web page in the browser.
[0036]
　In the present embodiment, the user 122 uses the user terminal 300a to check the product 104 housed in the storage devices 100a to d, and purchases the product 104 that he / she likes on the Web. Then, it later goes to the storage devices 100a to 100d and receives the purchased product 104. This transaction mode is called "pre-purchase method for products in storage".
[0037]
　The electronic ticket used in this embodiment is issued to the user 122 who has purchased the product 104. The application program of the user terminal 300a saves the electronic ticket received from the server 400, and realizes a function of displaying the electronic ticket as a QR code on the display.
[0038]
　FIG. 7 is a schematic diagram showing a pre-purchase method for products in the storage.
　In this example, the clerk 120 stores the product 104 in the storage device 100a at 11:30 before the lunch break. The product 104 in this example is a lunch box or the like. The product 104 to be stored is selected by the store. The information of the stored product 104 is notified to the server 400 and disclosed on the site of the server 400. As a result, the user terminal 300 can access the site of the server 400 and browse the product 104 stored in the storage device 100a in real time.
[0039]
　After that, at 11:40, the user 122 browses the product 104 in the storage device 100a on the user terminal 300, selects and purchases the product 104 that he / she likes. At this point, the transaction is completed and the server 400 records sales. Then, the purchased product 104 will be owned by the user 122. However, this product 104 is still housed in the storage device 100a. Further, when the user 122 purchases the product 104, the server 400 transmits an electronic ticket to the user terminal 300. The user terminal 300 stores the received electronic ticket.
[0040]
　At 12:10 during the lunch break, the user 122 carries the user terminal 300 and moves to the installation location of the storage device 100a. The user 122 operates the user terminal 300 to display the QR code of the electronic ticket, and holds the QR code over the ticket reader 114 of the storage device 100a. When the ticket reader 114 reads the QR code of the electronic ticket, the door 102 is unlocked. Then, the user 122 opens the door 102 of the storage device 100a and takes out the product 104 purchased by himself / herself. When the user 122 closes the door 102 of the storage device 100a, the door 102 is locked. When the user 122 takes out the product 104 that has not been purchased, a warning is issued, and the user 122 retakes the product 104. Since the electronic ticket in this example is valid only once, it is deleted from the ticket list when the purchased product 104 is taken out. That is, the user 122 cannot open the door 102 of the storage device 100a again using the same electronic ticket. As for payment, a conventional method such as prepaid or postpaid electronic payment or cash payment may be used. Hereinafter, the processing in this method will be described in detail.
[0041]
　FIG. 8 is a functional block diagram of the user terminal 300.
　The user terminal 300 includes a user interface processing unit 310, a data processing unit 340, a communication unit 350, and a data storage unit 380. The user interface processing unit 310 accepts operations from the user via a touch panel or the like, and is in charge of user interface processing such as image display and audio output. The communication unit 350 is in charge of communication processing via the network. The data storage unit 380 stores various data. The data processing unit 340 executes various processes based on the data acquired by the communication unit 350 and the data stored in the data storage unit 380. The data processing unit 340 also functions as an interface for the user interface processing unit 310, the communication unit 350, and the data storage unit 380.
[0042]
　The user interface processing unit 310 includes an input unit 320 that accepts operation input by the user and an output unit 330 that presents information to the user. The input unit 320 includes an operation reception unit 322 that accepts user operations. The output unit 330 includes a ticket output unit 332 and an image output unit 334. The ticket output unit 332 displays the electronic ticket with a QR code. The image output unit 334 displays various screens.
[0043]
　The data processing unit 340 includes a position detection unit 342 that detects the current position of the user terminal 300. The position detection unit 342 operates when, for example, the server 400 requests the current position.
[0044]
　The communication unit 350 includes a transmission unit 360 for transmitting data and a reception unit 370 for receiving data.
　The transmission unit 360 includes a request transmission unit 362, a location transmission unit 364, and an account information transmission unit 366. The request transmission unit 362 transmits various requests. The position transmission unit 364 transmits the current position of the user terminal 300. The account information transmission unit 366 transmits account information.
[0045]
　The receiving unit 370 includes a screen data receiving unit 372 and a ticket receiving unit 374. The screen data receiving unit 372 receives data on various screens. The ticket receiving unit 374 receives the electronic ticket.
[0046]
　The data storage unit 380 includes a ticket storage unit 382 that stores an electronic ticket given by the server 400 and an account information storage unit 384 that stores account information.
[0047]
　FIG. 9 is a functional block diagram of the server 400.
　The server 400 includes a data processing unit 440, a communication unit 450, and a data storage unit 480. The communication unit 450 is in charge of communication processing via the network. The data storage unit 480 stores various data. The data processing unit 440 executes various processes based on the data acquired by the communication unit 450 and the data stored in the data storage unit 480. The data processing unit 440 also functions as an interface between the communication unit 450 and the data storage unit 480.
[0048]
　The data processing unit 440 includes a product list management unit 442, a user authentication unit 443, a screen data generation unit 444, a storage selection unit 445, a ticket generation unit 446, a transaction management unit 448, and a product verification unit 449.
　The product list management unit 442 manages a list of products 104 (hereinafter, referred to as “product list in storage”) accommodated in the storage device 100. The user authentication unit 443 performs the user authentication process when the access is received from the user terminal 300. In the user authentication process, unauthorized access is eliminated and the user ID is specified in the legitimate access. The user authentication process may be a conventional technique. The screen data generation unit 444 generates data of various screens displayed on the user terminal 300. The storage selection unit 445 selects the storage device 100. The ticket generation unit 446 generates an electronic ticket. The ticket generation unit 446 may generate paper ticket data in a modified example described later. The transaction management unit 448 manages transactions such as sales and reservations of the product 104. The product verification unit 449 determines whether or not the product 104 taken out from the storage device 100 or the product 104 stored in the storage device 100 is valid.
[0049]
　The communication unit 450 includes a transmission unit 460 for transmitting data and a reception unit 470 for receiving data.
　The transmission unit 460 includes a screen data transmission unit 462, a ticket transmission unit 464, a recognition / rejection notification transmission unit 466, a storage instruction transmission unit 468, and a reservation notification transmission unit 452.
　The screen data transmission unit 462 transmits data of various screens displayed on the user terminal 300. The ticket transmission unit 464 transmits an electronic ticket. The approval / rejection notification transmission unit 466 transmits the approval / rejection notification. The storage instruction transmission unit 468 will be described in Modification 4 described later. The reservation notification transmission unit 452 will be described in a modified example 8 described later.
[0050]
　The receiving unit 470 includes a storage notification receiving unit 472, a request receiving unit 474, an fetching notification receiving unit 476, a position receiving unit 478, and an account information receiving unit 479.
　The storage notification receiving unit 472 receives the storage notification. The request receiving unit 474 receives various requests. The take-out notification receiving unit 476 receives the take-out notice. The position receiving unit 478 receives the current position of the user terminal 300. The account information receiving unit 479 receives the account information.
[0051]
　The data storage unit 480 includes a store table storage unit 481, a product master table storage unit 482, a storage table storage unit 483, a storage product list storage unit 484, a user table storage unit 485, a ticket table storage unit 486, and a sales table storage unit 488. And the reservation table storage unit 490.
[0052]
　The store table storage unit 481 stores the store table. The store table has a record for each store. The record stores a store ID, a store name, a store location, and the like. The store ID is an identifier of the store used for information processing and does not have to be disclosed to the outside. The store name is, for example, "Central station square store". The store location includes the address, building name and floor, latitude and longitude, and the like.
[0053]
　The product master table storage unit 482 stores the product master table. The product master table has a record for each product 104 handled by the storage device 100. The record stores the product ID, the product type, the product name, the data of the product barcode 118, the price, the photo data, and the like. The product ID is an identifier of the product 104 used for information processing and does not have to be disclosed to the outside. The types of products are, for example, lunch boxes, salads and drinks. The product names are, for example, "tempura bento" and "sukiyaki bento". The photographic data is used to include the appearance of the product 104 in the product purchase screen displayed on the user terminal 300. The product purchase screen will be described later in relation to FIG.
[0054]
　The storage table storage unit 483 stores the storage table. The storage table has a record for each storage device 100. The record stores a storage ID, a storage name, an installation location, a management store ID, a floor sketch, and the like. The storage ID is an identifier of the storage device 100 used for information processing and does not have to be disclosed to the outside. The storage name is, for example, "building A-F4" or "building A-F1". The installation location includes the address, building name and floor, latitude and longitude, etc. The management store ID is the store ID of the store that manages the storage device 100. The floor sketch is included in the storage confirmation screen displayed on the user terminal 300. The floor sketch will be described later in relation to FIG.
[0055]
　The product list storage unit 484 in the storage stores the product list in the storage. The list of products in storage will be described later in relation to FIG.
[0056]
　The user table storage unit 485 stores the user table. The user table has a pre-registered user, that is, a record for each member. The record stores a user ID, a user name, account information, a storage device ID of a storage device 100 near the work location, a storage device ID of the storage device 100 near the home, information on an electronic payment means, and the like. The storage device 100 near the work location is the target of product introduction assuming work. The storage device 100 near the home is a target of product introduction assuming that the storage device 100 is at home. The condition assuming employment may be a time zone or the current position of the user terminal 300. Similarly, the condition assuming that the person is at home may be determined based on the time zone or the current position. The storage device 100 near the work location and the storage device 100 near the home can be operated and registered by the user. The registration of these storage devices 100 will be described later in relation to FIG.
[0057]
　The ticket table storage unit 486 stores the ticket table. The ticket table will be described later in relation to FIG.
[0058]
　The sales table storage unit 488 stores the sales table. The sales table will be described later in relation to FIG.
[0059]
　The reservation table storage unit 490 stores the reservation table. The reservation table will be described in Modification 1 described later.
[0060]
　FIG. 10 is an example of a storage arrangement screen.
　When the server 400 is accessed from the user terminal 300, the storage arrangement screen is displayed. This example assumes work. The installation location of the storage device 100 near the current position (black circle in the figure) is displayed on the map. In particular, the storage device 100 registered as the storage device 100 near the work location is highlighted. Then, these storage devices 100 are the targets of product introduction. As the storage device 100 near the work location, a storage device 100 within a predetermined range from the work location may be set as a default. When the storage confirmation button is touched, the storage confirmation screen (FIG. 11) is displayed. When the product menu button is touched, the product purchase screen (FIG. 12) is displayed.
[0061]
　FIG. 11 is an example of a storage confirmation screen.
　A floor sketch is displayed on the storage confirmation screen. The floor sketch shows the location of the storage device 100 within the floor. The floor sketch is an example of data displaying the position in the building or site where the storage device 100 is installed. In this example, since the storage device 100 is registered near the work location, a pattern is attached to the registration button. When the user touches the release button, the registration of the storage device 100 is canceled. On the contrary, when the storage device 100 is not registered near the work location, a pattern is attached to the release button, and when the registration button is touched, the storage device 100 is registered.
[0062]
　FIG. 12 is an example of a product purchase screen.
　On the product purchase screen in this example, the product 104 that can be purchased in the storage device 100 that is the target of product introduction is displayed. The product purchase screen of FIG. 12 is displayed on the user terminal 300. Among the products 104 that can be purchased, for example, a lunch box is selected, and the product name, price, photograph, and storage device name are displayed. Further, a purchase button for applying for purchase corresponding to the product 104 is also displayed. For example, when the user 122 touches the purchase button of the "tempura lunch box", the user 122 purchases the "tempura lunch box" housed in the storage device 100a. The purchased product 104 is not displayed on the product purchase screen. In this example, if there is only one "tempura bento" from the beginning, the "tempura bento" will not be displayed on the product purchase screen after the purchase of the user 122.
[0063]
　Touching a button indicating the type of another product 104, such as a salad button or a drink button, switches to a list of products 104 of that type.
[0064]
　When you touch the recommendation button, the recommended combination of products 104 is displayed. For example, a combination of "tempura bento", "radish salad" and "green tea" is displayed. The recommended product 104 combinations are stored in the server 400. The operator of the server 400 may set the recommended combination of products 104, or the manager of the store may set the recommended combination. The combination of products 104 may be determined according to the time. The total calories of the product 104 in the recommended combination and the calories to be consumed by exercise may be displayed according to the total calories. Further, the distance to be walked and the number of stairs to be climbed may be calculated and displayed based on the calories to be consumed.
[0065]
　Touch the standard button to switch to the list of products 104 that have been purchased most often. The product 104 may be determined based on the purchase history of the individual user, or the product 104 may be determined based on the purchase history of the user group having common user attributes (for example, gender, age, etc.). Further, the product 104 may be determined based on the purchase history of all users. In addition, you may refer to the purchase history at unmanned stores.
[0066]
　When you touch the discount button, a list of discounted products 104 is displayed. The server 400 may automatically set a discount according to the expiration date. Discounts may be set automatically according to the number of unsold items. The discount may be given preferentially to the user who is near the storage device 100. Discounts may be set according to the amount of consumption by the user.
[0067]
　When the user touches the confirm button, the product purchase screen is closed and the route navigation screen is displayed.
[0068]
　FIG. 13 is an example of a route navigation screen.
　The route navigation screen shows a route connecting the storage devices 100 in which the products purchased by the user are stored. How to decide the route is not limited. The route of the shortest distance may be shown. Alternatively, an exercise may be promoted by indicating a route that is equal to or greater than the reference distance. Further, the route may be recalculated and displayed when the pre-purchased or pre-booked product is out of stock in the storage device 100 or delivered to the storage device 100 closer to the storage device 100.
[0069]
　FIG. 14 is a data structure diagram of the product list in the storage.
　The in-storage product list is used to grasp the products stored in each storage device 100. A product list in storage is provided for each storage device 100. In the product list in the storage, the product ID and the purchase status of each product stored in the storage device 100 are stored. The purchase status indicates either unpurchased or purchased. In this example, it is shown that four kinds of lunch boxes having the product IDs LB01, LB02, LB03 and LB04 are housed in the storage device 100a having the storage device ID ST001. The product 104 of LB01 and LB02 indicates that it has not been purchased and can be purchased at this time, and the product 104 of LB03 and LB04 indicates that it has been purchased and cannot be purchased at this time.
[0070]
　FIG. 15 is a data structure diagram of the ticket table.
　The ticket table is used to manage the electronic tickets issued by the server 400. The ticket table has a record for each electronic ticket issued by the server 400. The record stores an electronic ticket ID, electronic ticket data, a user ID, and the like. The electronic ticket ID is an identifier of an electronic ticket used for information processing and does not have to be disclosed to the outside. The electronic ticket data is a unique code string that is converted into a QR code figure. The user ID identifies the user to whom this electronic ticket has been granted. The user ID may be included in the electronic ticket data, or the product ID or product barcode data of the purchased product 104 may be included. The electronic ticket data may be an electronic ticket ID.
[0071]
　FIG. 16 is a data structure diagram of the sales table.
　It is a table for managing sales made by sales transactions. The sales table has a record for each sales transaction. The record stores a transaction ID, a product ID, a user ID, a selling price, an electronic ticket ID, a storage device ID, a withdrawal status, and the like. The transaction ID is assigned to each sales transaction. The product ID identifies the sold product 104. The user ID identifies the purchased user 122. The electronic ticket ID identifies the electronic ticket used in this sale. The storage device ID identifies the storage device 100 used in this sale. The withdrawal status indicates whether or not the product 104 has been taken out from the storage device 100, that is, has not been taken out or has been taken out.
[0072]
　FIG. 17 is a functional block diagram of the clerk terminal 600.
　The clerk terminal 600 includes a user interface processing unit 610, a data processing unit 640, a communication unit 650, and a data storage unit 680. The user interface processing unit 610 accepts operations from a clerk via a touch panel or the like, and is in charge of user interface processing such as image display and voice output. The communication unit 650 is in charge of communication processing via the network. The data storage unit 680 stores various data. The data processing unit 640 executes various processes based on the data acquired by the communication unit 650 and the data stored in the data storage unit 680. The data processing unit 640 also functions as an interface for the user interface processing unit 610, the communication unit 650, and the data storage unit 680.
[0073]
　The user interface processing unit 610 includes an input unit 620 that receives an operation input by a store clerk and an output unit 630 that presents information to the store clerk. The input unit 620 includes an operation reception unit 622 that accepts operations by a clerk.
　The output unit 630 includes a ticket output unit 632 and a storage list output unit 634. The ticket output unit 632 displays the clerk ticket as a QR code on the display. The clerk 120 is provided with a clerk ticket for opening the door 102 of the storage device 100 as a business. The clerk ticket is displayed as a QR code on the clerk terminal 600 in the same manner as the electronic ticket given to the user 122. A clerk ticket is a type of ticket that can be used over and over again. The storage list output unit 634 will be described in Modification 4 described later.
[0074]
　The communication unit 650 includes a transmission unit 660 for transmitting data and a reception unit 670 for receiving data. The transmission unit 660 includes a storage list request unit 662 that requests a storage list from the store terminal 600. The receiving unit 670 includes a storage list receiving unit 672. The storage list request unit 662 and the storage list receiving unit 672 will be described in a modified example 4 described later.
[0075]
　The data storage unit 680 includes a ticket storage unit 682 and a storage list storage unit 684. The ticket storage unit 682 stores the clerk ticket. The storage list storage unit 684 will be described in Modification 4 described later.
[0076]
　FIG. 18 is a sequence diagram when the store clerk 120 stores the product 104 in the storage device 100a.
　When the clerk 120 tries to store the product taken out from the store in the storage device 100a, the clerk terminal 600 is operated to display an electronic ticket, and the QR code is held over the ticket reader 114 of the storage device 100a (S40).
[0077]
　The basic operation of the storage device 100a is as described with reference to FIG. Here, only a part of the basic operations will be described.
[0078]
　When the clerk ticket obtained by the ticket reading unit 222 of the storage device 100a is successfully authenticated (S42) and the clerk 120 finishes storing the product 104, the storage notification transmitting unit 262 transmits the storage notification to the server 400. (S44). The storage notification includes the data of the product barcode 118 of the stored product 104 and the used clerk ticket.
[0079]
　When the storage notification receiving unit 472 of the server 400 receives the storage notification, the product list management unit 442 adds the product ID corresponding to the product barcode 118 of the stored product 104 to the product list in the storage (S46). Not purchased is set for the corresponding purchase status. Then, the approval / rejection notification transmission unit 466 transmits a notification indicating approval to the storage device 100a.
[0080] [0080]
　19 and 20 are sequence diagrams when the user 122 accesses the site of the server 400 from the user terminal 300a and purchases the product 104 in the storage device 100a.
　When the application program of the user terminal 300a is started, the account information transmission unit 366 transmits the account information stored in the account information storage unit 384 to the server 400 (S300).
[0081]
　When the account information receiving unit 479 of the server 400 receives the account information, the user authentication unit 443 performs user authentication (S302). If the user authentication is successful, the storage selection unit 445 selects the storage device 100 to be displayed (S304). Specifically, the one registered as the storage device 100 near the work location is selected. Alternatively, the current location of the user terminal 300a may be acquired to extract the storage device 100 within a certain distance from the user terminal 300a.
[0082]
　The screen data generation unit 444 of the server 400 refers to the storage table and generates a storage arrangement screen (S306). The screen data transmission unit 462 transmits the data of the storage arrangement screen to the user terminal 300a (S308).
[0083]
　When the screen data receiving unit 372 of the user terminal 300a receives the data of the storage arrangement screen, the image output unit 334 displays the storage arrangement screen (S310). When the operation reception unit 322 receives the touch of the storage confirmation button (S312). The request transmission unit 362 transmits a storage confirmation request to the server 400.
[0084]
　When the request receiving unit 474 of the server 400 receives the storage confirmation request, the screen data generation unit 444 refers to the storage table and generates a storage confirmation screen (S314). The screen data transmission unit 462 transmits the data on the storage confirmation screen to the user terminal 300a (S316).
[0085]
　When the screen data receiving unit 372 receives the data on the storage confirmation screen, the image output unit 334 displays the storage confirmation screen (S318). When the operation reception unit 322 receives the touch of the close button (S320), the storage confirmation screen is closed and the storage arrangement screen is redisplayed.
[0086]
　When the operation reception unit 322 receives the touch of the product menu button on the storage arrangement screen, the request transmission unit 362 transmits the product menu request to the server 400. (S322).
[0087]
　Move on to FIG. When the request receiving unit 474 of the server 400 receives the product menu request, the screen data generation unit 444 generates a product purchase screen based on the product list in the storage of the selected storage device 100 (S50). Then, the screen data transmission unit 462 transmits the generated product purchase screen data to the user terminal 300a (S52).
[0088]
　When the screen data receiving unit 372 of the user terminal 300 receives the data on the product purchase screen, the image output unit 334 displays the product purchase screen. When the user 122 selects the product 104 and touches the purchase button on the product purchase screen, the operation reception unit 322 accepts the touch of the purchase button and identifies the product ID and the storage device ID corresponding to the product 104 to be purchased ( S54). The request transmission unit 362 transmits a purchase request including the product ID and the storage device ID to the server 400. Since the product 104 is picked up after the pre-purchase, the purchase request also has the meaning of the product 104 pick-up request.
[0089]
　When the request receiving unit 474 of the server 400 receives the purchase request, the ticket generation unit 446 generates an electronic ticket for the user 122 who has purchased the product 104 (S56). One electronic ticket is issued to one user 122, and the same electronic ticket is not issued to different users 122. The electronic tickets repeatedly issued to one user 122 may be different or common each time. When the same electronic ticket is reused like a member authentication code, the electronic ticket itself may not be sent, but only an instruction for validating the electronic ticket held by the user terminal 300 may be sent. The ticket generation unit 446 adds a new electronic ticket record to the ticket table storage unit 486. Then, the ticket transmission unit 464 transmits the electronic ticket to the storage device 100a and the user terminal 300 (S58).
[0090]
　When the ticket receiving unit 272 of the storage device 100a receives the electronic ticket, the ticket list management unit 252 adds the received electronic ticket to the ticket list (S60). Further, when the ticket receiving unit 374 of the user terminal 300 receives the electronic ticket, the electronic ticket is stored in the ticket storage unit 382.
[0091]
　Following S58, the transaction management unit 448 of the server 400 adds a new record to the sales table as a sales process of the purchased product (S62). The product list management unit 442 changes the purchase status of the purchased product 104 from the product list in the storage of the storage device 100a to purchased (S64). The transaction management unit 448 may perform settlement processing together with sales processing. The payment process may be a conventional method such as prepaid or postpaid electronic payment or cash payment. Similarly, for the modification described later, settlement processing may be performed together with sales processing.
[0092]
　FIG. 21 is a sequence diagram when the user 122 takes out the product 104 purchased from the storage device 100a.
　When the operation reception unit 322 receives the operation of the QR code display instruction, the ticket output unit 332 converts the electronic ticket stored in the ticket storage unit 382 into a QR code figure and displays it on the display (S70). .. The user 122 holds the displayed QR code over the ticket reader 114 of the storage device 100a.
[0093]
　When the ticket reading unit 222 of the storage device 100a reads this QR code (electronic ticket), the ticket authentication unit 242 authenticates the read electronic ticket (S72). If it matches any of the electronic tickets in the ticket list, the authentication is successful. If it does not match any of the electronic tickets in the ticket list, authentication will fail. In this example, the authentication is successful because it matches the electronic ticket stored in S60 of FIG. After that, when the user 122 takes out the product 104 and closes the door 102, the take-out notification transmission unit 264 transmits the take-out notification to the server 400 (S74). The withdrawal notification includes the data of the product barcode 118 of the retrieved product 104 and the electronic ticket used.
[0094]
　When the take-out notification receiving unit 476 of the server 400 receives the take-out notification, the product verification unit 449 determines whether or not the product 104 taken out from the storage device 100 is valid (S75). Specifically, the product verification unit 449 refers to the product master table and specifies the product ID corresponding to the product barcode 118. This product ID corresponds to a product taken out from the storage device 100a. Next, the product verification unit 449 refers to the ticket table to specify the user ID corresponding to the electronic ticket, and further refers to the sales table to obtain the storage device ID and the user ID corresponding to the source of the withdrawal notification. Specify the product ID corresponding to the set. This product ID corresponds to a product purchased by the user 122 in the storage device 100a. If both product IDs match, it means that the user 122 has taken out the purchased product, and the verification is successful. On the other hand, if both product IDs do not match, it means that the product other than the product purchased by the user has been taken out, and the verification fails. If the verification fails, the approval / rejection notification transmission unit 466 sends a notification indicating the rejection to the storage device 100a, and returns to the process of S74.
[0095]
　On the other hand, if the verification is successful, the product list management unit 442 deletes the record of the product ID corresponding to the product taken out from the storage device 100a in the product list in the storage (S76). Further, the transaction management unit 448 changes the take-out status corresponding to the product ID corresponding to the product purchased by the user to the taken-out status in the sales table (S78). Then, the approval / rejection notification transmission unit 466 transmits a notification indicating approval to the storage device 100a (S80).
[0096]
　When the approval / rejection notification receiving unit 274 of the storage device 100a receives the notification indicating approval, the ticket list management unit 252 deletes the used electronic ticket from the ticket list (S82).
[0097]
　The transaction management unit 448 may perform the settlement process after confirming that the items have been taken out from the sales table.
[0098]
[Modification 1] In the
　modification 1, the product 104 is reserved from the user terminal 300. That is, the user 122 operates the user terminal 300 to check the product 104 stored in the storage device 100, and reserves the product 104 that he / she likes on the Web. Then, later, the user goes to the storage device 100, takes out the reserved product 104, and purchases the reserved product 104. This transaction mode is called "advance reservation method for products in storage". The electronic ticket in the first modification is issued to the user 122 who has reserved the product 104.
[0099]
　FIG. 22 is a schematic diagram showing a reservation purchase method for products in the storage.
　Similar to the case of FIG. 7, the clerk 120 stores the product 104 in the storage device 100a at 11:30 before the lunch break.
[0100]
　After that, at 11:40, the user 122 browses the product 104 in the storage device 100a on the user terminal 300a, selects the product 104 that he / she likes, and makes a reservation. At this point, the transaction has not been completed yet. When the user 122 reserves the product 104, the server 400 transmits an electronic ticket to the user terminal 300a. The user terminal 300 stores the received electronic ticket.
[0101]
　At 12:10 during the lunch break, the user 122 carries the user terminal 300a and moves to the installation location of the storage device 100a. The user 122 operates the user terminal 300a to display the QR code of the electronic ticket, and when the QR code is held over the ticket reader 114 of the storage device 100a, the lock of the door 102 is released. When the user 122 closes the door 102 of the storage device 100a, the door 102 is locked. When the user 122 takes out the unreserved product 104, a warning is issued, and the user 122 retakes the product 104. When the user 122 retrieves the product 104 reserved by himself / herself, the electronic ticket is deleted from the ticket list. The electronic ticket in this example shall be valid only once. At this point, the transaction is completed and the server 400 records sales.
[0102]
　The sequence when the clerk 120 stores the product 104 in the storage device 100a is as shown in FIG.
[0103]
　In the case of the first modification, the product ID in the storage and the reservation status of each product stored in the storage device 100 are stored in the product list. The reservation status indicates either unreserved or reserved. Items that have already been reserved will not be duplicated.
[0104]
　In the case of the first modification, the product reservation screen is used instead of the product purchase screen. On the product reservation screen, a reservation button is displayed instead of the purchase button. In S54 of FIG. 20, the operation reception unit 322 receives the touch of the reservation button and identifies the product ID corresponding to the product 104 to be reserved. Then, the request transmission unit 362 transmits a reservation request including the product ID and the storage device ID to the server 400. Since the product 104 is picked up after making a reservation, the reservation request also has the meaning of a pick-up request for the product 104.
[0105]
　In the case of the first modification, in S62 of FIG. 20, instead of the sales processing of the purchased product, the transaction management unit 448 of the server 400 adds new reservation information to the reservation table.
[0106]
　In the case of the first modification, the reservation table is used in addition to the sales table. The reservation table is a table for managing purchase reservations. The reservation table has a record for each purchase reservation. The record stores reservation information such as a reservation ID, a product ID, a user ID, a selling price, an electronic ticket ID, and a storage device ID. The reservation ID is assigned to each purchase reservation. The product ID identifies the reserved product 104. The user ID identifies the reserved user 122. The electronic ticket ID identifies an electronic ticket used for delivery of the reserved product. The storage device ID identifies the storage device 100 in which the reserved product is housed.
[0107]
　In the case of the first modification, in S75 of FIG. 21, when the take-out notification receiving unit 476 of the server 400 receives the take-out notification, the product verification unit 449 determines whether or not the product 104a taken out from the storage device 100 is valid. Judgment (S75). Specifically, the product verification unit 449 refers to the product master table and specifies the product ID corresponding to the product barcode 118. This product ID corresponds to a product taken out from the storage device 100. Next, the product verification unit 449 refers to the ticket table to specify the user ID corresponding to the electronic ticket, and further refers to the reservation table to obtain the storage device ID and the user ID corresponding to the source of the withdrawal notification. Specify the product ID corresponding to the set. This product ID corresponds to a product reserved by the user 122 in the storage device 100. If both product IDs match, it means that the user 122 has taken out the reserved product, and the verification is successful. On the other hand, if both product IDs do not match, it means that the product other than the product reserved by the user has been taken out, and the verification fails. If the verification fails, the approval / rejection notification transmission unit 466 sends a notification indicating the rejection to the storage device 100, and returns to the process of S74.
[0108]
　In the case of the first modification, after S78 in FIG. 21, the transaction management unit 448 of the server 400 adds a new record to the sales table as sales processing of the purchased product. In the case of the first modification, it is not necessary to manage the withdrawal status in the sales table. Further, the transaction management unit 448 deletes the reservation information in the reservation table.
[0109]
[Modification 2] In the
　modification 2, only the product 104 is browsed from the user terminal 300, and no purchase or reservation is made. That is, the user 122 operates the user terminal 300 to check whether the storage device 100 has a product 104 that he / she likes. When the user 122 wants to purchase any of the products 104 in the storage device 100, the user terminal 300 requests the issuance of an electronic ticket and obtains an electronic ticket for opening the storage device 100. In the case of the second modification, the person who actually took out the storage device 100 first purchases it on a first-come, first-served basis. Therefore, it may not be possible to purchase the product 104 viewed on the user terminal 300. This transaction mode is called "voluntary purchase method of products in storage".
[0110]
　FIG. 23 is a schematic diagram showing a method of voluntarily purchasing products in the storage.
　Similar to the case of FIG. 7, the clerk 120 stores the product 104 in the storage device 100a at 11:30 before the lunch break.
[0111]
　After that, when the user 122 browses the product 104 of the storage device 100a on the user terminal 300 and intends to purchase the product 104 at 12:00, he / she requests the issuance of an electronic ticket. The electronic ticket in the second modification is issued to the user 122 who has browsed the product 104 in the storage device 100a in advance. When the server 400 is requested to issue an electronic ticket, the server 400 transmits the electronic ticket to the user terminal 300. The user terminal 300 stores the received electronic ticket.
[0112]
　When the user 122 arrives at the installation location of the storage device 100a at 12:10, the user terminal 300 is operated to display the QR code of the electronic ticket, and the QR code is held over the ticket reader 114 of the storage device 100a. The user 122 opens the unlocked door 102 and freely takes out the desired product 104. All the products 104 housed in the storage device 100a can be purchased. When the user 122 closes the door 102 of the storage device 100a, the electronic ticket is deleted from the ticket list. The electronic ticket in this example shall be valid only once. However, the door 102 may be allowed to open and close more than once. When one of the doors 102 is taken out and the door 102 is closed, the transaction is completed and the server 400 records the sales.
[0113]
　The sequence when the clerk 120 stores the product 104 in the storage device 100a is as shown in FIG.
[0114]
　In the case of the second modification, the product ID of each product stored in the storage device 100 is managed in the product list in the storage, but the purchase status and the reservation status may not be managed.
[0115]
　In the case of the second modification, the product browsing screen is used instead of the product purchase screen. On the product browsing screen, one ticket issuance button is displayed. In S54 of FIG. 20, when the operation reception unit 322 receives the touch of the ticket issuing button, the request transmission unit 362 transmits the ticket request to the server 400. By acquiring the electronic ticket, the user 122 is permitted to use the storage device 100 containing the product 104.
[0116]
　In the case of the second modification, the sales processing of the product shown in S62 of FIG. 20 is not performed. In addition, the purchase status in the in-storage product list shown in S64 is not updated.
[0117]
　In the case of the second modification, in S75 of FIG. 21, the product verification unit 449 determines that the product 104 taken out from the storage device 100 is valid in any case, and the verification succeeds.
[0118]
　In the case of the second modification, after S78 in FIG. 21, the transaction management unit 448 of the server 400 adds a new record to the sales table as sales processing of the purchased product. In the case of the modification 2, it is not necessary to manage the withdrawal status in the sales table.
[0119]
[Modification 3] In the
　modification 3, the same electronic ticket is reused like a member authentication code as a modification of the voluntary purchase method of products in the storage. That is, the issuance of tickets is omitted. The user 122 may directly take out the product 104 from the storage device 100 without browsing the product 104 of the storage device 100.
[0120]
　In the case of the third modification, the server 400 sends the electronic ticket of the user 122 to the storage device 100 near the registered work location. The storage device 100 permanently holds the sent electronic ticket in the ticket list, and does not delete the electronic ticket shown in S82 of FIG. 21.
[0121]
　Further, instead of the electronic ticket, a QR code printed on a card or paper may be used as a ticket.
[0122]
[Modification 4] In the
　above-mentioned example, an example of purchasing the product 104 housed in the storage device 100 is shown. That is, the product 104 that is not in the storage device 100 cannot be purchased. On the other hand, in the modification 4, the product 104 is ordered from the store. Specifically, the user 122 selects a desired product 104 from the products 104 that can be purchased as inventory in the store, and has the user select the desired product 104 and deliver it to the predetermined storage device 100. In this way, a transaction mode in which the store inventory product 104 is purchased in advance and then delivered to the storage device 100 is referred to as a "store inventory product pre-purchase method".
[0123]
　As described above, the modified example 4 can be applied even when the lunch box is purchased at lunch time, but here, an example in which the product 104 is delivered to the storage device 100 near the home will be described.
[0124]
　FIG. 24 is a layout diagram of the storage device 100.
　The home of user 122 is on the 5th floor of the condominium P away from the office building A. As shown in the figure, storage devices 100pt to t are installed on the 1st to 5th floors of the condominium P.
[0125]
　There is a store next to Mansion P, which sells lunch boxes, sandwiches, salads and other delicatessen packs, and drinks. The storage devices 100p to t are managed by this store. That is, the product 104 housed in the storage device 100p to t is supplied by this store.
[0126]
　The store sells lunch boxes, sandwiches, salads and other delicatessen packs and drinks for residents of Condominium P at any time. The user 122 operates the user terminal 300 to check the product 104 in the store, and orders the product 104 that he / she likes on the Web. The store clerk 120 delivers the product 104 ordered by the user 122 to the storage device 100 used by the user 122. Residents can purchase the product 104 without having to stop by the store, which is convenient. In addition to the sales floor in the store, the product 104 can be sold in the storage devices 100pt to t, so it is expected that the sales of the store will increase. In addition, it can be expected that the unsold product 104 will be eliminated.
[0127]
　The store manages a plurality of storage devices 100 in the vicinity in addition to the storage devices 100pt to t, and the store clerk periodically performs delivery to these storage devices 100 collectively. For example, delivery is delivered every 30 minutes, such as 17:00, 17:30, 18:00, and 18:30. Since it is a problem if the ordered product 104 is sold out between the time the order is received and the time the product is delivered, the clerk reserves the product 104.
[0128]
　FIG. 25 is a schematic diagram showing a pre-purchase method for store inventory products.
　In this example, at 17:40 before leaving the office, the user 122 browses the product 104 in the store that manages the storage device 100p near the home on the user terminal 300a, selects and purchases the product 104 that he / she likes. At this point, the transaction is completed and the server 400 records sales. When the user 122 purchases the product 104, the server 400 transmits an electronic ticket to the user terminal 300a. The user terminal 300a stores the received electronic ticket. However, at this stage, the product 104 is still in the store.
[0129]
　Information on the purchased product 104 is transmitted to the store, and at 17:45, the clerk reserves the product 104.
[0130]
　At 18:00, the delivery time, the clerk heads for delivery of the reserved product 104. At 18:05, the clerk arrives at the 5th floor of the condominium P and stores the product 104 in the storage device 100p.
[0131]
　The user 122 who returned to the condominium P at 18:20 operates the user terminal 300 to display the QR code of the electronic ticket, and holds the QR code over the ticket reader 114 of the storage device 100p. Then, the unlocked door 102 is opened, and the product 104 purchased by himself / herself is taken out. Since the electronic ticket in this example is valid only once, it is deleted from the ticket list when the purchased product 104 is taken out. However, when using a type of electronic ticket that can be used repeatedly, it is not necessary to delete the electronic ticket from the ticket list. Similarly, when the QR code printed on the card or paper is used as a ticket that can be used repeatedly, the ticket data does not have to be deleted.
[0132]
　The store terminal 700 constantly manages the product 104, which is the stock of the store, as a list. This list is called the store inventory list. Further, it is assumed that the server 400 performs data synchronization with the store terminal 700 and holds the same store inventory list. The server 400 has a store inventory list storage unit (not shown) that stores the store inventory list in association with the store ID.
[0133]
　The goods 104 that are in stock and can be sold are disclosed on the site of the server 400. As a result, the user terminal 300 can access the site of the server 400 and browse the product 104 that can be delivered to the storage device 100p in real time. Hereinafter, the processing in this method will be described.
[0134]
　FIG. 26 is a functional block diagram of the store terminal 700.
　The store terminal 700 includes a user interface processing unit 710, a data processing unit 740, a communication unit 750, and a data storage unit 780. The user interface processing unit 710 accepts operations from the store manager via a touch panel or the like, and is in charge of user interface processing such as image display and voice output. The communication unit 750 is in charge of communication processing via the network. The data storage unit 780 stores various data. The data processing unit 740 executes various processes based on the data acquired by the communication unit 750 and the data stored in the data storage unit 780. The data processing unit 740 also functions as an interface for the user interface processing unit 710, the communication unit 750, and the data storage unit 780.
[0135]
　The user interface processing unit 710 includes an input unit 720 that accepts operation input by the store manager and an output unit 730 that presents information to the store manager.
[0136]
　The data processing unit 740 includes a storage list management unit 742, a transaction management unit 744, a product verification unit 746, and a settlement unit 748. The storage list management unit 742 manages the storage list. The transaction management unit 744 manages transactions such as sales and reservations of the product 104. The product verification unit 746 verifies the removed product. The settlement unit 748 performs settlement processing. The transaction management unit 744, the product verification unit 746, and the settlement unit 748 are used in the modification 9 described later.
[0137]
　The communication unit 750 includes a transmission unit 760 for transmitting data and a reception unit 770 for receiving data.
　The transmission unit 760 includes a storage list transmission unit 762 and a approval / disapproval notification transmission unit 764. The storage list transmission unit 762 transmits the storage list. The approval / disapproval notification transmission unit 764 transmits the approval / disapproval notification. The approval / rejection notification transmission unit 764 is used in the modification 8 described later.
[0138]
　The receiving unit 770 includes a storage instruction receiving unit 772, a reservation notification receiving unit 774, and a fetching notification receiving unit 776. The storage instruction receiving unit 772 receives the storage instruction. The reservation notification receiving unit 774 receives the reservation notification. The take-out notification receiving unit 776 receives the take-out notice. The reservation notification receiving unit 774 and the taking-out notification receiving unit 776 are used in the modified example 8 described later.
[0139]
　The data storage unit 780 includes a storage list storage unit 782, a reservation table storage unit 784, and a sales table storage unit 786. The storage list storage unit 782 stores the storage list. The storage list has a record for each product 104 to be stored. The product ID and the storage device ID are stored in the record. The product ID identifies the product to be delivered. The storage device ID identifies the storage device at the delivery destination.
[0140]
　The reservation table storage unit 784 stores the reservation table. The sales table storage unit 786 stores the sales table. The reservation table storage unit 784 and the sales table storage unit 786 are used in the modified example 8 described later.
[0141]
　FIG. 27 is a sequence diagram when the user 122 accesses the site of the server 400 from the user terminal 300a and purchases the product 104 in the store.
　In this example, it is assumed that the storage device 100p near the home registered in advance by the user 122 is automatically selected.
[0142]
　The screen data generation unit 444 of the server 400 reads the management store ID corresponding to the storage device 100p from the storage table, and generates a product purchase screen based on the store inventory list specified by the management store ID (S90). Then, the screen data transmission unit 462 transmits the generated product purchase screen data to the user terminal 300a (S92).
[0143]
　The image output unit 334 of the user terminal 300a displays a product purchase screen. When the user 122 selects the product 104 on the product purchase screen and touches the purchase button, the operation reception unit 322 identifies the product ID corresponding to the product 104 to be purchased (S94). The request transmission unit 362 transmits a purchase request including this product ID to the server 400.
[0144]
　When the request receiving unit 474 of the server 400 receives the purchase request, the transaction management unit 448 of the server 400 adds a new record to the sales table as a sales process of the purchased product (S96). Then, the storage instruction transmission unit 468 transmits the storage instruction of the purchased product to the store terminal 700 (S98). The storage instruction includes a product ID that identifies the product to be delivered and a storage device ID that identifies the storage device 100p (storage device near the home) of the delivery destination.
[0145]
　When the storage instruction receiving unit 772 of the store terminal 700 receives the storage instruction, the product ID and the storage device ID are registered in the storage list (S100).
[0146]
　The ticket generation unit 446 generates an electronic ticket for the user 122 who has purchased the product 104 (S102). Then, the screen data transmission unit 462 transmits the electronic ticket to the storage device 100p and the user terminal 300a (S104).
[0147]
　When the ticket receiving unit 272 of the storage device 100p receives the electronic ticket, the ticket list management unit 252 adds the received electronic ticket to the ticket list. Further, when the ticket receiving unit 374 of the user terminal 300 receives the electronic ticket, the electronic ticket is stored in the ticket storage unit 382.
[0148]
　When the receiving unit 770 of the store terminal 700 receives the request for the storage list, the storage list transmission unit 762 transmits the storage list to the store clerk terminal 600. At this time, the storage list transmission unit 762 converts the product ID included in the storage list into the product name, and converts the storage device ID into the storage device name. The store terminal 700 has a storage table storage unit and a product master table storage unit similar to the server 400.
[0149]
　When the storage list receiving unit 672 of the clerk terminal 600 receives the storage list, the storage list storage unit 684 stores the storage list, and the storage list output unit 634 displays the storage list. The storage list requesting unit 662 of the store clerk terminal 600 may request the storage list by the operation of the store clerk.
[0150]
　The sequence when the clerk 120 stores the product 104 in the storage device 100p is the same as in FIG.
[0151]
　The sequence when the user 122 takes out the product 104 purchased from the storage device 100p is the same as in the case of FIG. 21.
[0152]
[Modification 5] The
　product 104 to be delivered in Modification 4 may be reserved without being purchased on the Web. This transaction mode is called "pre-order purchase method for store inventory products".
[0153]
　FIG. 28 is a schematic diagram showing a reservation purchase method for store inventory products.
　At 17:40, user 122 reserves product 104. At this point, no sales are recorded. The work of the clerk 120 at 17:45 and 18:05 is the same as in the case of FIG. 25. At 18:20, when the user 122 takes out the product 104, the sales are recorded.
[0154]
　In the modified example 5, the product reservation screen is used instead of the product purchase screen of the modified example 4. The reserved product 104 is set aside and delivered in the same manner as the purchased product of the modified example 4.
[0155]
　The processing related to the product list in storage, the reservation table, and the sales table is the same as in the case of the reservation purchase method of the products in storage.
[0156]
[Modification 6] In each of the
　above examples, it is assumed that the storage device 100 is installed outside the store, but the storage device 100e may be installed inside the store. In this example, we support the sale of hot snacks at the cash register installation site (hereinafter abbreviated as "cash register"). Hot snacks are light meals and delicacies that are eaten warm, such as french fries, croquettes, and fried chicken.
[0157]
　It is troublesome for the cashier 120 to take the hot snack out of the case, pack it in a bag, and hand it to the user 122, and if the customers are in a line, hesitate to buy the hot snack from the customer behind. There was a problem that it was difficult to do. In the sixth modification, the hot snack is taken out by the user 122, and the work of the cashier is reduced. The faster the interaction near the cashier, the easier it will be for customers who tend to be reluctant to buy hot snacks.
[0158]
　The storage device 100e accommodates hot snacks as a commercial product. Hot snacks are packed in a bag or container in advance, and the product bar code attached to the bag or container is recognized to detect the product. Alternatively, the installation range may be set for each type of hot snack, the number of products in the range may be detected, and the type and quantity of the products taken out may be specified.
[0159]
　In the modification 6, the user terminal 300 is not used. A paper ticket printed with a QR code is issued at the cash register 800, and the use of the storage device 100e is permitted by this paper ticket. This transaction form is called a "paper ticket advance payment method".
[0160]
　FIG. 29 is a schematic diagram showing a prepaid payment method using a paper ticket.
　At 15:00, user 122 tells the cashier clerk 120 the type and quantity of hot snacks he wants to buy and pays the fee. At that time, a paper ticket is output from the cash register 800. A unique QR code is printed on the paper ticket. The paper ticket is handed to the user 122.
[0161]
　At 15:02, the user 122 causes the ticket reader 114 of the storage device 100e to read the paper ticket and takes out the purchased hot snack. At this time, if the taken out hot snack does not match the purchased hot snack, a warning is issued. This prevents the product 104 from being mistakenly picked up.
[0162]
　FIG. 30 is a functional block diagram of the cash register 800.
　The cash register 800 includes a user interface processing unit 810, a data processing unit 840, a communication unit 850, and a data storage unit 880. The user interface processing unit 810 accepts operations from the person in charge of the register via a touch panel or the like, and is in charge of user interface processing such as image display and audio output. The communication unit 850 is in charge of communication processing via the network. The data storage unit 880 stores various data. The data processing unit 840 executes various processes based on the data acquired by the communication unit 850 and the data stored in the data storage unit 880. The data processing unit 840 also functions as an interface for the user interface processing unit 810, the communication unit 850, and the data storage unit 880.
[0163]
　The user interface processing unit 810 includes an input unit 820 that receives operation input by the cashier clerk 120 and an output unit 830 that presents information to the cashier clerk 120.
　The input unit 820 includes a product input unit 822 and a ticket reading unit 824. The product input unit 822 inputs the type and quantity of the purchased product (hot snack). The ticket reading unit 824 reads paper tickets and electronic tickets. The ticket reading unit 824 is used in the modification 7 described later. The output unit 830 includes a ticket output unit 832 that outputs a paper ticket.
[0164]
　The data processing unit 840 includes a settlement unit 842, a ticket generation unit 844, a ticket management unit 846, and a product verification unit 848. The settlement unit 842 performs settlement processing. The payment process may be conventional cash payment or electronic payment. The ticket generation unit 844 generates paper ticket data. The ticket management unit 846 manages the ticket table. The product verification unit 848 verifies the product to be purchased.
[0165]
　The communication unit 850 includes a transmission unit 860 for transmitting data and a reception unit 870 for receiving data. The transmission unit 860 includes a ticket transmission unit 862 and a approval / disapproval notification transmission unit 864. The ticket transmission unit 862 transmits an electronic ticket. The approval / rejection notification transmission unit 864 transmits the approval / rejection notification. The receiving unit 870 includes a take-out notification receiving unit 872 that receives the take-out notification.
[0166]
　The data storage unit 880 includes a ticket table storage unit 882 that stores the ticket table. The ticket table in the sixth modification has a record for each paper ticket issued by the server 400. The record stores the type and quantity of purchased products in association with the data of the paper ticket.
[0167]
　FIG. 31 is a sequence diagram relating to the exchange at the cash register.
　The product input unit 822 of the cash register 800 inputs the type and quantity of the purchased product (hot snack) (S110). The settlement unit 842 performs settlement processing in the same manner as in the past (S112).
[0168]
　The ticket generation unit 844 determines the data of the paper ticket (S114). Since it is sufficient that the data converted into the QR code is unique, it may be a simple serial number. The ticket management unit 846 registers the data of the paper ticket and the type and quantity of the purchased product in the ticket table in association with each other (S116). The ticket transmission unit 862 transmits the data of the paper ticket to the storage device 100e (S118). Then, the ticket output unit 832 prints and outputs a paper ticket (S120). The paper ticket is handed to the user by the cashier clerk 120.
[0169]
　When the ticket receiving unit 272 of the storage device 100e receives the paper ticket data, the ticket list management unit 252 registers the paper ticket data in the ticket list (S122).
[0170]
　FIG. 32 is a sequence diagram relating to the removal of the product 104.
　When the ticket reading unit 222 reads the paper ticket (S130), the ticket authentication unit 242 authenticates the paper ticket (S132). If the read paper ticket data does not match the paper ticket data stored in the ticket list, authentication fails and the lock is not released. On the other hand, if it matches the data of the paper ticket stored in the ticket list, the authentication is successful and the lock is released.
[0171]
　When the user takes out the product 104 (hot snack) and closes the door 102, the take-out notification transmission unit 264 transmits the take-out notification to the server 400 (S134). The withdrawal notice includes the type and quantity of the goods 104 taken out and the data of the used paper ticket.
[0172]
　When the take-out notification receiving unit 872 of the cash register 800 receives the take-out notification, the product verification unit 848 verifies the purchased product (S136). Specifically, the product verification unit 848 reads from the ticket table the type and quantity of the purchased product corresponding to the paper ticket data included in the withdrawal notification. Then, if the type and quantity of the extracted goods 104 match the type and quantity of the purchased goods, the verification is successful. If the verification is successful, the approval / disapproval notification transmission unit 864 transmits a notification indicating approval to the storage device 100e (S138).
[0173]
　When the approval / rejection notification receiving unit 274 of the storage device 100e receives the notification indicating approval, the ticket list management unit 252 deletes the used paper ticket data from the ticket list (S140).
[0174]
　If the type and quantity of the taken out product 104 do not match the type and quantity of the purchased product and the product verification unit 848 of the cash register 800 determines that the verification has failed, the approval / disapproval notification transmission unit 864 indicates a denial. The notification is transmitted to the storage device 100e. Then, the warning output unit 232 of the storage device 100e outputs a warning.
[0175]
[Modification 7] In the
　modification 6, the payment is completed before the product 104 (hot snack) is taken out, but the payment may be performed after the product 104 is taken out. This transaction form is called "post-payment method using paper tickets".
[0176]
　FIG. 33 is a schematic diagram showing a post-payment method using a paper ticket.
　At 15:00, user 122 offers the cashier clerk 120 to purchase a hot snack. At this time, it is not necessary to tell the type and quantity of hot snacks. That is, the user 122 may freely select the hot snack he / she wants to buy. At this time, a paper ticket is output from the cash register 800. A unique QR code is printed on the paper ticket. The paper ticket is handed to the user 122.
[0177]
　At 15:02, the user 122 causes the ticket reader 114 of the storage device 100e to read the paper ticket and takes out the hot snack to be bought. When the user 122 closes the door 102, the type and quantity of the hot snacks taken out are transmitted from the storage device 100e to the cash register 800.
[0178]
　At 15:04, the user 122 who finished taking out the hot snack returns the paper ticket to the cashier clerk 120. Then, payment is made according to the type and quantity of the hot snacks taken out.
[0179]
　Also in the case of the modification 7, the ticket table has a record for each paper ticket issued by the server 400. However, in the record, the payment status is stored in addition to the type and quantity of the purchased product in association with the data of the paper ticket. The payment status indicates either unsettled or settled.
[0180]
　FIG. 34 is a sequence diagram relating to the issuance of paper tickets.
　The ticket generation unit 844 determines the data of the paper ticket in the same manner as in the modification 6 (S150). The ticket management unit 846 registers the data of the paper ticket in the ticket table (S152). At this stage, the type and quantity of hot snacks are undecided. The ticket transmission unit 862 transmits the data of the paper ticket to the storage device 100e (S154). Then, the ticket output unit 832 prints and outputs a paper ticket (S156). The paper ticket is handed to the user by the cashier clerk 120.
[0181]
　When the ticket receiving unit 272 of the storage device 100e receives the paper ticket data, the ticket list management unit 252 registers the paper ticket data in the ticket list (S158).
[0182]
　FIG. 35 is a sequence diagram relating to the removal and settlement of the product 104.
　When the ticket reading unit 222 reads the paper ticket (S160), the ticket authentication unit 242 authenticates the paper ticket (S162).
[0183]
　If the authentication is successful, the lock will be released. When the user takes out the product 104 (hot snack) and closes the door 102, the take-out notification transmission unit 264 transmits the take-out notification to the server 400 (S164). The withdrawal notice includes the type and quantity of the goods 104 taken out and the data of the used paper ticket.
[0184]
　When the take-out notification receiving unit 872 of the cash register 800 receives the take-out notification, the ticket management unit 846 uses the type and quantity of the taken-out product 104 as the type and quantity of the purchased product corresponding to the data of the used paper ticket. Register in the ticket table (S166). At this point, the settlement status indicates unsettled. Then, the approval / rejection notification transmission unit 864 transmits a notification indicating approval to the storage device 100e (S168).
[0185]
　When the approval / rejection notification receiving unit 274 of the storage device 100e receives the notification indicating approval, the ticket list management unit 252 deletes the used paper ticket data from the ticket list (S170).
[0186]
　When the user hands the paper ticket to the cashier clerk 120, the ticket reading unit 824 of the cash register 800 is made to read the paper ticket (S172). Then, the settlement unit 842 refers to the ticket table and specifies the type and quantity of the purchased product corresponding to the read paper ticket (S174). The settlement unit 842 performs settlement processing according to the type and quantity of purchased products (S176). When the payment process is completed, the payment status is changed to settled (S178).
[0187]
[Modification 8]
　Regarding the purchase of store products such as hot snacks, electronic tickets may be used instead of paper tickets. In the modification 8, the product 104 (hot snack) is reserved from the user terminal 300. This transaction form is called "pre-order purchase method for store products".
[0188]
　FIG. 36 is a schematic diagram showing a reservation purchase method for store products.
　At 14:30 before going to the store, the user 122 browses the product (hot snack) in the store on the user terminal 300a, determines the type and quantity of the product (hot snack), and makes a reservation. When the user 122 reserves the product 104, the server 400 transmits an electronic ticket to the user terminal 300a. The user terminal 300a stores the received electronic ticket.
[0189]
　At 14:35, information on the reserved product is transmitted to the store, and the clerk confirms the preparation status of the product 104, and if it is not ready, cooks it and replenishes the product (hot snack).
[0190]
　When the user 122 arrives at the store, the user 122 goes straight to the storage device 100e without stopping at the cash register. Then, the electronic ticket is presented and the reserved product is taken out from the storage device 100e. If the taken out product is valid, the sales will be recorded as it is. As for payment, conventional methods such as prepaid or postpaid electronic payment and cash payment may be used.
[0191]
　FIG. 37 is a sequence diagram when the user 122 accesses the site of the server 400 from the user terminal 300a and reserves the product 104 (hot snack) in the store.
[0192]
　The screen data generation unit 444 of the server 400 generates a product purchase screen based on the store inventory list specified by the store ID (S180). Then, the screen data transmission unit 462 transmits the generated product purchase screen data to the user terminal 300a (S182).
[0193]
　The image output unit 334 displays a product purchase screen. On the product purchase screen, the products 104 (hot snacks) that can be purchased are displayed. When the user 122 selects the product 104 on the product purchase screen and touches the reservation button, the operation reception unit 322 identifies the product ID corresponding to the product 104 to be reserved (S184). The request transmission unit 362 transmits a reservation request including the product ID and the storage device ID to the server 400.
[0194]
　When the request receiving unit 474 of the server 400 receives the reservation request, the ticket generation unit 446 generates an electronic ticket for the user 122 who has reserved the product 104 (S186). Then, the ticket transmission unit 464 transmits the electronic ticket to the storage device 100e and the user terminal 300a (S188).
[0195]
　When the ticket receiving unit 272 of the storage device 100e receives the electronic ticket, the ticket list management unit 252 adds the received electronic ticket to the ticket list. Further, when the ticket receiving unit 374 of the user terminal 300a receives the electronic ticket, the electronic ticket is stored in the ticket storage unit 382.
[0196]
　After the process of S188, the reservation notification transmission unit 452 transmits the reservation notification to the store terminal 700 (S192). The booking notification includes the type and quantity of electronic tickets and reserved merchandise (hot snacks).
[0197]
　When the reservation notification receiving unit 774 of the store terminal 700 receives the reservation notification, the transaction management unit 744 registers the reservation information in the reservation table (S194). The reservation table has a record for each purchase reservation. The record stores reservation information such as a reservation ID, a product type and quantity, a user ID, a selling price, an electronic ticket ID, a storage device ID, and a withdrawal status.
[0198]
　FIG. 38 is a sequence diagram when the user 122 takes out the product 104 purchased from the storage device 100e.
　When the operation reception unit 322 of the user terminal 300a receives the operation of the QR code display instruction, the ticket output unit 332 converts the electronic ticket stored in the ticket storage unit 382 into a QR code figure and displays it on the display. (S200). The user 122 holds the displayed QR code over the ticket reader 114 of the storage device 100e.
[0199]
　When the ticket reading unit 222 of the storage device 100e reads this QR code (electronic ticket), the ticket authentication unit 242 authenticates the read electronic ticket (S202). When the authentication is successful and the user 122 takes out the product 104 and closes the door 102, the take-out notification transmission unit 264 transmits the take-out notification to the store terminal 700 (S204). The withdrawal notice includes the type and quantity of the goods 104 (hot snacks) taken out, and the electronic ticket used.
[0200]
　When the take-out notification receiving unit 776 of the store terminal 700 receives the take-out notification, the product verification unit 746 determines whether or not the type and quantity of the product 104 (hot snack) taken out from the storage device 100e are valid ( S208). Specifically, the product verification unit 746 refers to the ticket table to specify the user ID corresponding to the electronic ticket, and further refers to the reservation table to indicate the storage device ID and the user corresponding to the source of the withdrawal notification. Specify the type and quantity of products corresponding to the ID set. This product ID corresponds to the type and quantity of the product reserved by the user 122. If the product type and quantity match, it means that the user 122 has taken out the reserved product, and the verification is successful. On the other hand, if the product type and quantity do not match, it means that the reserved product has not been taken out correctly, and the verification fails. If the verification fails, the approval / rejection notification transmission unit 764 sends a notification indicating the rejection to the storage device 100e, and returns to the process of S204.
[0201]
　On the other hand, if the verification is successful, the approval / disapproval notification transmission unit 764 of the store terminal 700 transmits a notification indicating approval to the storage device 100e (S208).
[0202]
　When the approval / rejection notification receiving unit 274 of the storage device 100e receives the notification indicating approval, the ticket list management unit 252 deletes the used electronic ticket from the ticket list (S210).
[0203]
　Following the process of S208, the reservation notification receiving unit 774 of the store terminal 700 deletes the reservation information in the reservation table (S212). Then, the settlement unit 748 performs the settlement process (S214).
[0204]
[Modification 9]
　Instead of the reservation in Modification 8, advance purchase may be performed. This transaction form is called "pre-purchase method for store products".
[0205]
　FIG. 39 is a schematic diagram showing a pre-purchase method for store products.
　At 14:30, user 122 reserves product 104. At this point, no sales are recorded. The work at 14:35 is the same as in the case of FIG. 36. At 15:00, when the user 122 takes out the product 104, the sales are recorded.
[0206]
　In the case of the modification 8, instead of the process shown in S192 of FIG. 37, the purchase notification transmission unit (not shown) of the server 400 transmits the purchase notification to the store terminal 700 (S192). The purchase notice includes the type and quantity of the electronic ticket and the purchased item (hot snack).
[0207]
　In the case of the modification 8, when the purchase notification receiving unit (not shown) of the store terminal 700 receives the purchase notification instead of the processing shown in S194 of FIG. 37, the payment unit 748 of the store terminal 700 performs the payment processing. ..
[0208]
　In the case of the modification 8, the settlement process shown in S214 of FIG. 38 is not performed.
[0209]
[Modified example of performing ticket authentication on the server 400] In the
　embodiment and the above-mentioned modified example, an example of performing ticket authentication on the storage device 100 is shown. Specifically, the ticket reading unit 222 of the storage device 100 reads the electronic ticket (S10 in FIG. 4), and the ticket authentication unit 242 of the storage device 100 authenticates the electronic ticket (S12 in FIG. 4). In order to authenticate the ticket, the storage device 100 has a ticket list storage unit 282 (FIG. 3).
[0210]
　However, the server 400 may be modified to perform ticket authentication instead of the storage device 100. That is, the server 400 may manage the ticket list of each storage device 100 and centrally authenticate the electronic ticket.
[0211]
　In this modification, the ticket list storage unit 282 is omitted from the functional blocks of the computer 200 of the storage device 100 shown in FIG. Instead, the server 400 has a ticket list storage unit (not shown) that stores the ticket list corresponding to each storage device 100.
[0212]
　Changes to the operation process of the storage device 100 shown in FIG. 4 will be described.
　The ticket authentication (S12) shown in FIG. 4 is omitted, and instead, the transmission of the electronic ticket and the reception of the authentication result are added. Ticket erasure (S34) is also omitted.
[0213]
　In this modification, the server 400 has a ticket list management unit (not shown) for managing the ticket list, a ticket receiving unit (not shown) for receiving electronic tickets, a ticket authentication unit (not shown) for authenticating electronic tickets, and a ticket authentication unit (not shown). It has an authentication result transmission unit (not shown) that transmits the authentication result of the electronic ticket. Further, the storage device 100 has a ticket transmission unit (not shown) for transmitting an electronic ticket and an authentication result receiving unit (not shown) for receiving the authentication result of the electronic ticket.
[0214]
　Hereinafter, a process of adding an electronic ticket to the ticket list of the server 400, a process of performing ticket authentication on the server 400, and a process of deleting the electronic ticket of the ticket list of the server 400 will be described in order. Here, the changes will be described based on the embodiment, but the server 400 may perform ticket authentication in the above-mentioned modifications 1 to 5 and the like.
[0215]
　A change regarding the addition of an electronic ticket will be described with reference to a sequence (FIG. 20) when the user terminal 300a is operated to make a pre-purchase.
　The transmission of the electronic ticket (S58) in the server 400 is omitted. Further, the list registration (S60) of the electronic ticket in the storage device 100a is also omitted. Instead, after the electronic ticket generation (S56), the ticket list management unit (not shown) of the server 400 registers the electronic ticket list. That is, the ticket list management unit adds the generated electronic ticket to the ticket list corresponding to the storage device 100a. The same applies to other modified examples such as the advance reservation method.
[0216]
　The changes related to ticket authentication will be described with reference to the sequence (FIG. 21) when the pre-purchased product 104 is taken out from the storage device 100a.
　The electronic ticket authentication (S72) in the storage device 100a is omitted. Instead, after the storage device 100a receives the electronic ticket from the user terminal 300a, the ticket transmission unit (not shown) of the storage device 100a transmits the electronic ticket to the server 400. When the ticket receiving unit (not shown) of the server 400 receives the electronic ticket, the ticket authentication unit (not shown) of the server 400 authenticates the received electronic ticket. If any of the electronic tickets included in the ticket list corresponding to the storage device 100a, which is the source of the electronic ticket, matches the received electronic ticket, the authentication is successful. On the other hand, if the received electronic tickets do not match any of the electronic tickets included in the ticket list corresponding to the storage device 100a, the authentication fails. The authentication result transmission unit (not shown) of the server 400 transmits the authentication result to the storage device 100a (the source of the electronic ticket). The authentication result receiving unit (not shown) of the storage device 100a receives the authentication result, and the storage device 100a performs the processing after S74 based on the received authentication result. The same applies to other modified examples such as the advance reservation method.
[0217]
　Subsequently, with reference to FIG. 21, changes regarding electronic ticket deletion will be described.
　The deletion of the list of electronic tickets (S82) in the storage device 100a is omitted. Then, after the approval notification is transmitted from the server 400 to the storage device 100a, the ticket list management unit 252 of the server 400 transfers the electronic ticket for which the authentication is successful from the ticket list corresponding to the storage device 100a (the sender of the electronic ticket). delete. The same applies to other modified examples such as the advance reservation method.
[0218]
[Composite method 1] As the
　composite method 1, the "pre-purchase method of products in storage" (embodiment) and the "arbitrary purchase method of products in storage" (modification 2 or modification 3) may be realized together. ..
　When the user 122 takes out the product 104 that has been pre-purchased by himself / herself, it is processed by the "pre-purchase method of the product in the storage". When the user 122 takes out the product 104 that no one has purchased in advance, it is processed by the "arbitrary purchase method of the product in the storage". Further, when the user 122 takes out the product 104 purchased in advance by another person, a warning message or a warning sound is emitted.
[0219]
[Composite method 2] Even if the "
　composite method 2" is realized by combining the "advance reservation method for products in storage" (modification example 1) and the "arbitrary purchase method for products in storage" (modification example 2 or modification 3). good.
　When the user 122 takes out the product 104 that has been pre-booked by himself / herself, it is processed by the "pre-booking method for the products in the storage". When the user 122 takes out the product 104 that no one has reserved in advance, it is processed by the "arbitrary purchase method of the product in the storage". Further, when the user 122 takes out the product 104 reserved in advance by another person, a warning message or a warning sound is emitted.
[0220]
[Composite method 3] As the
　composite method 3, "advance purchase method of products in storage" (embodiment), "advance reservation method of products in storage" (modification example 1), and "arbitrary purchase method of products in storage" (transformation). Example 2 or modification 3) may also be realized.
　When the user 122 takes out the product 104 that has been pre-purchased by himself / herself, it is processed by the "pre-purchase method of the product in the storage". When the user 122 takes out the product 104 that has been pre-booked by himself / herself, it is processed by the "pre-booking method for the products in the storage". When the user 122 takes out the product 104 that no one has pre-purchased or pre-booked, it is processed by the "arbitrary purchase method of the product in the storage". Further, when the user 122 takes out the product 104 that has been pre-purchased or pre-booked by another person, a warning message or a warning sound is emitted.
[0221]
[Storage Body] The
　storage device 100 described in the embodiment and the above-described modification is an example of a storage body that accommodates an article such as a product 104 and operates to deliver the article to a user. The storage body may be a device such as the storage device 100, an indoor area such as a room, or a facility such as a store. Hereinafter, an example of the storage body will be described.
[0222]
[Multi-door type storage device 100] Although
　FIG. 1 shows a form in which there is only one door 102, the storage device 100 may have a plurality of doors 102. A storage space having a shelf and a camera 110 may be formed in the back of each door 102 as in FIG. 1. The boundaries of the accommodation space may be separated by a wall material having ventilation holes so that the temperature and humidity of all the accommodation spaces can be adjusted by one temperature control device 112.
[0223]
　The ticket reader 114, the open / close sensor 106, and the lock mechanism 108 are provided for each door 102, but the computer 200 and the speaker 116 may be one each.
[0224]
[Storage room] The
　storage body may be a room having a function of storing the product 104 and delivering the product 122 to the user 122. This room is called a "storage room". The storage room can serve as an alternative to, for example, a shop in a school, a retail store in a train station, or a vending machine corner in a building.
[0225]
　The point that the user 122 browses the product 104 in the storage room, makes a pre-purchase, a pre-reservation, and the like by using the user terminal 300 is the same as in the case of the embodiment and the above-described modification. .. Instead of the storage device 100, the user 122 can take out a pre-purchased or pre-booked product 104, an arbitrarily selected product 104, or the like from the storage room. However, it is assumed that each person enters the room and takes out the product 104.
[0226]
　Inside the storage room, a plurality of shelves for placing the product 104 are provided. The product 104 placed on the shelf is photographed by a camera installed above the shelf, as in the case of the storage device 100. The space in the storage room is adjusted by the temperature adjusting device 112, and the computer 200 controls the operation as in the case of the storage device 100. The computer 200 has an automatic door control unit (not shown) as a functional module.
[0227]
　The operation of the storage room will be described with reference to FIG. 4, which shows the operation of the storage device 100.
　It is assumed that operations such as advance purchase and advance reservation have been completed as in the case of the embodiment and the above-mentioned modification. The user 122 who comes to the storage room holds the QR code of the electronic ticket over the ticket reader 114 installed outside the automatic door. As a result, the ticket reading unit 222 detects the reading of the electronic ticket by the ticket reader 114 (S10), and the ticket authentication unit 242 authenticates the read ticket (S12).
[0228]
　Similar to the case of the storage device 100, the internal product detection (S14) shown in FIG. 4 is performed. Then, instead of unlocking (S16), the automatic door control unit (not shown) instructs the automatic door to open. When the user 104 enters the room, the automatic door closes as a normal operation. At this time, instead of the door open detection (S18), the entry / exit sensor (not shown) detects the entry of the user 122, and the automatic door control unit (not shown) instructs the automatic door to lock the door.
[0229]
　In the storage room, the user 104 finds out the pre-purchased or pre-booked product 104 and picks it up. In the case of the voluntary purchase method, the user 104 selects the desired product 104 and picks it up. Then, the user 104 goes to the inside of the automatic door as it is.
[0230]
　When the entrance / exit sensor detects a person (user 104) inside the automatic door instead of the door close detection (S20), the product detection unit 244 detects the product 104 housed inside the storage room at that time. do. Then, the product detection unit 244 calculates the difference from the product 104 detected in S14.
[0231]
　As in the case of the storage device 100, the take-out notification transmission unit 264 transmits a take-out notification to the server 400 (S24), and the acceptance / rejection notification receiving unit 274 receives the acceptance / rejection notification from the server 400 (S26). When the approval / rejection notification indicates rejection, the warning output unit 232 outputs a warning (S30).
[0232]
　On the other hand, when the received approval / disapproval notification indicates approval, the automatic door control unit (not shown) instructs the automatic door to unlock and open the door instead of locking (S32). When the user 104 leaves the room, the automatic door closes as a normal operation. At this time, when the entry / exit sensor (not shown) detects the exit of the person (user 104), the ticket is erased as in the case of the storage device 100 (S34).
[0233]
[Unmanned store (product check machine method)] The
　unmanned store has a function of storing the product 104 and delivering the product 104 to the user 122, and can be regarded as a kind of storage body. The point that the user 122 browses the product 104 in the unmanned store, makes a pre-purchase, a pre-reservation, and the like by using the user terminal 300 is the same as in the case of the embodiment and the above-mentioned modification. .. However, the user 122 can take out the pre-purchased or pre-booked product 104, the arbitrarily selected product 104, or the like from the unmanned store instead of the storage device 100.
[0234]
　The unmanned store of the product check machine system is equipped with a product check machine that checks the product 104 brought out by the user 122. The product check machine is installed near the doorway and is used to read the barcode of the product 104 that the user 122 finally wants to bring out and determine whether or not the product 104 to be taken out is appropriate. The product check machine may also serve as a self-registration or a semi-self-registration.
[0235]
　The movement of the user 122 and the operation of the product check machine in the unmanned store of the product check machine method will be described.
　It is assumed that operations such as advance purchase and advance reservation have been completed as in the case of the embodiment and the above-mentioned modification. When a user 122 who comes to pick up a pre-purchased or pre-booked product 104 or an arbitrary product 104 enters an unmanned store, the store entry check is not performed. The user 122 who freely enters the store takes the pre-purchased or pre-booked product 104 or the arbitrarily selected product 104 to the product check machine and operates the product check machine by himself / herself.
[0236]
　Like the storage device 100, the product checker includes a ticket reader 114, a speaker 116, and a computer 200. Since the product checker does not have a function of storing products, it does not have a door 102, a camera 110, an open / close sensor 106, a lock mechanism 108, and a temperature control device 112. The product checker is equipped with a barcode reader (not shown) in order to detect the product 104 to be taken out. The barcode reader reads the product barcode 118 attached to the product 104 to be taken out and identifies the product ID. A graphic code such as a QR code may be read instead of the product barcode 118. Further, a tag reader that receives the product ID transmitted from the IC tag attached to the product 104 may be used. The ticket reader 114 may also serve as a barcode reader, or a barcode reader may be provided separately from the ticket reader 114. The barcode reader may be built in the housing of the product checker, or may be a hand-held one connected by a cord. The product checker also includes a display (eg, a liquid crystal display). Further, the computer 200 of the product checker has an operation guide display processing unit (not shown) as a functional module that performs a process of displaying a message that guides the user how to operate.
[0237]
　The operation of the product checker will be described with reference to FIG. 4, which shows the operation of the storage device 100.
　The operation guide display processing unit (not shown) of the computer 200 of the product checker displays, for example, a message "Please hold the electronic ticket of the smartphone over the ticket reader" on the display in the standby state.
[0238]
　The user 122 who comes to the product check machine with the product 104 operates the user terminal 300 to display the QR code of the electronic ticket, and holds the QR code over the ticket reader 114 of the storage device 100. As a result, the ticket reading unit 222 detects the reading of the electronic ticket by the ticket reader 114 (S10), and the ticket authentication unit 242 authenticates the read ticket (S12). The method of ticket authentication is the same as that of the storage device 100. As described above, the server 400 may perform ticket authentication. If authentication fails, no further processing is performed. If the authentication fails, the warning output unit 232 may output a warning message or a warning sound. If the authentication is successful, the operation guide display processing unit (not shown) may say, for example, "Hold the barcode of the product over the barcode reader." Or "Read the barcode of the product with the barcode reader." A message such as "." Is displayed on the display.
[0239]
　The product checker does not perform operations corresponding to the internal product detection (S14), unlock (S16), door open detection (S18), and door close detection (S20) shown in FIG.
[0240]
　In the product check machine, the product to be taken out is detected in S22 by a method different from that in the case of the storage device 100. When the user 122 holds the product barcode 118 of the product 104 to be taken out over the barcode reader, the product detection unit 244 detects the product barcode 118 read by the barcode reader and identifies the product ID.
[0241]
　Similar to the case of the storage device 100, the take-out notification transmission unit 264 of the computer 200 of the storage device 100 transmits the take-out notification to the server 400 (S24). The withdrawal notification includes the data of the product barcode 118 of the product 104 to be taken out and the electronic ticket used.
[0242]
　Similar to the case of the storage device 100, the approval / rejection notification receiving unit 274 of the computer 200 of the storage device 100 receives the approval / rejection notification from the server 400 (S26). When the approval / rejection notification indicates rejection, the warning output unit 232 outputs a warning (S30). If the product 104 to be taken out is not appropriate, for example, a warning message or a warning sound such as "This product cannot be taken out. Please return it to the shelf." Is emitted.
[0243]
　On the other hand, when the received approval / disapproval notification indicates approval, the ticket is deleted as in the case of the storage device 100 (S34). In the product check machine, there is no operation corresponding to the unlocking (S32) shown in FIG.
[0244]
[Unmanned store (automatic check method)]
　Instead of placing a product check machine in the unmanned store, the image taken in the unmanned store may be analyzed and the user 122 and the product 104 may be linked. By doing so, the product 104 can be automatically checked.
[0245]
　An automatic check-type unmanned store is equipped with a large number of surveillance cameras that take pictures of the inside of the store from various angles. Each surveillance camera provides the captured moving image to the computer 200. Further, at the entrance of the unmanned store, a gate equipped with a ticket reader 114 is provided. The computer 200 has a tracking processing unit (not shown), an action detection unit (not shown), and a product specifying unit (not shown).
[0246]
　The movement of the user 122 and the operation of the computer 200 in the unmanned store of the automatic check method will be described with reference to FIG. 4, which shows the operation of the storage device 100.
　It is assumed that operations such as advance purchase and advance reservation have been completed as in the case of the embodiment and the above-mentioned modification. The user 122 who came to the unmanned store of the automatic check method first operates the user terminal 300 to display the QR code of the electronic ticket, and holds the QR code over the ticket reader 114 of the gate. As a result, the ticket reading unit 222 detects the reading of the electronic ticket by the ticket reader 114 (S10), and the ticket authentication unit 242 authenticates the read ticket (S12). The method of ticket authentication is the same as that of the storage device 100. As described above, the server 400 may perform ticket authentication. If authentication fails, no further processing is performed. If the authentication fails, the warning output unit 232 may output a warning message or a warning sound such as "This ticket cannot be used."
[0247]
　The internal product detection (S14) and door open detection (S18) shown in FIG. 4 are omitted. Instead of unlocking (S16), the gate opens. As a result, the user 122 can enter the store. Further, at this point, the user ID of the user 122 who has entered the store is specified in the computer 200.
[0248]
　The tracking processing unit tracks the user 122 based on the moving image taken by the surveillance camera installed at the entrance, and identifies the position of the user 122 in the store at any time. When the user 122 moves to the shooting range of another surveillance camera, the tracking of the user 122 is continued based on the moving image shot by the surveillance camera, and the position in the store of the user 122 is continuously specified. This process is continued until the user 122 goes out of the store.
[0249]
　The action detection unit detects that the action of taking out the product has been performed from the behavior of the user 122 shown in the moving image. The action detection unit (not shown) determines, for example, that if the hand of the user 122 extends to the shelf and then something is held in the hand, the action of taking out the product has been performed.
[0250]
　When the action of taking out the product is performed, the product specifying unit performs a process of specifying the product taken out by the user 122. For example, the product specifying unit determines which product 104 is taken out by matching the product shown in the hand of the user 122 in the moving image with the sample image of each product 104 in the store. Alternatively, the product identification unit may determine that the product 104 has been taken out because the product 104 at the position where the user 122 reached out has disappeared from the moving image. Then, the extracted product ID is stored as a product list corresponding to the user ID.
[0251]
　In this way, the user 104 finds out the pre-purchased or pre-booked product 104 and picks it up. In the case of the voluntary purchase method, the user 104 selects the desired product 104 and picks it up. The product ID of each product 104 is also added to the product list. Then, the user 104 goes out of the unmanned store. You do not have to go through the gate when you move out. At this time, the tracking processing unit detects the exit of the user 104 instead of the door close detection (S20) shown in FIG.
[0252]
　As in the case of the storage device 100, the take-out notification transmission unit 264 transmits a take-out notification to the server 400 (S24), and the acceptance / rejection notification receiving unit 274 receives the acceptance / rejection notification from the server 400 (S26). In unmanned stores with an automatic check method, it is assumed that at least the voluntary purchase method will be adopted, so it will not be denied. As a general rule, a notification of approval or disapproval indicating approval arrives as a confirmation response from the server 400. However, if the user 104 has not taken out the pre-purchased product or has not taken out the pre-booked product, the server 400 notifies the user terminal 300 to note that (for example, "pre-purchased XX". You may send a message such as "Please bring your (product name)" or "Please bring your pre-booked XX (product name).").
[0253]
　The lock lock (S32) shown in FIG. 4 is omitted. When the user 104 moves out, the ticket is erased as in the case of the storage device 100 (S34).
[0254]
　When a plurality of users 104 visit the store, the processing is performed in parallel for each user 104.
That is, the tracking process, the action detection process, the product identification process, and the like are performed simultaneously for each user 104.
[0255]
[Manned store]
　Like the unmanned store, the manned store has a function of storing the product 104 and delivering the product 104 to the user 122, so that it can be regarded as a kind of storage body. The manned store may be a product check machine system or an automatic check system, as in the case of an unmanned store.
[0256]
　In the case of a manned store, the store clerk may perform the operation of reading the product barcode 118 of the product 104 on the product check machine. The clerk may reserve the product 104 pre-purchased or pre-booked by the user 122. Further, the clerk may hand over the product 104 that is not placed on the shelf to the user 122. The product check machine may also serve as a POS (Point of sale) cash register, in addition to a self-checkout machine and a semi-self-checkout machine.
[0257]
[Reservation method that does not limit
　the storage device 100 ] A group to which a plurality of storage devices 100 belong may be regarded as a virtual store, and reserved products may be taken out from any storage device 100 belonging to the virtual store.
[0258]
　For example, a user may have reserved a product 104 in a nearby storage device 100 (ST-A), but the circumstances may change and he / she may want to take the product 104 from another storage device 100 (ST-B). Be done. According to this method, in such a case, the reserved product can be taken out from other than the reserved storage device 100 (ST-A).
[0259]
　Specifically, when a reservation is accepted for the product 104 of a certain storage device 100 (ST-A), the ticket transmission unit 464 of the server 400 is not only the storage device 100 (ST-A) but also other members in the group. The electronic ticket is also transmitted to the storage device 100 (ST-B) and the storage device 100 (ST-C) of the above. Information on the storage device 100 belonging to the same group is stored in a group storage unit (not shown) of the server 400.
[0260]
　When the ticket receiving unit 272 of the storage device 100 (ST-B) receives the electronic ticket, the ticket list management unit 252 adds the received electronic ticket to the ticket list. The same applies to the storage device 100 (ST-C).
[0261]
　When the reserved product is taken out by the storage device 100 (ST-B) other than the initially reserved storage device 100 (ST-A), it is processed as a purchase based on the advance reservation. Further, when the take-out notification receiving unit 476 of the server 400 receives the take-out notification sent from the storage device 100 (ST-B) from which the reserved product is taken out, the cancellation notification transmitting unit (not shown) of the server 400 receives the take-out notification. The cancellation notice regarding the electronic ticket included in the above is sent to the other storage devices 100 (ST-A) and the storage device 100 (ST-C) that belong to the same group as the storage device 100 (ST-B) that is the source of the withdrawal notification. Send. The cancellation notice includes the electronic ticket to be canceled.
[0262]
　When the cancellation notification receiving unit (not shown) of the storage device 100 (ST-A) receives the cancellation notification, the ticket list management unit 252 deletes the same electronic ticket included in the cancellation notification from the ticket list. The same applies to the storage device 100 (ST-C).
[0263]
　As described above, the server 400 may perform ticket authentication. In that case, the ticket list of the initially reserved storage device 100 (ST-A) is updated in the server 400, and the storage device 100 (ST-B) and the storage device 100 (ST-C) in the same group are updated. ) Ticket list is also updated.
[0264]
　The storage devices 100 within a geographically close range may be grouped, or the storage devices 100 storing the same type of products 104 may be grouped. Further, all the storage devices 100 operated by the same operator may be grouped together.
[0265]
　Regarding the initially reserved storage device 100 (ST-A), the removal of reserved products by a person other than the reservation person is restricted, and the other storage devices 100 (ST-B) and storage device 100 (ST-C) are restricted. May treat the reserved product as a provisional reservation so that a person other than the reservation person can freely take out the reserved product.
[0266]
[Other variants]
　Electronic ticket authentication does not have to be subject to reservation or purchase. The lock may be unlocked whenever an electronic ticket that can identify a member is read, provided that the member is registered in advance.
[0267]
　A surveillance camera may be installed near the storage device 100 for recording. The recording may be analyzed to identify the fraudulent user and the content of the fraud.
[0268]
　The storage device 100 may be used as a delivery box. The delivery person of the carrier opens the storage device 100 with the ticket of the delivery person and stores the cargo. The consignee opens the storage device 100 with his / her ticket and withdraws the luggage. When the storage device 100 is shared by a plurality of people, a warning may be given when a package addressed to another person is taken out. Further, when the consignee receives the notification of arrival from the server 100 and notifies the server 100 of the receipt, the ticket for receipt may be given.
　Further, a human may be allowed to enter the storage device 100.
[0269]
　The door 102 of the storage device 100 may be a sliding door type.
[0270]
　It may be provided with a display for displaying operation guidance and warning messages. The warning output unit 232 may display a warning message on the display.
[0271]
　An operation guidance unit may be provided to emit an operation guidance message from the speaker 116 or to display the operation guidance message on the display.
[0272]
　The electronic ticket may be electronic data transmitted by short-range radio. The ticket reader 114 may be a near field radio receiver.
[0273]
　A product QR code may be used instead of the product barcode 118. Moreover, you may use an IC tag. When an IC tag is used, the product tag code is read from the IC tag by a tag reader provided in the storage device 100.
[0274]
　The clerk ticket may be a paper ticket given to the clerk. Alternatively, it may be a QR code printed on the clerk ID card.
[0275]
　When it is determined that a shortage has occurred by referring to the product list in the storage or the store inventory list, the recommended combination of products 104 or the product 104 stored in the storage device 100 may be automatically adjusted.
[0276]
　The present invention is not limited to the above-described embodiment or modification, and the components can be modified and embodied within a range that does not deviate from the gist. Various inventions may be formed by appropriately combining a plurality of components disclosed in the above-described embodiments and modifications. In addition, some components may be deleted from all the components shown in the above embodiments and modifications.
The scope of the claims
[Claim 1]
　An article accommodating system including a storage body for accommodating articles and a server connected to the storage entity,
　wherein the server includes
　an interface providing unit that provides a user interface for inquiring about articles by a user to a user terminal. The
　storage body includes
　an article accommodating unit that performs an operation for delivering the article in the storage body to the user.
[Claim 2]
　The server
　further includes a storage position storage unit that stores storage position information that identifies a position where the storage unit
　is installed, and the interface providing unit is installed with the storage unit that houses the article. The article storage system according to claim 1, wherein data displaying the position is transmitted to the user terminal.
[Claim 3]
　An article accommodating system including a storage body for accommodating an article and an information processing device connected to the
　storage body , wherein the storage body includes an
　article picked up by a user and the user who picked up the article. first notification unit for notifying the corresponding information to the information processing apparatus, comprising a
　said information processing apparatus,
　based on the corresponding information, recording unit for recording the receipt of said article from said storage body by said user An article storage system, characterized in that it comprises.
[Claim 4]
　Wherein the storage body,
　the second notification unit for notifying the article that accommodates to the information processing apparatus, further comprising a
　said information processing apparatus,
　the articles contained in the storage body to the terminal of the user The article storage system according to claim 3, further comprising a third notification unit for notifying.
[Claim 5]
　The article accommodating system includes a plurality of storage bodies, the
　information processing apparatus
　further includes a selection unit for selecting a storage body for the user from the plurality of storage bodies, and
　the third notification unit includes a third notification unit. The article storage system according to claim 4, wherein the article stored in the storage body selected for the user is notified to the user's terminal.
[Claim 6]
　5. The third notification unit is characterized in that, with respect to the article housed in the storage body selected for the user, the recommended combination of the articles is notified to the user's terminal. The article storage system described.
[Claim 7]
　5. The information processing device is
　further provided with a fourth notification unit for notifying the user's terminal of a route through two or more storage bodies accommodating the article to be picked up by the user. The article storage system according to 6.
[Claim 8]
　The information processing device
　further includes a permission issuing unit that issues a permission to pick up the article by the user from the storage body to the terminal of the user, and the
　storage body further includes the storage body when the
　pick-up permission is confirmed. The article accommodating system according to any one of claims 3 to 7, further comprising an operating unit that performs an operation for picking up the article by a user.
[Claim 9]
　The
　eighth aspect of claim is that the permission issuing unit issues the pick-up permission of the goods by the user when the user applies for the purchase of the goods or the user reserves the purchase of the goods. Goods storage system.
[Claim 10]

　The article accommodating system according to claim 8, 　wherein the permission issuing unit issues the pick-up permission of the article by the user in response to a pick-up request of the article from the terminal of the user.
[Claim 11]

　Claims 3 to 10 further 　include the information processing apparatus , which further includes a settlement unit for making a settlement for the purchase of the article by the user based on a record of the receipt of the article from the storage body by the user. The article storage system described in any of the above.
[Claim 12]
　A server that connects to a storage unit that has an operation unit that performs an operation to deliver the stored article to the user,
　and a reception unit that receives an inquiry request for the article stored in the storage body from the user terminal.
　A server including a presenting unit that presents the article housed in the storage body to the user terminal.
[Claim 13]
　A method of accommodating an article by an article accommodating system including a storage body for accommodating an article and a server connected to the storage body,
　wherein the server provides a user interface for inquiring an article by a user to a user terminal. A
　method for accommodating an article, comprising the step of performing an operation for delivering the article in the storage body to the user.
[Claim 14]
　A
　function of receiving an inquiry request for the article housed in the storage body from a user terminal to a server connected to the storage body having an operation unit for delivering the housed article to the user, and the
　storage body. A program characterized by exerting a function of presenting the article housed in the user terminal to the user terminal.
[Claim 15]
　An information processing apparatus connected to the storage body for the article storage,
　from said storage body, and an article taken off the user, a receiver for receiving the corresponding information with the user who taken off the article,
　the receiving An information processing device including a recording unit that records the collection of the article from the storage body by the user based on the associated information.
[Claim 16]
　A method of accommodating an article by an article accommodating system including a storage body for accommodating an article and an information processing device connected to the
　storage body , wherein the storage body has picked up an article picked up by a user and the article. A step of notifying the information processing apparatus of the information associated with the user, and
　a step of recording the receipt of the article from the storage body by the user based on the information processing apparatus. A method for accommodating goods, which comprises.
[Claim 17]
　The information processing device connected to the storage body for accommodating the
　article has a function of receiving the link information between the article picked up by the user and the user who picked up the article from the storage body, and the
　received string. A program characterized by exerting a function of recording the collection of the article from the storage body by the user based on the attached information.