Self-checkout system and program

Abstract

To provide a self-checkout system and a program that prevent customers from leaving a store with unpaid articles with a reduced computational load.SOLUTION: A self-checkout system includes an article registration device where customers register articles by themselves, a settlement device where the customers settle for registered articles by themselves, and an exit gate that allows the customers to leave the settlement area. The article registration device generates article registration information containing article identification information and extracts characteristics of the customers during registration, and storing both in association with each other. The settlement device extracts the characteristics of the customers performing settlement. When the extracted characteristics of the customers match those stored by the article registration device, the settlement device performs settlement for the registered article information and stores the extracted characteristics of the customers associated with the settled information. The exit gate extracts the characteristics of the customers before passage. When the extracted characteristics of the customers match those stored by the settlement device, the exit gate allows the customers to exit.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] FIELD OF THE INVENTION An embodiment of the present invention relates to a self-checkout system and program. [Background technology]

[0002] Conventionally, a self-checkout system has been known in which, in a store, features extracted from an image of a customer taken when registering a product are stored in association with product registration information, and then, at the time of payment, information indicating that payment has been made is added to the product registration information, and the customer is allowed to exit if features extracted from an image of the customer taken when the customer leaves the store are stored in association with information indicating that payment has been made (for example, Patent Document 1).

[0003] However, such conventional self-checkout systems require extracting the characteristics of all customers when registering products, taking into consideration the possibility that other customers who visit the store together with the customer who registered the products may also be paying, which results in a high computational load for information processing. Therefore, there is a need for a system that can reduce the computational load and prevent fraudulent behavior in which customers leave the store with unpaid products. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a self-checkout system and program that can prevent customers from leaving a store with unpaid items, with a smaller calculation load. [Means for solving the problem]

[0005] A self-checkout system according to an embodiment includes a product registration device that registers products to be purchased through a customer's own operation, a checkout device that performs checkout for the registered products through a customer's own operation, and an exit gate that allows the customer to exit the area where the checkout device is installed. The product registration device includes a product registration unit, a first feature extraction unit, and a first memory unit. The product registration unit generates product registration information in which identification information for products purchased by the customer is registered. The first feature extraction unit extracts features of the customer who performs product registration. The first memory unit associates and stores the customer features extracted by the first feature extraction unit with the product registration information. The checkout device also includes a second feature extraction unit, a checkout processing unit, and a second memory unit. The second feature extraction unit extracts features of the customer who performs checkout. The checkout processing unit performs checkout for the product registration information on the condition that the customer features stored in the first memory unit match the customer features extracted by the second feature extraction unit. The second memory unit stores the customer characteristics extracted by the second feature extraction unit in association with information indicating that payment has been completed. The exit gate also includes a third feature extraction unit and an exit control unit. The third feature extraction unit extracts the customer's characteristics before passing through the exit gate. The exit control unit allows the customer to exit through the exit gate on the condition that the customer characteristics extracted by the third feature extraction unit match the customer characteristics stored in the second memory unit. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram showing an example of a schematic configuration of a self-checkout system according to the first embodiment. [Figure 2] FIG. 2 is an external view showing an example of a product registration device provided in the self-checkout system. [Figure 3] FIG. 3 is a diagram illustrating an example of the appearance of a settlement device included in the self-checkout system. [Figure 4] FIG. 4 is an external view showing an example of an exit gate provided in the self-checkout system. [Figure 5] FIG. 5 is a hardware block diagram showing an example of the hardware configuration of a merchandise registration device included in the self-checkout system. [Figure 6] FIG. 6 is a diagram illustrating an example of a data structure of a product registration file generated by the product registration device. [Figure 7] FIG. 7 is a hardware block diagram showing an example of the hardware configuration of a settlement device included in the self-checkout system. [Figure 8] FIG. 8 is a diagram illustrating an example of the data structure of a settlement file generated by the settlement device. [Figure 9] FIG. 9 is a hardware block diagram showing an example of the hardware configuration of an exit gate provided in the self-checkout system. [Figure 10] FIG. 10 is a functional block diagram illustrating an example of the functional configuration of the self-checkout system according to the first embodiment. [Figure 11] FIG. 11 is a flowchart showing an example of the flow of processing performed by the merchandise registration device included in the self-checkout system of the first embodiment. [Figure 12] FIG. 12 is a flowchart illustrating an example of the flow of processing performed by the settlement device included in the self-checkout system of the first embodiment. [Figure 13] FIG. 13 is a flowchart showing an example of the flow of processing performed by the exit gate included in the self-checkout system of the first embodiment. [Figure 14] FIG. 14 is a block diagram showing an example of a schematic configuration of a self-checkout system according to the second embodiment. [Figure 15] FIG. 15 is a hardware block diagram illustrating an example of the hardware configuration of a server device included in the self-checkout system. [Figure 16] FIG. 16 is a functional block diagram illustrating an example of the functional configuration of the self-checkout system according to the second embodiment. [Figure 17] FIG. 17 is a flowchart showing an example of the flow of processing performed by the merchandise registration device included in the self-checkout system of the second embodiment. [Figure 18]FIG. 18 is a flowchart showing an example of the flow of processing performed by the settlement device included in the self-checkout system of the second embodiment. [Figure 19] FIG. 19 is a flowchart showing an example of the flow of processing performed by the exit gate included in the self-checkout system of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

[0008] (First embodiment) A self-checkout system 100 according to a first embodiment of the present disclosure will be described below with reference to the drawings.

[0009] (Outline of self-checkout system configuration) The general configuration of a self-checkout system 100 will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the general configuration of a self-checkout system according to a first embodiment.

[0010] The self-checkout system 100 includes a product registration device 10, a payment device 30, and an exit gate 50. The product registration device 10, the payment device 30, and the exit gate 50 are communicably connected to each other via an in-store network 1 such as a LAN. The in-store network 1 is configured as a communication network such as a wireless LAN or a wired LAN.

[0011] The product registration device 10 registers products to be purchased through the customer's own operation. More specifically, the product registration device 10 generates product registration information in which identification information (e.g., product code) of the product to be purchased by the customer is registered in response to the customer's registration operation. The product registration device 10 also extracts characteristics of the customer performing the registration operation and stores the extracted characteristics in association with the product registration information. The extracted customer characteristics are information that represents the customer's appearance and physical characteristics. Examples of customer characteristics include the customer's clothing, accessories worn by the customer, the customer's face, the customer's hairstyle, etc.

[0012] The settlement device 30 settles the payment for registered products through the customer's own operation. More specifically, the settlement device 30 performs the payment process for the product registration information registered by the customer in the product registration device 10, i.e., the payment process for the product price, using the payment method selected by the customer. The settlement device 30 also extracts the characteristics of the customer making the settlement, and settles the payment only if the extracted characteristics match the customer characteristics stored in the product registration device 10. The settlement device 30 also associates the extracted customer characteristics with information indicating that the payment has been completed and stores them.

[0013] The exit gate 50 includes, for example, an openable door 545 (see FIG. 4) and allows customers to exit the area where the payment device 30 is installed. The exit gate 50 extracts characteristics of customers before they pass through. The exit gate 50 also opens the door 545 to allow the customer to exit on the condition that the extracted customer characteristics match the customer characteristics stored in the payment device 30 and that the payment device 30 stores information indicating that payment has been completed.

[0014] At least one merchandise registration device 10 and one settlement device 30 are installed. At least one exit gate 50 is also installed.

[0015] (General configuration of product registration device) The general configuration of the product registration device 10 will be described with reference to Fig. 2. Fig. 2 is an external view showing an example of a product registration device provided in a self-checkout system.

[0016] The product registration device 10 generates product registration information by having a customer read the identification information of a product to be purchased through their own operation. The product identification information is, for example, a product code such as a JAN (Japanese Article Number) code that uniquely identifies the product. The product code is registered in a code symbol such as a barcode printed or affixed to the outer box or packaging of the product.

[0017] The product registration device 10 includes various devices for product registration on the top of the housing 147.

[0018] A product stand 149 is provided on the side of the housing 147. A customer places a shopping basket or the like containing unregistered products on the product stand 149.

[0019] A product stand 148 is formed on the top surface of the housing 147. The customer places registered products in a bag or the like placed on the product stand 148.

[0020] On the top of the housing 147, a display device 141, an operation device 142, a scanner 143, a printer 144, a camera 145, and a warning light 146 are provided.

