Table payment system and table payment method

Abstract

This invention provides a table settlement system and method that allow for easy reuse of sets of sub-units and information storage media. [Solution] The table settlement system comprises a master terminal, a plurality of slave units that can communicate with the master terminal via low-power wireless communication over a network, a plurality of information storage media installed with each of the plurality of slave units, and a management server that can communicate with the master terminal and user terminals via a network and has a storage device. A set of slave units and information storage media is installed at each of the plurality of tables, and the management server stores management information in its storage device that includes a plurality of correspondence pieces in which slave unit identification information, information storage media identification information and related information are associated with each other. The management server can change the correspondence of the correspondence pieces.

Description

Technical Field

[0001] The present invention relates to a table settlement system and a table settlement method.

Background Art

[0002] In restaurants such as restaurants and cafes, various technologies have been introduced to improve the convenience of customers. Among them, a table settlement system is attracting attention, which is a system that allows customers to complete orders and payments at the table without contacting employees using their own smartphones or tablets.

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

[0004] In the restaurant where this conventional system is introduced, on all the tables where customers sit, labels with QR codes (registered trademarks) as two-dimensional codes in which the store number information of the store, the unique table number information for all tables, and the address information of the system are recorded in advance are pasted. When a customer visits the store, by using the QR code (registered trademark) reading function of their own smartphone to read the QR code (registered trademark) printed on the label, the system placed on the cloud and the customer's smartphone are linked through the Internet. After that, the customer can use their own smartphone to follow the procedures executed by the system and perform food order and payment processing for the ordered food without going through the store staff.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] The inventors of this application are considering a novel table payment system comprising a master terminal, a set of multiple slave units that communicate wirelessly with the master terminal using low-power wireless communication, and one or more information storage media (such as QR codes and NFC (Near Field Communication) tags). In this table payment system, a set of slave units and one or more information storage media can be installed at any location (table), allowing customers to place orders and make payments at that location. This table payment system requires the reuse of the set of slave units and information storage media at tables other than the specific table and at other stores in order to accommodate changes in table layout and reuse at other stores.

[0007] In the conventional system, the QR code (registered trademark) stores desk number information corresponding to a specific desk and store number information corresponding to a specific store. The conventional system installs the QR code (registered trademark) at the specific desk and store indicated by the information embedded in the QR code (registered trademark), enabling ordering and payment at those locations.

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

[0009] This invention was made to solve the above problems. Specifically, one of the objectives of this invention is to provide a table settlement system and a table settlement method that allows for easy reuse of sets of sub-units and information storage media. [Means for solving the problem]

[0010] To solve the above problems, the table settlement system of the present invention comprises a master terminal, a plurality of slave units that can communicate with the master terminal via low-power wireless communication, a plurality of information storage media installed on a table together with the slave units, and a management server that can communicate with the master terminal and user terminals via a network and has a storage device, wherein the management server stores management information in its storage device that includes a plurality of correspondence pieces of information which are associated with each other, and the correspondence pieces of information which are associated with each other, and the management server can change the correspondence of the correspondence pieces of information.

[0011] The present invention provides a table settlement method that includes a master terminal, a plurality of slave units that can communicate with the master terminal via low-power wireless communication, a plurality of information storage media installed on a table together with the slave units, and a management server that can communicate with the master terminal and user terminals via a network and has a storage device, wherein the management server stores in its storage device management information that includes a plurality of correspondence pieces of information, each of which is associated with a slave unit identification information that identifies the slave unit, an information storage medium identification information that identifies the information storage media installed on the table together with the slave unit, and related information that is information related to the slave unit and the information storage media, and the management server can change the association of the correspondence pieces of information. [Effects of the Invention]

[0012] According to the present invention, the set of the slave unit and the information storage medium can be easily reused. The effects described herein are not necessarily limited, and any of the effects described herein may be present. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 shows an example configuration of a table settlement system according to the first embodiment of the present invention. [Figure 2]FIG. 2 is a diagram showing an example of the hardware configuration of the management server. [Figure 3A] FIG. 3A is a diagram for explaining the child unit QR management information. [Figure 3B] FIG. 3B is a diagram for explaining a specific example of the child unit QR management information. [Figure 3C] FIG. 3C is a diagram for explaining the parent unit - child unit management information. [Figure 4] FIG. 4 is a diagram showing an example of the hardware configuration of the parent unit terminal. [Figure 5] FIG. 5 is a diagram showing an example of the hardware configuration of the terminal with a display. [Figure 6A] FIG. 6A is a diagram showing an example of the hardware configuration of the child unit. [Figure 6B] FIG. 6B is a diagram showing the appearance of the child unit and the QR. [Figure 7] FIG. 7 is a diagram showing an example of the hardware configuration of the user terminal. [Figure 8A] FIG. 8A is a sequence diagram for explaining the operation of the table settlement system. [Figure 8B] FIG. 8B is a sequence diagram for explaining the operation of the table settlement system. [Figure 9A] FIG. 9A is a sequence diagram for explaining the operation of the table settlement system.​​​​​​​​​​​​​​​​​​​​Figure 14 is a diagram illustrating a use case. [Figure 15] Figure 15 is a diagram illustrating a use case. [Figure 16] Figure 16 is a diagram illustrating a use case. [Figure 17] Figure 17 shows the external appearance of the sub-unit and QR. [Figure 18A] Figure 18A shows an example configuration of a table settlement system according to a second embodiment of the present invention. [Figure 18B] Figure 18B is a diagram illustrating the operation of the table settlement system according to the second embodiment. [Modes for carrying out the invention]

