Table payment system and table payment method

Abstract

To provide a table settlement system and a table settlement method which allow simple reuse of a set of a slave unit and an information storage medium. [Solution] The tabletop payment system includes a parent terminal, multiple child devices capable of low-power wireless communication with the parent terminal via a network, multiple information storage media installed with each of the multiple child devices, and a management server equipped with a storage device and capable of communicating with the parent terminal and user terminals via the network. A set of a child device and an information storage medium is installed at each of the multiple tables, and the management server stores management information in the storage device, including multiple pieces of correspondence information in which child device identification information, information storage medium identification information, and related information are associated with each other. The management server is capable of changing the association of the correspondence information.

Description

[Technical Field]

[0001] The present invention relates to a tabletop payment system and a tabletop payment method. [Background technology]

[0002] Restaurants, cafes, and other food service establishments are introducing various technologies to improve customer convenience. Among these, tabletop payment systems are attracting attention as they allow customers to order and pay at their tables using their smartphones or tablets without having to come into contact with staff.

[0003] Patent Document 1 discloses a cashless food ordering system for a restaurant (hereinafter referred to as the "conventional system").

[0004] In restaurants where this conventional system has been introduced, a label with a QR code (registered trademark) printed on it, which is a two-dimensional code that records the restaurant's store number, a unique table number for each table, and the system's address information, is affixed to every table where customers sit. When a customer visits the restaurant, they use the QR code (registered trademark) reading function on their smartphone to read the QR code (registered trademark) printed on the label, which links the customer's smartphone to the cloud-based system via the Internet. From then on, the customer can use their smartphone to order food and pay for the food they ordered by following the procedures executed by the system without going through a waiter. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2020-004353 Summary of the Invention [Problem to be solved by the invention]

[0006] The inventors of the present application are studying a novel tabletop payment system that includes a base terminal, multiple sub-units that communicate with the base terminal via low-power wireless communication, and a set of one or more information storage media (QR, NFC (Near Field Communication) tags, etc.). In this tabletop payment system, a set of sub-units and one or more information storage media is installed at any location (table), allowing customers to place orders and make payments at the installation location. This tabletop payment system is required to be able to reuse the set of sub-units and information storage media at other tables and other stores, in order to accommodate changes in table layout and reuse at other stores.

[0007] In the conventional system, desk number information corresponding only to a specific desk and store number information corresponding only to a specific store are stored in the QR code (registered trademark). In the conventional system, the QR code (registered trademark) is placed at the specific desk and specific store indicated by the information embedded in the QR code (registered trademark), enabling orders and payments to be made at the installation location.

[0008] In conventional systems, information identifying a specific desk or a specific store is embedded in the QR code (registered trademark), so the QR code (registered trademark) must be installed at that specific desk or store, and the QR code (registered trademark) cannot be reused at desks other than the specific desk or store other than the specific store.

[0009] The present invention has been made to solve the above-mentioned problems. That is, one of the objects of the present invention is to provide a tabletop payment system and a tabletop payment method that allow easy reuse of a set of a handset and an information storage medium. [Means for solving the problem]

[0010] In order to solve the above problem, the tabletop payment system of the present invention is a tabletop payment system comprising a parent terminal, a plurality of child devices capable of low-power wireless communication with the parent terminal, a plurality of information storage media installed on a table together with the child devices, and a management server capable of communicating with the parent terminal and user terminals via a network and having a memory device, wherein the management server stores in the memory device management information including a plurality of correspondence information in which child device identification information identifying the child device, information storage medium identification information identifying the information storage medium installed on the table together with the child device, and related information which is information related to the child device and the information storage medium are associated with each other, and the management server is capable of changing the association of the correspondence information.

[0011] The table settlement method of the present invention is a table settlement method that uses a parent terminal, multiple child devices that are capable of low-power wireless communication with the parent terminal, multiple information storage media that are placed on the table together with the child devices, and a management server that is capable of communicating with the parent terminal and user terminals via a network and has a memory device, wherein the management server stores management information in the memory device that includes multiple pieces of correspondence information that correspond to each other, such as child device identification information that identifies the child device, information storage medium identification information that identifies the information storage medium placed on the table together with the child device, and related information that is information related to the child device and the information storage medium, and the management server is capable of changing the correspondence of the correspondence information. [Effects of the Invention]

[0012] According to the present invention, a set of a slave unit and an information storage medium can be easily reused. Note that the effects described here are not necessarily limited to those described herein, and may be any of the effects described in this disclosure. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a tabletop payment system according to a first embodiment of the present invention. [Figure 2]FIG. 2 is a diagram illustrating an example of the hardware configuration of the management server. [Figure 3A] FIG. 3A is a diagram for explaining handset QR management information. [Figure 3B] FIG. 3B is a diagram for explaining a specific example of handset QR management information. [Figure 3C] FIG. 3C is a diagram for explaining master-slave management information. [Figure 4] FIG. 4 is a diagram illustrating an example of the hardware configuration of the parent terminal. [Figure 5] FIG. 5 is a diagram showing an example of the hardware configuration of a terminal with a display. [Figure 6A] FIG. 6A is a diagram illustrating an example of the hardware configuration of the slave device. [Figure 6B] FIG. 6B is a diagram showing the appearance of the handset and the QR. [Figure 7] FIG. 7 is a diagram illustrating an example of the hardware configuration of a user terminal. [Figure 8A] FIG. 8A is a sequence diagram illustrating the operation of the tabletop payment system. [Figure 8B] FIG. 8B is a sequence diagram for explaining the operation of the tabletop payment system. [Figure 9A] FIG. 9A is a sequence diagram illustrating the operation of the tabletop payment system. [Figure 9B] FIG. 9B is a sequence diagram illustrating the operation of the tabletop payment system. [Figure 10A] FIG. 10A is a sequence diagram illustrating the operation of the tabletop payment system. [Figure 10B] FIG. 10B is a sequence diagram for explaining the operation of the tabletop payment system. [Figure 11] FIG. 11 is a diagram for explaining a use case. [Figure 12] FIG. 12 is a diagram for explaining the operation of a person who modifies the slave unit QR management information when updating the slave unit QR management information. [Figure 13] FIG. 13 is a diagram for explaining a use case. [Figure 14]FIG. 14 is a diagram for explaining a use case. [Figure 15] FIG. 15 is a diagram for explaining a use case. [Figure 16] FIG. 16 is a diagram for explaining a use case. [Figure 17] FIG. 17 shows the external appearance of the handset and QR. [Figure 18A] FIG. 18A is a diagram showing an example of the configuration of a tabletop payment system according to the second embodiment of the present invention. [Figure 18B] FIG. 18B is a diagram for explaining the operation of the table-top payment system according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] Each embodiment of the present invention will be described below with reference to the drawings. Note that in all drawings of the embodiments, the same or corresponding parts may be assigned the same reference numerals. In the following description, various information may be described using expressions such as "table" and "record," but the various information may be expressed using other data structures. When describing identification information, the expression "ID" is used, but other expressions are possible. In the following description, processing may be described using a device as the subject, but the subject of the processing may be a CPU or the like instead of a device.