[0021] The display device 141 displays various information related to product registration to the customer. The various information related to product registration includes, for example, registered product information, total price, etc. The display device 141 is, for example, a liquid crystal monitor or an organic EL monitor.

[0022] The operation device 142 acquires various pieces of operation information related to product registration from the customer. The various pieces of operation information related to product registration include, for example, an instruction to start registration, an instruction to end registration, etc. The operation device 142 is, for example, a touch panel stacked on the display device 141.

[0023] The scanner 143 reads a code symbol (for example, a barcode) in which a product code is registered, which is held over a reading window 1431. The scanner 143 is a so-called fixed type scanner.

[0024] The commodity registration device 10 may be provided with a hand scanner (not shown) in addition to the scanner 143. This allows the code symbol to be read by the hand scanner for heavy goods such as rice or boxed beverages, for which it is difficult to hold the code symbol over the scanner 143.

[0025] After completing the registration of all products, the printer 144 prints and issues a transaction code that uniquely identifies the registered product information (product registration file 123 (see Figure 5) described below), for example in the form of a code symbol (e.g., a barcode).

[0026] The camera 145 takes an image of the customer who is registering a product. The product registration device 10 processes the image taken by the camera 145 to extract and store the customer's characteristics. The extracted characteristics include, for example, clothing, accessories worn, face, hairstyle, etc. The product registration device 10 extracts and stores as many characteristics as possible. The camera 145 is installed in a position that makes it as easy as possible to photograph the customer, such as on the upper edge of the display device 141, facing the customer. When all product registrations have been completed, the product registration device 10 stores the characteristics of the customer who has registered the products in association with the product registration information.

[0027] The warning light 146 is installed at the tip of a pole extending above the housing 147, and emits light in blue, red, or the like. For example, when a customer who is registering a product calls a store clerk, the warning light 146 lights up in a predetermined lighting pattern or flashes in a predetermined flashing pattern to notify the store clerk of a request for assistance.

[0028] (General configuration of the settlement device) The general configuration of the settlement device 30 will be described with reference to Fig. 3. Fig. 3 is an external view showing an example of a settlement device provided in a self-checkout system.

[0029] The settlement device 30 performs settlement (also called payment) to pay the price related to the product registration information registered by the product registration device 10. The settlement device 30 performs cash settlement and cashless settlement. Cash settlement is a payment method using banknotes and coins. The settlement device 30 can also perform cashless payments such as credit card settlement, code settlement, and electronic money payment.

[0030] Credit card payment is a payment method that uses a customer's credit card. When making a credit card payment, the customer inserts their credit card into the payment terminal 344 described below and has the personal information and debit account information registered on the credit card read to make the payment.

[0031] Code payment is a payment method in which payment is made using a payment app pre-installed on a mobile device owned by the customer. When making a code payment, the customer displays a code symbol on their mobile device and has the displayed code symbol read by a scanner 343 (described later) to complete the payment.

[0032] Electronic money payment is a payment method in which payment is made using electronic money loaded onto, for example, an IC card. When making an electronic money payment, a customer holds their electronic money card over the payment terminal 344, and short-range wireless communication is established between the payment terminal 344 and the electronic money card, which reads the remaining balance on the electronic money card and allows payment to be made within the remaining balance.

[0033] The settlement device 30 is provided with various devices for making payments inside and on top of the housing 349.

[0034] A change dispenser 345 is provided inside the housing 349. The change dispenser 345 accepts payments of bills and coins from customers. The change dispenser 345 also dispenses change, in the form of bills or coins, that is the total amount including tax registered in the product registration information from the total amount paid by the customer.

[0035] A customer inserts coins into a coin slot 3451. A customer inserts bills into a bill slot 3453.

[0036] The change machine 345 dispenses predetermined coins as change from the coin outlet 3452. The change machine 345 also dispenses predetermined banknotes as change from the banknote outlet 3454.

[0037] On the top of the housing 349, a display device 341, an operation device 342, a scanner 343, a payment terminal 344, a receipt printer 346, a camera 347, and a warning light 348 are provided.

[0038] The display device 341 displays various information related to the settlement to the customer. The various information related to the settlement includes, for example, product registration information related to the settlement, payment method options, operation guidance, etc. The display device 341 is, for example, an LCD monitor or an organic EL monitor.

[0039] The operation device 342 acquires various operation information related to payment from the customer. The various operation information related to payment is, for example, the result of selection of a payment method, etc. The operation device 342 is, for example, a touch panel stacked on the display device 341.

[0040] Scanner 343 reads the transaction code issued by product registration device 20 when it is held over reading window 3431. Checkout device 30 reads out the product registration information corresponding to the transaction code read by scanner 343 and prepares to perform the checkout related to the product registration information. If the customer has registered as a member of the store, the transaction code previously transmitted from product registration device 10 to the customer's mobile terminal may be displayed on the mobile terminal and read by scanner 343.

[0041] The payment terminal 344 performs various cashless payments. The payment terminal 344 includes a display device 3441, a numeric keypad 3442, and a card slot 3443. The settlement device 30 causes the payment terminal 344 to perform payment (settlement) on the condition that the customer's characteristics included in the image captured by the camera 347 match the customer's characteristics stored in the product registration device 20. On the other hand, if the customer's characteristics included in the image captured by the camera 347 do not match the customer's characteristics stored in the product registration device 20, the settlement device 30 prompts the customer to have the customer who registered the product in the product registration device 20 settle the payment. Furthermore, when the payment (settlement) is completed, the settlement device 30 associates the characteristics of the customer who performed the settlement with information indicating that the settlement has been completed and stores them.

[0042] The display device 3441 displays various information such as operation guidance when various cashless payments are made. The display device 3441 is, for example, a liquid crystal monitor or an organic EL monitor.

[0043] The ten keys 3442 are operation keys for inputting various personal identification numbers and the like related to cashless payment.

[0044] The card insertion slot 3443 is an insertion slot for inserting an IC card such as a credit card or electronic money card when making a cashless payment.

[0045] The payment terminal 344 may further include a scanning groove (not shown) for reading a magnetic card.

[0046] The receipt printer 346 issues a receipt on which the name, quantity, and price of the purchased product, as well as the payment result, etc. are printed.

[0047] The camera 347 takes an image of the customer making the payment. The payment device 30 processes the image taken by the camera 347 to extract and store the customer's characteristics. The extracted characteristics include, for example, clothing, accessories worn, face, hairstyle, etc. The camera 347 is installed in a position that makes it as easy as possible to photograph the customer, such as on the upper edge of the display device 341, facing the customer. The camera 145 provided in the product registration device 10 and the camera 347 provided in the payment device 30 are installed so that they can photograph the customer from as close to the same height and direction as possible.

[0048] Warning light 348 is installed at the tip of a pole extending above housing 349, and emits light such as blue or red. For example, when a customer who is paying calls a store clerk, warning light 348 lights up in a predetermined lighting pattern or flashes in a predetermined flashing pattern to notify the store clerk of a request for assistance.

[0049] (Outline of exit gate configuration) The general configuration of the exit gate 50 will be described with reference to Fig. 4. Fig. 4 is an external view showing an example of an exit gate provided in a self-checkout system.

[0050] The exit gate 50 is provided with a pair of doors 545 that can be opened and closed between a pair of left and right pillar members 544 .

[0051] The pillar members 544 each support a door 545 so that the door 545 can be opened and closed.

[0052] A warning light 543 is installed on the top of the pillar member 544. Depending on the image of the customer taken by a camera 541 (described later), the warning light 543 lights up in blue, green, or the like if the customer is being asked to exit, and lights up or flashes in red or the like if the customer is not being asked to exit. When the warning light 543 lights up or flashes red, a store employee who notices this will run over to the exit gate 50, explain to the customer why they cannot exit, and then check the situation.

[0053] Door 545 is driven by a motor controlled by gate controller 542 installed inside pillar member 544. When a customer leaves the checkout area, door 545 rotates approximately 90 degrees around the Z axis shown in FIG. 4 to form an exit path for the customer. Once opened, door 545 closes after a predetermined time has passed, preventing the next customer from exiting. Door 545 forms a so-called flapper gate.

[0054] A camera 541 is installed above a warning light 543 on one of the pillar members 544. The camera 541 takes images of customers waiting to exit. The exit gate 50 extracts characteristics of the customers by processing the images taken by the camera 541. The extracted characteristics include, for example, clothing, accessories worn, face, hairstyle, etc. The camera 541 is installed in a position that makes it as easy as possible to photograph customers, such as the top of the pillar member 544, facing the customers waiting to exit.