[0014] The embodiments of the present invention will be described below with reference to the drawings. In all the drawings of the embodiments, the same or corresponding parts may be denoted by the same reference numerals. In the following description, various types of information may be described using expressions such as "table" and "record," but these types of information may be represented by data structures other than these. When describing identification information, the expression "ID" will be used, but other expressions are possible. In the following description, the device may be used as the subject when describing processing, but the subject of the processing may be the CPU or the like instead of the device.

[0015] <<First Embodiment>> A table payment system according to the first embodiment of the present invention will now be described. Figure 1 is a diagram showing an example configuration of a table payment system according to the first embodiment of the present invention. As shown in Figure 1, the table 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 QR codes 500c, a payment service provider server 600, and a user terminal 700. Although not shown in the diagram, the table payment system may also include a terminal for an administrator who manages the table payment system.

[0016] In this example, a table payment system is installed in store A, which is operated by restaurant operator X. Store A is equipped with a master terminal 200, a terminal with a display 300, slave units 1 400a, 2 400b, 3 400c, QR11 500a, QR12 500b, QR13 500c, table A 800A, table B 800B, and table C 800C.

[0017] Table A800A is equipped with slave unit 1 400a and QR11 500a, table B800B is equipped with slave unit 2 400b and QR12 500b, and table C800C is equipped with slave unit 3 400c and QR13 500c. Hereafter, slave unit 1 400a, slave unit 2 400b, and slave unit 3 400c may be referred to as "slave unit 400" when there is no need to distinguish between them. QR11 500a, QR12 500b, and QR13 500c may be referred to as "QR500" when there is no need to distinguish between them. Tables A800A, B800B, and C800C may be referred to as "table 800" when there is no need to distinguish between them.

[0018] The management server 100, the master terminal 200, the payment service provider server 600, and the user terminal 700 are connected to each other via network NW1, enabling communication between them. The master terminal 200 and multiple slave units 400a to 400c are connected to each other via low-power wireless communication using low-power wireless technologies (such as PAN (Personal Area Network) and LPWA (Low Power Wide Area)).

[0019] Figure 2 shows an example of the hardware configuration of the management server 100. As shown in Figure 2, the management server 100 includes 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, storage device 110, memory 120, input / output interface 140, and network interface 150 are connected via a bus 160.

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

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

[0022] Database 112 includes child device QR management information 112a, master-child device management information 112b, and menu information 112c. Child device QR management information 112a and / or master-child device management information 112b may be referred to as "management information".

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

[0024] Specifically, the slave unit ID 112a1 stores the slave unit ID (slave unit identification information) for identifying slave unit 400. The QRID 112a2 stores the QRID (QR identification information) for identifying QR500. The related information 112a3 stores related information. Related information is information related to slave units 400 and QR500 that is associated with the slave unit ID and QRID, and is at least one of the following: for example, table identification information, store identification information, and restaurant operator identification information.

[0025] The information (records) at the row level is sometimes referred to as "correspondence information." Correspondence information associates the identification information (slave unit ID, QRID) of the slave unit 400 and QR500 installed together on the table with store identification information indicating the store where the slave unit 400 and QR500 are installed, and restaurant business identification information indicating the restaurant business operator that manages the store where the slave unit 400 and QR500 are installed.

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

[0027] In the example shown in Figure 3B, only one child ID and one QR ID are associated with the related information (table identification information, store identification information, and restaurant operator identification information) in a single record. However, multiple child IDs and multiple QR IDs may be associated.

[0028] Figure 3C is a diagram illustrating the master-slave management information 112b. As shown in Figure 3C, the master-slave management information 112b includes the master ID 112b1, slave 1 112b2, slave 2 112b3, and slave 3 112b4 as columns for storing information (values). The master-slave management information 112b stores information corresponding to each column regarding the master terminal 200 and the multiple slave units 400 that perform low-power wireless communication with the master terminal 200, with the information being associated with each other and stored as row-level information (records).

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

[0030] Menu information 112c contains information about the menu items offered as part of the food and beverage services provided at the store.

[0031] Referring again to Figure 2, as mentioned above, the program 111 executed by the CPU 130 is loaded into memory 120, and data used by the CPU 130 when executing program 111 is temporarily stored there.

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

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