[0015] <<First Embodiment>> A tabletop payment system according to a first embodiment of the present invention will now be described. FIG. 1 is a diagram showing an example of the configuration of the tabletop payment system according to the first embodiment of the present invention. As shown in FIG. 1, the tabletop payment system includes a management server 100, a master terminal 200, a terminal with a display 300, a plurality of slave terminals 400a to 400c, a plurality of QR codes 500a to 500c, a payment service provider server 600, and a user terminal 700. Although not shown in the figures, the tabletop payment system may also include a terminal of an administrator who manages the tabletop payment system.

[0016] In this example, the table-based payment system is introduced in store A, which is run by restaurant operator X. Store A is equipped with a base terminal 200, a terminal with a display 300, sub-unit 1 400a, sub-unit 2 400b, sub-unit 3 400c, QR11 500a, QR12 500b, QR13 500c, table A 800A, table B 800B, and table C 800C.

[0017] Table A800A has handset 1 400a and QR11 500a installed, table B800B has handset 2 400b and QR12 500b installed, and table C800C has handset 3 400c and QR13 500c installed. Note that hereinafter handset 1 400a, handset 2 400b, and handset 3 400c may be referred to as "handsets 400" when there is no need to particularly distinguish between them. QR11 500a, QR12 500b, and QR13 500c may be referred to as "QR500" when there is no need to particularly distinguish between them. Table A800A, table B800B, and table C800C may be referred to as "table 800" when there is no need to particularly distinguish between them.

[0018] The management server 100, the parent terminal 200, the payment service provider server 600, and the user terminal 700 are connected to each other via a network NW1 so as to be able to communicate with each other. The parent terminal 200 and the multiple child devices 400a to 400c are connected to each other so as to be able to communicate with each other via low-power wireless technology (such as a personal area network (PAN) or a low-power wide area (LPWA)).

[0019] Fig. 2 is a diagram showing an example of the hardware configuration of the management server 100. As shown in Fig. 2, the management server 100 has a non-volatile storage device 110 that can read and write data, a memory 120 (e.g., RAM), a CPU 130, an input / output interface 140, and a network interface 150. The CPU 130, the storage device 110, the memory 120, the input / output interface 140, and the network interface 150 are connected via a bus 160.

[0020] A device including the CPU 130, the storage device 110, the memory 120, the input / output interface 140, the network interface 150, and the bus 160 may be referred to as an "information processing device." The information processing device may be a virtual information processing device constructed on multiple information processing devices or a cloud. The CPU 130 may be referred to as an "arithmetic device."

[0021] The storage device 110 holds (stores, holds) a program 111 and a database 112. The CPU 130 loads the program 111 stored in the storage device 110 into the memory 120. The CPU 130 executes the program 111 loaded into the memory 120 to realize various functions of the management server 100.

[0022] The database 112 includes slave device QR management information 112a, master device-slave device management information 112b, and menu information 112c. The slave device QR management information 112a and / or the master device-slave device management information 112b may be referred to as "management information."

[0023] 3A is a diagram illustrating slave device QR management information 112a. As shown in FIG. 3A, slave device QR management information 112a includes slave device ID 112a1, QRID 112a2, and related information 112a3 as columns for storing information (values). In slave device QR management information 112a, information corresponding to each column relating to slave device 400 and the QRID used in combination with slave device 400 is associated with each other and stored as row-based information (records).

[0024] Specifically, the slave ID 112a1 stores a slave ID (slave identification information) for identifying the slave 400. The QRID 112a2 stores a QRID (QR identification information) for identifying the QR 500. The related information 112a3 stores related information. The related information is information related to the slave 400 and the QR 500 that is associated with the slave ID and the QR ID, and is, for example, at least one of table identification information, store identification information, and restaurant business identification information.

[0025] The row-based information (record) may be referred to as “correspondence information.” The correspondence information associates the identification information (sub-unit ID, QRID) of each of sub-units 400 and QR500 installed together on a table, store identification information indicating the store where sub-units 400 and QR500 are installed, and restaurant business identification information indicating the restaurant business that operates the store where sub-units 400 and QR500 are installed.

[0026] Fig. 3B is a diagram illustrating a specific example of slave device QR management information 112a. Slave device QR management information 112a in Fig. 3B includes table 112a4, store 112a5, and restaurant operator 112a6 as related information 112a3. Table 112a4 stores table identification information for identifying table 800. Store 112a5 stores store identification information for identifying the store. Restaurant operator 112a6 stores restaurant operator identification information for identifying the restaurant operator.

[0027] In the example of Figure 3B, in one record, only one slave ID and one QR ID are associated with related information (table identification information, store identification information, restaurant business identification information), but multiple slave IDs may be associated, and multiple QR IDs may be associated.

[0028] 3C is a diagram illustrating parent-child device management information 112b. As shown in FIG. 3C, parent-child device management information 112b includes parent device ID 112b1, child device 1 112b2, child device 2 112b3, and child device 3 112b4 as columns for storing information (values). In parent-child device management information 112b, information corresponding to each column relating to parent terminal 200 and multiple child devices 400 that perform power-saving wireless communication with parent terminal 200 is associated with each other and stored as row-based information (records).

[0029] Specifically, the parent device ID 112b1 stores parent device terminal identification information (parent device ID) for identifying the parent device terminal 200. The child device 1 112b2 stores identification information (child device ID) for identifying the child device 1 400a. The child device 2 112b3 stores identification information (child device ID) for identifying the child device 2 400b. The child device 3 112b4 stores identification information (child device ID) for identifying the child device 3 400c.