[0055] The exit gate 50 opens a door 545 and lets the customer exit the payment area on condition that the customer's features extracted from the image photographed by the camera 541 match the customer's features stored in the payment device 30.

[0056] On the other hand, if the customer characteristics extracted from the image taken by camera 541 do not match the customer characteristics stored in checkout device 30, and if the customer characteristics extracted from the image taken by camera 541 match the customer characteristics stored in product registration file 123, i.e., the characteristics of the customer who registered the product, exit gate 50 will not open door 545 and will not allow the customer to exit the checkout area. Exit gate 50 then alerts the store clerk by turning on or flashing a warning light in red, etc.

[0057] The exit gate 50 may not be provided with the door 545 and may be a simple gate that only issues an alarm.

[0058] (Hardware configuration of product registration device) The hardware configuration of the product registration device 10 will be described with reference to Fig. 5. Fig. 5 is a hardware block diagram showing an example of the hardware configuration of a product registration device provided in a self-checkout system.

[0059] The product registration device 10 has a configuration in which a control unit 11, a storage unit 12, a peripheral device controller 14, and a communication controller 15 are interconnected by an internal bus 13.

[0060] The control unit 11 controls the overall operation of the product registration device 10. The control unit 11 includes a CPU (Central Processing Unit) 111, a ROM (Read Only Memory) 112, and a RAM (Random Access Memory) 113. The CPU 111 is connected to the ROM 112 and the RAM 113 via internal buses such as an address bus and a data bus. The CPU 111 loads various programs stored in the ROM 112 and the storage unit 12 into the RAM 113. The CPU 111 controls the operation of the product registration device 10 by operating in accordance with the various programs loaded into the RAM 113. In other words, the control unit 11 has the configuration of a typical computer.

[0061] The storage unit 12 is a storage device such as an HDD or SSD. Alternatively, the storage unit 12 may be a non-volatile memory such as a flash memory that retains stored information even when the power is turned off. The storage unit 12 stores a control program 121, a product master 122, and a product registration file 123.

[0062] The control program 121 is a program that controls the overall operation of the product registration device 10. The control program 121 may be provided in a state stored in the storage unit 12, or may be provided by being recorded in an installable or executable file on a computer-readable non-transitory recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD. The control program 121 may also be provided by being stored on a computer connected to a network and downloaded via the network. Furthermore, the control program 121 may be provided or distributed via a network such as the Internet.

[0063] The product master 122 is a master file that stores product information (product name, unit price, etc.) corresponding to a product code. Since the registered contents of the product master 122 are updated daily, the product registration device 10 acquires the latest product master 122 from a store server (not shown in FIG. 1) as needed.

[0064] The product registration file 123 is a file that stores product information (product name, quantity, unit price, total amount, etc.) corresponding to the product code of the product registered in the product registration device 10. The product registration device 10 acquires the product information corresponding to the product code from the product master 122. The product registration file 123 is an example of product registration information in the present disclosure.

[0065] The product registration file 123 also stores a transaction code and customer characteristics. The transaction code is identification information that uniquely identifies the product registration file 123. The customer characteristics Fa are information that indicate the customer's appearance and physical characteristics, extracted from an image captured by the camera 145 provided in the product registration device 10. The data structure of the product registration file 123 will be described in detail later (see FIG. 6).

[0066] The control unit 11 is connected to a display device 141, an operation device 142, a scanner 143, a printer 144, a camera 145, and a warning light 146, which input and output various types of information, via a peripheral device controller 14. The outline of each input / output device is as described above. The peripheral device controller 14 controls the operation of these peripheral devices in accordance with instructions from the control unit 11.

[0067] The control unit 11 also communicates with the settlement device 30 and the exit gate 50 via the communication controller 15. The product registration device 10 outputs a product registration file 123 to the settlement device 30. The product registration device 10 also outputs the product registration file 123 to the exit gate 50.

[0068] (Product registration file data structure) The data structure of the product registration file 123 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the data structure of the product registration file generated by the product registration device.

[0069] The product registration file 123 stores the product name, quantity, unit price, and subtotal of the product registered by the customer in the product registration device 10 in association with the product code of the product. The subtotal is the total amount calculated by adding up the unit price and quantity for each product. The product registration file 123 also stores the total amount of the registered products.

[0070] The product registration file 123 also stores the customer's characteristic Fa, which is extracted from the image captured by the camera 145 and who has registered the product. At least one customer characteristic Fa is stored, but multiple characteristics may be stored. For example, the reliability of the characteristics extracted from the image captured by the camera 145 may be calculated, and the characteristics whose reliability is equal to or greater than a threshold may be stored. After the customer has completed the registration of all products, the product registration device 10 stores the customer's characteristic Fa in association with the product registration file 123.

[0071] Furthermore, the product registration file 123 stores a transaction code X issued by the product registration device 10, which uniquely identifies the registration contents of the product registration file 123. The transaction code X is issued by the product registration device 10 when all product registrations are completed. Note that the product registration device 10 determines that all product registrations are completed, for example, when the operation device 342 detects that the registration end button displayed on the display device 341 has been pressed.

[0072] The product registration file 123 may further store identification information that uniquely identifies the product registration device 10 and the date and time when the product registration file 123 was created.

[0073] (Hardware configuration of settlement device) The hardware configuration of the settlement device 30 will be described with reference to Fig. 7. Fig. 7 is a hardware block diagram showing an example of the hardware configuration of a settlement device provided in a self-checkout system.

[0074] The settlement device 30 has a configuration in which a control unit 31, a storage unit 32, a peripheral device controller 34, and a communication controller 35 are connected to one another via an internal bus 33.

[0075] The control unit 31 controls the overall operation of the settlement device 30. The control unit 31 includes a CPU 311, a ROM 312, and a RAM 313. The CPU 311 is connected to the ROM 312 and the RAM 313 via internal buses such as an address bus and a data bus. The CPU 311 loads various programs stored in the ROM 312 and the storage unit 32 into the RAM 313. The CPU 311 controls the operation of the settlement device 30 by operating in accordance with the various programs loaded into the RAM 313. In other words, the control unit 31 has the configuration of a typical computer.

[0076] The storage unit 32 is a storage device such as an HDD or SSD. Alternatively, the storage unit 32 may be a non-volatile memory such as a flash memory that retains stored information even when the power is turned off. The storage unit 32 stores a control program 321 and a payment file 323.

[0077] The control program 321 is a program that controls the overall operation of the settlement device 30. The control program 321 may be provided in a state stored in the storage unit 32, or may be provided by being recorded in an installable or executable file on a computer-readable non-transitory recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD. The control program 321 may also be stored on a computer connected to a network and provided by being downloaded via the network. Furthermore, the control program 321 may be provided or distributed via a network such as the Internet.

[0078] The payment file 322 is a file that stores the payment details and is generated when the payment device 30 completes the payment. In addition to the information stored in the product registration file 123, the payment file 322 stores identification information Z that indicates the payment method. Furthermore, the payment file 322 stores customer characteristics Fb extracted from an image captured by the camera 347 equipped on the payment device 30, instead of the customer characteristics Fa registered in the product registration file 123. The data structure of the payment file 322 will be described in detail later (see FIG. 8).

[0079] The control unit 31 is connected to a display device 341, an operation device 342, a scanner 343, a payment terminal 344, a change dispenser 345, a receipt printer 346, a camera 347, and a warning light 348, which input and output various types of information, via a peripheral device controller 34. The outline of each input / output device is as described above. The peripheral device controller 34 controls the operation of these peripheral devices according to instructions from the control unit 31.

[0080] The control unit 31 also communicates with the product registration device 10 and the exit gate 50 via the communication controller 35. The settlement device 30 acquires the product registration file 123 to be processed for settlement from the product registration device 10. The settlement device 30 also outputs a settlement file 323 to the exit gate 50.

[0081] (Payment file data structure) The data structure of the settlement file 322 will be described with reference to Fig. 8. Fig. 8 is a diagram showing an example of the data structure of the settlement file generated by the settlement device.

[0082] As shown in FIG. 8, the payment file 323 stores identification information Z indicating the payment method in the contents of the product registration file 123 for each transaction code. In addition, the payment file 323 stores customer characteristics Fb extracted from an image captured by the camera 347 instead of the customer characteristics Fa stored in the product registration file 123. Note that if the same customer registers a product and performs payment, the customer characteristics Fa and customer characteristics Fb will match. In this case, the payment file 323 may store the customer characteristics Fa as is. Note that at least one customer characteristic Fb is stored, but multiple characteristics may also be stored.