[0034] The CPU 210 loads the program stored in the storage device 230 into the memory 220. The CPU 210 executes various processes by running the program loaded into the memory 220. The storage device 230 is a non-volatile storage device that can be read from and written to. The storage device 230 stores (retains and holds) programs for controlling the master terminal 200. The storage device 230 also stores slave device management information 231. The slave device management information 231 stores information necessary for communication with the slave device 400. The storage device 230 also stores a master device ID for identifying the master 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 connecting to the terminal 300 with a display.

[0036] Figure 5 shows an example of the hardware configuration of a terminal with a display 300. As shown in Figure 5, the terminal with a display 300 includes a CPU 310, memory 320, storage device 330, display 340, and communication unit 350.

[0037] The CPU 310 loads the program stored in the storage device 330 into the memory 320. The CPU 310 executes various processes by running the program loaded into the memory 320. The storage device 330 stores programs for controlling the terminal 300 with a display, 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 master terminal 200.

[0038] Figure 6A shows an example of the hardware configuration of the slave unit 400. As shown in Figure 6A, the slave unit 400 includes 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 program stored in the storage device 430 into the memory 420. The CPU 410 executes various processes by running the program loaded into the memory 420. The storage device 430 stores programs for controlling the slave device 400, etc. The storage device 430 is a non-volatile storage device that can read and write data. The storage device 430 stores (remembers, holds) programs, etc. The storage device 430 also stores master device information 431. The master device information 431 stores information necessary for communication with the master terminal 200. The storage device 430 also stores a slave device ID for identifying the slave device 400.

[0040] The first communication unit 440 is a communication interface used for communication with the master terminal 200. The button 450 is an operating device operated by the 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 for supplying power to the slave unit 400.

[0041] Figure 6B shows the external appearance of the slave unit 400 and QR500. As shown in Figure 6B, the slave unit 400 and QR500 are installed as a single unit on each table 800. Further details will be described in the second embodiment, but the slave unit 400 and QR500 may also be installed separately on each table 800 (see Figure 17).

[0042] QR500 is an information storage medium that stores information and allows that information to be read by a specific device (e.g., a user terminal 700). QR500 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 similar material. QR500 stores information necessary for executing electronic payments, such as information indicating the location of the management server 100 and the payment service provider server 600 on the network NW1 (URL (Uniform Resource Locator)), QR500 identification information (QRID), and information necessary to identify the table 800 where the customer is seated. Note that other information storage media, such as NFC tags capable of storing information, may be used instead of QR codes (registered trademark) in QR500. The QR500 identification information (QRID) and the NFC tag identification information may be referred to as "information storage medium identification information."

[0043] The payment service provider server 600 provides electronic payment services. The payment service provider server 600 can be configured with the same hardware configuration as the management server 100 shown in Figure 2.

[0044] Figure 7 shows an example of the hardware configuration of a user terminal 700. As shown in Figure 7, the user terminal 700 includes a CPU 710, memory 720, 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, memory 720, storage device 730, various sensors 740, touch panel 750, communication unit 760, NFC communication unit 770, and imaging unit 780 are connected via a bus. An example of a 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 memory 720. The CPU 710 executes various processes by running the programs loaded into memory 720. The storage device 730 is a non-volatile storage device that can read and write data. The storage device 730 stores (retains) programs for controlling the user terminal 700 and applications for using electronic payment services.

[0046] The various sensors 740 include position sensors, geomagnetic sensors, distance sensors, acceleration sensors, and gyroscopes. These sensors enable the detection of the user terminal 700's position, orientation, direction of movement, motion, tilt, etc. The user terminal 700 may also be equipped with other sensors, such as illuminance sensors and proximity sensors.

