Server device and program

Abstract

To provide a server device and a program for supporting a customer making a payment.SOLUTION: A server includes: acquisition means for acquiring, from a terminal device being operated by a customer, first identification information to identify a product that the customer purchases and second identification information to identify the customer or the terminal device; registration means for registering the first identification information and the second identification information in association with each other in a data table; first calculation means for calculating, for each piece of the second identification information, a first time period to be required to make a payment for the product on the basis of the number of pieces of registered first identification information; allocation means for allocating each piece of the second identification information to any one of a plurality of payment devices on the basis of the first time period of the second identification information; second calculation means for calculating, for each piece of the second identification information, a second time period to be required to make a payment for the product at the allocation destination payment device on the basis of the first time period of the second identification information and a result of the allocation to the payment devices; and notification means for notifying the terminal device of the allocation destination payment device and the second time period.SELECTED DRAWING: Figure 10

Description

[Technical field]

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

[0002] Traditionally, in stores such as supermarkets, store clerks operate Point Of Sale (POS) terminals to register products and make payments (also called accounting or settlement). In recent years, store systems have become available that allow customers to register products while moving around the store using a terminal device attached to a shopping cart or a device such as a smartphone owned by the customer, and then allow the store clerk or the customer to pay for the registered products using a payment device installed in the store.

[0003] In the above-mentioned store system configuration, customers move to a payment device to make a payment, but when it is crowded, they have to wait in line around the payment device until a payment device becomes available. This so-called cash register queue is dissatisfying for customers, so there is a need to improve it. For example, a technology has been proposed that, when a notification of the completion of product registration is received from a customer's terminal device, a payment device with a short waiting time is selected and guidance information indicating the selected payment device is output to the customer's terminal device.

[0004] However, in the conventional technology described above, the customer cannot grasp the status of the payment device until the customer notifies the customer that he or she has completed registration. Also, if other customers notify the customer that they have completed registration at the same time, there is a possibility that multiple customers will rush to the same payment device, and there is room for further improvement. Summary of the Invention [Problem to be solved by the invention]

[0005] The problem to be solved by the present invention is to provide a server device and a program capable of supporting a customer in relation to payment. [Means for solving the problem]

[0006] The server device of the embodiment includes an acquisition means for acquiring, from a terminal device operated by a customer, first identification information capable of identifying a product purchased by the customer and second identification information capable of identifying the customer or the terminal device; a registration means for associating the first identification information and the second identification information acquired by the acquisition means and registering them in a data table; a first calculation means for calculating a first time required to pay for the product for each of the second identification information based on the registered number of the first identification information registered in association with the second identification information; an allocation means for assigning each of the second identification information to one of a plurality of payment devices based on the first time of the second identification information; a second calculation means for calculating a second time required to pay for the product at the payment device to which the product is assigned, for each of the second identification information, based on the first time of the second identification information and the allocation result of the payment device; and a notification means for notifying the terminal device corresponding to the second identification information of the payment device to which the product is assigned and the second time. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a store system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the terminal device according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of a server according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a data configuration of the product master according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a data configuration of a sales registration table according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a functional configuration of a terminal device and a server according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of a payment waiting table according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a data configuration of the intermediate table according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a data configuration of the allocation management table according to the embodiment. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of product sales data processing performed between the terminal device and the server according to the embodiment. [Figure 11] FIG. 11 is a flowchart illustrating an example of a payment support process performed by the server according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] The server device and the program according to the present embodiment will be described in detail below with reference to the accompanying drawings. In the following embodiment, a store system introduced in a store such as a supermarket will be described as an example. Note that the invention is not limited to this application example.

[0009] Fig. 1 is a diagram showing an example of a store system 1 according to an embodiment. As shown in Fig. 1, the store system 1 includes a terminal device 2, a server 4, and a payment device 8. The server 4 and the payment device 8 are communicatively connected via a network Na.

[0010] The network Na may be the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, or the like, either alone or in appropriate combination. As an example, the network Na may be a combination of the Internet and a mobile communication network.

[0011] In addition, a wireless access point 7 is connected to the network Na. The wireless access point 7 is connected to the terminal device 2 via a network Nb such as a wireless LAN. Therefore, the terminal device 2 can communicate with the server 4 and the payment device 8.

[0012] The cart 3 is a shopping cart that can be moved while loaded with products. A customer borrows the cart 3 from a store, and while moving around the store with the cart 3, loads the products he or she wants to purchase from the products on display into the cart.

[0013] The terminal device 2 is a terminal device operated by a customer who uses the store. The terminal device 2 acquires first identification information (hereinafter also referred to as a product code) capable of identifying a product purchased by the customer from an image captured by the imaging unit 29 described later, and executes a sales registration process for the product. Here, the sales registration process means a process of transmitting the product code of the product to be purchased by the customer to the server 4 and registering it in the server 4.

[0014] For example, the terminal device 2 reads a symbol, such as a barcode or a two-dimensional code, attached to a product from an image of the product, and acquires a product code, such as a JAN code, stored in the symbol.