[0083] The settlement file 323 may further store identification information that uniquely identifies the settlement device 30 and the date and time when the settlement file 323 was created.

[0084] The settlement device 30 generates the settlement file 323 after the settlement process is completed.

[0085] (Exit gate hardware configuration) The hardware configuration of the exit gate 50 will be described with reference to Fig. 9. Fig. 9 is a hardware block diagram showing an example of the hardware configuration of the exit gate provided in the self-checkout system.

[0086] The exit gate 50 has a configuration in which a control unit 51, a storage unit 52, a peripheral device controller 54, and a communication controller 55 are interconnected by an internal bus 53.

[0087] The control unit 51 controls the overall operation of the exit gate 50. The control unit 51 includes a CPU 511, a ROM 512, and a RAM 513. The CPU 511 is connected to the ROM 512 and the RAM 513 via internal buses such as an address bus and a data bus. The CPU 511 loads various programs stored in the ROM 512 and the storage unit 52 into the RAM 513. The CPU 511 controls the operation of the exit gate 50 by operating in accordance with the various programs loaded into the RAM 513. In other words, the control unit 51 has the configuration of a typical computer.

[0088] The storage unit 52 is a storage device such as an HDD or SSD. Alternatively, the storage unit 52 may be a non-volatile memory such as a flash memory that retains stored information even when the power is turned off. The storage unit 52 stores a control program 522.

[0089] The control program 522 is a program that controls the overall operation of the exit gate 50. The control program 522 may be provided in a state stored in the storage unit 52, or may be provided by being recorded in an installable or executable file on a computer-readable non-transitory recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD. The control program 522 may also be provided by being stored on a computer connected to a network and downloaded via the network. Furthermore, the control program 522 may be provided or distributed via a network such as the Internet.

[0090] The control unit 51 is connected to a camera 541, a gate controller 542, and a warning light 543, which input and output various information, via a peripheral device controller 54. The outline of each input / output device is as described above. The peripheral device controller 54 controls the operation of these peripheral devices in accordance with instructions from the control unit 51.

[0091] The camera 541 provided at the exit gate 50, the camera 145 provided at the merchandise registration device 10, and the camera 347 provided at the settlement device 30 are installed so as to photograph customers from as close to the same height and direction as possible.

[0092] The control unit 51 also communicates with the product registration device 10 and the settlement device 30 via the communication controller 55. The exit gate 50 acquires the product registration file 123 from the product registration device 10. The exit gate 50 also acquires the payment file 322 from the settlement device 30.

[0093] (Functional configuration of self-checkout system) The functional configuration of the self-checkout system 100 will be described with reference to Fig. 10. Fig. 10 is a functional block diagram showing an example of the functional configuration of the self-checkout system of the first embodiment.

[0094] The control unit 11 of the product registration device 10 deploys the control program 121 in the RAM 113 and runs it to realize, as functional units, the product code reading unit 21, the product registration unit 22, the customer feature extraction unit 23, the customer feature storage unit 24, the transaction code numbering unit 25, and the product registration file output unit 26 shown in Fig. 10. Note that some or all of these functional units may be realized by dedicated hardware.

[0095] The product code reading unit 21 reads a code symbol attached to a product in which product identification information (product code) is registered, and acquires the product code registered in the code symbol.

[0096] The product registration unit 22 registers the product having the product code registered in the code symbol read by the product code reading unit 21 in the product registration file 123. In addition, the product registration unit 22 determines that the customer has finished product registration by detecting, for example, that a registration end button displayed on the display device 341 has been pressed.

[0097] The customer feature extraction unit 23 captures images using the camera 145. The customer feature extraction unit 23 also extracts the features of the customer who is registering a product from the images captured by the camera 145. It is preferable that the customer feature extraction unit 23 processes multiple images captured repeatedly and extracts the customer's features from each image. The customer feature extraction unit 23 extracts the customer who is registering a product and their features by, for example, using a recognition algorithm that uses a learning model that learns person-likeness through well-known deep learning. The customer feature extraction unit 23 is an example of a first feature extraction unit in the present disclosure.

[0098] The customer characteristic storage unit 24 stores the customer characteristics extracted by the customer characteristic extraction unit 23 in association with the product registration file 123. The customer characteristic storage unit 24 is an example of a first storage unit in the present disclosure.

[0099] When product registration is completed, the transaction code issuing unit 25 issues a transaction code that uniquely identifies the product registration file 123. The transaction code issuing unit 25 also prints and issues the issued transaction code using the printer 144, for example, in the form of a barcode.

[0100] In response to an instruction from the settlement device 30, the product registration file output unit 26 outputs the product registration file 123 to the settlement device 30. In addition, in response to an instruction from the exit gate 50, the product registration file output unit 26 outputs the product registration file 123 to the exit gate 50.

[0101] The control unit 31 of the settlement device 30 loads and runs the control program 321 in RAM 313, thereby realizing the following functional units: a transaction code reading unit 41, a product registration file acquisition unit 42, a customer characteristic extraction unit 43, a customer characteristic comparison unit 44, a payment method acceptance unit 45, a settlement processing unit 46, a customer characteristic storage unit 47, and an operator change guidance unit 48, all of which are shown in Fig. 10. Note that some or all of these functional units may be realized by dedicated hardware.

[0102] The transaction code reading unit 41 reads the transaction code issued by the merchandise registration device 10 and printed by the printer 144 .

[0103] The product registration file acquisition unit 42 acquires the product registration file 123 corresponding to the transaction code read by the transaction code reading unit 41 from the product registration device 10 .

[0104] Next, the customer feature extraction unit 43 captures an image using the camera 347. The customer feature extraction unit 43 extracts the features of the customer making the payment from the image captured by the camera 347. It is preferable that the customer feature extraction unit 43 processes multiple images captured repeatedly and extracts the customer's features from each image. The customer feature extraction unit 43 extracts the customer making the payment and their features by, for example, using a recognition algorithm that uses a learning model that has learned person-likeness through well-known deep learning. The customer feature extraction unit 43 is an example of a second feature extraction unit in the present disclosure.

[0105] The customer feature comparison unit 44 compares the customer features stored in the product registration file 123 with the customer features extracted by the customer feature extraction unit 43 to determine whether they match.

[0106] The payment method acceptance unit 45 accepts the payment method (settlement method) based on the customer's operation information.

[0107] The settlement processing unit 46 performs settlement related to the product registration file 123 using the method accepted by the payment method acceptance unit 45, on the condition that the customer feature comparison unit 44 determines that the customer features stored in the customer feature storage unit 24 match the customer features extracted by the customer feature extraction unit 43. The settlement processing unit 46 also generates a settlement file 322 indicating the result of the settlement. The settlement processing unit 46 also issues a receipt on which the result of the settlement is printed.

[0108] The customer characteristic storage unit 47 associates the customer characteristics extracted by the customer characteristic extraction unit 43 with information indicating that payment has been completed, and stores the information in the payment file 322 that stores the payment details. The customer characteristic storage unit 47 is an example of a second storage unit in the present disclosure.

[0109] The operator change guidance unit 48 provides guidance to the customer who has registered a product in the product registration device 10 to settle the bill, on the condition that the customer characteristics stored in the customer characteristic storage unit 24 do not match the customer characteristics extracted by the customer characteristic extraction unit 43. The operator change guidance unit 48 may provide guidance by displaying a guidance message on the display device 341, or may provide audio guidance from a speaker not shown in Fig. 7. The operator change guidance unit 48 is an example of an operator guidance unit in the present disclosure.

[0110] The control unit 51 of the exit gate 50 implements the customer characteristic extraction unit 61, the customer characteristic comparison unit 62, the door opening / closing control unit 63, and the notification unit 64 shown in Fig. 10 as functional units by loading and running the control program 522 in the RAM 513. Note that some or all of these functional units may be implemented by dedicated hardware.

[0111] The customer feature extraction unit 61 captures images using the camera 541. The customer feature extraction unit 61 extracts the features of customers before they pass through the exit gate 50 from the images captured by the camera 541. It is preferable that the customer feature extraction unit 61 processes multiple images captured repeatedly and extracts the features of customers from each image. The customer feature extraction unit 61 extracts customers and their features before they leave by, for example, using a recognition algorithm that uses a learning model that has learned person-likeness through well-known deep learning. The customer feature extraction unit 61 is an example of a third feature extraction unit in the present disclosure.