[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 that can be connected to the network NW1. Under the control of the CPU 710, the communication unit 760 communicates with external devices connected to the network NW1. For example, the communication unit 760 communicates with external devices such as the management server 100 and the payment service provider server 600.

[0049] The NFC communication unit 770 performs NFC communication when in close proximity to a compatible reader / writer. The NFC communication unit 770 is equipped with a coding circuit, a decoding circuit, an antenna, and the like.

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

[0051] The communication unit 760 may also include other communication units, such as a Bluetooth® communication unit or an infrared communication unit.

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

[0053] Referring again to Figure 1, in a restaurant (store A) to which the table payment system according to the first embodiment is applied, a master terminal 200 and a set of slave units 400 and QR 500 are installed. The set of slave units 400 and QR 500 is installed at each table 800. The management server 100 holds slave unit QR management information 112a which includes multiple records (correspondence information) in which the slave unit ID, QR ID, and related information are associated.

[0054] In the table payment system, the sub-unit 400 and QR 500 are installed at any location (tables A800A to C800C in the example in Figure 1), and table identification information indicating the installation location (table 800) is associated with the sub-unit 400 and QR 500 in the sub-unit QR management information 112a. In the table payment system, customers can order food and beverages and make payments for food and beverage services at the location (table 800) where the sub-unit 400 and QR 500 are installed, without any contact with employees.

[0055] The detailed operation of the table payment system will be described later with reference to Figures 8A to 10B, but in the table payment system, the management server 100 identifies the table 800 (place where orders are placed and food and beverage services are received) where the customer is seated (the place where orders are placed and food and beverage services are received) based on the slave unit ID sent from the slave unit 400, the QR ID sent from the user terminal 700, and the slave unit QR management information 112a, and notifies the employee. The employee recognizes the table 800 where the customer to whom food and beverage services are to be provided is seated.

[0056] In the table payment system, the management server 100 sends the menu (menu information 112c) to the user terminal 700. By selecting from the menu displayed on the user terminal 700, customers can order food and beverage services (dishes, drinks, etc.) from the menu.

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

[0058] In this way, the table payment system allows customers at a restaurant (store A) to order and pay at table 800 without any contact with staff.

[0059] <Operation> Figure 8A is a sequence diagram illustrating the operation of the table payment system when a customer enters store A and sits down at table A800A. Figure 8A further illustrates the operation of the table payment system when, after the customer sits down at table A800A, the management server 100 identifies the table A800A where the customer is seated and makes it possible to place an order. The appropriate operation for placing an order is the operation of the slave unit 400 (button operation) and the reading of the QR code 500 by the user terminal.

[0060] S501: Button 450 on handset 400 is operated by the customer.

[0061] S502: When button 450 is pressed, the sub-unit 400 transmits the sub-unit ID (sub-unit ID: 1) to the master terminal 200.

[0062] S503: When the master terminal 200 receives the child device ID (child device ID: 1) from the child device 400, it sends the child device ID to the management server 100.

[0063] S504: User terminal 700 obtains the QRID (QRID:11) by reading the QRID (QRID:11) from QR11 500a.

[0064] S505: When user terminal 700 obtains a QRID (QRID:11), it sends the QRID (QRID:11) to the management server 100.

[0065] S506: When the management server 100 receives the child device ID (child device ID:1) and QRID (QRID:11), it refers to the child device QR management information 112a to identify the table identification information corresponding to the child device ID (child device ID:1) and QRID (QRID:11). In this example, table identification information indicating table A800A corresponding to child device ID:1 and QRID:11 is identified.

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

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

[0068] S509: When the master terminal 200 receives the identified table identification information (Table A) and the slave unit ID (Slave unit ID: 1), it sends a voice guidance command to the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1).

[0069] S510: When the sub-unit 400 receives a voice guidance command, it provides voice guidance via the voice guidance unit 460. An example of voice guidance is, "Thank you for visiting. Please begin placing your order." The sub-unit 400 may also generate a buzzer sound using the buzzer 470 or illuminate the light-emitting unit 480, either in conjunction with or instead of voice guidance. In this case, the command may be referred to as a "guidance command."

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

[0071] S512: When the terminal 300 with a display receives the identified table identification information (table A), it displays information on the display 340 indicating that a customer is seated at the identified table identification information (table A). By checking the display 340, the employee can recognize that a customer is seated at table 800 (table A800A).

[0072] Figure 8B is a sequence diagram illustrating the operation of the table payment system when a customer enters store A and sits down at table A800A. Figure 8B also illustrates the operation of the table payment system when the customer does not perform the appropriate steps to place an order after sitting down at table A800A.

[0073] Steps S501 through S503 are the same as those described in Figure 8B.

[0074] S513: Management server 100 has only received the child device ID (child device ID: 1), therefore it determines that the table cannot be identified.

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

[0076] S515: When the master terminal 200 receives a warning and a slave unit ID (Slave unit ID: 1) from the management server 100, it sends a voice guidance command to the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1).

[0077] S516: When the sub-unit 400 receives a voice guidance command, it provides voice guidance via the voice guidance unit 460. An example of voice guidance is, "Thank you for visiting. Please scan the QR code on the table." The sub-unit 400 may also generate a buzzer sound using the buzzer 470 or illuminate the light-emitting unit 480, either in conjunction with or instead of voice guidance.

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

[0079] S515: When the terminal 300 with a display receives a warning from the master terminal 200, it displays information on the display 340 indicating that the customer is not performing the correct operation. By checking the display 340, employees can recognize that the customer is not performing the correct operation.

[0080] Figures 9A and 9B are sequence diagrams illustrating the operation of the table payment system when a customer makes a payment for food and beverage services received at table A800A. Figures 9A and 9B illustrate the operation of the table payment system when payment is completed by the customer performing the appropriate actions for payment at table 800A. The appropriate actions for payment include operating the sub-unit 400 (button operation) and reading the QR code 500 with the user terminal 700.

[0081] S521: Button 450 on handset 400 is operated by the customer.

[0082] S522: When button 450 is pressed, the sub-unit 400 sends the sub-unit ID (sub-unit ID: 1) and payment request to the master terminal 200 (master terminal ID: 100).

[0083] S523: When the master terminal 200 receives the slave ID (Slave ID: 1) and payment request, it sends the slave ID (Slave ID: 1), master ID (Master ID: 200), and payment request to the management server 100.

[0084] S524: User terminal 700 obtains the QRID (QRID:11) by reading the QRID (QRID:11) from QR11 500a.