[0015] The terminal device 2 may be, for example, a tablet terminal that is attached to the cart 3 and moves together with the cart 3. The terminal device 2 may also be a smartphone carried by the customer or a mobile terminal rented out by the store.

[0016] The server 4 is an example of a server device. The server 4 uses the terminal device 2 as a user interface terminal and performs information processing to provide a service for carrying out a buying and selling transaction of goods in a store where the user interface terminal is used. The server 4 may be, for example, a store server provided in the store, or a server device provided outside the store. Note that, although the server 4 is realized by a single device in this embodiment, it may also be a cloud server (or a cloud system) realized by multiple devices connected to a network.

[0017] The server 4 stores a product master in which product names, prices, etc. of products sold in a store are registered in a database (not shown) or the like, and provides the product master to the terminal device 2 and the payment device 8. The server 4 also stores and manages the product codes transmitted from each of the terminal devices 2 in association with second identification information (hereinafter also referred to as customer identification information) capable of identifying the terminal device 2 that transmitted the product or the customer operating the terminal device 2. The server 4 also calculates the time required for payment of the product corresponding to the product code (hereinafter also referred to as payment time) based on the product code stored for each piece of customer identification information, and assigns a payment device 8 to which the payment will be made, for each piece of customer identification information. Here, the payment time is an example of the first time.

[0018] The server 4 also notifies the terminal device 2 corresponding to the customer identification information of information that can identify the allocated payment device 8 (hereinafter also referred to as a register number) and the time required to settle the commodity at the allocated payment device (hereinafter also referred to as a register waiting time) derived based on the settlement required time. Here, the register waiting time is an example of the second time.

[0019] The settlement device 8 is an example of a settlement device (also called an accounting machine or settlement device) installed in a store. The settlement device 8 executes settlement processing for products based on product information registered in the server 4. The settlement processing includes processing such as displaying the total price and tax amount of products related to one transaction, calculating and displaying change based on the deposit received from the customer, and issuing a receipt on which product information and settlement information (total price, deposit amount, change amount, etc.) are printed.

[0020] A plurality of payment devices 8 are provided in the checkout area in the store, and each payment device 8 is assigned a unique register number. The register number is also displayed in a visible state, for example, by being written on a display plate or the like attached to the payment device 8. The payment device 8 may be a type of payment device operated by a store clerk, or a self-service type payment device operated by the customer himself.

[0021] Next, the configurations of the above-mentioned terminal device 2 and server 4 will be described.

[0022] Fig. 2 is a diagram showing an example of a hardware configuration of the terminal device 2. As shown in Fig. 2, the terminal device 2 includes a CPU (Central Processing Unit) 21, a ROM (Read Only Memory) 22, a RAM (Random Access Memory) 23, a storage unit 24, a display unit 25, an operation unit 26, a communication unit 27, a connection unit 28, and the like.

[0023] The CPU 21 is an example of a processor, and controls the overall operation of the terminal device 2. The ROM 22 stores various programs. The RAM 23 is a workspace in which programs and various data are expanded.

[0024] The CPU 21, the ROM 22, and the RAM 23 are connected via a bus or the like to constitute a computer-configured control unit 200. In the control unit 200, the CPU 21 operates in accordance with a program stored in the ROM 22 or the storage unit 24 and loaded in the RAM 23, thereby executing various types of processing.

[0025] The storage unit 24 has a storage medium such as a hard disk drive (HDD) or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 24 stores programs that the CPU 21 can execute and various setting information. The storage unit 24 also stores customer identification information and the like. The customer identification information may be, for example, an IP address or a terminal ID assigned to the terminal device 2, or account information that can identify a customer who operates the terminal device 2.

[0026] The display unit 25 is a display device such as an LCD (Liquid Crystal Display). The display unit 25 displays various information under the control of the CPU 21. The operation unit 26 is an input device such as a keyboard or a pointing device. The operation unit 26 outputs operation contents input via the input device to the CPU 21. The operation unit 26 may be a touch panel provided on the display unit 25.

[0027] The communication unit 27 is a wired or wireless communication interface connectable to the network Nb. The communication unit 27 is communicatively connected to the wireless access point 7 via the network Nb. The control unit 200 communicates with the server 4 and the payment device 8 via the communication unit 27.

[0028] The connection unit 28 is an interface for connecting a peripheral device. The connection unit 28 is a wired or wireless interface conforming to standards such as USB (Universal Serial Bus) and Bluetooth (registered trademark). In this embodiment, the connection unit 28 is connected to an imaging unit 29.

[0029] The imaging unit 29 is a camera module equipped with an imaging element such as a CCD or a CMOS. The imaging unit 29 may be provided integrally with the terminal device 2, or may be provided separately from the imaging unit 29. Also, instead of the imaging unit 29, a reading device capable of reading a code symbol may be connected to the connection unit 28.

[0030] Fig. 3 is a diagram showing an example of a hardware configuration of the server 4. As shown in Fig. 3, the server 4 includes a CPU 41, a ROM 42, a RAM 43, a storage unit 44, a communication unit 45, and the like.