[0030] The menu information 112c stores information about the menu of food and drink service items provided at the store.

[0031] Referring back to FIG. 2, the program 111 executed by the CPU 130 is loaded into the memory 120 as described above, and data used when the CPU 130 executes the program 111 is temporarily stored therein.

[0032] The input / output interface 140 is an interface for connecting operation devices such as a keyboard and a mouse, a display, etc. The network interface 150 is an interface for connecting the management server 100 to the network NW1.

[0033] Fig. 4 is a diagram showing an example of the hardware configuration of the parent terminal 200. As shown in Fig. 4, the parent terminal 200 has a CPU 210, a memory 220, a storage device 230, a first communication unit 240, a second communication unit 250, and a third communication unit 260. The CPU 210, the memory 220 (e.g., RAM), the storage device 230, the first communication unit 240, and the second communication unit 250 are connected via a bus.

[0034] The CPU 210 loads the programs stored in the storage device 230 into the memory 220. The CPU 210 executes various processes by executing the programs loaded into the memory 220. The storage device 230 is a non-volatile storage device from which data can be read and written. The storage device 230 stores (memorizes, holds) programs for controlling the parent terminal 200, etc. The storage device 230 also stores child device management information 231. The child device management information 231 stores information necessary for communication with the child device 400. The storage device 230 also stores a parent device ID for identifying the parent terminal 200.

[0035] The first communication unit 240 is a communication interface used for communication with the slave unit 400. The second communication unit 250 is a communication interface used for communication with the external management server 100 via the network NW1. The second communication unit 250 is connected to the management server 100 via the network NW1. The third communication unit 260 is an interface for connection to the terminal with a display 300.

[0036] 5 is a diagram showing an example of the hardware configuration of the display-equipped terminal 300. As shown in FIG. 5, the display-equipped terminal 300 has a CPU 310, a memory 320, a storage device 330, a display 340, and a communication unit 350.

[0037] The CPU 310 loads programs stored in the storage device 330 into the memory 320. The CPU 310 executes various processes by executing the programs loaded into the memory 320. The storage device 330 stores programs for controlling the display-equipped terminal 300, etc. The display 340 is a display device capable of displaying images. The communication unit 350 is a communication interface used for communication with the parent terminal 200.

[0038] 6A is a diagram showing an example of the hardware configuration of child device 400. As shown in FIG. 6A, child device 400 has a CPU 410, a memory 420, a storage device 430, a first communication unit 440, a button 450, a voice guidance unit 460, a buzzer 470, a light-emitting unit 480, and a battery device 490.

[0039] The CPU 410 loads the programs stored in the storage device 430 into the memory 420. The CPU 410 executes various processes by executing the programs loaded into the memory 420. The storage device 430 stores programs for controlling the slave device 400 and the like. The storage device 430 is a non-volatile storage device that is capable of reading and writing data. The storage device 430 stores (memorizes, holds) programs and the like. The storage device 430 also stores parent device information 431. The parent device information 431 stores information necessary for communication with the parent device terminal 200. The storage device 430 also stores a child device ID for identifying the child device 400.

[0040] The first communication unit 440 is a communication interface used for communication with the parent terminal 200. The button 450 is an operating device operated by a customer. The voice guidance unit 460 is a device that generates voice. The buzzer 470 is a device that generates a buzzer sound. The light emitting unit 480 is a device that emits light (for example, an LED). The battery device 490 is a device that supplies power to the child device 400.

[0041] Fig. 6B is a diagram showing the appearance of the slave units 400 and the QR 500. As shown in Fig. 6B, the slave units 400 and the QR 500 are installed as a single unit on each table 800. Note that, although details will be described later in the second embodiment, the slave units 400 and the QR 500 may be installed as separate units on each table 800 (see Fig. 17).

[0042] The QR code 500 is an information storage medium that stores information and can be read by a specific device (e.g., the user terminal 700). The QR code 500 is an information storage medium on which a code, such as a two-dimensional code like a QR code (registered trademark), is printed on paper or the like. The QR code 500 stores information necessary for executing electronic payment, such as information indicating the location of the management server 100 or the payment processor server 600 on the network NW1 (a Uniform Resource Locator (URL)), and information necessary for identifying the table 800 where the customer is seated, such as identification information (QRID) of the QR code 500. Note that instead of the QR code (registered trademark), other information storage media, such as an NFC tag capable of storing information, may be used for the QR code 500. The identification information (QRID) of the QR code 500 and the identification information of the NFC tag may be referred to as "information storage medium identification information."

[0043] The payment processor server 600 provides electronic payment services. The payment processor server 600 can have the same hardware configuration as the management server 100 shown in FIG.

[0044] Fig. 7 is a diagram showing an example of the hardware configuration of a user terminal 700. As shown in Fig. 7, the user terminal 700 has a CPU 710, a memory 720, a storage device 730, various sensors 740, a touch panel 750, a communication unit 760, an NFC communication unit 770, and an imaging unit 780. The CPU 710, the memory 720, the storage device 730, the various sensors 740, the touch panel 750, the communication unit 760, the NFC communication unit 770, and the imaging unit 780 are connected via a bus. An example of the user terminal 700 is a smartphone.

[0045] The CPU 710 controls the operation of the user terminal 700. The CPU 710 loads programs stored in the storage device 730 into the memory 720. The CPU 710 executes various processes by executing the programs loaded into the memory 720. The storage device 730 is a non-volatile storage device that can read and write data. The storage device 730 stores (memorizes, holds) programs for controlling the user terminal 700, applications for using electronic payment services, and the like.

[0046] The various sensors 740 include various sensors such as a position sensor, a geomagnetic sensor, a distance sensor, an acceleration sensor, and a gyro sensor. These sensors make it possible to detect the position, orientation, direction of movement, movement, tilt, etc. of the user terminal 700. The user terminal 700 may also be equipped with other sensors such as an illuminance sensor and a proximity sensor.

[0047] The touch panel 750 is a display device that can display images and also functions as an input device.

[0048] The communication unit 760 is a communication interface connectable to the network NW1. The communication unit 760 communicates with external devices connected to the network NW1 under the control of the CPU 710. For example, the communication unit 760 communicates with external devices such as the management server 100 and the payment processor server 600.