[0085] S525: When user terminal 700 obtains a QRID (QRID:11), it sends the QRID (QRID:11) to management server 100.

[0086] S526: When the management server 100 receives the child device ID (child device ID:1) and QRID (QRID:11), it refers to the child device QR management information 112a to identify the table identification information (table A) corresponding to the child device ID (child device 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 the process of 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 necessary information for authorization (such as the store identification information and restaurant business identification information identified in S527) and the necessary information for authorization received from the user terminal 700 (such as information identifying the user) along with the request.

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

[0089] S529: When the management server 100 receives the authorization result, it sends the table identification information (table A), the authorization result, and the child device ID (child device ID: 1) to the master terminal 200.

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

[0091] S531: When the master terminal 200 completes the payment for the product, it sends a payment completion message (information indicating payment completion) to the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1).

[0092] S532: The sub-unit 400 provides voice guidance via the voice guidance unit 460. An example of voice guidance is, "Payment has been completed." The sub-unit 400 may also generate a buzzer sound via the buzzer 470 or illuminate the light-emitting unit 480, either in conjunction with or instead of voice guidance.

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

[0094] S534: When the terminal with display 300 receives table identification information (table A) and payment completion information (information indicating payment completion) from the master terminal 200, it displays information on the display 340 indicating that table A800A, indicated by the table identification information, has been paid for. By checking the display 340, employees can recognize that payment for the food and beverage services provided to the customer at table A800A has been completed.

[0095] Figures 10A and 10B are sequence diagrams illustrating the operation of the table payment system when a customer makes a payment for food and beverage services received at table A800A. Figures 10A and 10B also illustrate the operation of the table payment system when payment becomes impossible due to the customer failing to perform the appropriate steps to make a payment at table 800.

[0096] Steps S521 through S523 are the same as those described in Figure 9A.

[0097] S610: The management server 100 has only received the child device ID (child device ID: 1) and has not received the QR ID. Therefore, it cannot refer to the child device QR management information 112a to identify the table identification information, store identification information, and restaurant identification information corresponding to the child device ID (child device ID: 1) and QR ID. In this case, the management server 100 does not send an authorization request to the payment service provider server 600 and the payment is not possible.

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

[0099] S612: When the master terminal 200 receives a warning and a slave unit ID (Slave unit ID: 1) from the management server 100, it commands the slave unit 400 indicated by the slave unit ID (Slave unit ID: 1) to send a voice guidance.

[0100] S613: When the sub-unit 400 receives a voice guidance command from the master terminal 200, it provides voice guidance. An example of voice guidance is, "Payment could not be processed. Please try the payment operation again." In addition, the sub-unit 400 may generate a buzzer sound using the buzzer 470 or illuminate the light-emitting unit 480 along with or instead of providing voice guidance.

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

[0102] S615: When the terminal 300 with a display receives a warning from the master terminal 200, it displays information on the display 340 indicating that table A800A cannot be settled.

[0103] As described above, the table payment system according to the first embodiment allows the association between the QR ID and the child device ID and the related information of the child device QR management information 112a held by the management server 100 to be changed. As a result, the restaurant can reuse the child device 400 and QR 500 set at tables 800 within the store simply by changing the related information (table identification information) associated with the QR ID and child device ID, and can easily accommodate changes in the table layout of the store or the substitution of child devices 400 and QR 500. In addition, the restaurant can easily accommodate changes in the number of child devices 400 and QR 500 installed at tables 800.

[0104] Furthermore, even if the restaurant operator changes, the restaurant can easily adapt to changes in the restaurant operator by simply changing the related information (restaurant operator identification information) associated with the 400 and QR500 handset set to another restaurant operator.

[0105] Furthermore, even if a restaurant uses the 400 and QR500 sub-units at a different location, they can easily reuse the 400 and QR500 set at another location simply by changing the associated information (store ID) linked to the 400 and QR500 set. This makes it easy to adapt to changes in the locations where the 400 and QR500 are used.

[0106] The following explains these effects using Use Cases 1 through 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 shown in Figure 1 is changed to the layout of table 800 shown in Figure 11. In the table 800 layout shown in Figure 11, tables A800A and B800B from Figure 1 are combined into a new table A800A1, and the set of sub-unit 1 400a and QR11 500a, and the set of sub-unit 2 400b and QR12 500b are installed on this new table A800A1. In other words, the set of sub-unit 2 400b and QR12 500b that was installed on table B800B in Figure 1 is reused on the new table A800A1.

[0108] In this case, the user who made the change updates the slave device QR management information 112a held by the management server 100 by inputting instructions to the management server 100 from the user's terminal (for example, an administrator terminal (not shown)), as shown in the flowchart of Figure 12.

[0109] Step 1205: The user making changes logs into the management server 100 via their terminal (for example, an administrator terminal (not shown)) connected to the management server 100 via network NW1.

[0110] Step 1210: The user making the change inputs a selection instruction for the child device QR management information 112a to be changed to the management server 100 via their terminal.

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