[0031] The CPU 41 is an example of a processor, and controls the overall operation of the server 4. The ROM 42 stores various programs. The RAM 43 is a workspace in which programs and various data are expanded.

[0032] The CPU 41, the ROM 42, and the RAM 43 are connected via a bus or the like to constitute a computer-configured control unit 400. In the control unit 400, the CPU 41 operates in accordance with a program stored in the ROM 42 or the storage unit 44 and loaded in the RAM 43, thereby executing various types of processing.

[0033] The storage unit 44 has a storage medium such as a HDD or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 44 stores programs that the CPU 41 can execute and various setting information. The storage unit 44 also stores a product master 441, a sales registration table 442, a settlement waiting table 443, an intermediate table 444, an allocation management table 445, and the like.

[0034] The product master 441 is a data table for managing data related to products sold in the store. The sales registration table 442 is a data table for managing product codes transmitted from the terminal device 2 in the sales registration process.

[0035] The payment waiting table 443 is a data table for managing the number of items registered as sales by a customer and the time expected to be required for payment of the items (payment required time). The intermediate table 444 is a data table for storing intermediate data of the process of allocating a payment device 8 as the payment destination to each customer. The allocation management table 445 is a data table for managing the correspondence between each payment device 8 and the customer allocated to the payment device 8.

[0036] Any or all of the settlement waiting table 443, the intermediate table 444, and the allocation management table 445 may be held in the RAM 43.

[0037] The communication unit 45 is a wired or wireless communication interface connectable to the network Na. The communication unit 27 communicates with the terminal device 2 and the payment device 8 via the network Na and the wireless access point 7.

[0038] Fig. 4 is a diagram showing an example of the data configuration of the product master 441. As shown in Fig. 4, the product master 441 stores product codes and product information in association with each other. The product code is an example of identification information capable of identifying (specifying) the type of product sold in a store. The product information is information related to a product corresponding to the product code. For example, the product name, price, genre, etc. are registered in the product information.

[0039] In this embodiment, the server 4 is configured to hold the product master 441, but the present invention is not limited to this, and each of the terminal devices 2 may hold the product master 441. In this case, the server 4 may distribute the product master 441 held by itself to each of the terminal devices 2, so that the product master 441 is locally held by the terminal devices 2.

[0040] Fig. 5 is a diagram showing an example of the data configuration of sales registration table 442. As shown in Fig. 5, sales registration table 442 stores customer identification information and product codes in association with each other. Here, the customer identification information of the customer terminal that transmitted the product code is registered in the customer identification information field. The product code transmitted from the customer terminal is registered in the product code field.

[0041] The data configuration of the sales registration table 442 is not limited to that shown in FIG. 5. For example, product information corresponding to a product code may be registered in association with the product code. Furthermore, date and time information indicating the date and time when the product code was registered may be registered in association with the product code. The data configurations of the payment waiting table 443, the intermediate table 444, and the allocation management table 445 will be described later.

[0042] Next, a description will be given of the functional configuration of the terminal device 2 and the server 4. Fig. 6 is a diagram showing an example of the functional configuration of the terminal device 2 and the server 4.

[0043] As shown in FIG. 6, the terminal device 2 includes an acquisition unit 201, a display control unit 202, and a sales registration unit 203 as functional components.

[0044] The functional configuration of the terminal device 2 is a software configuration realized by the processor of the terminal device 2 operating in accordance with a program stored in the ROM 22 or the memory unit 24, but is not limited to this. For example, some or all of the functional configuration of the terminal device 2 may be realized by hardware such as a dedicated circuit.

[0045] The acquisition unit 201 acquires information held in the code symbol by decoding the code symbol included in the image captured by the imaging unit 29. For example, the acquisition unit 201 acquires the product code held in the code symbol by decoding the code symbol attached to the product from the captured image of the product.

[0046] The display control unit 202 cooperates with other functional units to display various screens and information on the display unit 25. For example, the display control unit 202 displays a list of product information of products registered for sale on the display unit 25. In addition, for example, the display control unit 202 displays the register number and the register waiting time notified from the server 4 on the display unit 25.

[0047] The sales registration unit 203 executes a sales registration process based on the product code acquired by the acquisition unit 201. Specifically, when the acquisition unit 201 acquires a product code, the sales registration unit 203 executes a sales registration process by transmitting the product code together with the customer identification information of the terminal device 2 to the server 4.

[0048] Furthermore, when the sales registration unit 203 acquires from the server 4 the product information corresponding to the product code acquired by the acquisition unit 201, the sales registration unit 203 cooperates with the display control unit 202 to display the acquired product information on the display unit 25. For example, the sales registration unit 203 displays the product information of the products for which the sales registration process has been executed in a list in the order in which they were registered.

[0049] In addition, when the sales registration unit 203 receives an operation (hereinafter also referred to as a closing operation) via the operation unit 26 to instruct the end of sales registration or the start of payment, it executes processing to make payment for the registered sales items at the payment device 8.