[0049] The NFC communication unit 770 performs NFC communication when in proximity to a compatible reader / writer. The NFC communication unit 770 includes an encoding circuit, a decoding circuit, an antenna, and the like.

[0050] The NFC communication unit 770 reads information from the NFC tag through NFC communication.

[0051] The communication unit 760 may further include other communication units such as a Bluetooth (registered trademark) communication unit or an infrared communication unit.

[0052] The imaging unit 780 is an imaging device having an image sensor such as a CCD (Charge Coupled Device) or a CMOS (Complementary MOS). For example, the imaging unit 680 is used to capture an image of a two-dimensional code or the like. In this case, the user terminal 700 reads information and the like from the image of the two-dimensional code included in the captured image.

[0053] 1 again, a restaurant (store A) to which the tabletop payment system according to the first embodiment is applied is equipped with a master terminal 200 and a set of slave 400 and QR 500. The set of slave 400 and QR 500 is installed at each table 800. The management server 100 stores slave QR management information 112a including multiple records (correspondence information) in which slave IDs, QR IDs, and related information are associated with each other.

[0054] In the tabletop payment system, the slaves 400 and QR codes 500 are installed at any location (tables A800A to C800C in the example of FIG. 1), and table identification information indicating the location (table 800) where they are installed is associated with the slaves 400 and QR codes 500 in the slave QR code management information 112a. In the tabletop payment system, customers can order food and drink service items and make payments for food and drink service at the location (table 800) where the slaves 400 and QR codes 500 are installed without coming into contact with staff.

[0055] 8A to 10B, in the tabletop payment system, management server 100 identifies table 800 where a customer is seated (where an order is placed and where food and drink service is received) based on the slave ID sent from slave 400, the QRID sent from user terminal 700, and slave QR management information 112a, and notifies an employee. The employee recognizes table 800 where a customer is seated to receive food and drink service.

[0056] In the tabletop payment system, the management server 100 transmits a menu (menu information 112c) to the user terminal 700. By selecting an item from the menu displayed on the user terminal 700, the customer can order food and beverage service items (food, drinks, etc.) from the menu.

[0057] In the tabletop payment system, when a customer makes a payment, the management server 100 identifies the table 800 for which the customer has made the payment based on the slave ID sent from the slave 400, the QRID sent from the user terminal 700, and the slave QR management information 112a, and notifies the staff that payment has been made for that table 800. Because the staff can recognize whether payment has been made for the table 800 for which the customer has received food and drink service, there is no need to confirm with the customer whether payment has been made when the customer leaves.

[0058] In this way, the table payment system allows customers at a restaurant (Store A) to place orders and make payments at their tables 800 without coming into contact with staff.

[0059] <Operation> Fig. 8A is a sequence diagram for explaining the operation of the tabletop payment system when a customer enters store A and sits at table A800A. Fig. 8A explains the operation of the tabletop payment system when, after the customer sits at table A800A, the customer performs an appropriate operation to place an order, thereby allowing the management server 100 to identify table A800A where the customer is seated and enable the customer to place an order. The appropriate operation to place an order is an operation (button operation) of the slave 400 and an operation to read the QR code 500 using the user terminal.

[0060] S501: The button 450 of the handset 400 is operated by the customer.

[0061] S502: When the button 450 is operated, the child device 400 transmits the child device ID (child device ID: 1) to the parent terminal 200.

[0062] S503: Upon receiving the child device ID (child device ID: 1) from the child device 400, the parent terminal 200 transmits the child device ID to the management server 100.

[0063] S504: The user terminal 700 acquires the QRID (QRID:11) by reading the QRID (QRID:11) from the QR11 500a.

[0064] S505: Upon acquiring the QRID (QRID: 11), the user terminal 700 transmits the QRID (QRID: 11) to the management server 100.

[0065] S506: Upon receiving the slave unit ID (slave unit ID: 1) and QRID (QRID: 11), the management server 100 refers to the slave unit QR management information 112a and identifies table identification information corresponding to the slave unit ID (slave unit ID: 1) and QRID (QRID: 11). In this example, table identification information indicating table A800A corresponding to slave unit ID: 1 and QRID: 11 is identified.

[0066] S507: When the management server 100 identifies the table identification information, it transmits the identified table identification information (table A) and the menu (menu information 112c) to the user terminal 700.

[0067] S508: The management server 100 transmits to the parent terminal 200 the identified table identification information (table A) and the child device ID: 1 received in S503.

[0068] S509: Upon receiving the specified table identification information (table A) and the handset ID (handset ID: 1), the base terminal 200 transmits a voice guidance command to the handset 400 indicated by the handset ID (handset ID: 1).

[0069] S510: When the handset 400 receives the voice guidance command, the voice guidance unit 460 provides voice guidance. An example of the voice guidance is, "Thank you for visiting us. Please begin your order." Note that the handset 400 may generate a buzzer sound using the buzzer 470 or may cause the light-emitting unit 480 to emit light in addition to or instead of the voice guidance. The command in this case may be referred to as a "guidance command."

[0070] S511: The parent terminal 200 transmits the identified table identification information (table A) to the terminal 300 with a display.

[0071] S512: When the display-equipped terminal 300 receives the specified table identification information (table A), it displays information indicating that a customer is seated at the specified table identification information (table A) on the display 340. By checking the display 340, the staff member can recognize that a customer is seated at table 800 (table A 800A).

[0072] Fig. 8B is a sequence diagram for explaining the operation of the tabletop payment system when a customer enters store A and sits down at table A800A. Fig. 8B explains the operation of the tabletop payment system when a customer does not perform the appropriate operation to place an order after sitting down at table A800A.

[0073] S501 to S503 are the same as the operations described in FIG. 8B.

[0074] S513: The management server 100 determines that the table cannot be identified because it has received only the slave device ID (slave device ID: 1).

[0075] S514: The management server 100 transmits the warning and the slave device ID (slave device ID: 1) received in S513 to the master terminal 200.

[0076] S515: Upon receiving the warning and the slave unit ID (slave unit ID: 1) from the management server 100, the master terminal 200 transmits a voice guidance command to the slave unit 400 indicated by the slave unit ID (slave unit ID: 1).