[0112] Step 1220: The user making the changes inputs an instruction to the management server 100 to save the edited child device QR management information 112a via the user's terminal (not shown). The management server 100, in accordance with the instruction, saves the modified child device QR management information 112a to the management server 100's storage device 110 (updating the child device QR management information 112a before the change to the modified child device QR management information 112a).

[0113] Step 1225: The person making the changes logs out of the management server 100 via their terminal (not shown).

[0114] In this way, when a restaurant changes the layout of table 800 from the layout shown in Figure 1 to the layout shown in Figure 11, the management server 100 can simply update the slave device QR management information 112a according to the instructions entered from the user's terminal, and the set of slave devices 2 400b and QR12 500c that was installed on table B800B can be reused on the new table A800A1. This allows restaurants to easily adapt to changes in table layouts.

[0115] <Use Case 2> The restaurant operator managing store A may change. For example, suppose the restaurant operator managing store A changes from restaurant operator X, as shown in Figure 1, to restaurant operator Y. In this case, as shown in the flowchart in Figure 12, the management server 100 updates the child device QR management information 112a according to the instructions entered from the terminal of the person making the change. In use case 2, in step 1215, the management server 100 edits the restaurant operator to change from "X" to "Y", as shown in Figure 14.

[0116] In this way, when a restaurant operator changes from restaurant operator X to restaurant operator Y as shown in Figure 1, the management server 100 can simply update the slave device QR management information 112a according to the instructions entered from the terminal of the operator who made the change, and the multiple sets of slave devices 400 and QR500 installed on tables A800A to C800C can be reused by the new restaurant operator Y. This allows restaurants to easily adapt to changes in their operator.

[0117] <Use Case 3> The store where the set of sub-unit 400 and QR50 is used may change. For example, suppose the store where the set of sub-unit 400 and QR50 is used changes from store A to store B as shown in Figure 1. In this case, as shown in the flowchart in Figure 12, the management server 100 updates the sub-unit QR management information 112a according to the instructions entered from the terminal of the person making the change. In use case 3, in step 1215, the management server 100 edits the store to change from "A" to "B" as shown in Figure 15.

[0118] In this way, when a restaurant changes the location where multiple sets of sub-units 400 and QR500 are used, from store A to store B, the management server 100 can simply update the sub-unit QR management information 112a according to the instructions entered from the terminal of the person making the change, allowing the multiple sets of sub-units 400 and QR500 used at store A to be reused at the new store B. This makes it easy for restaurants to respond to changes in the locations where sets of sub-units 400 and QR500 are used.

[0119] <Use Case 4> There are cases where the sub-units 400 and QR500 become unusable. For example, suppose at least one of the sub-units 400 and QR500 becomes unusable in table A800A as shown in Figure 1. In this case, suppose there is a customer who has reserved table A800A, and table B800B is not scheduled to be used, so the use of table A800A must be prioritized. In this case, the person making the change installs the set of sub-units 400 and QR500 from table B800B into table A800A. As shown in the flowchart in Figure 12, the management server 100 updates the sub-unit QR management information 112a according to the instructions entered from the terminal of the person making the change. In use case 4, in step 1215, the management server 100 edits the table identification information corresponding to the sub-unit ID:2 before the change from "B" to "A", as shown in Figure 13.

[0120] In this way, if at least one of the sub-units 400 and QR500 becomes unusable, the restaurant can easily make the change by simply updating the sub-unit QR management information 112a.

[0121] <Use Case 5> In some cases, two sets of child devices 400 and QR500 may be placed in a single table 800. For example, suppose two sets of child devices 400 and QR500 are placed in table A800A as shown in Figure 1 by adding one set of child devices 400 and QR500. In this case, as shown in the flowchart in Figure 12, the management server 100 updates the child device QR management information 112a according to the instructions entered from the user's terminal. In use case 5, in step 1215, the management server 100 edits to add a record that includes child device ID: 4, QRID: 14, table: A, store: A, and restaurant operator: X, as shown in Figure 16.

[0122] In this way, if a restaurant installs two sub-units (400 and QR500) on a single table (800), the person making the change can easily handle it by simply updating the sub-unit QR management information (112a).

[0123] <Benefits of implementing the system> The table settlement system according to the first embodiment has the advantage of significantly reducing the lead time for system implementation compared to conventional technologies that require the placement of QR codes on tables to embed specific table identification information, as described below. This effect will be explained below using Use Case 6 as an example.

[0124] <Use Case 6> In the table payment system according to the first embodiment, multiple sets of sub-units 400 and QR 500 can be prepared in advance for provision to restaurant operators. For example, when the table payment system is introduced to restaurant operator X's store A, the required number of sets of sub-units 400 and QR 500 are provided to restaurant operator X from the multiple sets of sub-units 400 and QR 500 prepared in advance. The table payment system can be operated simply by registering the sub-unit identification information of the provided sub-unit 400, the identification information of the QR 500 and related information in the sub-unit QR management information 112a. In conventional technology, it is necessary to embed specific information in the QR according to the restaurant operator and store where the system is introduced, but in the table payment system according to the first embodiment, this is not necessary, and it is only necessary to register the ID of the pre-prepared and provided sub-unit 400, the QRID of the QR 500 and related information in the sub-unit QR management information 112a.