[0050] For example, the sales registration unit 203 displays the customer identification information of its own terminal device 2, which has been converted into a code symbol, on the display unit 25. This allows the settlement device 8 to read the customer identification information displayed on the display unit 25 of the terminal device 2 and obtain from the server 4 the product registered in association with the customer identification information.

[0051] Also, for example, the sales registration unit 203 may transmit the customer identification information of its own terminal device 2 to the payment device 8 via the communication unit 27. In this case, the payment device 8 can obtain, based on the customer identification information transmitted from the terminal device 2, from the server 4, the product registered in association with the customer identification information.

[0052] When the payment device 8 acquires customer identification information from the terminal device 2, it acquires from the server 4 the product code registered in the sales registration table 442 in association with the customer identification information, and the product information registered in the product master 441 in association with the product code. The payment device 8 calculates the total price of the products based on the acquired product code and product information, and executes a payment process to settle the total price with the payment amount to be paid by the customer. Then, when the payment process is completed, the payment device 8 transmits to the server 4 the customer identification information that was the subject of the payment process and information indicating the completion of the payment.

[0053] On the other hand, as shown in FIG. 6, the server 4 includes a registration processing unit 401, a payment support unit 402, and a cooperation processing unit 403 as functional components.

[0054] The registration processing unit 401 is an example of an acquisition means and a registration means. The registration processing unit 401 acquires a pair of a product code and customer identification information transmitted from the terminal device 2. The registration processing unit 401 also associates the pair of the product code and customer identification information acquired from the terminal device 2 and registers them in the sales registration table 442. The registration processing unit 401 also reads out product information corresponding to the product code transmitted from the terminal device 2 from the product master 441, and provides it to the terminal device 2 that transmitted the information.

[0055] The payment support unit 402 is an example of a first calculation means, an allocation means, a second calculation means, a notification means, and a determination means. The payment support unit 402 executes a process for supporting the payment of products registered by a customer. Specifically, based on the information registered in the sales registration table 442, the payment support unit 402 calculates the payment time required for the registered products and allocates a payment device 8 to be the payment destination for each customer identification information. Then, the payment support unit 402 notifies the terminal device 2 corresponding to the customer identification information of the register number of the payment device 8 allocated to the customer identification information and the register waiting time.

[0056] The operation of the payment support unit 402 will be described below. First, the payment support unit 402 refers to the sales registration table 442 and counts the registered number of items (hereinafter also referred to as the number of purchased items) registered in the sales registration table 442 for each customer identification information. The payment support unit 402 also registers and manages the counted result of the registered number in the payment waiting table 443.

[0057] Fig. 7 is a diagram showing an example of the data configuration of the payment waiting table 443. As shown in Fig. 7, the payment waiting table 443 stores customer identification information, the number of purchased products, and the time required for payment in association with each other.

[0058] 7 shows an example in which the number of products purchased is associated with each of the customer identification information "A" to "F" and registered. For example, for customer identification information "A", it is shown that five products are registered in sales registration table 442. Also, for customer identification information "F", it is shown that four products are registered in sales registration table 442.

[0059] Furthermore, when the payment support unit 402 registers (or updates) the number of purchased products, it calculates the time required for payment based on the number of purchased products, and registers it in association with the customer identification information.

[0060] For example, the payment support unit 402 may calculate the payment required time by multiplying the number of purchased items by a predetermined fixed value for calculating the payment required time. As an example, if the fixed value is 5 seconds, the payment required time when the number of purchased items is 5 will be 25 seconds, calculated by multiplying 5 (items) by 5 (seconds). The payment waiting table 443 shown in FIG. 7 shows the calculation result of the payment required time when the fixed value is 5 seconds.

[0061] The method of calculating the time required for settlement is not limited to the above example. For example, the settlement support unit 402 may identify the characteristics of the actually registered products (product name, genre, etc.) from the product master 441, and calculate the time required for settlement for each piece of customer identification information by adding a weight coefficient according to the product characteristics. Specifically, the time required for settlement may be calculated by multiplying a fixed value by a weight coefficient according to the product characteristics to derive an adjusted fixed value for the number of products purchased, and adding the adjusted fixed value thus derived for the number of products purchased.

[0062] Further, the timing of updating the payment waiting table 443 is not particularly important, but from the viewpoint of real-time performance, it is preferable that the latest state of the sales registration table 442 is promptly reflected. For example, the payment support unit 402 may update the payment waiting table 443 every time the sales registration table 442 is updated. Also, for example, the payment support unit 402 may update the payment waiting table 443 at relatively short time intervals (such as every 10 seconds).

[0063] When the payment facilitating unit 402 updates the payment waiting table 443, it combines the customer identification information registered in the payment waiting table 443, and calculates the total value of the payment required time for each combination (hereinafter, the total payment required time) by adding up the payment required time of the customer identification information related to each combination. Then, the payment facilitating unit 402 registers each set of customer identification information and the total payment required time related to the set in the intermediate table 444.