[0112] The customer feature comparison unit 62 compares whether the customer features extracted by the customer feature extraction unit 61 match with the customer features stored in the customer feature storage unit 47. The customer feature comparison unit 62 also compares whether the customer features extracted by the customer feature extraction unit 61 match with the customer features stored in the customer feature storage unit 24.

[0113] The door opening / closing control unit 63 opens the door 545 and allows the customer to exit, on the condition that the customer feature comparison unit 62 determines that the customer features extracted by the customer feature extraction unit 61 match the customer features stored in the customer feature storage unit 47. In this case, the door opening / closing control unit 63 determines that the customer is a customer who has registered a product and paid. Furthermore, the door opening / closing control unit 63 opens the door 545 and allows the customer to exit, on the condition that the customer feature comparison unit 62 does not determine that the customer features extracted by the customer feature extraction unit 61 match the customer features stored in the customer feature storage unit 47 and the customer features stored in the customer feature storage unit 24. In this case, the door opening / closing control unit 63 determines that the customer is a companion customer who has not registered a product or paid. The door opening / closing control unit 63 is an example of an exit control unit in the present disclosure.

[0114] The notification unit 64 issues a notification by closing the door 545 and turning on or flashing the warning light 543, on the condition that the customer feature comparison unit 62 does not determine that the customer feature extracted by the customer feature extraction unit 61 of the exit gate 50 matches the customer feature stored in the customer feature storage unit 47 of the settlement device 30, and the customer feature comparison unit 62 determines that the customer feature extracted by the customer feature extraction unit 61 of the exit gate 50 matches the customer feature stored in the customer feature storage unit 24 of the merchandise registration device 10. The notification unit 64 may further include a speaker (not shown in FIG. 4) and issue a notification by outputting sound or voice from the speaker.

[0115] (Processing flow performed by the product registration device) The flow of processing performed by the merchandise registration device 10 included in the self-checkout system 100 will be described with reference to Fig. 11. Fig. 11 is a flowchart showing an example of the flow of processing performed by the merchandise registration device included in the self-checkout system of the first embodiment.

[0116] The product code reader 21 determines whether the product code has been read from the code symbol attached to the product (step S11). If it is determined that the product code has been read (step S11: Yes), the process proceeds to step S12. On the other hand, if it is not determined that the product code has been read (step S11: No), step S11 is repeated.

[0117] If it is determined in step S11 that the product code has been read, customer feature extraction unit 23 takes an image with camera 145 (step S12). At this time, customer feature extraction unit 23 may take a plurality of consecutive images.

[0118] The customer feature extraction unit 23 extracts the features of the customer who is registering the product from the image captured by the camera 145 (step S13).

[0119] The product registration unit 22 updates the product registration file 123 by registering the product code read in step S11 in the product registration file 123 (step S14).

[0120] The product registration unit 22 determines whether product registration is complete (step S15). If it is determined that product registration is complete (step S15: Yes), the process proceeds to step S16. On the other hand, if it is not determined that product registration is complete (step S15: No), the process returns to step S11. Note that the product registration unit 22 determines that product registration is complete when, for example, a registration completion button displayed on the display device 341 is pressed.

[0121] If it is determined in step S15 that the product registration is completed, the transaction code issuing unit 25 issues a transaction code that uniquely identifies the product registration file 123 (step S16).

[0122] Furthermore, the transaction code issuing unit 25 prints and issues the issued transaction code using the printer 144 (step S17).

[0123] Next, the customer feature storage unit 24 stores the customer features extracted by the customer feature extraction unit 23 in association with the merchandise registration file 123 (step S18). After that, the merchandise registration device 10 ends the process.

[0124] In this way, the product registration device 10 takes an image of the customer and extracts their features each time a product is registered. The customer feature storage unit 24 preferably stores, with priority, features commonly extracted from multiple images. This allows for more accurate storage of customer features.

[0125] (Processing flow performed by the settlement device) The flow of processing performed by the settlement device 30 included in the self-checkout system 100 will be described with reference to Fig. 12. Fig. 12 is a flowchart showing an example of the flow of processing performed by the settlement device included in the self-checkout system of the first embodiment.

[0126] The transaction code reader 41 determines whether the scanner 343 has read the transaction code (step S21). If it is determined that the transaction code has been read (step S21: Yes), the process proceeds to step S22. On the other hand, if it is not determined that the transaction code has been read (step S21: No), step S21 is repeated.

[0127] If it is determined in step S21 that the transaction code has been read, the product registration file acquisition unit 42 acquires the product registration file 123 corresponding to the transaction code read by the transaction code reading unit 41 from the product registration device 10 (step S22).

[0128] The customer feature extraction unit 43 captures an image with the camera 347 (step S23). At this time, the customer feature extraction unit 43 may capture a plurality of consecutive images.

[0129] Next, the customer feature extraction unit 43 extracts the features of the customer making the payment from the image captured by the camera 347 (step S24).

[0130] The customer feature comparison unit 44 compares the customer features stored in the product registration file 123 acquired in step S22, i.e., the features of the customer who registered the product, with the customer features extracted by the customer feature extraction unit 43 to determine whether they match (step S25). If it is determined that the customer features match (step S25: Yes), the process proceeds to step S26. On the other hand, if it is determined that the customer features do not match (step S25: No), the process proceeds to step S31.

[0131] If it is determined in step S25 that the customer's characteristics match, the payment method acceptance unit 45 accepts the settlement method (payment method) based on the customer's operation information (step S26).

[0132] Next, the settlement processing unit 46 settles the payment using the settlement method accepted in step S26 (step S27).

[0133] When the settlement is completed, the settlement processing unit 46 generates a settlement file 322 indicating the result of the settlement (step S28).

[0134] The customer feature storage unit 47 stores the customer features extracted by the customer feature extraction unit 43 in association with the settlement file 322 (step S29).

[0135] The settlement processing unit 46 issues a receipt on which the settlement result is printed from the receipt printer 346 (step S30). After that, the settlement device 30 ends the process.

[0136] Return to step S25. If it is determined in step S25 that the customer characteristics do not match, the operator change notification unit 48 notifies the customer who registered the product in the product registration device 10 that the payment will be made by the customer (step S31). Thereafter, the payment confirmation device 30 returns to step S23 and continues processing.

[0137] (Processing flow performed by the exit gate) The flow of processing performed by the exit gate 50 included in the self-checkout system 100 will be described with reference to Fig. 13. Fig. 13 is a flowchart showing an example of the flow of processing performed by the exit gate included in the self-checkout system of the first embodiment.

[0138] The customer feature extraction unit 61 uses the camera 541 to capture an image of the customer before passing through the exit gate 50 (step S41). At this time, the customer feature extraction unit 61 may capture a plurality of consecutive images.

[0139] Next, the customer feature extraction unit 61 extracts the features of the customer before passing through the exit gate 50 from the image captured by the camera 541 (step S42).

[0140] The customer feature comparison unit 62 determines whether there is a payment file 322 stored in the settlement device 30 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S43). If it is determined that there is a payment file 322 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S43: Yes), the process proceeds to step S44. On the other hand, if it is not determined that there is a payment file 322 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S43: No), the process proceeds to step S45.

[0141] In step S43, if it is determined that there is a payment file 322 that stores the same features as those extracted by the customer feature extraction unit 61, the door opening / closing control unit 63 opens the door 545 and allows the customer to exit (step S44). The door opening / closing control unit 63 closes the opened door 545 after a predetermined time required for the customer to exit has elapsed. The length of the predetermined time is set appropriately. Thereafter, the exit gate 50 ends the process.

[0142] On the other hand, if it is determined in step S43 that there is no payment file 322 storing the same features as the features extracted by the customer feature extraction unit 61, the customer feature comparison unit 62 determines whether there is a product registration file 123 stored in the product registration device 10 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S45). If it is determined that there is a product registration file 123 storing the same features as the features extracted by the customer feature extraction unit 61 (step S45: Yes), the process proceeds to step S46. On the other hand, if it is not determined that there is a product registration file 123 storing the same features as the features extracted by the customer feature extraction unit 61 (step S45: No), the process proceeds to step S44.