[0125] Furthermore, for example, if the table payment system is to be introduced to a restaurant operated by a different restaurant operator than restaurant operator X, the required number of sets of sub-units 400 and QR500 will be provided to the other restaurant operator from a pre-prepared set of sub-units 400 and QR500. Even in this case, the table payment system can be operated simply by registering the sub-unit ID of the provided sub-unit 400 and the QRID and related information of the QR500 in the sub-unit QR management information 112a.

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

[0127] In the table payment system according to the first embodiment, the slave units 400 and QR 500 are installed in any location (tables A800A to C800C in the example of Figure 1), and table identification information indicating the installation location (table 800) is associated with the identification information of the slave units 400 and QR 500 installed in table 800 in the slave unit QR management information 112a. Furthermore, the table payment system allows the association between the related information held by the management server 100 and the QR ID and slave unit ID to be changed. As a result, the table payment system can reuse sets of slave units 400 and QR 500 in tables 800 within the store simply by changing the related information (table identification information) associated with the QR ID and slave unit ID, making it easy to respond to changes in the table layout in the store, substitution of slave units 400 and QR 500, and changes in the number of slave units 400 and QR 500 installed in table 800.

[0128] Furthermore, the table payment system can easily accommodate changes in restaurant operators, as it only requires updating the associated information (restaurant operator identification information) linked to the 400 and QR500 handset set, allowing the set to be reused by a different restaurant operator.

[0129] Furthermore, the table payment system allows for easy adaptation to changes in the stores using the 400 and QR500 devices, as the only change required is the associated information (store identification information) linked to the 400 and QR500 device set.

[0130] The table payment system according to the first embodiment can significantly reduce the lead time for system implementation compared to conventional systems that require a QR code to be placed on the table to embed specific table information. <<Second Embodiment>> A table payment system according to a second embodiment of the present invention will now be described. The table payment system according to the second embodiment differs from the table payment system according to the first embodiment in that, as shown in Figure 17, the slave unit 400 and QR 500 are installed separately on the table 800.

[0131] The following explanation will focus on these differences.

[0132] Figure 18A shows an example of the configuration of a table payment system according to the second embodiment. As shown in Figure 18A, the table payment system has a slave unit 400 and a QR 500 installed separately on the table 800.

[0133] When the sub-unit 400 and QR500 are installed separately on table 800, due to vandalism or employee negligence, as shown in Figure 18B, QR12 500b may be moved to table A800A and QR11 500a may be moved to table B, resulting in QR12 500b and QR11 500a not being installed on the correct table 800.

[0134] In this case, with the table payment system, when a customer sits down at table A and operates the sub-unit 400, the sub-unit ID 1 is transmitted from the sub-unit 400 to the management server 100 via the master terminal 200. When the user terminal 700 reads the QR12 500b, the QRID (QRID:12) is transmitted to the management server 100.

[0135] The management server 100 determines that, in the slave QR management information 112a in Figure 3B, there is no corresponding information (record) where the received slave ID (slave ID: 1) and QRID (QRID: 12) are associated, and therefore either QR12 500a or slave 1 400a is not placed in the correct table 800 (improper placement). In this case, the management server 100 sends a warning to the master terminal 200. Upon receiving the warning, the master terminal 200 displays a warning on the display 340 of the display-equipped terminal 300 indicating that there is an improper placement of QR12 500a and slave 1 400a.

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

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

[0138] <<Variation>> The present invention is not limited to the embodiments described above, and various modifications can be adopted within the scope of the invention. Furthermore, the embodiments described above can be combined with each other as long as they do not depart from the scope of the invention. In the embodiments described above, the store may be a mobile store.

[0139] In each of the above embodiments, the sub-unit 400 may be equipped with two buttons: a button for entering the store and sitting down, and a button for payment. In this case, the button for entering the store and sitting down is operated when the customer enters the store and sits down at the table 800, and the button for payment is operated when the customer makes a payment.

[0140] In each of the above embodiments, a QR code 500 for entry and seating and a QR code 500 for payment may be installed together with the sub-unit 400. The QR code 500 for entry and seating is to be read by the customer using the user terminal 700 when entering and seating. The QR code 500 for payment is to be read by the customer using the user terminal when making a payment.

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

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

Claims

1. The main terminal and The aforementioned master terminal and multiple slave units capable of low-power wireless communication with each other, Multiple information storage media are installed on the table together with the aforementioned sub-unit, The aforementioned master terminal and user terminal can communicate with each other via a network, and the management server has a storage device, A table payment system equipped with, The management server stores management information in the storage device, which includes a plurality of correspondence pieces of information, each of which is associated with the child device, child device identification information, information storage medium identification information, and related information, which is information related to the child device and the information storage medium. The management server is capable of changing the mapping of the correspondence information. Table payment system.