[0064] Fig. 8 is a diagram showing an example of the data configuration of intermediate table 444. As shown in Fig. 8, intermediate table 444 has data items of group information and total settlement time required. Other data items will be described later.

[0065] In the group information, information indicating a group of customer identification information is registered. The payment facilitator 402 finds all combinations of customer identification information registered in the payment waiting table 443, and calculates the total payment time required for each group. Specifically, the payment facilitator 402 finds all combinations of customer identification information using the combination formula "nCr".

[0066] Here, n corresponds to the total number of different customer identification information registered in the payment waiting table 443. In this embodiment, an example is shown in which the number r of customer identification information to be combined from n pieces is "2". In this case, the total number of combinations for the customer identification information "A" to "F" registered in the payment waiting table 443 in FIG. 7 is 15 (pairs), as shown in FIG. 8. Note that the number r is not limited to "2", and may be 3 or more (and less than n).

[0067] When the payment support unit 402 finds all combinations of customer identification information, it calculates a total payment time by adding up the payment time for each set of customer identification information, and registers this in the intermediate table 444 in association with the corresponding set of customer identification information.

[0068] For example, for a pair of customer identification information (A, B), the payment facilitator 402 calculates a total time required for payment of "35 seconds" by adding the time required for payment for "A" of "25 seconds" and the time required for payment for "B" of "10 seconds." Similarly, the payment facilitator 402 calculates the total time required for payment for each pair.

[0069] Next, the payment facilitator 402 calculates an index value for determining a combination of customer identification information to be assigned to payment device 8, based on the total payment time calculated for each group. Specifically, the payment facilitator 402 calculates an average value of the total payment time calculated for each group as an index value. Then, the payment facilitator 402 registers the calculated index value in the index value field of intermediate table 444.

[0070] 8 shows an example in which the average value of the total settlement time is registered in the index value column for the pair of customer identification information (A, B), but other pairs may be registered in a similar manner. Also, intermediate table 444 may not have an index time column, and the calculated index value may be temporarily stored in RAM 43 or the like. Note that the index value is not limited to the average value of the total settlement time, and may be another statistical value such as a median.

[0071] Next, the payment support unit 402 calculates the difference between the total payment time and the index value for each set, and derives the absolute value of the difference. Fig. 8 shows an example in which the difference between the total payment time and the index value and the absolute value are registered in the intermediate table 444.

[0072] Next, the payment facilitator 402 determines the set of customer identification information to be assigned to the same payment device 8 based on the absolute value derived for each set. Specifically, the payment facilitator 402 assigns evaluation values ​​to sets in ascending order of absolute value, that is, sets having the closest distance (difference) from the average value. The closer the distance from the average value, the higher the evaluation value assigned. FIG. 8 shows an example in which the evaluation value of the set having the closest distance from the average value is set to "1," and ascending numbers are assigned as the distance (difference) from the average value increases.

[0073] In this way, the payment support unit 402 determines the set of customer identification information to be actually assigned based on the index value derived from the total payment time required for each set of customer identification information registered in the payment waiting table 443. In this way, the payment support unit 402 can pair customer identification information with a combination that minimizes the deviation from the index value, taking into account the product registration status of all customers circulating in the store.

[0074] Next, the payment facilitator 402 selects pairs of customer identification information to be assigned to the same payment device 8 in descending order of the evaluation value assigned to each pair. Here, the payment facilitator 402 excludes customer identification information that has already been assigned from the selection candidates to avoid duplicate assignment.

[0075] For example, in the intermediate table 444 of FIG. 8, the payment facilitating unit 402 first selects a combination of customer identification information (C, D) with an evaluation value of "1". The next combination of customer identification information with an evaluation value of "2" is (B, D), and since "D" has already been selected, the payment facilitating unit 402 excludes it from the selection candidates. There are two next combinations of customer identification information with an evaluation value of "3", (B, E) and (D, F), both of which are new combinations. In this case, the payment facilitating unit 402 selects one of the combinations ((B, E) in FIG. 8). The next combination of customer identification information with an evaluation value of "5" is (A, F), which is a new combination, and so the payment facilitating unit 402 selects this combination.

[0076] In intermediate table 444 in Fig. 8, data entries related to the selected combination of customer identification information are highlighted. If the number of pieces of customer identification information registered in sales registration table 442 (payment waiting table 443) is odd, one piece of customer identification information will remain after the above-mentioned combination selection. In this case, payment support unit 402 selects the one remaining piece of customer identification information as the sole combination.

[0077] Next, the payment support unit 402 executes allocation to the payment device 8 for each combination of selected customer identification information. Specifically, the selected combination of customer identification information is assigned to the same register number. For example, if there are two payment devices 8 and the register numbers of the payment devices 8 are register numbers "1" and "2", the payment support unit 402 assigns the set of customer identification information (C, D) with the highest evaluation value to register number "1". Next, the payment support unit 402 assigns the set of customer identification information (B, E) with the next highest evaluation value to register number "2". Next, the payment support unit 402 assigns the set of customer identification information (A, F) with the next highest evaluation value to register number "1". Then, the payment support unit 402 registers the sets of customer identification information assigned to each payment device 8 in the allocation management table 445.