[0143] In step S45, if it is determined that there is a product registration file 123 that stores the same features as those extracted by customer feature extraction unit 61, door opening / closing control unit 63 closes door 545 (more accurately, leaves door 545 closed) (step S46). In this case, either a customer different from the customer who registered the product has made a payment at payment device 30, or a product has been registered but not yet made a payment.

[0144] Next, the notification unit 64 issues a notification using the warning light 543 (step S47). Thereafter, the exit gate 50 ends the process. Note that a store clerk who notices the notification will rush to the customer, explain the situation, and confirm the details of the transaction.

[0145] On the other hand, if it is determined in step S45 that there is no product registration file 123 that stores the same characteristics as those extracted by the customer characteristic extraction unit 61, the corresponding customer is determined to be a customer who visited the store together with the customer who registered the product and made the payment, and the exit gate 50 proceeds to step S44, opens the door 545, and allows the customer to exit.

[0146] (Operation and effect of the first embodiment) As described above, the self-checkout system 100 of the first embodiment comprises a product registration device 10 that registers products to be purchased by a customer's own operation, a payment settlement device 30 that settles the payment for the registered products by a customer's own operation, and an exit gate 50 that allows the customer to exit the area where the payment settlement device 30 is installed. The product registration device 10 comprises a product registration unit that generates a product registration file 123 (product registration information) in which identification information of products purchased by customers is registered, a customer feature extraction unit 23 (first feature extraction unit) that extracts characteristics of customers who register products, and a customer feature storage unit 24 (first storage unit) that stores the customer features extracted by the customer feature extraction unit 23 in association with the product registration file 123. The payment device 30 includes a customer feature extraction unit 43 (second feature extraction unit) that extracts the features of a customer who is making a payment; a payment processing unit 46 that performs payment related to the product registration file 123 on the condition that the customer features stored in the customer feature storage unit 24 match the customer features extracted by the customer feature extraction unit 43; and a customer feature storage unit 47 (second storage unit) that stores the customer features extracted by the customer feature extraction unit 43 in association with information indicating that payment has been completed. The exit gate 50 includes a customer feature extraction unit 61 (third feature extraction unit) that extracts the features of a customer before passing through the exit gate 50; and a door opening / closing control unit 63 (exit control unit) that allows a customer to exit the store through the exit gate 50 on the condition that the customer features extracted by the customer feature extraction unit 61 match the customer features stored in the customer feature storage unit 47. Therefore, since there is no need to store the features of customers other than those who have registered products, it is possible to prevent customers from leaving the store with unpaid products with a smaller computational load.

[0147] Furthermore, in the self-checkout system 100 of the first embodiment, the settlement device 30 further includes an operator change guidance unit 48 (operator guidance unit) that guides the customer who registered the product in the product registration device 10 to settle the payment, on the condition that the customer characteristics stored in the customer characteristic storage unit 24 (first storage unit) do not match the customer characteristics extracted by the customer characteristic extraction unit 43 (second characteristic extraction unit). Therefore, by guiding the customer who registered the product to settle the payment for the registered product, it is possible to prevent the act of only registering products and leaving without storing the characteristics of any customer other than the customer who registered the product.

[0148] Furthermore, in the self-checkout system 100 of the first embodiment, the door opening / closing control unit 63 (exit control unit) further allows a customer to exit through the exit gate 50 on the condition that the customer characteristics extracted by the customer characteristic extraction unit 61 (third characteristic extraction unit) do not match the customer characteristics stored in the customer characteristic storage unit 24 (first storage unit) and the customer characteristics stored in the customer characteristic storage unit 47 (second storage unit). Therefore, accompanying customers who have not registered products or paid for their purchases can unconditionally exit through the exit gate 50 because their characteristics are not stored in advance. This prevents accompanying customers from being held up at the exit gate 50.

[0149] Furthermore, in the self-checkout system 100 of the first embodiment, after the product registration unit 22 has registered all products, the customer characteristic storage unit 24 (first storage unit) stores the characteristics of the customer who registered the products in association with the product registration file 123 (product registration information). Therefore, while the products are being registered, the customer characteristics can be repeatedly extracted, and highly reliable characteristics can be stored.

[0150] (Second embodiment) Next, a second embodiment of the self-checkout system 101 will be described. The self-checkout system 101 has the same functions as the self-checkout system 100 described in the first embodiment, but differs only in the detailed configuration and functions.

[0151] (Outline of self-checkout system configuration) The schematic configuration of the self-checkout system 101 will be described with reference to Fig. 14. Fig. 14 is a block diagram showing an example of the schematic configuration of the self-checkout system of the second embodiment.

[0152] The self-checkout system 101 has a configuration in which a server device 70 is further added to the configuration of the self-checkout system 100 described in the first embodiment.

[0153] The server device 70 acquires the product registration file 123 generated by the product registration device 10 and the settlement file 322 generated by the settlement device 30, and manages them in a unified manner.

[0154] In the first embodiment, the exit gate 50 communicates with the product registration device 10 and the settlement device 30, respectively, and refers to the product registration file 123 and the payment file 322. In contrast, in the self-checkout system 101 of the present embodiment, the exit gate 50 communicates with the server device 70, and refers to the product registration file 722 (see FIG. 15) and the payment file 723 (see FIG. 15).

[0155] (Server hardware configuration) The hardware configuration of the server device 70 will be described with reference to Fig. 15. Fig. 15 is a hardware block diagram showing an example of the hardware configuration of the server device included in the self-checkout system.

[0156] The server device 70 has a configuration in which a control unit 71, a storage unit 72, and a communication controller 74 are connected to one another via an internal bus 73.

[0157] The control unit 71 controls the overall operation of the server device 70. The control unit 71 includes a CPU 711, a ROM 712, and a RAM 713. The CPU 711 is connected to the ROM 712 and the RAM 713 via internal buses such as an address bus and a data bus. The CPU 711 loads various programs stored in the ROM 712 and the storage unit 72 into the RAM 713. The CPU 711 controls the operation of the server device 70 by operating in accordance with the various programs loaded into the RAM 713. In other words, the control unit 71 has the configuration of a typical computer.

[0158] The storage unit 72 is a storage device such as an HDD or SSD. Alternatively, the storage unit 72 may be a non-volatile memory such as a flash memory that retains stored information even when the power is turned off. The storage unit 72 stores a control program 721, a product registration file 722, and a payment file 723.

[0159] The control program 721 is a program that controls the overall operation of the server device 70. The control program 721 may be provided in a state stored in the storage unit 72, or may be provided by being recorded in an installable or executable file on a computer-readable non-transitory recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD. The control program 721 may also be provided by being stored on a computer connected to a network and downloaded via the network. Furthermore, the control program 721 may be provided or distributed via a network such as the Internet.

[0160] The product registration file 722 is the product registration file 123 generated by the product registration device 10 and output to the server device 70. Although different reference numerals are used to make the explanation easier to understand, the product registration file 722 and the product registration file 123 are the same file. Note that the product registration file 722 may include identification information that uniquely identifies the product registration device 10 that generated it.

[0161] The settlement file 723 is the settlement file 322 generated by the settlement device 30 and output to the server device 70. Although different reference numerals are used to make the explanation easier to understand, the settlement file 723 and the settlement file 322 are the same file. The settlement file 723 may include identification information that uniquely identifies the settlement device 30 that generated it.

[0162] The control unit 71 communicates with the product registration device 10, the settlement device 30, and the exit gate 50 via the communication controller 74. The server device 70 acquires the product registration file 123 from the product registration device 10. The server device 70 also acquires the settlement file 322 from the settlement device 30. The server device 70 then outputs the product registration file 722 corresponding to the specified transaction code to the settlement device 30. The server device 70 also accepts a reference instruction to the product registration file 722 and the settlement file 723 from the exit gate 50.

[0163] The hardware configuration of the product registration device 10 in this embodiment is almost the same as the configuration described in the first embodiment (see FIG. 5), so a repeated description will be omitted. The only difference is that the communication controller 15 connects the product registration device 10 and the server device 70 so that they can communicate with each other.

[0164] The hardware configuration of the settlement device 30 in this embodiment is almost the same as the configuration described in the first embodiment (see FIG. 7), so a repeated description will be omitted. The only difference is that the communication controller 35 connects the settlement device 30 and the server device 70 so that they can communicate with each other.

[0165] The hardware configuration of the exit gate 50 in this embodiment is almost the same as the configuration described in the first embodiment (see FIG. 9), so a repeated description will be omitted. The only difference is that the communication controller 55 connects the exit gate 50 and the server device 70 so that they can communicate with each other.