[0077] S516: When the handset 400 receives the voice guidance command, the voice guidance unit 460 provides voice guidance. An example of the voice guidance is, "Thank you for visiting. Please scan the QR code on the table." Note that the handset 400 may generate a buzzer sound using the buzzer 470 or may cause the light-emitting unit 480 to emit light in addition to or instead of the voice guidance.

[0078] S517: The base terminal 200 transmits a warning to the terminal 300 with a display.

[0079] S515: When the display-equipped terminal 300 receives the warning from the base terminal 200, it displays information indicating that the customer is not performing appropriate operations on the display 340. By checking the display 340, the staff member can recognize that the customer is not performing appropriate operations.

[0080] 9A and 9B are sequence diagrams for explaining the operation of the tabletop payment system when a customer makes a payment for food and drink service received at table A 800A. Note that Fig. 9A and 9B explain the operation of the tabletop payment system when a customer completes payment by performing an appropriate operation to make payment at table 800A. The appropriate operation to make payment is to operate sub-unit 400 (button operation) and read QR 500 using user terminal 700.

[0081] S521: The button 450 of the handset 400 is operated by the customer.

[0082] S522: When the button 450 is operated, the slave device 400 transmits the slave device ID (slave device ID: 1) and a payment request to the master device terminal 200 (master device ID: 100).

[0083] S523: Upon receiving the slave ID (slave ID: 1) and the payment request, the master terminal 200 transmits the slave ID (slave ID: 1), master ID (master ID: 200), and the payment request to the management server 100.

[0084] S524: The user terminal 700 acquires the QRID (QRID:11) by reading the QRID (QRID:11) from the QR11 500a.

[0085] S525: Upon acquiring the QRID (QRID: 11), the user terminal 700 transmits the QRID (QRID: 11) to the management server 100.

[0086] S526: When the management server 100 receives the sub-unit ID (sub-unit ID: 1) and QRID (QRID: 11), it refers to the sub-unit QR management information 112a to identify the table identification information (table A) corresponding to the sub-unit ID (sub-unit ID: 1) and QRID (QRID: 11), as well as the store identification information (A) and restaurant business identification information (X).

[0087] S527: The management server 100 requests authorization from the payment service provider server 600. Authorization is a process for determining whether electronic payment is permitted for a purchaser (user). Authorization is sometimes referred to as "authorization." When authorization is performed, the management server 100 sends the information required for authorization (such as the store identification information and restaurant business identification information identified in S527) and the information required for authorization received from the user terminal 700 (such as information for identifying the user) together with the request.

[0088] S528: When the payment processor server 600 receives the authorization request and the information required for authorization from the management server 100, it performs authorization and sends the authorization result (information indicating whether electronic payment is possible or not) to the management server 100.

[0089] S529: Upon receiving the authorization result, the management server 100 transmits the table identification information (table A), the authorization result, and the slave device ID (slave device ID: 1) to the master terminal 200.

[0090] S530: When the parent terminal 200 receives the table identification information (table A), the authorization result, and the child device ID (child device ID: 1), it completes the settlement for the service (payment of the fee for the service).

[0091] S531: When the base terminal 200 completes payment for the product, it transmits payment completion (information indicating payment completion) to the handset 400 indicated by the handset ID (handset ID: 1).

[0092] S532: The handset 400 provides voice guidance using the voice guidance unit 460. An example of the voice guidance is, "Payment has been completed." Note that the handset 400 may generate a buzzer sound using the buzzer 470 or may cause the light-emitting unit 480 to emit light in addition to or instead of the voice guidance.

[0093] S533: The base terminal 200 transmits the table identification information (table A) and the payment completion (information indicating the payment completion) to the terminal 300 with a display.

[0094] S534: When the display-equipped terminal 300 receives the table identification information (table A) and payment completion (information indicating payment completion) from the base terminal 200, it displays information indicating that payment has been completed for table A 800A indicated by the table identification information on the display 340. By checking the display 340, the staff member can recognize that payment for the food and drink service provided to the customer at table A 800A has been completed.

[0095] 10A and 10B are sequence diagrams for explaining the operation of the tabletop payment system when a customer makes a payment for food and drink service received at table A 800A. Note that Fig. 10A and Fig. 10B explain the operation of the tabletop payment system when the payment is not possible because the customer does not perform the appropriate operation to make the payment at table 800A.

[0096] S521 to S523 are the same as the operations described in FIG. 9A.

[0097] S610: The management server 100 has received only the slave ID (slave ID: 1) and has not received the QRID, and therefore cannot identify the table identification information, store identification information, and restaurant identification information corresponding to the slave ID (slave ID: 1) and the QRID by referring to the slave QR management information 112a. In this case, the management server 100 does not send an authorization request to the payment service provider server 600 and disallows the payment.

[0098] S611: The management server 100 transmits to the parent terminal 200 a warning and the child device ID (child device ID: 1) received in S611.

[0099] S612: Upon receiving the warning and the slave unit ID (slave unit ID: 1) from the management server 100, the master terminal 200 commands the slave unit 400 indicated by the slave unit ID (slave unit ID: 1) to provide voice guidance.

[0100] S613: When the handset 400 receives a voice guidance command from the base terminal 200, it provides voice guidance. An example of the voice guidance is, "Payment cannot be completed. Please perform the payment operation again." Note that the handset 400 may generate a buzzer sound using the buzzer 470 or may cause the light-emitting unit 480 to emit light in addition to or instead of the voice guidance.

[0101] S614: The base terminal 200 transmits a warning to the terminal 300 with a display.

[0102] S615: When the display-equipped terminal 300 receives the warning from the base terminal 200, it displays on the display 340 information indicating that the table A 800A is not available for payment.

[0103] As described above, the tabletop payment system according to the first embodiment makes it possible to change the association between the related information in the slave QR management information 112a stored in the management server 100 and the QRID and slave ID. This allows the restaurant to reuse a set of slave 400 and QR500 at tables 800 within the restaurant simply by changing the related information (table identification information) associated with the QRID and slave ID, making it easy to change the table layout in the restaurant and to substitute slave 400 and QR500. Furthermore, the restaurant can easily change the number of slaves 400 and QR500 installed on tables 800.

[0104] Furthermore, even if the restaurant operator changes, the restaurant can reuse the set of handset 400 and QR500 at another restaurant operator simply by changing the associated information (restaurant operator identification information) associated with the set of handset 400 and QR500, making it easy to respond to changes in restaurant operator.