[0078] Fig. 9 is a diagram showing an example of the data configuration of allocation management table 445. As shown in Fig. 9, allocation management table 445 stores register numbers and allocation results in association with each other.

[0079] The register number is the register number of a payment device 8 in the store. The allocation result is a set of customer identification information assigned to the corresponding register number. Fig. 9 shows an example in which the allocation results for the above-mentioned register numbers "1" and "2" are registered in allocation management table 445.

[0080] In the present embodiment, an example has been described in which the sets of customer identification information with the highest evaluation value are assigned to the payment devices 8 in order, but the order of assignment is not limited to this. For example, the sets of customer identification information with the lowest evaluation value may be assigned to the payment devices 8 in order, or the sets of customer identification information may be assigned to the payment devices 8 in a random order.

[0081] In this way, the payment support unit 402 allocates the selected set of customer identification information to the payment devices 8 with the same register number. In addition, the payment support unit 402 allocates in a round robin manner so as to avoid imbalance in the allocation destination payment devices 8.

[0082] Next, the payment support unit 402 calculates the call order and register waiting time of the customer identification information assigned to each payment device 8. Here, the call order is an example of a payment order, and is a concept corresponding to the order or priority of payments made at the assigned payment device 8. The call order is determined within the customer identification information assigned to the payment devices 8 with the same register number.

[0083] The method of determining the call order is not particularly limited, and various methods can be adopted. For example, when multiple sets of customer identification information are assigned to the payment device 8 with the same register number, the payment support unit 402 may determine the call order by giving priority to the set with the highest evaluation value. Also, for example, when determining the read order within a set of customer identification information, the payment support unit 402 may determine the call order by giving priority to the customer identification information registered in the payment waiting table 443 that requires the shortest (or longest) payment time.

[0084] When determining the call order according to the above-mentioned decision rules, the payment support unit 402 determines the call order for each pair of customer identification information (C, D) and (A, F) assigned to register number "1" in the order of C → D → F → A. In addition, the payment support unit 402 determines the call order for the pair of customer identification information (B, E) assigned to register number "2" in the order of B → E.

[0085] Next, the payment support unit 402 calculates the waiting time (register waiting time) until payment can be made at the assigned payment device 8 for each customer identification information assigned to the payment device 8. Specifically, the payment support unit 402 calculates the register waiting time for the customer identification information corresponding to each call order by adding up the payment required time for the customer identification information assigned to the same payment device 8 in the order of call.

[0086] For example, based on the payment time required for each customer identification information assigned to register number "1" and the call order, the payment support unit 402 calculates a register waiting time of 15 seconds for customer identification information C, 55 seconds (=15 seconds+40 seconds) for customer identification information D, 75 seconds (=15 seconds+40 seconds+20 seconds) for customer identification information F, and 100 seconds (=15 seconds+40 seconds+20 seconds+25 seconds) for customer identification information A. Also, based on the payment time required for each customer identification information assigned to register number "2" and the call order, the payment support unit 402 calculates a register waiting time of 10 seconds for customer identification information B, and 60 seconds (=10 seconds+50 seconds) for customer identification information E.

[0087] Then, the payment support unit 402 notifies the terminal device 2 corresponding to the customer identification information of a pair of the register number and the register waiting time obtained for each piece of customer identification information. Here, the register number and the register waiting time notified for each piece of customer identification information are the payment device 8 of the payment destination and the expected time until the payment is completed at the payment device 8 when the payment for the registered sales item is made at the current time.

[0088] In addition, when each terminal device 2 receives notification of the register number and register waiting time notified from the server 4, the display control unit 202 notifies the customer by displaying the notified register number and register waiting time on the display unit 25.

[0089] This allows the customer operating the terminal device 2 to easily check the current congestion status of the payment device 8. Specifically, the customer can determine whether it is better to make a payment now or wait a little later based on the register waiting time, thereby improving convenience regarding payment.

[0090] Furthermore, a customer operating the terminal device 2 can complete payment for registered products in a time equivalent to the wait time by heading to the payment device 8 with the specified register number based on the displayed register number and wait time. This can alleviate the situation where a payment (waiting at the register) occurs around the payment device 8. Also, by showing customers the congestion status of the payment device 8, it is possible to encourage them to move around the store, thereby increasing the opportunities to purchase products.

[0091] Returning to FIG. 6, the link processing unit 403 executes processing related to linking with the payment device 8. Specifically, when the link processing unit 403 is notified of customer identification information from the payment device 8, it reads out product codes related to the notified customer identification information from the sales registration table 442. Next, the link processing unit 403 transmits the read product codes and product information corresponding to each of the product codes to the payment device 8 that sent the notification. This allows the payment device 8 to calculate the total amount of the products for which the customer has registered sales, based on the product information provided by the server 4.

[0092] In addition, when the link processing unit 403 is notified of customer identification information and completion information indicating that the payment has been completed from the payment device 8, it excludes the data entry in the sales registration table 442 related to the notified customer identification information from the payment target.