2. In the table settlement system described in claim 1, The management server receives information transmitted from the slave unit via the master terminal and information transmitted from the user terminal based on the customer's operation of the slave unit and the customer's reading operation of the information storage medium by the user terminal, and uses the received information to process for the customer to receive services at the table where they are seated, and to process for the customer to settle the payment for the services received at the table. Table payment system.

3. In the table settlement system described in claim 1, The aforementioned related information includes table identification information indicating the table on which the slave unit and the information storage medium are installed. When the table on which the set of the slave device and the information storage medium is installed is modified, 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 modified table, in accordance with the instructions input to the management server. Table payment system.

4. In the table settlement system described in claim 1, The related information includes store identification information indicating a store where multiple slave units and multiple information storage media are installed. When the store where the multiple slave units and multiple 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 media identification information to store identification information indicating the changed store, in accordance with the instructions input to the management server. Table payment system.

5. In the table settlement system described in claim 1, The aforementioned related information includes restaurant business identification information that identifies a restaurant business operator that operates a store where multiple slave units and multiple information storage media are installed. When the restaurant operator managing the store is changed, the management server, in accordance with the instructions input to the management server, changes the restaurant operator identification information associated with the slave unit identification information and the information storage medium identification information to the restaurant operator identification information indicating the changed restaurant operator. Table payment system.

6. In the table settlement system described in 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 aforementioned management server The master terminal receives the slave device identification information, and the user terminal receives the information storage medium identification information that the user terminal has read from the information storage medium via communication. Based on the management information, the system identifies the related information associated with the received slave device identification information and the information storage medium identification information. Table payment system.

7. In the table settlement system described in claim 3, The system includes a terminal with a display that is communicatively connected to the aforementioned master terminal and has a display capable of displaying images, The aforementioned sub-unit is equipped with an operating device, When a customer enters the store and sits down at the table where the sub-unit is installed, and operates the operating device of the sub-unit, the sub-unit identification information is transmitted to the master terminal. When the master terminal receives the slave identification information, it transmits the slave identification information to the management server. The aforementioned management server The master terminal receives the slave device identification information, and the user terminal receives the information storage medium identification information that the user terminal has read from the information storage medium via communication. If, based on the management information, the received sub-unit identification information and the information storage medium identification information can be associated with the table identification information, the identified table identification information and the sub-unit identification information are transmitted to the user terminal and the master terminal. The master terminal transmits a guidance command to the slave unit indicated by the slave unit identification information, and transmits the identified 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 customer is seated at the table indicated by the table identification information. Table payment system.

8. In the table settlement system described in claim 1, The system includes a terminal with a display that is communicatively connected to the aforementioned master terminal and has a display capable of displaying images, The aforementioned sub-unit is equipped with an operating device, The related information includes table identification information indicating the table on which the slave unit and the information storage medium are installed, store identification information indicating the store on which multiple slave units and multiple information storage mediums are installed, and restaurant business identification information identifying the restaurant business operator that operates the store on which multiple slave units and multiple information storage mediums are installed. When the operating device of the sub-unit is operated by the customer who has received service at the table on which the sub-unit is installed, the sub-unit transmits the sub-unit identification information and payment request to the master terminal. When the master terminal receives the slave device identification information and the payment request, it transmits the slave device identification information and the payment request to the management server. The aforementioned management server Based on the management information, if the received sub-unit identification information and the information storage medium identification information can be associated with the table identification information, the store identification information, and the restaurant business operator identification information, an authorization request is sent to the payment service provider server, the authorization result is received from the payment service provider server, and the authorization result, the identified table identification information, and the sub-unit identification information are transmitted to the master terminal. The master terminal transmits information indicating the completion of payment and guidance commands to the slave terminal indicated by the slave terminal identification information based on the authorization result, and transmits the identified 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 of the table indicated by the table identification information has been completed. Table payment system.

9. In the table settlement system described in claim 1, The system includes a terminal with a display that is communicatively connected to the aforementioned master terminal and has 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 aforementioned management server The master terminal receives the slave device identification information, and the user terminal receives the information storage medium identification information that the user terminal has read from the information storage medium via communication. The aforementioned management server If the received slave device identification information and the information storage medium identification information are not associated with the corresponding information in the management information, A warning is sent to the master terminal indicating that there is a problem with the installation of the information storage medium and the slave unit. The terminal with a display displays a warning on the display indicating that there is a problem with the installation of the information storage medium and the slave unit. Table payment system.

10. The main terminal and The aforementioned master terminal and multiple slave units capable of low-power wireless communication with each other, Multiple information storage media are installed on the table together with the aforementioned sub-unit, The aforementioned master terminal and user terminal can communicate with each other via a network, and the management server has a storage device, A table payment method using, The management server stores management information in the storage device, which includes multiple correspondence pieces of information, each of which is associated with the child device, child device identification information, information storage medium identification information, and related information, which is information related to the child device and the information storage medium. The management server is capable of changing the mapping of the correspondence information. Table payment method.

Images