[0105] Furthermore, even if the restaurant uses the handset 400 and QR500 at another store, the restaurant can reuse the set of handset 400 and QR500 at another store simply by changing the associated information (store ID) associated with the set of handset 400 and QR500, making it easy to respond to changes in the store where the handset 400 and QR500 are used.

[0106] These effects will be explained below using use cases 1 to 5 as examples.

[0107] <Use Case 1> In store A, the layout of table 800 may be changed. For example, suppose the layout of table 800 is changed from that shown in FIG. 1 to that shown in FIG. 11. In the layout of table 800 shown in FIG. 11, table A800A and table B800B in FIG. 1 are combined into a new table A800A1, and a set of handset 1 400a and QR11 500a and a set of handset 2 400b and QR12 500b are installed on this new table A800A1. In other words, the set of handset 2 400b and QR12 500b that was installed on table B800B in FIG. 1 is reused on the new table A800A1.

[0108] In this case, the person making the change updates the slave QR management information 112a held by the management server 100 by inputting instructions to the management server 100 using the person making the change (e.g., an administrator terminal (not shown)), as shown in the flowchart of Figure 12.

[0109] Step 1205: The person who makes the change logs in to the management server 100 using the person who makes the change (for example, an administrator terminal (not shown)) connected to the management server 100 via the network NW1.

[0110] Step 1210: The person making the change inputs to the management server 100, via the terminal of the person making the change, an instruction to select the slave unit QR management information 112a to be changed.

[0111] Step 1215: The person making the change inputs, via the person making the change's terminal (not shown), an instruction to edit the slave device QR management information 112a to be changed to the management server 100. In this example, as shown in Fig. 13, in accordance with the editing instruction, the management server 100 edits the slave device QR management information 112a so as to change the table identification information corresponding to the pre-change slave device ID: 2 from "B" to "A."

[0112] Step 1220: The person making the change inputs, via the person making the change's terminal (not shown), an instruction to save the edited slave device QR management information 112a to the management server 100. In accordance with the instruction, the management server 100 saves the changed slave device QR management information 112a in the storage device 110 of the management server 100 (updating the pre-change slave device QR management information 112a to the changed slave device QR management information 112a).

[0113] Step 1225: The person who makes the change logs out from the management server 100 via the person who makes the change (not shown).

[0114] In this way, when the restaurant changes the layout of table 800 from that shown in Fig. 1 to that shown in Fig. 11, the set of handset 2 400b and QR12 500c installed at table B 800B can be reused at new table A 800A1 simply by having management server 100 update handset QR management information 112a in accordance with instructions entered from the terminal of the person making the change. This allows the restaurant to easily respond to changes in table layout.

[0115] <Use Case 2> There are cases where the restaurant operator that operates store A changes. For example, suppose that the restaurant operator that operates store A is changed from restaurant operator X shown in FIG. 1 to restaurant operator Y. In this case, as shown in the flowchart of FIG. 12, management server 100 updates slave QR management information 112a in accordance with instructions entered from the terminal of the person who made the change. In use case 2, in step 1215, management server 100 edits the information to change the restaurant operator from "X" to "Y," as shown in FIG. 14.

[0116] In this way, when the restaurant operator changes from restaurant operator X shown in Fig. 1 to restaurant operator Y, the management server 100 simply updates the handset QR management information 112a in accordance with instructions input from the terminal of the person making the change, and the multiple sets of handset 400 and QR 500 installed on tables A800A to C800C can be reused by the new restaurant operator Y. This allows the restaurant to easily respond to changes in restaurant operator.

[0117] <Use Case 3> There may be cases where the store where the set of handset 400 and QR50 is used changes. For example, suppose the store where the set of handset 400 and QR50 is used is changed from store A shown in FIG. 1 to store B. In this case, as shown in the flowchart of FIG. 12, the management server 100 updates the handset QR management information 112a in accordance with instructions input from the terminal of the person who made the change. In use case 3, in step 1215, the management server 100 edits the information to change the store from "A" to "B," as shown in FIG. 15.

[0118] In this way, when the restaurant changes the store where multiple sets of handset 400 and QR500 are used from store A to store B, the management server 100 simply updates the handset QR management information 112a in accordance with instructions input from the terminal of the person making the change, and the multiple sets of handset 400 and QR500 used in store A can be reused in the new store B. This allows the restaurant to easily respond to changes in the store where the sets of handset 400 and QR500 are used.

[0119] <Use Case 4> There are cases where the handset 400 and the QR code 500 become unusable. For example, assume that at least one of the handset 400 and the QR code 500 becomes unusable at table A800A shown in FIG. 1 . In this case, assume that a customer has reserved table A800A, and table B800B is not scheduled for use, so that priority must be given to the use of table A800A. In this case, the person making the change places the handset 400 and the QR code 500 set for table B800B at table A800A. As shown in the flowchart of FIG. 12, the management server 100 updates the handset QR code management information 112a in accordance with instructions input from the person making the change. In use case 4, in step 1215, the management server 100 edits the table identification information corresponding to the pre-change handset ID: 2 from "B" to "A," as shown in FIG. 13.

[0120] In this way, if at least one of the handset 400 and the QR code 500 becomes unusable and the restaurant wishes to use another handset 400 or QR code 500 instead, the person making the change can simply update the handset QR code management information 112a.

[0121] <Use Case 5> There are cases where two sets of slave units 400 and QR500 are installed in one table 800. For example, suppose that two sets of slave units 400 and QR500 are installed by adding one set of slave units 400 and QR500 to table A800A shown in FIG. 1. In this case, as shown in the flowchart of FIG. 12, the management server 100 updates the slave unit QR management information 112a in accordance with instructions input from the terminal of the person making the change. In use case 5, in step 1215, the management server 100 edits the table to add a record including slave unit ID: 4, QRID: 14, table: A, store: A, and restaurant operator: X, as shown in FIG. 16.

[0122] In this way, when two handset units 400 and QR codes 500 are installed on one table 800, the restaurant side can easily accommodate this by the person making the change simply updating the handset QR code management information 112a.