[0093] For example, the linking processor 403 moves the data entry related to the notified customer identification information to another data table for managing pairs of customer identification information and product codes for which payment has been completed. Also, for example, the linking processor 403 adds flag information indicating that payment has been completed to the data entry related to the notified customer identification information, thereby excluding it from the payment target. Note that the payment support unit 402 excludes the pair of customer identification information and product code excluded from the payment target from the calculation of the payment processing time and the allocation to the payment device 8.

[0094] An example of the process performed between the terminal device 2 and the server 4 will be described below. Fig. 10 is a sequence diagram showing an example of the product sales data process performed between the terminal device 2 and the server 4. Note that in this process, a configuration example will be described in which the register number and the register waiting time are notified each time the sales registration process is performed on the terminal device 2.

[0095] First, the acquisition unit 201 of the terminal device 2 acquires a product code from an image captured by the imaging unit 29 (step S11). Next, the sales registration unit 203 executes a sales registration process by transmitting the product code acquired in step S11 and the customer identification information of the terminal device 2 to the server 4 (step S12).

[0096] When the registration processing unit 401 of the server 4 acquires a pair of the product code and the customer identification information transmitted from the terminal device 2 (step S21), it associates the product code with the customer identification information and registers them in the sales registration table 442 (step S22). The registration processing unit 401 also reads out the product information corresponding to the product code registered in the sales registration table 442 from the product master 441 (step S23), and transmits it to the terminal device 2 that transmitted the information (step S24).

[0097] Next, the payment support unit 402 executes a payment support process to derive the register number and register wait time of the payment device 8 to be allocated (step S25). Then, the cooperation processing unit 403 notifies the terminal device 2 that sent the information of the register number and register wait time derived in the payment support process (step S26). Note that in this process, the terminal device 2 that performed the sales registration process is notified of the register number and register wait time related to the terminal device 2, but the present invention is not limited to this, and the configuration may be such that the register number and register wait time related to the terminal device 2 are notified to all terminal devices 2.

[0098] When the display control unit 202 of the terminal device 2 acquires product information from the server 4, it causes the display unit 25 to display the product name, price, and the like included in the product information (step S13). Furthermore, when the display control unit 202 acquires a register number and a register waiting time from the server 4, it causes the display unit 25 to display the acquired register number and register waiting time, thereby providing the operator with support information related to the current payment (step S14). For example, the display control unit 202 causes the display unit 25 to display a message indicating that if the operator goes to the payment device 8 with the "register number" now, the payment can be completed in the "register waiting time".

[0099] Thereafter, in the sales registration unit 203, step S11 is performed each time a product code is read until the closing operation is performed. In other words, the customer operating the terminal device 2 can check the register number and register waiting time corresponding to the registered product at that time in real time each time a product is added. In addition, in the case where the configuration is such that the register number and register waiting time are notified to each terminal device 2, the customer operating each terminal device 2 can check the register number and register waiting time corresponding to the registered product at that time in real time each time a product is added to his or her own or other terminal device 2.

[0100] Next, an example of the payment support process performed by the server 4 will be described with reference to Fig. 11. Fig. 11 is a flowchart showing an example of the payment support process performed by the server 4. Note that this process corresponds to the process of step S25 described in Fig. 10.

[0101] First, the payment support unit 402 calculates the payment time required for payment of the product for each customer identification information based on the registered number of product codes for each customer identification information registered in the sales registration table 442 (step S31). The calculated payment time required for each customer identification information is registered in the payment waiting table 443.

[0102] Next, the payment support unit 402 generates group information for each group by combining customer identification information (step S32), and calculates the total payment time for each group of group information (step S33). Next, the payment support unit 402 calculates an index value related to the determination of the combination of customer identification information by obtaining the average or median of the total payment time for each group (step S34).

[0103] Next, the payment facilitator 402 calculates the difference between the total payment time required for each group and the index value (step S35), and selects group information of customer identification information to be assigned to the payment device 8 based on the calculated difference value (step S36). Next, the payment facilitator 402 assigns each of the selected group information to the payment device 8 to which it is assigned (step S37).

[0104] Next, the payment support unit 402 determines the call order for each of the customer identification information at the payment device 8 based on the payment time required for the customer identification information included in the group information assigned to the payment device 8 (step S38). Next, the payment support unit 402 calculates the register waiting time for each of the customer identification information by adding up the payment time required for the customer identification information assigned to the same payment device 8 in the order of the call order (step S39), and proceeds to step S26 in FIG. 10.

[0105] As described above, when the server 4 obtains the product code of the product purchased by the customer and the customer identification information from the terminal device 2 operated by the customer, it stores them in association with the sales registration table 442. In addition, the server 4 calculates the payment required time for each customer identification information from the registered number of product codes registered in association with the customer identification information, and determines the payment device 8 to which the payment is to be allocated based on the payment required time. Then, the server 4 calculates the register wait time required for payment of the product at the allocation destination payment device 8 for each customer identification information, and notifies the terminal device 2 of the calculated register wait time together with the register number of the allocation destination payment device 8.