[0166] (Functional configuration of self-checkout system) The functional configuration of the self-checkout system 101 will be described with reference to Fig. 16. Fig. 16 is a functional block diagram showing an example of the functional configuration of the self-checkout system of the second embodiment.

[0167] The control unit 11 of the product registration device 10 deploys the control program 121 in the RAM 113 and runs it to realize the product code reading unit 21, product registration unit 22, customer feature extraction unit 23, customer feature storage unit 24, and product registration file output unit 27 as functional units shown in Fig. 16. Note that some or all of these functional units may be realized by dedicated hardware.

[0168] The functions of the product code reading unit 21, product registration unit 22, customer feature extraction unit 23, and customer feature storage unit 24 are the same as those described in the first embodiment, and therefore will not be described again.

[0169] The product registration file output unit 27 outputs the product registration file 123 that it has generated to the server device 70.

[0170] The control unit 31 of the settlement device 30 deploys and operates the control program 321 in RAM 313, thereby realizing as functional units the product registration file acquisition unit 49, customer characteristic extraction unit 43, customer characteristic comparison unit 44, payment method acceptance unit 45, settlement processing unit 46, customer characteristic storage unit 47, operator change guidance unit 48, and payment file output unit 68 shown in Fig. 16. Note that some or all of these functional units may be realized by dedicated hardware.

[0171] The functions of the customer characteristic extraction unit 43, payment method acceptance unit 45, settlement processing unit 46, customer characteristic storage unit 47, and operator change guidance unit 48 are the same as those described in the first embodiment, so further explanation will be omitted.

[0172] The customer feature comparison unit 44 compares and references the product registration files 722 stored in the server device 70 to see if there is a product registration file 722 that stores features that match the customer features extracted by the customer feature extraction unit 43.

[0173] The product registration file acquisition unit 49 acquires an instruction to start payment from the customer. Specifically, the product registration file acquisition unit 49 determines that an instruction to start payment has been given when it detects that the payment start button displayed on the display device 341 has been pressed. In addition, the product registration file acquisition unit 49 acquires from the server device 70 a product registration file 722 that stores the same customer characteristics as those extracted by the customer characteristic extraction unit 43 of the payment device 30.

[0174] The payment file output unit 68 outputs the payment file 322 that it has generated to the server device 70.

[0175] The control unit 71 of the server device 70 deploys the control program 721 in the RAM 713 and runs it to realize, as functional units, a product registration file acquisition unit 81 and a payment file acquisition unit 82 shown in Fig. 16. Note that some or all of these functional units may be realized by dedicated hardware.

[0176] The product registration file acquisition unit 81 acquires the generated product registration file 123 from the product registration device 10.

[0177] The settlement file acquisition unit 82 acquires the generated settlement file 322 from the settlement device 30.

[0178] The control unit 51 of the exit gate 50 implements, as functional units, a customer characteristic extraction unit 61, a customer characteristic comparison unit 62, a door opening / closing control unit 63, and an alarm unit 64 shown in Fig. 16 by loading and running the control program 522 in the RAM 513. Note that some or all of these functional units may be implemented by dedicated hardware.

[0179] The functions of the customer feature extraction unit 61, the door opening / closing control unit 63, and the notification unit 64 are the same as those described in the first embodiment, so a repeated description will be omitted.

[0180] The customer feature comparison unit 62 compares whether there is a payment file 723 in which the same features as the features extracted by the customer feature extraction unit 61 are stored among the payment files 723 stored in the server device 70. In addition, the customer feature comparison unit 62 compares whether there is a product registration file 722 in which the same features as the features extracted by the customer feature extraction unit 61 are stored among the product registration files 722 stored in the server device 70.

[0181] (Processing flow performed by the product registration device) The flow of processing performed by the merchandise registration device 10 included in the self-checkout system 101 will be described with reference to Fig. 17. Fig. 17 is a flowchart showing an example of the flow of processing performed by the merchandise registration device included in the self-checkout system of the second embodiment.

[0182] The product code reader 21 determines whether the product code has been read from the code symbol attached to the product (step S51). If it is determined that the product code has been read (step S51: Yes), the process proceeds to step S52. On the other hand, if it is not determined that the product code has been read (step S51: No), step S51 is repeated.

[0183] If it is determined in step S51 that the product code has been read, customer feature extraction unit 23 takes an image with camera 145 (step S52). At this time, customer feature extraction unit 23 may take a plurality of consecutive images.

[0184] The customer feature extraction unit 23 extracts the features of the customer who is registering the product from the image captured by the camera 145 (step S53).

[0185] The product registration unit 22 updates the product registration file 123 by registering the product code read in step S51 in the product registration file 123 (step S54).

[0186] The product registration unit 22 determines whether product registration is complete (step S55). If it is determined that product registration is complete (step S55: Yes), the process proceeds to step S56. On the other hand, if it is not determined that product registration is complete (step S55: No), the process returns to step S51. Note that the product registration unit 22 determines that product registration is complete when, for example, a registration completion button displayed on the display device 341 is pressed.

[0187] If it is determined in step S15 that the product registration is completed, the transaction code issuing unit 25 issues a transaction code that uniquely identifies the product registration file 123 (step S16).

[0188] Next, the customer feature storage unit 24 stores the customer features extracted by the customer feature extraction unit 23 in association with the product registration file 123 (step S56).

[0189] The product registration file output unit 27 outputs the product registration file 123 to the server device 70 (step S57). The server device 70 stores the acquired product registration file 123 as the product registration file 722. Thereafter, the product registration device 10 ends the process.

[0190] (Processing flow performed by the settlement device) The flow of processing performed by the settlement device 30 included in the self-checkout system 101 will be described with reference to Fig. 18. Fig. 18 is a flowchart showing an example of the flow of processing performed by the settlement device included in the self-checkout system of the second embodiment.

[0191] The product registration file acquisition unit 49 determines whether the customer has instructed to start payment (step S61). If it is determined that the customer has instructed to start payment (step S61: Yes), the process proceeds to step S62. On the other hand, if it is not determined that the customer has instructed to start payment (step S61: No), the process repeats step S61.

[0192] When it is determined in step S61 that an instruction to start payment has been given, the customer feature extraction unit 43 captures an image with the camera 347 (step S62). At this time, the customer feature extraction unit 43 may capture a plurality of consecutive images.

[0193] Next, the customer feature extraction unit 43 extracts the features of the customer making the payment from the image captured by the camera 347 (step S63).

[0194] The customer feature comparison unit 44 determines whether there is a product registration file 722 stored in the server device 70 that stores features that match the customer features extracted by the customer feature extraction unit 43 (step S64). If it is determined that there is a product registration file 722 with matching customer features (step S64: Yes), the process proceeds to step S65. On the other hand, if it is not determined that there is a product registration file 722 with matching customer features (step S64: No), the process proceeds to step S72.

[0195] In step S64, if it is determined that there is a product registration file 722 that matches the customer characteristics, the product registration file acquisition unit 49 acquires from the server device 70 a product registration file 722 that stores the same customer characteristics as those extracted by the customer characteristic extraction unit 43 of the settlement device 30 (step S65).

[0196] The payment method acceptance unit 45 accepts the settlement method (payment method) based on the customer's operation information (step S66).

[0197] Next, the settlement processing unit 46 settles the payment using the settlement method accepted in step S66 (step S67).

[0198] When the settlement is completed, the settlement processing unit 46 generates a settlement file 322 indicating the result of the settlement (step S68).

[0199] The customer characteristic storage unit 47 stores the customer characteristics extracted by the customer characteristic extraction unit 43 in association with the settlement file 322 (step S69).

[0200] The payment file output unit 68 outputs the payment file 322 generated in step S69 to the server device 70 (step S70). The server device 70 stores the acquired payment file 322 as a payment file 723.

[0201] The settlement processing unit 46 issues a receipt on which the settlement result is printed from the receipt printer 346 (step S71). After that, the settlement device 30 ends the process.

[0202] Return to step S64. If it is determined in step S64 that there is no product registration file 722 that matches the customer's characteristics, the operator change guidance unit 48 notifies the customer who registered the product in the product registration device 10 that the customer will be making the payment (step S72). Thereafter, the settlement device 30 returns to step S62 and continues processing.

[0203] (Processing flow performed by the exit gate) The flow of processing performed by the exit gate 50 included in the self-checkout system 101 will be described with reference to Fig. 19. Fig. 19 is a flowchart showing an example of the flow of processing performed by the exit gate included in the self-checkout system of the second embodiment.