[0123] <Benefits of introducing the system> As described below, the tabletop payment system according to the first embodiment has the advantage of significantly reducing the lead time for system implementation compared to conventional technology, which requires a QR code to be placed on the table and which requires specific table identification information to be embedded. This effect will be explained below using Use Case 6 as an example.

[0124] <Use Case 6> In the tabletop payment system according to the first embodiment, a restaurant operator can prepare multiple sets of handset 400 and QR500 for provision. For example, when the tabletop payment system is introduced to store A of restaurant operator X, the restaurant operator X is provided with the necessary number of sets of handset 400 and QR500 from the multiple sets of handset 400 and QR500 prepared in advance. The tabletop payment system can be operated simply by registering the handset identification information of the provided handset 400 and the identification information and related information of the QR500 in the handset QR management information 112a. In conventional technology, it is necessary to embed specific information in the QR depending on the restaurant operator and store where the system is introduced. However, in the tabletop payment system according to the first embodiment, this is not necessary. It is only necessary to register the ID of the handset 400 prepared and provided in advance, the QR ID of the QR500, and related information in the handset QR management information 112a.

[0125] Furthermore, for example, if the tabletop payment system is introduced in a store of a restaurant operator other than restaurant operator X, the other restaurant operator will be provided with the necessary number of sets of handset 400 and QR500 from multiple sets of handset 400 and QR500 prepared in advance. Even in this case, the tabletop payment system can be operated simply by registering the handset ID of the provided handset 400 and the QRID of the QR500 and related information in handset QR management information 112a.

[0126] <Effects> As described above, the table payment system according to the first embodiment allows customers to order food and beverage service items and make payments for food and beverage service without contacting staff at the location where the sub-unit 400 and QR code 500 are installed.

[0127] In the tabletop payment system according to the first embodiment, the slave units 400 and the QR codes 500 are placed in any location (tables A800A to C800C in the example of FIG. 1 ), and table identification information indicating the location (table 800) where the units are placed is associated with the identification information of the slave units 400 and the QR codes 500 placed on the table 800 in the slave unit QR management information 112a. Furthermore, the tabletop payment system makes it possible to change the association between the associated information held by the management server 100 and the QR ID and the slave unit ID. This allows the tabletop payment system to reuse a set of slave units 400 and QR codes 500 at tables 800 in a store simply by changing the associated information (table identification information) associated with the QR ID and the slave unit ID. This makes it possible to easily accommodate changes in the table layout in a store, substitution of slave units 400 and QR codes 500, changes in the number of slave units 400 and QR codes placed on a table 800, and the like.

[0128] Furthermore, even if the restaurant operator that operates the store changes, the tabletop payment system can easily accommodate changes in restaurant operator, as it allows the set of handset 400 and QR500 to be reused at a different restaurant operator simply by changing the related information (restaurant operator identification information) associated with the set of handset 400 and QR500.

[0129] Furthermore, even if the handset 400 and QR500 are used at a different store, the tabletop payment system can easily accommodate changes in the store where the handset 400 and QR500 are used, since the set of handset 400 and QR500 can be reused at a different store simply by changing the associated information (store identification information) associated with the set of handset 400 and QR500.

[0130] The tabletop payment system according to the first embodiment can significantly reduce the lead time for system implementation compared to conventional systems that require specific table information to be embedded and QR codes to be placed on tables. <<Second embodiment>> The following describes a tabletop payment system according to a second embodiment of the present invention. The tabletop payment system according to the second embodiment differs from the tabletop payment system according to the first embodiment only in that the sub-unit 400 and the QR code 500 are installed separately on the table 800, as shown in Fig. 17 .

[0131] The following description will focus on this difference.

[0132] Fig. 18A is a diagram showing an example of the configuration of a tabletop payment system according to Embodiment 2. As shown in Fig. 18A, in the tabletop payment system, a sub-unit 400 and a QR code 500 are installed separately on a table 800.

[0133] When the handset 400 and the QR500 are placed separately on the table 800, it may happen that, due to mischief or employee negligence, the QR12 500b is moved to table A 800A and the QR11 500a is moved to table B, as shown in FIG. 18B, and the QR12 500b and the QR11 500a are not placed on the correct table 800.

[0134] In this case, in the tabletop payment system, when a customer sits at table A and operates handset 400, handset 400 transmits handset ID1 to management server 100 via master terminal 200. User terminal 700 reads QR12 500b, and transmits QRID (QRID:12) to management server 100.

[0135] 3B, there is no correspondence information (record) in which the received slave unit ID (slave unit ID: 1) and QRID (QRID: 12) are associated, and therefore the management server 100 determines that either QR12 500a or slave unit 1 400a is not placed in the correct table 800 (improper installation). In this case, the management server 100 transmits a warning to the master terminal 200. Upon receiving the warning, the master terminal 200 displays a warning on the display 340 of the terminal with display 300 that QR12 500a and slave unit 1 400a are improperly installed.

[0136] By checking the warning displayed on the display 340, the employee can recognize that either the QR12 500a or the handset 1 400a is not placed on the correct table 800 and can take action to correct the incorrect installation.

[0137] <Effects> As described above, the table-top payment system according to the second embodiment of the present invention has the same effects as the first embodiment. Furthermore, the table-top payment system according to the second embodiment can notify an employee of improper installation of the sub-units 400 and QR codes 500 due to mischief or employee negligence.

[0138] <<Modifications>> The present invention is not limited to the above-described embodiments, and various modifications can be adopted within the scope of the present invention. Furthermore, the above-described embodiments can be combined with each other without departing from the scope of the present invention. In the above-described embodiments, the store may be a mobile store.

[0139] In each of the above embodiments, the slave unit 400 may be provided with two buttons: a button for entering and taking a seat, and a button for payment. In this case, when a customer enters the store and takes a seat at the table 800, the slave unit 400 operates the button for entering and taking a seat, and when the customer makes a payment, the slave unit 400 operates the button for payment.

[0140] In each of the above embodiments, a QR code 500 for entering and sitting down and a QR code 500 for payment may be installed together with the sub-unit 400. The QR code 500 for entering and sitting down is required to be read by the user terminal 700 when the customer enters and sits down. The QR code 500 for payment is required to be read by the user terminal when the customer makes a payment.

[0141] In each of the above embodiments, the display-equipped terminal 300 may be a smartphone, tablet, or the like used by an employee. [Explanation of symbols]