[0106] This allows a customer operating the terminal device 2 to easily check the current congestion status of the payment device 8 based on the register number and register waiting time notified by the server 4. Also, a customer operating the terminal device 2 can easily check the payment device 8 when making a payment and the expected time until the payment is completed based on the register number and register waiting time notified by the server 4. Therefore, the server 4 can alleviate congestion at the payment device 8 and efficiently support customers in making payments.

[0107] The above-described embodiment can be modified as appropriate by changing a part of the configuration or function of each of the above-described devices. Therefore, some modified examples of the above-described embodiment will be described below as other embodiments. Note that the following mainly describes the differences from the above-described embodiment, and a detailed description of the common points with the contents already described will be omitted. The modified examples described below may be implemented individually or in appropriate combination.

[0108] (Variation 1) In the above embodiment, a product code capable of identifying a product is obtained by reading a code symbol attached to the product, but the method of identifying the product is not limited to this. For example, a known general object recognition technology may be used to identify (recognize) the type of the product from a captured image of the product.

[0109] In this case, the acquisition unit 201 of the terminal device 2 identifies (recognizes) the product that is the subject of the image captured by the imaging unit 29, and acquires the product code of the identified product. The acquisition unit 201 acquires the product code of the recognized product based on a machine learning model related to product recognition and data that associates the relationship between the appearance features of each product and the product code. The acquisition unit 201 may also acquire the product code of the product shown in the image by working with another device (not shown) for product recognition that is connected to the network Na.

[0110] The programs executed by each device in the above-described embodiments (and the modified examples) are provided in a state where they are pre-installed in a ROM, a storage unit, etc. The programs executed by each device in the above-described embodiments may be provided by being recorded in a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD) in the form of an installable or executable file.

[0111] Furthermore, the programs executed by each device of the above-described embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the programs executed by each device of the above-described embodiments may be provided or distributed via a network such as the Internet.

[0112] Although the embodiment of the present invention has been described above, this embodiment is presented as an example and is not intended to limit the scope of the invention. These new embodiments and their modifications can be implemented in various other forms, and various omissions, substitutions, changes, and combinations can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0113] 1 Store System 2 Terminal Equipment 3 Cart 4 Server 8 Payment Device 200 Control section 201 Acquisition Department 202 Display control unit 203 Sales Registration Department 400 Control section 401 Registration processing unit 402 Payment Support Department 403 Collaboration Processing Unit 441 Product Master 442 Sales registration table 443 Payment waiting table 444 Intermediate Table 445 Allocation Management Table [Prior art documents] [Patent documents]

[0114] [Patent Document 1] JP 2016-045617 A

Claims

1. an acquisition means for acquiring, from a terminal device operated by a customer, first identification information capable of identifying a product purchased by the customer and second identification information capable of identifying the customer or the terminal device; a registering means for registering the first identification information and the second identification information acquired by the acquiring means in a data table in association with each other; a first calculation means for calculating a first time required for payment of the product for each of the second identification information based on a registered number of the first identification information registered in association with the second identification information; an allocation means for allocating each of the second identification information to any one of a plurality of payment devices based on the first time of the second identification information; a second calculation means for calculating a second time required for payment of the product at the payment device to which the second identification information is allocated, based on the first time of the second identification information and the allocation result of the payment device; a notification means for notifying the terminal device corresponding to the second identification information of the payment device to which the second identification information is assigned and the second time; A server device comprising:

2. The first calculation means calculates the first time based on a characteristic of a product corresponding to the first identification information registered in association with the second identification information. The server device according to claim 1 .

3. The allocation means determines the set of second identification information to be allocated to the same payment device based on a total value of the first time for each set of the second identification information. The server device according to claim 1 .

4. The allocation means determines the set of second identification information to be allocated to the same payment device based on a difference between a sum of the first times of each set of the second identification information and an average or median of the sum. The server device according to claim 3.

5. a determination unit that determines a payment order in the payment device for each of the second identification information assigned to the same payment device based on an assignment result of the assignment unit, the second calculation means calculates the second time related to each of the second identification information by adding up the first time of the second identification information assigned to the same payment device in the order of the payment. The server device according to claim 1 .

6. The computer of the server device, an acquisition means for acquiring, from a terminal device operated by a customer, first identification information capable of identifying a product purchased by the customer and second identification information capable of identifying the customer or the terminal device; a registering means for registering the first identification information and the second identification information acquired by the acquiring means in a data table in association with each other; a first calculation means for calculating a first time required for payment of the product for each of the second identification information based on a registered number of the first identification information registered in association with the second identification information; an allocation means for allocating each of the second identification information to any one of a plurality of payment devices based on the first time of the second identification information; a second calculation means for calculating a second time required for payment of the product at the payment device to which the second identification information is allocated, based on the first time of the second identification information and the allocation result of the payment device; a notification means for notifying the terminal device corresponding to the second identification information of the payment device to which the second identification information is assigned and the second time; A program to make it function as such.

Images