[0204] The customer feature extraction unit 61 uses the camera 541 to capture an image of the customer before passing through the exit gate 50 (step S81). At this time, the customer feature extraction unit 61 may capture a plurality of consecutive images.

[0205] Next, the customer feature extraction unit 61 extracts the features of the customer before passing through the exit gate 50 from the image captured by the camera 541 (step S82).

[0206] The customer feature comparison unit 62 determines whether there is a payment file 723 stored in the server device 70 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S83). If it is determined that there is a payment file 723 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S83: Yes), the process proceeds to step S84. On the other hand, if it is not determined that there is a payment file 723 that stores the same features as the features extracted by the customer feature extraction unit 61 (step S83: No), the process proceeds to step S85.

[0207] In step S83, if it is determined that there is a payment file 723 that stores the same features as those extracted by the customer feature extraction unit 61, the door opening / closing control unit 63 opens the door 545 and allows the customer to exit (step S84). The door opening / closing control unit 63 closes the opened door 545 after a predetermined time required for the customer to exit has elapsed. The length of the predetermined time is set appropriately. Thereafter, the exit gate 50 ends the process.

[0208] On the other hand, if it is determined in step S83 that there is no payment file 723 storing the same features as the features extracted by the customer feature extraction unit 61, the customer feature comparison unit 62 determines whether there is a product registration file 722 storing the same features as the features extracted by the customer feature extraction unit 61 among the product registration files 722 stored in the server device 70 (step S85). If it is determined that there is a product registration file 722 storing the same features as the features extracted by the customer feature extraction unit 61 (step S85: Yes), the process proceeds to step S86. On the other hand, if it is not determined that there is a product registration file 722 storing the same features as the features extracted by the customer feature extraction unit 61 (step S85: No), the process proceeds to step S84.

[0209] In step S85, if it is determined that there is a product registration file 722 that stores the same features as those extracted by the customer feature extraction unit 61, the door opening / closing control unit 63 closes the door 545 (more accurately, keeps the door 545 closed) (step S86). In this case, either a customer other than the customer who registered the product has made a payment at the payment device 30, or a product has been registered but not yet made a payment.

[0210] Next, the notification unit 64 issues a notification using the warning light 543 (step S87). Thereafter, the exit gate 50 ends the process. Note that a store clerk who notices the notification will rush to the customer, explain the situation, and confirm the details of the transaction.

[0211] On the other hand, if it is determined in step S85 that there is no product registration file 722 that stores the same characteristics as those extracted by the customer characteristic extraction unit 61, the corresponding customer is determined to be a customer who visited the store together with the customer who registered the product and made the payment, and the exit gate 50 proceeds to step S84, opens the door 545, and allows the customer to exit.

[0212] (Effects of the second embodiment) As described above, in the self-checkout system 101 of the second embodiment, the settlement processing unit 46 retrieves the product registration file 722 stored in the server device 70 from the product registration file 123 (product registration information) generated by the product registration device 10 (more precisely, the product registration file 722 stored in the server device 70) in association with features that match the customer features extracted by the customer feature extraction unit 43 (second feature extraction unit), and then settles the account. Therefore, when product registration is complete, settlement for the registered products can be performed without generating a transaction code. This simplifies the process.

[0213] Furthermore, in the self-checkout system 101 of the second embodiment, the settlement device 30 communicates with the server device 70 to acquire product information and customer characteristics. Furthermore, the exit gate 50 communicates with the server device 70 to acquire product registration information and characteristics of the customer who registered the product. Furthermore, the exit gate 50 communicates with the server device 70 to acquire characteristics of the customer who registered the product and characteristics of the customer who settled the payment. Therefore, access to the product registration device 10 and the settlement device 30 does not occur each time communication is performed, and it is possible to prevent the product registration device 10 and the settlement device 30 from being accessed from outside while they are in use, which would otherwise cause a decrease in processing capacity.

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

[0215] 10 Product registration device 100,101 Self-checkout system 122 Product Master 123 Product registration file (product registration information) 141 Display Devices 142 Operating Devices 143 Scanner 144 printers 145 Camera 146 Warning light 21 Product code reader 22 Product Registration Department 23 Customer feature extraction unit (first feature extraction unit) 24 Customer characteristics memory unit (first memory unit) 25 Transaction Code Numbering Section 26,27 Product registration file output section 30 Payment device 322 Payment File 343 Scanner 344 Payment Terminal 345 Change machine 346 Receipt Printer 347 Camera 348 Warning light 41 Transaction code reader 42,49 Product registration file acquisition section 43 Customer feature extraction unit (second feature extraction unit) 44 Customer Characteristics Comparison Section 45 Payment Method Reception Department 46 Settlement Processing Section 47 Customer characteristics memory unit (second memory unit) 48 Operator change guide section (operator guide section) 50 Exit Gate 541 Camera 542 Gate Controller 543 Warning light 545 Door 61 Customer feature extraction unit (third feature extraction unit) 62 Customer Characteristics Comparison Section 63 Door opening / closing control unit (exit control unit) 64 Information Department 68 Payment File Output Section 70 Server equipment 722 Product Registration File 723 Payment File 81 Product registration file acquisition unit 82 Payment File Acquisition Department [Prior art documents] [Patent documents]

[0216] [Patent Document 1] Japanese Patent Publication No. 2022-9251

Claims

1. A self-checkout system comprising: a product registration device that a customer operates to register products to be purchased; a payment device that the customer operates to settle payments for the registered products; and an exit gate that allows customers to exit an area where the payment device is installed, The product registration device a product registration unit that generates product registration information in which identification information of products purchased by customers is registered; a first feature extraction unit that extracts features of a customer who registers a product; a first storage unit that stores the customer characteristics extracted by the first characteristic extraction unit and the product registration information in association with each other, The settlement device a second feature extraction unit that extracts features of a customer making a payment; a payment processing unit that performs payment related to the product registration information on the condition that the customer characteristics stored in the first storage unit and the customer characteristics extracted by the second characteristic extraction unit match; a second storage unit that stores the customer characteristics extracted by the second characteristic extraction unit in association with information indicating that payment has been completed, The exit gate is a third feature extraction unit that extracts features of a customer before passing through the exit gate; and an exit control unit that allows the customer to exit through an exit gate on condition that the customer characteristics extracted by the third characteristic extraction unit match the customer characteristics stored in the second storage unit. Self-checkout system.

2. The settlement device The system further includes an operator guidance unit that guides a customer who has registered a product in the product registration device to settle their account, on the condition that the customer characteristics stored in the first storage unit do not match the customer characteristics extracted by the second characteristic extraction unit. The self-checkout system of claim 1 .

3. The exit control unit further allows the customer to exit through the exit gate on condition that the customer characteristics extracted by the third characteristic extraction unit do not match the customer characteristics stored in the first storage unit and the customer characteristics stored in the second storage unit. The self-checkout system of claim 1 .

4. After the product registration unit has registered all the products, the first storage unit stores the product registration information in association with characteristics of the customer who registered the products. The self-checkout system of claim 1 .

5. the settlement processing unit acquires, from the product registration information generated by the product registration device, product registration information stored in association with a feature that matches the customer feature extracted by the second feature extraction unit, and performs settlement. The self-checkout system of claim 1 .

6. A computer that controls a self-checkout system that includes a product registration device that registers products to be purchased by a customer's own operation, a payment device that performs payment for the registered products by a customer's own operation, and an exit gate that allows customers to exit an area where the payment device is installed. The product registration device, a product registration unit that generates product registration information in which identification information of the product purchased by the customer is registered; a first feature extraction unit that extracts features of a customer who registers a product; a first storage unit that stores the customer characteristics extracted by the first characteristic extraction unit and the product registration information in association with each other, The settlement device, a second feature extraction unit that extracts features of a customer making a payment; a payment processing unit that performs payment related to the product registration information on the condition that the customer characteristics stored in the first storage unit and the customer characteristics extracted by the second characteristic extraction unit match; a second storage unit that stores the customer characteristics extracted by the second characteristic extraction unit in association with information indicating that payment has been completed, The exit gate, a third feature extraction unit that extracts features of a customer before passing through the exit gate; A program that functions as an exit control unit that allows a customer to exit through an exit gate on the condition that the customer characteristics extracted by the third feature extraction unit match the customer characteristics stored in the second memory unit.

Images