[0142] 100... Management server, 110... Storage device, 111... Program, 112... Database, 112a... Child device QR management information, 112b... Parent device / child device management information, 112c... Menu information, 120... Memory, 130... CPU, 140... Input / output interface, 150... Network interface, 160... Bus, 200... Parent device terminal, 300... Terminal with display, 400... Child device, 500... QR, 600... Payment service provider server, 700... User terminal

Claims

1. A parent terminal; a plurality of slave devices capable of wirelessly communicating with the master terminal in a low-power manner; a plurality of information storage media placed on a table together with the slave unit; a management server that can communicate with the parent terminal and the user terminal via a network and has a storage device; A table payment system comprising: the management server stores in the storage device management information including a plurality of pieces of correspondence information in which child device identification information for identifying the child device, information storage medium identification information for identifying the information storage medium installed on the table together with the child device, and related information which is information related to the child device and the information storage medium are associated with each other; the management server is capable of changing the association of the association information; Table payment system.

2. The tabletop payment system according to claim 1, The management server receives information transmitted from the slave unit via the master terminal based on the operation of the slave unit by the customer and the reading operation of the information storage medium by the customer's user terminal, and information transmitted from the user terminal, and performs processing for receiving service at the table where the customer is seated and processing for making payment for the service received by the customer at the table using the received information. Table payment system.

3. The tabletop payment system according to claim 1, the association information includes table identification information that indicates the table in which the slave device and the information storage medium are installed, when the table in which the set of the slave device and the information storage medium is installed is changed, the management server changes the table identification information associated with the slave device identification information and the information storage medium identification information to the table identification information indicating the changed table in accordance with an instruction input to the management server. Table payment system.

4. The tabletop payment system according to claim 1, the related information includes store identification information indicating a store in which the plurality of slave units and the plurality of information storage media are installed, when the store in which the plurality of slave units and the plurality of information storage media are installed is changed, the management server changes the store identification information associated with the slave unit identification information and the information storage medium identification information to the store identification information indicating the changed store, in accordance with an instruction input to the management server. Table payment system.

5. The tabletop payment system according to claim 1, the related information includes restaurant business operator identification information that identifies a restaurant business operator that operates a store in which the plurality of slave units and the plurality of information storage media are installed, When the restaurant business operator that operates the store is changed, the management server changes the restaurant business operator identification information associated with the slave unit identification information and the information storage medium identification information to the restaurant business operator identification information that indicates the changed restaurant business operator, in accordance with instructions input to the management server. Table payment system.

6. The tabletop payment system according to claim 1, the master terminal receives the slave device identification information from the slave device and transmits the received slave device identification information to the management server; The management server receiving the child device identification information from the parent device terminal, and receiving the information storage medium identification information read by the user terminal from the information storage medium through communication from the user terminal; identifying the related information associated with the received slave unit identification information and information storage medium identification information based on the management information; Table payment system.

7. The tabletop payment system according to claim 3, a display-equipped terminal communicably connected to the parent terminal and having a display capable of displaying images; The slave unit includes an operating device, When a customer enters the store and sits at the table where the handset is installed operates the operation device of the handset, the handset transmits the handset identification information to the base terminal, Upon receiving the child device identification information, the parent terminal transmits the child device identification information to the management server; The management server receiving the child device identification information from the parent device terminal, and receiving the information storage medium identification information read by the user terminal from the information storage medium through communication from the user terminal; If the table identification information associated with the received slave device identification information and information storage medium identification information can be identified based on the management information, the identified table identification information and slave device identification information are transmitted to the user terminal and the master terminal; the base terminal transmits a guide command to the slave unit identified by the slave unit identification information, and transmits the specified table identification information received from the management server to the terminal with a display; the display-equipped terminal displays on the display information indicating that the customer is seated at the table identified by the table identification information. Table payment system.

8. The tabletop payment system according to claim 1, a display-equipped terminal communicably connected to the parent terminal and having a display capable of displaying images; The slave unit includes an operating device, the related information includes table identification information indicating the table at which the slave unit and the information storage medium are installed, store identification information indicating a store at which a plurality of the slave units and a plurality of the information storage media are installed, and restaurant business operator identification information identifying a restaurant business operator that operates the store at which a plurality of the slave units and a plurality of the information storage media are installed, When the customer who has received a service at the table where the slave is installed operates the operation device of the slave, the slave transmits the slave identification information and a payment request to the base terminal; When the master terminal receives the slave identification information and the payment request, the master terminal transmits the slave identification information and the payment request to the management server; The management server If the table identification information, the store identification information, and the restaurant business identification information associated with the received slave unit identification information and information storage medium identification information can be identified based on the management information, an authorization request is made to a payment business server, an authorization result is received from the payment business server, and the authorization result, the identified table identification information, and the slave unit identification information are transmitted to the parent terminal; The parent terminal transmits information indicating the completion of the payment and a guidance command to the child device indicated by the child device identification information based on the authorization result, and transmits the specified table identification information received from the management server to the terminal with a display, the terminal with a display displays on the display information indicating that the settlement for the table identified by the table identification information has been completed. Table payment system.

9. The tabletop payment system according to claim 1, a display-equipped terminal communicably connected to the parent terminal and having a display capable of displaying images; the master terminal receives the slave device identification information from the slave device and transmits the received slave device identification information to the management server; The management server receiving the child device identification information from the parent device terminal, and receiving the information storage medium identification information read by the user terminal from the information storage medium through communication from the user terminal; The management server If the correspondence information in which the received slave unit identification information and the information storage medium identification information are associated does not exist in the management information, transmitting a warning to the parent terminal that the information storage medium and the child device are installed improperly; the terminal with a display displays on the display a warning that the information storage medium and the slave unit are improperly installed. Table payment system.

10. A parent terminal; a plurality of slave devices capable of wirelessly communicating with the master terminal in a low-power manner; a plurality of information storage media placed on a table together with the slave unit; a management server that can communicate with the parent terminal and the user terminal via a network and has a storage device; A table settlement method using the management server stores in the storage device management information including a plurality of pieces of correspondence information in which child device identification information for identifying the child device, information storage medium identification information for identifying the information storage medium installed on the table together with the child device, and related information which is information related to the child device and the information storage medium are associated with each other; the management server is capable of changing the association of the association information; Table payment method.

Images