Server device, terminal device and program

Abstract

To provide a server device configured to improve convenience of a remote drinking and eating provision service, a terminal device, and a program.SOLUTION: A server device includes: a reservation receiving unit (management unit) which receives accesses from a plurality of store terminals or user terminals (terminal devices) and manages locations of access sources, the terminal devices, and users operating the terminal devices, in association with each other; a terminal communication unit (communication control unit) which connects the associated terminal devices to communicate with each other; a screen display control unit (display control unit) which causes a display unit connected to each of the terminal devices to display a main screen in which images captured by an imaging unit (imaging apparatus) corresponding to each of the terminal devices are arranged; a GUI provision unit (menu provision unit) which provides menu information to be provided in places to which the terminal devices belong so as to be browsed among the terminal devices; an order receiving unit (order receiving unit) which transmits order information received from the terminal devices to a store; and a screen display control unit (price display unit) which displays an amount to be paid for each of the terminal devices on the display unit, in association with images corresponding to the terminal devices.SELECTED DRAWING: Figure 14

Description

[Technical field]

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

[0002] With the spread of teleworking and remote work, web conferencing systems that hold conferences via a network are becoming widely used. Web conferencing systems are also being used for purposes other than business. For example, so-called remote drinking parties are held where drinking parties and other events are held using a web conferencing system. In such remote drinking parties, multiple users visit different stores or stay at home, and each user holds a web conference using a terminal device, allowing them to communicate with other users while eating and drinking food and drink provided by the store or delivered to them.

[0003] Meanwhile, ordering systems for brick-and-mortar stores have been proposed (for example, Patent Document 1). However, the conventional technology assumes that orders are placed at the same store, and does not anticipate situations such as remote drinking parties. Therefore, irregular payment methods such as splitting the bill across stores were not anticipated. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem that the present invention aims to solve is to provide a server device, a terminal device, and a program that can improve the convenience of remote food and drink provision services. [Means for solving the problem]

[0005] The server device of the embodiment includes a management unit, a communication control unit, a display control unit, a menu providing unit, an order receiving unit, and an amount display unit. The management unit receives access from each of terminal devices placed in a plurality of locations, and manages the location of the access source, the terminal device, and a user who operates the terminal device in association with each other. The communication control unit connects the terminal devices associated by the management unit to each other so that they can communicate with each other. The display control unit displays a main screen in which images captured by imaging devices corresponding to each terminal device are arranged on a display unit connected to each terminal device associated by the management unit. The menu providing unit provides menu information indicating products that can be provided at the location to which the terminal device belongs, so that the menu information can be viewed by the terminal devices connected to each other ... [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram showing an example of a system configuration of a remote food and drink providing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the server device according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of a store terminal and a user terminal according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a hardware configuration of the order receiving terminal according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a data configuration of a store management table according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of the remote run management table according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of a delivery store management table according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a data configuration of a store menu management table according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a data configuration of a delivery menu management table according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a data configuration of a user management table according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a data configuration of a reservation management table according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a data configuration of a store order management table according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a data configuration of a delivery order management table according to the embodiment. [Figure 14] FIG. 14 is a functional block diagram showing an example of the functional configuration of the remote food and drink providing system according to the embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a start screen for a remote drinking party displayed on a store terminal or a user terminal. [Figure 16] FIG. 16 is a diagram showing an example of a main screen displayed on a store terminal or a user terminal during a remote drinking party. [Figure 17] FIG. 17 is a first diagram showing an example of a menu selection screen displayed on a store terminal or a user terminal. [Figure 18] FIG. 18 is a second diagram showing an example of a menu selection result displayed on the store terminal or the user terminal. [Figure 19] FIG. 19 is a diagram showing an example of a confirmation screen displayed when presenting a menu to another participant. [Figure 20] FIG. 20 is a diagram showing an example of a confirmation screen displayed when a menu is provided by another participant. [Figure 21] FIG. 21 is a diagram showing an example of an order history displayed on a store terminal or a user terminal. [Figure 22]FIG. 22 is a diagram showing an example of a checkout screen displayed on a store terminal or a user terminal. [Figure 23] FIG. 23 is a diagram showing an example of an amount input screen displayed on the store terminal or the user terminal. [Figure 24] FIG. 24 is a diagram showing an example of a payment screen displayed on the store terminal or the user terminal. [Diagram 25] FIG. 25 is a diagram showing an example of the operation of accounting processing executed by the accounting processing unit. [Figure 26] FIG. 26 is a diagram showing an example of a payment screen when a user leaves midway. [Figure 27] FIG. 27 is a first diagram showing an example of the accounting screen when a user leaves midway. [Figure 28] FIG. 28 is a second diagram showing an example of the accounting screen when a user leaves midway. [Figure 29] FIG. 29 is a diagram showing an example of a main screen that is displayed when a user who is leaving the remote drinking party operates the remote drinking party end button. [Diagram 30] FIG. 30 is a diagram showing an example of a billing screen that is displayed when a user leaving a remote drinking party asks another user to pay. [Diagram 31] FIG. 31 is a flowchart illustrating an example of the flow of the login process executed by the server device of the embodiment. [Diagram 32] FIG. 32 is a flowchart illustrating an example of the flow of a menu selection screen providing process executed by the server device of the embodiment. [Diagram 33] FIG. 33 is a flowchart illustrating an example of the flow of an order process executed by the server device of the embodiment. [Diagram 34] FIG. 34 is a flowchart showing an example of the flow of transaction processing executed by the server device in the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0008] (Outline of remote food and beverage supply system) Fig. 1 is a block diagram showing an example of a system configuration of a remote food and drink provision system according to an embodiment. As shown in Fig. 1, a remote food and drink provision system 10 has a server device 20, store terminals 30 and 40, a user terminal 41, and an order receiving terminal 50. The store terminals 30 and 40 or the user terminal 41 are communicatively connected to the server device 20 via a network N such as the Internet or a mobile phone network. The server device 20, the store terminals 30 and 40, the user terminal 41, and the order receiving terminal 50 may be connected to the network N via wired communication or wireless communication.

[0009] The store terminal 30 is a terminal device provided in each store 60, which is a restaurant such as an izakaya. The store terminal 30 is, for example, an ordering terminal for self-ordering provided at each seat in the store 60, and is realized by, for example, a PC (Personal Computer) or a tablet terminal. There is no particular limit to the number of store terminals 30 provided in the store 60, and there may be more than one. The store terminal 30 is an example of a terminal device.

[0010] Each of the stores 60 is equipped with a store server (not shown) for receiving order information sent from the store terminal 30 and the server device 20. Each of the stores 60 may be affiliated with a chain store or the like, or each may be an independent store.

[0011] The store terminal 40 is a terminal device provided in each remote restaurant 61. The remote restaurant 61 is a restaurant that does not have a kitchen (cooking area) and where customers can eat menu items delivered from a delivery store 62. The store terminal 40 is, for example, an ordering terminal for self-ordering provided at each seat in the remote restaurant 61, and is realized by, for example, a PC or a tablet terminal. There is no particular limit to the number of store terminals 40 provided in the remote restaurant 61, and there may be more than one.

[0012] Order information for a product placed from the store terminal 40 of the remote restaurant 61 is transmitted to the server device 20. The server device 20 selects, from among a plurality of delivery stores 62, a delivery store 62 that is considered to be able to deliver the ordered product to the order destination most quickly, and transmits a delivery order to the order receiving terminal 50 of the selected delivery store 62.

[0013] The order receiving terminal 50 is a terminal device that receives delivery orders and is provided in each delivery store 62. The delivery store 62 is realized by, for example, a PC or a tablet terminal. There is no particular limit to the number of order receiving terminals 50 provided in the delivery store 62, and there may be more than one. The order receiving terminal 50 can also communicate with a handheld terminal (not shown) carried by a delivery person at the delivery store 62, thereby enabling the delivery status of the ordered items to be checked at any time.

[0014] The user terminal 41 is a terminal device used by a user who uses the remote food and drink providing system 10. The user terminal 41 can be realized by a portable terminal device such as a PC, a smartphone, or a tablet terminal. The user terminal 41 is an example of a terminal device.

[0015] The server device 20 is realized by an information processing device such as a workstation. In the present embodiment, the server device 20 is described as a single device, but is not limited to this. For example, the server device 20 may be configured to operate functions in a distributed manner across multiple server devices.

[0016] The server device 20 provides a remote food and drink provision service by working in cooperation with the store terminal 30 of each store 60, the store terminal 40 of each remote restaurant 61, the order receiving terminal 50 of each delivery store 62, and each user terminal 41. More specifically, the server device 20 controls communications between the store terminal 30 provided in each of the multiple stores 60, the store terminal 40 provided in each of the multiple remote restaurants 61, the order receiving terminal 50 provided in each of the multiple delivery stores 62, and the multiple user terminals 41, thereby providing a service (remote food and drink provision service) in which multiple users in different locations can talk to each other and share screens.

[0017] Hereinafter, providing (receiving) a remote food and drink provision service using the remote food and drink provision system 10 will be referred to as a "remote drinking party."

[0018] The system configuration of the remote food and drink providing system 10 is not limited to the example shown in Fig. 1. For example, a server device other than the server device 20 that manages multiple delivery stores 62 may be provided, and the delivery order sent from the server device 20 may be received by the server device other than the server device 20, and the optimal delivery store 62 may be selected.

[0019] (Server hardware configuration) Next, a hardware configuration of the server device 20 will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of a hardware configuration of the server device according to the embodiment.

[0020] The server device 20 includes a computer configuration including a central processing circuit (CPU) 21, a read only memory (ROM) 22, and a random access memory (RAM) 23.

[0021] The CPU 21 is an example of a processor, and performs overall control of each unit of the server device 20. The ROM 22 stores various programs and various data. The RAM 23 is a workspace in which the programs and various data are expanded.

[0022] The server device 20 also includes a communication unit 24 and a storage unit 25. The communication unit 24 is a communication interface connectable to a network N. The communication unit 24 communicates with external devices such as the store terminals 30, 40, a user terminal 41, and an order receiving terminal 50 via the network N.

[0023] The storage unit 25 is composed of a storage medium such as a hard disk drive (HDD) or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 25 stores programs that the CPU 21 can execute and various setting information. For example, the storage unit 25 stores programs (server programs) prepared for a remote drinking party and contents related to the display of a GUI (Graphical User Interface). The CPU 21 executes various processes by expanding the programs stored in the ROM 22 or the storage unit 25 into the RAM 23 and running them.

[0024] The storage unit 25 also stores various data necessary for executing a remote drinking party. Specifically, the storage unit 25 stores a store management table 251, a remote restaurant management table 252, a delivery store management table 253, a store menu management table 254, a delivery menu management table 255, a user management table 256, a reservation management table 257, a store order management table 258, and a delivery order management table 259. The contents of each table will be described in detail later.

[0025] (Hardware configuration of store terminals and user terminals) Next, the hardware configuration of the store terminals 30, 40 or the user terminal 41 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the hardware configuration of the store terminal and the user terminal according to the embodiment.

[0026] The store terminal 30 includes a computer configuration including a CPU 31, a ROM 32, and a RAM 33. The CPU 31 is an example of a processor, and controls each unit of the store terminal 30. The ROM 32 stores various programs and various data. The RAM 33 is a workspace in which the programs and various data are expanded.

[0027] The store terminal 30 also includes a communication unit 34 , a storage unit 35 , a display unit 36 ​​, an operation unit 37 , an imaging unit 38 , and an audio input / output unit 39 .

[0028] The communication unit 34 is a communication interface connectable to the network N. The communication unit 34 communicates with external devices such as the server device 20 via the network N. The communication unit 34 also communicates with a store server in its own store, other store terminals 30, 40, or a user terminal 41.

[0029] The storage unit 35 is composed of a storage medium such as a HDD or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 35 stores programs that the CPU 31 can execute and various setting information. For example, the storage unit 35 stores programs (client programs) prepared for a remote drinking party and contents related to GUI display. The CPU 31 executes various processes by expanding the programs stored in the ROM 32 and the storage unit 35 into the RAM 33 and running them.

[0030] The display unit 36 ​​is a display device such as an LCD (Liquid Crystal Display), and displays various information and screens under the control of the CPU 31. The operation unit 37 has various operation keys, and outputs operation contents according to user operations to the CPU 31. The operation unit 37 may be a touch panel provided on the surface of the display unit 36.

[0031] The imaging unit 38 is an imaging device equipped with an imaging element such as a CCD (Charge Coupled Device). For example, the imaging unit 38 captures an image of a user operating the store terminal 30, thereby acquiring image data (still image, video) of the user, and outputs the acquired image data to the CPU 31. The imaging unit 38 may be built into the store terminal 30, or may be separate from the store terminal 30.

[0032] The audio input / output unit 39 includes an audio input device such as a microphone and an audio output device such as a speaker. The audio input / output unit 39 acquires user's audio data and outputs the acquired audio data to the CPU 31. The audio input / output unit 39 also outputs the audio data input from the CPU 31 as audio.

[0033] It should be noted that the hardware configuration of the store terminal 30 is not limited to the configuration in Fig. 3. Also, the store terminal 40 and the user terminal 41 will be described assuming that they have the same hardware configuration as the store terminal 30.

[0034] (Order terminal hardware configuration) Next, the hardware configuration of the order receiving terminal 50 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the hardware configuration of the order receiving terminal according to the embodiment.

[0035] The order receiving terminal 50 includes a computer configuration including a CPU 51, a ROM 52, and a RAM 53. The CPU 51 is an example of a processor, and controls each part of the order receiving terminal 50. The ROM 52 stores various programs and various data. The RAM 53 is a workspace in which the programs and various data are expanded.

[0036] The order receiving terminal 50 also includes a communication unit 54 , a storage unit 55 , a display unit 56 , and an operation unit 57 .

[0037] The communication unit 54 is a communication interface that can be connected to the network N. The communication unit 54 communicates with external devices such as the server device 20 via the network N.

[0038] The storage unit 55 is composed of a storage medium such as a HDD or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 55 stores programs that the CPU 51 can execute and various setting information. For example, the storage unit 55 stores a program (client program) prepared for handling orders and contents related to GUI display. The CPU 51 executes various processes by expanding the programs stored in the ROM 52 and the storage unit 55 into the RAM 53 and running them.

[0039] The display unit 56 is a display device such as an LCD, and displays various information and screens under the control of the CPU 51. The operation unit 57 has various operation keys, and outputs operation contents according to user operations to the CPU 51. The operation unit 57 may be a touch panel provided on the surface of the display unit 56.

[0040] It should be noted that the hardware configuration of the order receiving terminal 50 is not limited to the configuration shown in FIG.

[0041] (Various data stored in the server device) Next, the data configurations of various data stored in the storage unit 25 of the server device 20 will be described with reference to FIGS.

[0042] 5 is a diagram showing an example of a data configuration of a store management table according to the embodiment. The store management table 251 stores store information on the store 60 corresponding to the store ID in association with the store ID of each store 60.

[0043] The store ID is identification information for identifying each store 60. The store information includes items such as the store name, address, contact information, and store image of the store 60. The store name is the trade name or branch name of the store 60. The address refers to the address indicating the location of the store 60. The contact information refers to address information such as the address of the store 60 or an IP address. The store image is image information such as an icon or logo that represents the store 60 corresponding to the store ID. It should be noted that the data configuration of the store management table 251 is not limited to the example of FIG. 5.

[0044] 6 is a diagram showing an example of the data configuration of the remote restaurant run management table according to the embodiment. The remote restaurant management table 252 stores remote restaurant run information on the remote restaurant 61 corresponding to the remote restaurant ID in association with the remote restaurant ID of each remote restaurant 61.

[0045] The remote restaurant ID is identification information for identifying each remote restaurant 61. The remote restaurant run information includes items such as the remote restaurant name, address, contact information, and remote restaurant image of the remote restaurant 61. The remote restaurant name is the trade name or branch name of the remote restaurant 61. The address refers to an address indicating the location of the remote restaurant 61. The contact information refers to address information such as the address or IP address of the remote restaurant 61. The remote restaurant image is image information such as an icon or logo mark representing the remote restaurant 61 corresponding to the remote restaurant ID. It should be noted that the data configuration of the remote restaurant management table 252 is not limited to the example of FIG. 6.

[0046] 7 is a diagram showing an example of a data configuration of a delivery store management table according to the embodiment. The delivery store management table 253 stores delivery store information on the delivery store 62 corresponding to the delivery store ID in association with the delivery store ID of each delivery store 62.

[0047] The delivery store ID is identification information for identifying each delivery store 62. The delivery store information includes items such as the delivery store name, address, contact information, and delivery store image of the delivery store 62. The delivery store name is the trade name or branch name of the delivery store 62. The address refers to the address indicating the location of the delivery store 62. The contact information refers to address information such as the address or IP address of the delivery store 62. The delivery store image is image information such as an icon or logo mark representing the delivery store 62 corresponding to the delivery store ID. It should be noted that the data configuration of the delivery store management table 253 is not limited to the example of FIG. 7.

[0048] 8 is a diagram showing an example of a data configuration of a store menu management table according to an embodiment. The store menu management table 254 stores menu information about each product (menu) available at the store 60 corresponding to the store ID in association with the store ID of each store 60. The server device 20 obtains the menu information from, for example, a store server of each store 60 and stores it in the store menu management table 254.

[0049] The menu information includes, for example, the product ID, product name, generic name, price, product image, and description of the product (menu).

[0050] The product ID is identification information for identifying products sold at each store 60. The product name is information indicating the product name (item, official name, etc.) of the product corresponding to the product ID. The general name is information indicating the general name, abbreviation, or name of the product. For example, assume that the "beer" sold at store A is "A beer large" and "A beer medium", and the "beer" sold at store B is "B beer". In this case, the product ID and product name indicating "A beer large" and "A beer medium" are registered in association with the store ID of store A, and the general name "beer" is registered in association with each of these product IDs. Furthermore, the product ID and product name indicating "B beer" are registered in association with the store ID of store B, and the general name "beer" is registered in association with this product ID.

[0051] The price is information indicating the unit price of the product corresponding to the product ID. The product image is image data (product image) such as a photograph or illustration that represents the product corresponding to the product ID. The description is information indicating a description of the product corresponding to the product ID, the estimated time required for cooking, the popularity of the product at the store corresponding to the store ID, etc.

[0052] The data configuration of the store menu management table 254 is not limited to the example in Fig. 8. The server device 20 may acquire the menu information in the store menu management table 254 from the store server of each store 60 periodically or as needed, thereby updating the menu information at a predetermined timing.

[0053] 9 is a diagram showing an example of a data configuration of a delivery menu management table according to an embodiment. The delivery menu management table 255 stores menu information on each product (menu) that can be provided (cooked) by the delivery store 62 corresponding to the delivery store ID, in association with the delivery store ID of each delivery store 62. The server device 20, for example, acquires menu information from each delivery store 62 and stores it in the delivery menu management table 255.

[0054] The menu information includes, for example, the product ID, product name, generic name, price, product image, and description of the product (menu). The contents of each item are the same as the data stored in the above-mentioned store menu management table 254. The server device 20 may manage the store menu and the delivery menu together as one menu management table, rather than separating them into the store menu management table 254 and the delivery menu management table 255.

[0055] 10 is a diagram showing an example of a data configuration of a user management table according to an embodiment. The user management table 256 stores user information on a user corresponding to a user ID in association with the user ID of each user. Here, the user ID is identification information for identifying each user.

[0056] The user information includes, for example, a user name, an address, contact information, and payment information. The user name is information indicating the name of the user corresponding to the user ID. A user icon that characterizes the user may be stored together with the user name. The address is information indicating the address or residence of the user corresponding to the user ID. The contact information is information indicating the contact information of the user corresponding to the user ID. Identification information such as the telephone number and terminal ID of the user terminal 41 possessed by the user is registered in the contact information. The payment information is information related to electronic payment such as credit card payment and electronic money payment. The payment information holds one or more pieces of information such as a credit card number, and is used when paying for a product by electronic payment.

[0057] The data configuration of the user management table 256 is not limited to the example in Fig. 10. For example, the user management table 256 may store information such as the gender, age, and preferences of the user corresponding to the user ID in association with the user ID of each user. Also, a flag indicating that the host of the remote drinking party is the host may be added to the host.

[0058] 11 is a diagram showing an example of a data configuration of a reservation management table according to the embodiment. The reservation management table 257 stores reservation information related to the reservation ID in association with the reservation ID.

[0059] The reservation ID is identification information for identifying a reservation for a remote drinking party. The server device 20 issues a unique reservation ID (for example, an ascending number) every time the server device 20 accepts a reservation for a remote drinking party from a user via the user terminal 41 or the like.

[0060] The reservation information includes, for example, information such as the reservation date and time, the user ID, the location of the remote drinking party, the terminal ID, and the login date and time.

[0061] The reservation date and time is information indicating the date and time when the remote drinking party is scheduled to be held. The reservation date and time is expressed, for example, by a period between a start date and time and an end date and time.

[0062] The user IDs of users who will participate in the remote drinking party are registered in the user ID. One or more user IDs can be associated with each reservation ID, and user IDs associated with the same reservation ID are managed as a group participating in the same remote drinking party. In other words, the reservation ID also functions as an identifier for identifying each group. Hereinafter, user IDs associated with the same reservation ID or users corresponding to the user IDs will also be referred to as users belonging to the same group.

[0063] The location of participation in a remote drinking party (hereinafter simply referred to as the participation location) is registered with the store ID of the store 60 used in the remote drinking party, the remote restaurant ID of the remote restaurant 61, or identification information that identifies the user's own home.

[0064] The terminal ID is registered with identification information of the store terminal 30, 40 or the user terminal 41 used in the remote drinking party. In addition, the login date and time is registered with the date and time when the use of the store terminal 30, 40 or the user terminal 41 corresponding to the terminal ID started.

[0065] In this embodiment, among the information included in the reservation information, the reservation date and time, the user ID, and the participation location are assumed to be registered before the remote drinking party is held. Also, among the information included in the reservation information, the terminal ID and the login date and time are assumed to be registered on the day of the remote drinking party, that is, when the user corresponding to the user ID arrives at the participation location. The participation location may be registered when the user arrives at the participation location on the day of the remote drinking party. Alternatively, the user and the user's participation location may be registered in association with each other. For example, the participation location may be registered in advance in association with the user ID registered in the reservation information of the reservation ID.

[0066] The data configuration of the reservation management table 257 is not limited to the example in Fig. 11. For example, the reservation management table 257 may store information indicating the name and subject of the remote drinking party in association with a reservation ID. The reservation management table 257 may also store information indicating the host or organizer of the remote drinking party in association with a user ID.

[0067] 12 is a diagram showing an example of the data configuration of a store order management table according to an embodiment. The store order management table 258 stores order history information on products ordered at the store 60 for a remote drinking party corresponding to a reservation ID, in association with the reservation ID. That is, when a menu item provided by the store 60 is ordered at the store 60, the order history of the order is recorded in the store order management table 258.

[0068] The order history information includes, for example, an order ID, an ordering user ID, an order recipient user ID, a participating location, a product ID, a quantity, a payment completed flag, etc. The participating location records the store ID where the menu item is ordered.

[0069] The order ID is identification information for identifying each order. The server device 20 issues a unique order ID (for example, an ascending number) every time it receives an order for a product from a user (the store terminal 30, 40 or the user terminal 41).

[0070] The user ID of the user who ordered the product is registered as the orderer user ID. The user ID of the user to whom the ordered product will be provided is registered as the order recipient user ID. For example, if a user orders a product to be consumed by himself / herself, the same user ID is registered as the orderer user ID and the order recipient user ID. Also, for example, if a user orders a product to be consumed by another user, different user IDs are registered as the orderer user ID and the order recipient user ID.

[0071] The participation location is registered with information for identifying the location where the user of the order destination user ID is located, such as the store ID of the store 60 used for the remote drinking party, the remote restaurant ID of the remote restaurant 61, or identification information for identifying the user's own home. The product ID is registered with the product ID of the product that is the subject of the order. The quantity is registered with the quantity of the product that is the subject of the order.

[0072] In the paid flag, flag information indicating whether or not the payment for the ordered product has been made is registered. In this embodiment, as described later, when a user wants to give a product as a gift to another user (hereinafter, this ordering method is also referred to as a "treat re-order"), it is possible to make the payment for the product first. In other words, when the ordering user ID and the order destination user ID are different and the user corresponding to the ordering user ID has completed the payment for the product, a flag indicating that payment has been made is registered in the paid flag. In other words, the paid flag also serves as an indicator of whether or not a treat order has been made. In addition, in FIG. 12, it is defined that unpaid is flagged as "0" and paid is flagged as "1".

[0073] It should be noted that the data configuration of the store order management table 258 is not limited to the example shown in Fig. 12. For example, the store order management table 258 may store information indicating the date and time of an order.

[0074] 13 is a diagram showing an example of a data configuration of a delivery order management table according to an embodiment. The delivery order management table 259 stores, in association with a reservation ID, order history information on products ordered from the delivery store 62 for a remote drinking party corresponding to the reservation ID, and delivery status information on the ordered products. That is, when a menu item provided by the delivery store 62 is ordered at the store 60, the remote restaurant 61, the user's home, etc., the order history of the order is recorded in the delivery order management table 259.

[0075] The delivery status information includes, for example, the order ID, the ordering user ID, the order recipient user ID, the delivery store ID, the delivery location (store ID, remote restaurant ID or the user's home), the product ID, the quantity, a payment completion flag, and a delivery status flag.

[0076] The order ID is identification information for identifying each delivery order. The server device 20 issues a unique order ID (for example, an ascending number) every time it receives a product delivery order from a user (the store terminal 30, 40 or the user terminal 41).

[0077] The user ID of the user who ordered the delivery of the product is registered as the ordering user ID. The user ID of the user to whom the ordered product will be provided is registered as the order recipient user ID. For example, if a user orders delivery of a product that they will consume themselves, the same user ID is registered as the ordering user ID and the order recipient user ID. Also, for example, if a user orders delivery of a product that another user will consume, different user IDs are registered as the ordering user ID and the order recipient user ID.

[0078] The delivery store ID field stores the delivery store ID of the delivery store 62 that is the order destination.

[0079] The delivery location is registered with information that identifies the delivery destination of the product. Specifically, information that identifies the location of the user of the order destination user ID, such as the store ID of the store 60 used in the remote drinking party, the remote restaurant ID of the remote restaurant 61, or identification information that identifies the user's own home, is registered.

[0080] The product ID of the product to be delivered is registered in the product ID field. The quantity of the product to be delivered is registered in the quantity field.

[0081] In the paid flag, flag information is registered which indicates whether or not the payment for the product to be delivered has been made. In this embodiment, as described later, when a user wants to give a product as a gift to another user (hereinafter, this ordering method is also referred to as a "treat re-order"), it is possible to make the payment for the product first. In other words, when the ordering user ID and the order destination user ID are different and the user corresponding to the ordering user ID has completed the payment for the product, a flag indicating that payment has been made is registered in the paid flag. In other words, the paid flag also serves as an indicator of whether or not a treat order has been made. In addition, in FIG. 13, it is defined that unpaid is flagged as "0" and paid is flagged as "1".

[0082] The delivery status flag is registered with information indicating the preparation status of the product to be delivered. The preparation status of the product to be delivered may be, for example, "preparing to cook", "cooking", "delivering", "delivery completed", "serving", etc.

[0083] The data configuration of the delivery order management table 259 is not limited to the example in Fig. 13. For example, the delivery order management table 259 may store information indicating the current location of a delivery person, an estimated delivery time, etc. Also, the server device 20 may manage the store order management table 258 and the delivery order management table 259 together as one order management table, rather than separating them.

[0084] (Functional configuration of the remote food and beverage supply system) The functional configuration of the remote food and drink providing system 10 will be described with reference to Fig. 14. Fig. 14 is a functional block diagram showing an example of the functional configuration of the remote food and drink providing system according to the embodiment.

[0085] The server device 20 has, as functional units, a reservation reception unit 201, a terminal-to-terminal communication unit 202, a screen display control unit 203, a GUI providing unit 204, an order reception unit 205, an accounting processing unit 206, a delivery status acquisition unit 207, and an amount redistribution unit 208.

[0086] A part or all of the functional units of the server device 20 may be a software configuration realized by cooperation between a processor (e.g., CPU 21) of the server device 20 and a program stored in a memory (e.g., ROM 22, storage unit 25). Also, a part or all of the functional units of the server device 20 may be a hardware configuration realized by a dedicated circuit or the like mounted on the server device 20.

[0087] The reservation reception unit 201 receives a reservation for a remote drinking party, and registers the details of the received reservation in the reservation management table 257. There is no particular restriction on the method of receiving the reservation, and various methods can be adopted.

[0088] For example, a website that allows users to specify the date and time of the remote drinking party and the store to be used may be published on the network N, and reservations may be accepted via the website. In this case, a user who will be the host or organizer (hereinafter also referred to as the organizer) accesses the website using the user terminal 41 and makes a reservation (new reservation) for the remote drinking party by inputting the date and time of the remote drinking party, his / her own user ID, the store SP (store ID) to be used, etc.

[0089] When the reservation reception unit 201 receives a new reservation, it issues a reservation ID and registers it in the reservation management table 354 together with the input details. The reservation reception unit 201 also notifies the user terminal 41 of the user of the issued reservation ID. The organizer then notifies the other users who will be participating in the remote drinking party of the user ID. Note that when making a new reservation, the user ID of a user other than the organizer may be input.

[0090] Meanwhile, the other user who has received the notification of the reservation ID uses his / her own user terminal 41 to access the above-mentioned website specifying the reservation ID. When the reservation reception unit 201 receives the access specifying the reservation ID, it reads out reservation information (date and time of the event, etc.) corresponding to the reservation ID from the reservation management table 257 and provides it visibly on the user terminal 41 from which the access originates. Then, the other user makes a reservation (additional reservation) for a remote drinking party by inputting his / her own user ID, the store 60 (store ID) and remote restaurant 61 (remote restaurant ID) that he / she will use, etc. When the reservation reception unit 201 receives the additional reservation, it additionally registers the items of the additional reservation to the reservation information of the previously input reservation ID.

[0091] In addition, the reservation reception unit 201 may compare the address stored in the user information with the address stored in the store information of each store 60 or each remote restaurant 61, and present to the user stores 60 or remote restaurants 61 located within a specified range (e.g., within 3 km) of the user's address as candidates for use for the remote drinking party.

[0092] By performing the above process (reservation process), the reservation reception unit 201 stores a pair of the user ID and the store ID used by each user participating in the same remote drinking party in the reservation management table 257 in association with a common reservation ID. In the above description, the other users who received the notification of the reservation ID individually register their own user IDs, etc., in the reservation information of the reservation ID, and register them additionally, but this is not limited to the above. For example, if a representative has acquired the user IDs of the participants in advance, the representative may register the user IDs of the participants collectively. After the reservation process is completed, the user terminal 41 may acquire the reservation ID and two-dimensional code information associated with the user ID or link information for displaying the two-dimensional code information for the user whose user ID has been registered. For example, on the day of the reservation, the two-dimensional code information may be displayed on the user terminal 41, and the displayed two-dimensional code information may be read by the store terminals 30 and 40, thereby executing the login process. In this way, the reservation reception unit 201 receives access from each of the terminal devices placed in multiple locations, and manages the location and terminal device from which the access originates in association with the user who operates the terminal device. Note that the reservation reception unit 201 is an example of a management unit.

[0093] The inter-terminal communication unit 202 functions as an example of a management unit together with the reservation reception unit 201. The inter-terminal communication unit 202 receives access from the store terminal 30 of the store 60, the store terminal 40 of the remote restaurant 61, or the user terminal 41, and manages the store 60 (store ID) and store terminal 30 (terminal ID), the remote restaurant 61 (store ID) and store terminal 40 (terminal ID), or the user terminal 41 (terminal ID) that is the access source, in association with the user (user ID) that operates the terminal device.

[0094] The inter-terminal communication unit 202 is an example of a communication control unit. The inter-terminal communication unit 202 connects terminal devices (store terminals 30, 40 or user terminals 41) operated by users associated with the same reservation ID, that is, users belonging to the same group, so that they can communicate with each other.

[0095] Specifically, when the inter-terminal communication unit 202 receives an access specifying participation information such as a reservation ID and a user ID from a terminal device (store terminal 30, 40 or user terminal 41), it identifies reservation information corresponding to the specified reservation ID from the reservation management table 257. The inter-terminal communication unit 202 executes a login process to determine whether or not the specified user ID is included in the identified reservation information. If the specified user ID is included in the reservation information, the inter-terminal communication unit 202 additionally registers the terminal ID of the accessing terminal device and the current date and time (login date and time) in association with the user ID to the reservation information.

[0096] Then, when the inter-terminal communication unit 202 registers the terminal ID and the login date and time in the reservation information, it performs control to connect the terminal devices having the terminal IDs registered in the reservation information so that they can communicate with each other. This allows data sharing between the terminal devices associated with the same reservation ID, so that users belonging to the same group can talk with other users while looking at images (face images) captured by the terminal devices operated by each user.

[0097] The inter-terminal communication unit 202 may be configured to register, in the reservation information, the terminal ID of the terminal device and the store ID of the store 60 or the remote restaurant 61 to which the terminal device belongs, when the terminal device accesses the inter-terminal communication unit 202.

[0098] Furthermore, the inter-terminal communication unit 202 may be configured to reject access when the user ID received from the terminal device is not included in the reservation information of the corresponding reservation ID, or may be configured to additionally register the user ID in the reservation information.

[0099] The screen display control unit 203 displays a main screen on the display unit 36 ​​connected to each of the store terminals 30, 40 or user terminals 41 (terminal devices) associated with the reservation reception unit 201, in which sub-screens displaying images captured by the imaging units 38 (imaging devices) corresponding to the respective terminal devices are arranged. The screen display control unit 203 also displays the order information received by the order reception unit in the main screen displayed on the display unit 36 ​​in association with the delivery destination of the ordered product. Furthermore, the screen display control unit 203 displays the payment amount for each terminal device based on the order information from each terminal device associated with the reservation reception unit 201 in association with the image displayed on the display unit 36 ​​corresponding to each terminal device. The screen display control unit 203 is an example of a display control unit and an amount display unit. The sub-screen and the main screen will be described later (see FIG. 16).

[0100] The GUI providing unit 204 is an example of a menu providing unit. The GUI providing unit 204 provides various GUIs to the store terminals 30, 40 or the user terminal 41 (terminal device). Specifically, the GUI providing unit 204 provides a screen that can be viewed by terminal devices communicatively connected via the inter-terminal communication unit 202, showing menu information showing products that can be provided at the store 60 to which the terminal device belongs, the remote restaurant 61, or at home where the user is participating in a remote drinking party from his or her own user terminal 41. The GUI providing unit 204 also provides each of the terminal devices with a screen for ordering products, a screen for making a payment, and the like. The various operation screens provided by the GUI providing unit 204 will be described later.

[0101] The order receiving unit 205 is an example of an order receiving unit. The order receiving unit 205 receives order information on a product and a delivery destination of the product from any of the terminal devices to which menu information has been provided, and notifies the received order information to the store 60 that provides the product or the delivery store 62.

[0102] Furthermore, each time the order receiving unit 205 receives an order for a product, it identifies the user ID of the user operating the terminal device that placed the order (ordering user ID) and the user ID of the user who will provide the ordered product (order destination user ID).The order receiving unit 205 then registers information such as the identified user ID, ordering store ID or delivery store ID, and product ID in the order history information in the store order management table 258 or the delivery order history information in the delivery order management table 259, which corresponds to the reservation ID corresponding to the identified user ID, in association with the newly issued order ID.

[0103] The accounting processor 206 executes accounting processing to pay the cost of the product accepted by the order accepting unit 205 to the store 60 that provides the product or the delivery store 62. Specifically, the accounting processor 206 executes accounting processing to pay the cost of the ordered product using the payment information stored in the user management table 256.

[0104] The payment of the product price is not limited to the method using the payment information. For example, other payment methods such as code payment using two-dimensional code information or cash payment may be used. In this case, the accounting processing unit 206 determines that the user's payment is complete on condition that it receives information indicating that the payment of the product price has been completed together with the user ID from a device such as the user terminal 41 or the store server.

[0105] The delivery status acquisition unit 207 acquires information indicating the delivery status of the menu item ordered for delivery from the order-receiving terminal 50. Specifically, the server device 20 acquires the delivery status of the ordered item and the current location of the delivery person by having the order-receiving terminal 50 communicate with the handheld terminal carried by the delivery person.

[0106] The amount redistribution unit 208 redistributes the total amount of payment for each user to each terminal device based on an instruction from the terminal device. More specifically, the amount redistribution unit 208 cooperates with the GUI providing unit 204 and the screen display control unit 203 to display a method for redistributing the total amount of payment and the amount of payment for the user associated with the terminal device based on the redistribution method in the accounting screen 160 (see FIG. 22) displayed on the display unit 36 ​​of each terminal device. In addition, when some of the multiple terminal devices are disconnected, the amount redistribution unit 208 redistributes the total amount of unsettled payment for each terminal device to each terminal device that is maintaining a connection, depending on whether the payment amount corresponding to the disconnected terminal device has been paid or whether the payment amount is to be entrusted to the user operating the terminal device that is maintaining the connection.

[0107] Returning to FIG. 14, the store terminal 30, 40 or the user terminal 41 (terminal device) includes a communication control unit 301, an output control unit 302, and an operation reception unit 303 as functional units.

[0108] Some or all of the functional units of the store terminals 30, 40 or the user terminal 41 (terminal device) may be software configurations realized by cooperation between the processor (e.g., CPU 31) of each terminal device and a program stored in a memory (e.g., ROM 32, storage unit 35). Also, some or all of the functional units of the terminal device may be hardware configurations realized by a dedicated circuit or the like mounted on each terminal device.

[0109] The communication control unit 301 controls the communication unit 34 to exchange various information (data) with the server device 20 and the store server. For example, the communication control unit 301 transmits image data and audio data acquired by the imaging unit 38 and audio input / output unit 39 to the server device 20. In addition, for example, the communication control unit 301 receives image data and audio data transmitted from other store terminals 30, 40 or user terminal 41 via the server device 20.

[0110] The output control unit 302 controls the display unit 36 ​​and the audio input / output unit 39 to output various information (data). For example, the output control unit 302 causes the display unit 36 ​​to display image data acquired by the imaging unit 38 or image data transmitted from the other store terminals 30, 40 or the user terminal 41. The output control unit 302 also causes the display unit 36 ​​to display various GUIs by working in cooperation with the server device 20. The output control unit 302 also causes the audio input / output unit 39 to output audio data acquired by the audio input / output unit 39 or audio data transmitted from the other store terminals 30, 40 or the user terminal 41.

[0111] The operation reception unit 303 receives the operation content of the user inputted via the operation unit 37. For example, the operation reception unit 303 receives an operation on the GUI displayed on the display unit 36. Note that the store terminals 30 and 40 or the user terminal 41 (terminal device) function as an input / output interface of the server device 20 in this embodiment.

[0112] The order receiving terminal 50 includes a communication control unit 501, an output control unit 502, and an operation receiving unit 503 as functional units.

[0113] The communication control unit 501 controls the communication unit 54 to exchange various information (data) with the server device 20. For example, the communication control unit 501 receives a delivery order made from the store terminal 40 via the server device 20. The communication control unit 501 also acquires the delivery status of the ordered menu item by communicating with a handheld terminal (not shown) carried by a delivery person.

[0114] The output control unit 502 outputs the received order information by controlling the display unit 56. For example, the output control unit 502 causes the display unit 56 to display the contents of the order information received by the communication control unit 501 from the server device 20. In addition, the output control unit 502 outputs the delivery status of the ordered menu to the server device 20.

[0115] The operation reception unit 503 receives the operation content of the clerk of the delivery store 62 inputted via the operation unit 57. For example, the operation reception unit 503 receives an operation on the GUI displayed on the display unit 56. In this embodiment, the order receiving terminal 50 functions as an input / output interface of the server device 20.

[0116] (Operation of server device) Next, the operation of the server device 20 will be described. The server device 20 executes various processes in response to operations based on the screens provided by the GUI providing unit 204 and the screen display control unit 203 to the store terminals 30, 40 or the user terminal 41 (terminal device). Therefore, the operation of the server device 20 will be described below based on the screens displayed on the display unit 36 ​​of the store terminals 30, 40 or the user terminal 41. It is assumed that the reservation for the remote drinking party has been made in advance.

[0117] First, when the inter-terminal communication unit 202 receives an access specifying a reservation ID and a user ID from the store terminal 30, 40 or the user terminal 41, it executes the login process described above to identify the reservation information. This access can be realized, for example, before a remote drinking party is held, by the organizer sending an invitation or the like that specifies the reservation ID and the user ID to the participants, and the participants accepting the invitation. In addition, the inter-terminal communication unit 202 registers the terminal ID and login date and time of the access source store terminal 30, 40 or the user terminal 41 in the identified reservation information.

[0118] Next, the inter-terminal communication unit 202 compares the reservation date and time included in the reservation information with the current date and time, and determines whether the start date and time of the remote drinking party has arrived.

[0119] Here, if it is determined that the start date and time has not been reached, the inter-terminal communication unit 202 cooperates with the GUI provision unit 204 and the screen display control unit 203 to cause the display unit 36 ​​of the store terminal 30, 40 or the user terminal 41 to display a standby screen (not shown) notifying that the start date and time has not been reached. For example, such a standby screen may display a countdown to the start date and time.

[0120] In addition, if it is determined that the start date and time has been reached or has been reached, the inter-terminal communication unit 202, in cooperation with the GUI providing unit 204 and the screen display control unit 203, causes the display unit 36 ​​of the store terminal 30, 40 or the user terminal 41 to display a start screen 100 that allows the start of a remote drinking party to be instructed.

[0121] Fig. 15 is a diagram showing an example of a start screen for a remote drinking party displayed on a store terminal or a user terminal. As shown in Fig. 15, a start screen 100 has a start button 101 which is an operator for instructing the start of a remote drinking party.

[0122] When the inter-terminal communication unit 202 receives operation of the start button 101 from the store terminal 30, 40 or the user terminal 41, it establishes communication between the store terminal 30, 40 or the user terminal 41 corresponding to the terminal ID registered in the reservation information, realizing a state in which data can be shared between them.

[0123] In addition, when the GUI providing unit 204 accepts operation of the start button 101 from the store terminal 30, 40 or the user terminal 41, working in cooperation with the screen display control unit 203, it causes a main screen 110 for displaying data (image data) shared between the store terminals 30, 40 or the user terminal 41 to be displayed on the display unit 36 ​​of the store terminal 30, 40 or the user terminal 41.

[0124] FIG. 16 is a diagram showing an example of a main screen displayed on a store terminal or a user terminal during a remote drinking party. As shown in FIG. 16, a main screen 110 has a plurality of sub-screens 112, 113, and 114 divided according to the number of participants of the remote drinking party. FIG. 16 shows an example in which the main screen 110 is divided into three sub-screens 112, 113, and 114 according to three users, namely, A (user A), B (user B), and C (user C). A screen title 111 indicating the status of the main screen is displayed at the top of the main screen 110. Specifically, the GUI providing unit 204 detects the operation content performed on the operation unit 37 of the terminal device and acquires a screen title 111 corresponding to the operation content. Since the operation content and the screen title correspond one-to-one, a table describing the correspondence between the two may be created in advance and stored in the server device 20. Then, the screen display control unit 203 displays the acquired screen title 111 on the main screen 110. In the following description, it is assumed that FIG. 15 shows the main screen 110 displayed on a terminal device operated by user A.

[0125] Each of the sub-screens 112, 113, and 114 is associated with a terminal ID of the store terminal 30, 40 or user terminal 41 (terminal device) operated by each user, a user ID of the user operating the terminal device, a store ID of the store 60 to which the store terminal 30 belongs, a store ID of the remote restaurant 61 to which the store terminal 40 belongs, etc. Also, each of the sub-screens 112, 113, and 114 displays image data acquired (captured) by the imaging unit 38 corresponding to the terminal device of the corresponding terminal ID. Also, the server device 20 provides each terminal device with audio data acquired by the audio input / output unit 39 corresponding to the terminal device, and the audio data is output from the audio input / output unit 39 by the output control unit 302.

[0126] This allows the users of the terminal devices to view the main screen 110 and talk to each of the participants of the remote drinking party while looking at each other's faces.

[0127] Further, on each of the sub-screens 112, 113, and 114, a user name and a user icon 117 corresponding to the user ID associated with the sub-screen 112, 113, and 114 are displayed. Specifically, the GUI providing unit 204 reads out the user name and the user icon corresponding to the user ID from the user management table 256. Then, the screen display control unit 203 causes the read out user name and the user icon 117 to be superimposed on the sub-screens 112, 113, and 114.

[0128] Further, on each of the sub-screens 112, 113, 114, the participation place 115 of the user associated with the corresponding sub-screen 112, 113, 114 is displayed. Specifically, the GUI providing unit 204 reads out the participation place of the user from the reservation management table 257. Then, the screen display control unit 203 superimposes and displays the read participation place 115 of the user on the sub-screens 112, 113, 114. Note that the number of sub-screens is appropriately set according to the number of terminal devices connected to each other by the action of the screen display control unit 203.

[0129] In the example of FIG. 16, the sub-screen 112 on the left displays a user name and user icon 117 indicating the user name "Mr. A", and Mr. A's participation location 115 (remote restaurant A). The sub-screen 113 in the middle displays a user name and user icon 117 indicating the user name "Mr. B", and Mr. B's participation location 115 (store A). The sub-screen 114 on the right displays a user name and user icon 117 indicating the user name "Mr. C", and Mr. C's participation location 115 (home). Since the host of the remote drinking party is Mr. A, a host icon 116 may be displayed on the sub-screen 112.

[0130] This allows the user of each terminal device to easily check the user name and location of each user who has participated in the remote drinking party by looking at the main screen 110.

[0131] Various operation buttons are also displayed on the main screen 110. In the example of Fig. 16, a call button 120, an order button 121, an order status confirmation button 122, a checkout button 123, a microphone control button 124, a camera control button 125, and a remote drinking party end button 126 are displayed.

[0132] The call button 120 is an operation button for calling a staff member of the store 60 or a staff member of the remote restaurant 61. Therefore, the call button 120 is not displayed on the user terminal 41 operated by the user C who is participating in the remote drinking party from home. Alternatively, even if the call button 120 is displayed, it is in an inoperable state.

[0133] The order button 121 is an operation button for calling up menu information that can be ordered from the store terminal 30, 40 or user terminal 41 (terminal device) on which the order button 121 is pressed. After the menu information is called up, the user can actually order the menu. When the GUI providing unit 204 accepts the operation of the order button 121 from the terminal device, the GUI providing unit 204 reads out menu information that can be ordered at the store 60, the remote restaurant 61, or the user's home associated with the terminal device on which the order button 121 is operated from the store menu management table 254 or the delivery menu management table 255. Then, the GUI providing unit 204 displays a menu subscreen 132 (see FIG. 17) based on the read menu information on the display unit 36 ​​of the operating terminal device. After that, the user operates the displayed menu subscreen 132 to place an order. This will be described in detail later.

[0134] The order status check button 122 is an operation button for checking the order status of the menu ordered from the delivery store 62. When the server device 20 accepts the operation of the order status check button 122 from the terminal device, the server device 20 refers to the delivery order management table 259 and identifies the delivery store 62 that has placed the delivery order from the terminal device where the order status check button 122 has been operated. Then, the server device 20 inquires of the identified delivery store 62 about the delivery status of the menu ordered for delivery. The order receiving terminal 50 that has received the inquiry acquires information on the progress of cooking at the delivery store 62 and information on the delivery status of the delivery staff. Then, the order receiving terminal 50 transmits the acquired information to the server device 20. Then, the server device 20 replies to the content received from the order receiving terminal 50 to the terminal device that made the inquiry. Then, information indicating the order status is displayed on the main screen 110 of the terminal device. This will be described in detail later (see FIG. 21).

[0135] The checkout button 123 is an operation button for making a payment for the ordered items. When the server device 20 accepts an operation of the checkout button 123 from a terminal device, it executes a checkout process for the ordered items based on the order history information of the corresponding reservation ID registered in the store order management table 258 and the delivery order management table 259. The reservation ID can be identified from the terminal ID of the terminal device on which the checkout button 123 was operated. The details of the checkout process will be described later.

[0136] The microphone control button 124 is an operation button for temporarily stopping the microphone function of the audio input / output unit 39 of the terminal device on which the microphone control button 124 is displayed. That is, every time the microphone control button 124 is pressed, the microphone is alternately operated and stopped (toggle operation).

[0137] The camera control button 125 is an operation button for temporarily stopping the operation of an imaging device provided in the imaging unit 38 of the terminal device on which the camera control button 125 is displayed. That is, every time the camera control button 125 is pressed, the imaging device is alternately operated and stopped (toggle operation).

[0138] The remote drinking party end button 126 is an operation button for declaring withdrawal from the remote drinking party. A user who wishes to withdraw from the remote drinking party presses the remote drinking party end button 126. At this time, the sub-screen on which the withdrawing user was displayed transitions to, for example, a black screen. Alternatively, the sub-screen on which the withdrawing user was displayed may be erased, and the main screen 110 may be re-divided into sub-screens for the remaining users. When a user declares withdrawal, the bill for the menu items that the user has ordered up to that point may be billed.

[0139] Fig. 17 is a first diagram showing an example of a menu selection screen displayed on a store terminal or a user terminal. Fig. 17 is an example of a menu selection screen 130 that is displayed when the order button 121 is pressed on the main screen 110.

[0140] When the order button 121 is pressed, the screen title 111 is changed to "Order". Then, menu categories 131 are displayed at the top of the screen. Menu categories 131 are a GUI that allows multiple menu categories to be selected. Here, an example will be described in which person A, displayed on the sub-screen 112, selects "Recommended Menu".

[0141] The menu selection screen 130 includes a plurality of menu sub-screens 132. The menu sub-screens 132 are displayed superimposed on the sub-screens 112, 113, and 114. The menu sub-screens 132 include a menu item name 133, a price 134, a store icon 135, a menu image 136, and a cooking time 137.

[0142] The menu item name 133 is information indicating the name of the menu. The menu item name 133 is recorded, for example, in the store menu management table 254 or the delivery menu management table 255. The price 134 is information indicating the name of the menu. The price 134 is recorded, for example, in the store menu management table 254 or the delivery menu management table 255. The store icon 135 is a symbol mark of the store 60 or the delivery store 62. The store icon 135 is recorded, for example, in the store management table 251 or the remote restaurant management table 252. The menu image 136 is image information of the menu. The menu image 136 is recorded, for example, in the store menu management table 254 or the delivery menu management table 255. The cooking time 137 is information indicating a standard time required to cook the menu. The cooking time 137 is recorded, for example, in the store menu management table 254 or the delivery menu management table 255.

[0143] A plurality of menu sub-screens 132 are displayed aligned horizontally on the screen. Scroll buttons 138 are displayed on the left and right ends of the screen. Menu sub-screens 132 can be scrolled left and right by pressing scroll buttons 138. Menu sub-screens 132 may also be scrolled left and right by flicking a finger over an area where menu sub-screens 132 are displayed.

[0144] In this way, in response to the operation of the order button 121, the GUI providing unit 204 causes the display unit 36 ​​of the terminal device from which the operation is made to display menu information indicating the products that can be provided at the location where the terminal device corresponding to the operated order button 121 is located.

[0145] 18 is a second diagram showing an example of a menu selection result displayed on a store terminal or a user terminal. User A can select a menu to order or a menu to give as a gift to another user from among multiple menu subscreens 132.

[0146] When selecting a menu item to be ordered by the user, the user presses and holds down the menu sub-screen 132 showing the menu item to be ordered and swipes to the sub-screen 112 for the user (Mr. A), who is the order recipient. At this time, the menu sub-screen 132 moves to the position of the sub-screen 112 in conjunction with the movement of the finger. Then, when the user releases the finger from the menu sub-screen 132, the menu item on the menu sub-screen 132 is selected. In this way, the menu sub-screen 132 functions as an operator for accepting product orders.

[0147] When a menu on the menu sub-screen 132 is selected, the GUI providing unit 204 generates an order icon 142 according to the selection result. The order icon 142 includes a user icon 117, a store icon 135, and a menu image 143. The user icon 117 and the store icon 135 are as described above. The menu image 143 may be an image obtained by reducing the entire menu image 136 displayed on the menu sub-screen 132, or an image obtained by cutting out a part of the menu image 136. The generated order icon 142 is displayed inside an order menu display area 141 generated in the menu selection screen 130 in conjunction with the generation of the order icon 142. The order icon 142 is an example of order information.

[0148] When selecting a menu to present to another user, the selected menu sub-screen 132 can be swiped to the sub-screen of the recipient user. For example, when person A presents menu C to person C, person A can swipe the menu sub-screen 132 of menu C to the sub-screen 114 showing person C. This generates an order icon 142 indicating that menu C is to be presented to person C. The generated order icon 142 is displayed inside the order menu display area 141, as shown in FIG. 18.

[0149] In addition, an order button 144 is displayed inside the order menu display area 141. The order button 144 is an operator for transmitting the content of the order icon 142 to the server device 20.

[0150] A confirmation screen may be displayed when a menu is presented to another user or when a menu is received as a present from another user. FIG. 19 is a diagram showing an example of the confirmation screen displayed when a menu is presented to another participant. As shown in FIG. 19, the confirmation screen 140 displays the user name (user D) of the order destination user ID and a message 145 for confirming that a present is to be given to the user. When multiple order destination users are selected, that is, when multiple products are selected, the selections are displayed in the message 145.

[0151] Furthermore, an operation button 146 for instructing to place an order and an operation button 147 for instructing to cancel the order are displayed on the confirmation screen 140. After checking the message 145, the ordering user operates either the operation button 146 or the operation button 147 to respond as to whether or not to place the order.

[0152] When the order receiving unit 205 receives an operation of the operation button 147 from the terminal device of the order source, it erases the confirmation screen 140. Furthermore, when the order receiving unit 205 receives an operation of the operation button 146 from the terminal device of the order source, it cooperates with the GUI providing unit 204 to display the order icon 142 shown in Fig. 18.

[0153] Fig. 20 is a diagram showing an example of a confirmation screen displayed when a menu is provided by another participant. Fig. 20 shows an example of a confirmation screen 148. As shown in Fig. 20, a message 149 for confirming whether or not to accept the order is displayed on the confirmation screen 148. Fig. 20 shows an example in which the message 149 displays the product name and price of the product to be ordered, as well as the user name of the user who placed the order.

[0154] Furthermore, an operation button 146 for instructing to accept the order and an operation button 147 for instructing to reject the order are displayed on the confirmation screen 148. After checking the message 149, the user of the order destination operates either the operation button 146 or the operation button 147 to respond as to whether or not to accept the order.

[0155] Here, when the order receiving unit 205 receives an operation of the operation button 147 from the terminal device, it displays information (not shown) indicating that the order recipient user has rejected the order on the terminal device from which the order originated.

[0156] In addition, when the order receiving unit 205 receives an operation of the operation button 146 from the order destination terminal device, it cooperates with the GUI providing unit 204 to generate the order icon 142 shown in FIG.

[0157] Fig. 21 is a diagram showing an example of an order history displayed on a store terminal or a user terminal. When the GUI providing unit 204 accepts an operation of the order button 144, it generates an order history icon 151. As shown in Fig. 21, the order history icon 151 is displayed superimposed on the sub-screen of the user corresponding to the ordering destination (delivery destination) of each menu.

[0158] The order history icon 151 includes a store icon 135 and a menu image 143. In the case of a menu ordered from the delivery store 62, the order status icon 152 may be further included. The store icon 135 and the menu image 143 are as described above. The order status icon 152 includes text information indicating the status of the product ordered to the delivery store 62 until it is delivered. The order status indicated by the order status icon 152 is read by the server device 20 from the delivery status flag of the delivery order management table 259. The server device 20 reads the store icon 135 from the store information recorded in the store management table 251 or the delivery store information recorded in the delivery store management table 253. The server device 20 reads the menu image 143 from the menu information recorded in the store menu management table 254 or the menu information recorded in the delivery menu management table 255. The server device 20 transmits the information read from each table to the terminal device to display it. Also, information recorded in a related table may be read out, and the read out information may be processed by the server device 20, and transmitted to the terminal device for display. For example, the order status icon 152 may be generated by transmitting text information corresponding to the delivery status flag read out by the server device 20 from the delivery order management table 259 to the terminal device for display.

[0159] The user can reorder the same menu item by selecting the order history icon 151. Specifically, the order receiving unit 205 detects that the order history icon 151 has been operated, and receives a reorder of the menu item indicated by the order history icon 151. In other words, the order history icon 151 also functions as an operator that receives a selection operation.

[0160] FIG. 22 is a diagram showing an example of an accounting screen displayed on a store terminal or a user terminal. FIG. 22 shows an example of an accounting screen 160 displayed when the accounting button 123 displayed on the main screen 110 is operated. When the GUI providing unit 204 accepts the operation of the accounting button 123 from a terminal device, the GUI providing unit 204 cooperates with the screen display control unit 203 to display the accounting screen 160 superimposed on the main screen 110 on the display unit 36 ​​of the terminal device that operated the accounting button 123. The accounting screen 160 shown in FIG. 22 is an example of a screen that is displayed when user C, who is displayed on the sub-screen 114, operates the accounting button 123 of the terminal device that he or she is operating. When another user operates the accounting button 123, the accounting screen 160 according to the user is displayed on the display unit 36 ​​of the terminal device that the user is operating.

[0161] The accounting screen 160 displays each user's meal and drink bill 161, a receipt icon 162, a total meal and drink bill amount for all users 163, and a payment amount by payment method 164.

[0162] The food and drink bill 161 indicates the total amount of food and drink bills based on the order history of each user. If the ordering user pays for another user's product, this amount is also added to the food and drink bill 161. The food and drink bill 161 is calculated based on the order history information corresponding to each user ID registered in the store order management table 258. The food and drink bill 161 of each user is calculated based on the order history information corresponding to each user ID registered in the store order management table 258, the menu information registered in the store menu management table 254, and the menu information registered in the delivery menu management table 255. The amount displayed in the food and drink bill 161 column is updated depending on the selection of the payment method described below.

[0163] The receipt icon 162 is an operator for displaying the order history of each user. That is, when the GUI providing unit 204 accepts an operation of the receipt icon 162 from the terminal device, it reads out the order history information corresponding to each user ID registered in the store order management table 258, the menu information registered in the store menu management table 254, and the menu information registered in the delivery menu management table 255. Then, the screen display control unit 203 displays the user's order history based on the read order history information and menu information on the accounting screen 160, superimposed on a sub-screen corresponding to the user who operated the receipt icon 162.

[0164] The total meal charge 163 indicates the total meal charge for all users. The total meal charge 163 is calculated based on the order history information corresponding to all user IDs registered in the store order management table 258, the menu information registered in the store menu management table 254, and the menu information registered in the delivery menu management table 255.

[0165] The payment amount by payment type 164 indicates the payment amount of the user who operated the accounting button 123, which corresponds to a plurality of different fee payment types. The payment amount by payment type 164 indicates the payment amount for each of a plurality of different payment types. In the example of FIG. 22, the payment amount for each of three payment types, splitting the amount eaten 165, splitting equally 166, and paying all at once 167, are displayed. More specifically, the amount redistribution unit 208 cooperates with the GUI providing unit 204 and the screen display control unit 203 to display, in the accounting screen 160 displayed on the display unit 36 ​​of each terminal device, the redistribution method of the total payment amount for each terminal device and the payment amount for each terminal device based on the redistribution method, in association with each other.

[0166] The split bill 165 is a form in which each user pays for the amount they ordered. In the example of FIG. 22, the fact that user C must pay 2600 yen for his / her own food and drink bill is displayed below the split bill 165. This amount of 2600 yen matches the amount displayed in user C's food and drink bill 161. When the users who have participated in the remote drinking party consult with each other and agree that each user will pay for the amount they ordered, one of the users operates the split bill 165. Then, the accounting processing unit 206 determines the amount to be paid by each user.

[0167] The equal split 166 is a form in which each user pays the total amount of food and drink charges of all users participating in the remote drinking party divided by the number of users. In the example of FIG. 22, 2460 yen, which is obtained by dividing 7380 yen displayed in the total food and drink charge 163 by 3, the number of users participating in the remote drinking party, is displayed below the equal split 166. When the users participating in the remote drinking party consult with each other and agree to split the bill for the time being, one of the users operates the equal split 166. Then, the accounting processing unit 206 determines the amount to be paid by each user.

[0168] The lump sum payment 167 is a form in which the user pays for all the food and drink expenses of all users participating in the remote drinking party. The example of FIG. 22 shows a case in which user C pays the entire amount of 7380 yen displayed in the total food and drink amount 163. As a modified example of the lump sum payment 167, it is also possible to set the user C to pay a certain amount of the total food and drink amount 163. For example, it is possible to set the user C to pay 3380 yen out of the total food and drink amount of 7380 yen. When making such a setting, user C operates the lump sum payment 167 to display the amount input screen 180 (see FIG. 23). Then, in the amount input screen 180, the user inputs the amount to be paid. Note that the server device 20 prohibits other users from operating the payment amount while user C operates the lump sum payment 167 to input the amount. Then, after it is decided that user C will pay a certain amount, the billing screen 160 is updated. After that, user A and user B set the payment method for the remaining 4000 yen in the updated billing screen 160.

[0169] In this way, the method of a specific user paying a fixed amount is also used when the user leaves the remote drinking party in the middle of the party and pays for the food and drink that the user ordered. Note that the variations of the payment amount by payment method 164 are not limited to the example shown in FIG. 22, and other payment methods may be selectable.

[0170] When setting the payment method on the accounting screen 160, only one user can perform the setting operation. This is because if multiple users set the payment method at the same time, the payment amounts will not be consistent. Therefore, when one user is setting the payment method, it is desirable to display this on the accounting screen 160 so that the next user can set the payment method when the payment method setting is completed. The payment amount for each user calculated based on the payment form selected in this way is displayed in the corresponding user's food and drink bill 161 column.

[0171] Some establishments may provide points that can be used for future meals at a fixed rate based on the amount of food and drink consumed. In the remote food and drink providing system 10 of this embodiment, points are provided to each user according to the amount of food and drink consumed by each user. Points may also be provided to each user according to the results of game content played during the remote drinking party. The provided points are registered in the user management table 256, for example.

[0172] FIG. 23 is a diagram showing an example of an amount input screen displayed on a store terminal or a user terminal. FIG. 23 shows an example of an amount input screen 180 on which a user inputs an amount when paying a certain amount. As shown in FIG. 23, the amount input screen 180 is provided with operation buttons 181 such as numeric keys and a display area 182. When a user operating a terminal device inputs a desired amount via the operation buttons 181, the input amount is displayed in the display area 182. FIG. 23 shows an example in which, for example, user C inputs that he will pay 3380 yen. The clear button included in the operation buttons 181 is an operator for clearing the input amount.

[0173] The amount input screen 180 is also provided with an OK button 183 and a cancel button 184. When the accounting processor 206 accepts operation of the cancel button 184 from the terminal device, it erases the amount input screen 180 and displays the accounting screen 160 again.

[0174] Furthermore, when the accounting processing unit 206 accepts operation of the OK button 183 from the terminal device, it sets the amount entered in the display area 182 as the payment amount (payment amount) to be made by the user of the terminal device. The accounting processing unit 206 then causes the accounting screen 160, with the payment amount updated, to be re-displayed on the display unit 36 ​​of the terminal device.

[0175] Fig. 24 is a diagram showing an example of a payment screen displayed on a store terminal or a user terminal. Fig. 24 shows an example of a payment screen 170 displayed on the display unit 36 ​​of a terminal device operated by each user when the payment amount by payment type 164 is determined on the accounting screen 160. When the GUI providing unit 204 receives an operation of the payment amount by payment type 164 from the terminal device, the GUI providing unit 204 cooperates with the screen display control unit 203 to display the payment screen 170 superimposed on the main screen 110 on the display unit 36 ​​of the terminal device operated by each user. Note that the example in Fig. 24 shows a case where Person A pays the total amount of 7,380 yen for food and drink in one lump sum.

[0176] The payment screen 170 displays a payment amount 171 and a payment method 174. The payment amount 171 indicates the amount to be paid by each user based on the payment method selected on the checkout screen 160.

[0177] Payment method 174 shows the options of the payment method. In the example of Fig. 24, code payment 175, smart payment 176, electronic money 177, and credit card payment 178, which have been registered in advance by Mr. A as his / her own payment information, are displayed as the options of the payment method. The options of the payment method displayed in the payment method 174 field are generated and provided by the GUI providing unit 204 based on the payment information in the user information registered in the user management table 256.

[0178] User A selects a payment method from payment methods 174 and operates the operation button corresponding to the selected payment method. The accounting processing unit 206 then performs the payment process using the selected payment method.

[0179] 25 is a diagram showing an example of the operation of the transaction process executed by the transaction processing unit 200. FIG 25 shows a schematic diagram of a case in which users A to C use stores A to C, respectively.

[0180] More specifically, it is assumed that the total amount of the products consumed by user A at store A is 1,480 yen, the total amount of the products consumed by user B at store B is 3,300 yen, and the total amount of the products consumed by user C at store C is 2,600 yen. It is also assumed that each user pays a flat amount of 2,460 yen by splitting the bill.

[0181] In this case, the accounting processor 206 uses the payment information of each of the users A to C to execute accounting processing to pay the total amount for food and drink to each of the stores A to C. First, the accounting processor 206 uses the payment information of each individual user to execute accounting processing to pay the amount due to the store used by that user.

[0182] For example, in the case of user A, the total amount at store A (1,480 yen) is less than the payment amount (2,460 yen). In this case, the accounting processor 206 uses user A's payment information to execute a process to pay 1,480 yen to store A. The accounting processor 206 then allocates the excess amount, 980 yen, to payments to other stores.

[0183] In the case of user B, the total amount at store B (3,300 yen) is more than the payment amount (2,460 yen). In this case, the accounting processor 206 executes processing to pay 2,460 yen to store B using user B's payment information. The accounting processor 206 then executes processing to pay the shortfall of 840 yen to store B using the payment information of user A, who paid the excess amount. This makes up for the shortfall in the payment to store B.

[0184] In the case of user C, the total amount at store C (2,600 yen) is more than the payment amount (2,460 yen). In this case, the accounting processor 206 executes processing to pay 2,600 yen to store C using user C's payment information. The accounting processor 206 then executes processing to pay the shortfall of 140 yen to store C using the payment information of user A, who paid the excess amount. This makes up for the shortfall in the payment to store C.

[0185] This makes it possible to compensate for the shortage that occurred at store B and store B. Therefore, the server device 20 can pay the cost of the products ordered at the remote drinking party to each of the order destination stores without any overage or shortage.

[0186] (Operation of server device when user leaves midway) Next, the operation of the server device 20 when a user leaves midway will be described with reference to FIGS.

[0187] Fig. 26 is a diagram showing an example of a payment screen when a user leaves midway. Fig. 27 is a first diagram showing an example of an accounting screen when a user leaves midway. Fig. 28 is a second diagram showing an example of an accounting screen when a user leaves midway.

[0188] A case will be described where, in the state of the billing screen 160 shown in FIG. 22, user C operating the terminal device corresponding to the sub-screen 114 operates the end remote drinking party button 126.

[0189] At this time, the exiting user C operates the split bill for the amount eaten 165 shown in Fig. 22 to settle his / her bill for food and drink. Fig. 26 is an example of a settlement screen 170 that is displayed when user C operates the split bill for the amount eaten 165. At this time, the payment amount 171 shows 2600 yen, which is the payment amount of user C based on the selected split bill for the amount eaten.

[0190] User C makes a payment by selecting one of the payment methods displayed on payment screen 170. When the payment is completed, the accounting screen 160 shown in FIG. 27 is displayed on the display unit 36 ​​connected to the terminal device operated by User C.

[0191] In the accounting screen 160 of Figure 27, in the food and drink cost column displayed on the sub-screen 114 corresponding to user C, a paid marker 193 indicating that payment has been made is displayed in cooperation with the GUI provision unit 204 and the screen display control unit 203.

[0192] Furthermore, the accounting screen 160 in Fig. 27 displays a message 190 for user C, and selection buttons 191 and 192. The message 190 includes content informing user C that payment has been completed, and content to confirm whether or not to exit. The selection button 191 is an operation button that informs the server device 20 that the user will exit. The selection button 192 is an operation button that informs the server device 20 that the user will not exit yet.

[0193] In Fig. 27, when user C operates the selection button 191, for example, the billing screen 160 shown in Fig. 28 is displayed on the display unit 36 ​​connected to the terminal device operated by user A. On the other hand, when user C operates the selection button 192, the display of the billing screen 160 in Fig. 27 is maintained, and the state in which the conversation of the three users participating in the remote drinking party can continue is maintained. Then, when it is time for user C to leave, he operates the selection button 191 to leave the remote drinking party.

[0194] On the accounting screen 160 in FIG. 28, the sub-screen 114 corresponding to the exiting user C is filled in black by the operation of the screen display control unit 203.

[0195] The accounting processor 206 then displays the total amount of 4780 yen, obtained by subtracting the payment amount of 2600 yen by User C from the total amount of 7380 yen for all users, in the total meal amount 163 field. The amount redistribution unit 208 then displays the payment amount corresponding to the split method used when User A and User B split the unpaid amount of 4780 yen on the accounting screen 160, as shown in FIG.

[0196] Fig. 29 is a diagram showing an example of a main screen displayed when a user who wants to leave the remote drinking party operates the remote drinking party end button. For example, when user C operates the remote drinking party end button 126 on the terminal device that he / she is operating, the main screen 110 shown in Fig. 29 is displayed on the display unit 36 ​​connected to the terminal device that user C is operating.

[0197] The main screen 110 displays a message 190 and selection buttons 194 and 195. The message 190 includes a message asking whether to exit midway. The selection button 194 is a selection button for notifying the server device 20 that the user will pay and then exit. The selection button 195 is a selection button for notifying the server device 20 that the user will exit without making a payment.

[0198] When the select button 194 is operated on the main screen 110 in FIG. 29, the screen transitions to the accounting screen 160 shown in FIG. 22, where the user is requested to select a method for splitting the bill. For example, when splitting the amount eaten is selected, the screen transitions to the settlement screen 170 shown in FIG. 26 described above. On the other hand, when the select button 195 is operated, the screen transitions to the accounting screen 160 shown in FIG. 22, where the user is requested to select who to ask to pay for their meal and drink. The method of selecting the person to ask to pay will be described in FIG. 30.

[0199] Fig. 30 is a diagram showing an example of an accounting screen that is displayed when a user leaving a remote drinking party asks another user to pay. Accounting screen 160 in Fig. 30 shows a state in which user A is set to pay for food and drink on behalf of user C. Information indicating user C's food and drink bill 161 and user icon 117 of user C are superimposed on sub-screen 112 showing user A.

[0200] Furthermore, the payment amount by payment type column is updated and displayed according to the payment type of user A.

[0201] The method of inputting the procedure when an exiting user requests another user to pay his / her bill is, for example, input by the exiting user C selecting the food and drink bill 161 displayed on his / her own sub-screen 114 and moving it to the position of the sub-screen 112 showing the person to whom payment is being requested, for example, person A. At this time, it is desirable to display a screen equivalent to the above-mentioned confirmation screens 140, 148 to confirm both the requester, user C, and the requested user, user A. The method of inputting the procedure when an exiting user requests another user to pay his / her bill is not limited to the above, and for example, when the selection button 195 is selected, a list for selecting the name of another user to be requested to pay may be displayed.

[0202] In this way, when some of the multiple terminal devices are disconnected, the amount redistribution unit 208 can redistribute the total amount of the unsettled payment amount for each terminal device to each terminal device that is maintaining its connection, depending on whether the payment amount corresponding to the disconnected terminal device has been paid or whether the payment amount is to be left to the user operating the terminal device that is maintaining its connection. This allows the user to complete the payment process or leave the payment to another user and leave the remote drinking party at any time.

[0203] (Processing flow performed by the server device) Hereinafter, the flow of the process performed by the server device 20 will be described with reference to the flowcharts of FIGS.

[0204] 31 is a flowchart illustrating an example of the flow of a login process executed by the server device according to the embodiment. Note that this process is performed assuming that a reservation for a remote drinking party has already been made.

[0205] When participation information including the user ID of the user who operates the terminal device, the reservation ID of the remote drinking party, etc. is transmitted from the terminal device (the store terminal 30, 40 or the user terminal 41), the inter-terminal communication unit 202 receives the participation information (step S11). Next, the inter-terminal communication unit 202 refers to the reservation management table 257 and identifies reservation information that meets the conditions of the participation information (step S12).

[0206] Next, the inter-terminal communication unit 202 compares the reservation date and time (start date and time) included in the reservation information with the current date and time to determine whether the reservation date and time has arrived (step S13). If it is determined that the reservation date and time has arrived (step S13: Yes), the process proceeds to step S15. On the other hand, if it is not determined that the reservation date and time has arrived (step S13: No), the inter-terminal communication unit 202 cooperates with the GUI provision unit 204 to provide a standby screen to the terminal device operated by each user participating in the remote drinking party (step S14), and returns the process to step S13.

[0207] If it is determined in step S13 that the reserved date and time has been reached, the inter-terminal communication unit 202 cooperates with the GUI provision unit 204 to provide the start screen 100 of the remote drinking party to the terminal device operated by each user participating in the remote drinking party (step S15).

[0208] Next, the inter-terminal communication unit 202 waits until it receives a start instruction from the terminal device (step S16: No). When the inter-terminal communication unit 202 receives the start instruction from the terminal device (step S16: Yes), it establishes communication between the terminal device that transmitted the participation information and the terminal device operated by the other user registered in the reservation information (step S17), and starts data sharing between the terminal devices (step S18).

[0209] Then, the GUI providing unit 204 provides the main screen 110 to the terminal device that transmitted the participation information (step S19), and this process ends.

[0210] By performing the above-mentioned processing, the server device 20 can realize an environment in the terminal device where a remote drinking party can be held.

[0211] Fig. 32 is a flowchart showing an example of the flow of a menu selection screen providing process executed by the server device of the embodiment. Note that Fig. 27 shows an example of the flow of a process executed by the server device 20 when the order button 121 is operated from the main screen 110 displayed on the display unit 36 ​​of the terminal device.

[0212] The GUI providing unit 204 receives a menu display instruction from the terminal device via the above-mentioned order button 121 (step S21). The reservation receiving unit 201 determines whether the user who operated the order button 121 is in the store 60 by referring to the reservation management table 257 (step S22). If it is determined that the user is in the store 60 (step S22: Yes), the process proceeds to step S23. On the other hand, if it is determined that the user is not in the store 60 (step S22: No), that is, if it is determined that the user is in the remote restaurant 61 or at home, the process proceeds to step S24.

[0213] When it is determined that the user is in a store, the GUI providing unit 204 reads out the menu information of the identified store 60 from the store menu management table 254, and provides the menu selection screen 130 based on the menu information to the terminal device on which the order button 121 was operated (step S23), and ends this process.

[0214] On the other hand, if it is determined that the user is not in the store 60, the reservation reception unit 201 identifies the user's participation location by referring to the user management table 256 and the reservation management table 257 (step S24). Next, the GUI providing unit 204 reads out menu information of the delivery store that can provide delivery to the user's participation location, i.e., the remote restaurant 61 or the user's home, from the delivery menu management table 255, and provides the menu selection screen 130 based on the menu information to the terminal device on which the order button 121 was operated (step S25), and ends this process.

[0215] By carrying out the above-mentioned processing, the server device 20 can display the menu selection screen 130 on the display unit 36 ​​of the terminal device.

[0216] FIG. 33 is a flowchart illustrating an example of the flow of an order process executed by the server device of the embodiment.

[0217] First, the order receiving unit 205 receives an order operation for a product from a terminal device (step S31). Next, the order receiving unit 205 judges whether the user ID of the orderer matches the user ID of the order recipient (step S32). If the two user IDs match (step S32: Yes), the order receiving unit 205 judges that the user has ordered a product to be consumed by himself / herself, and notifies the order recipient store 60 or the delivery store 62 of the order contents (product ID, orderer user ID, etc.) (step S33). In addition, the order receiving unit 205 registers order history information including the received order contents in association with the corresponding reservation ID in the store order management table 258 or the delivery order management table 259 (step S34).

[0218] Next, the inter-terminal communication unit 202 cooperates with the GUI providing unit 204 and the screen display control unit 203 to display the order history icon 151 on the display unit 36 ​​of the terminal device (step S35). The order history icon 151 is displayed on a sub-screen corresponding to the user who is the ordering party. After that, the server device 20 ends this process.

[0219] On the other hand, if it is determined in step S32 that the two user IDs are different (step S32: No), the order receiving unit 205 determines whether a method in which the user who placed the order pays for the product (treat) has been instructed (step S36).

[0220] If it is determined in step S36 that the ordering user has not specified a payment method (step S36: No), the order receiving unit 205 displays a confirmation screen for confirming the order contents on the display unit 36 ​​of the terminal device operated by the order destination user (step S37).Then, the order receiving unit 205 waits until it receives the confirmation result from the order destination user (step S38).

[0221] If a response rejecting the order is received (step S38: No), the order receiving unit 205 ends this process without placing an order for the product. In this case, the order receiving unit 205 may provide result information indicating that to the terminal device operated by the user who placed the order.

[0222] If a response indicating consent to accept the order details is obtained in step S38 (step S38: Yes), the order receiving unit 205 notifies the order details (product ID, order destination user ID, etc.) to the order destination store 60 or delivery store 62 (step S39). The order receiving unit 205 also registers the order history information including the accepted order details in association with the corresponding reservation ID in the store order management table 258 or delivery order management table 259 (step S40), and proceeds to step S35.

[0223] On the other hand, if a payment method by the ordering user is specified in step S36 (step S36: Yes), the order receiving unit 205 causes the terminal device operated by the ordering user to display a confirmation screen for confirming the order details (step S41). The order receiving unit 205 also causes the display unit 36 ​​of the terminal device operated by the order destination user to display a confirmation screen for confirming the order details (step S42). The order receiving unit 205 then waits until it receives the confirmation result from the order destination user (step S43).

[0224] If a reply to reject the order is received from the order destination user (step S43; No), the order receiving unit 205 ends this process without placing an order for the product. Note that if the order destination user rejects the order, the order receiving unit 205 may provide result information indicating this to the terminal device operated by the order source user.

[0225] If the order destination user responds that they agree to accept the order details (step S43; Yes), the order receiving unit 205 notifies the order destination store 60 or delivery store 62 of the order details (product ID, order destination user ID, etc.) (step S44). The order receiving unit 205 also registers the order history information including the accepted order details in association with the corresponding reservation ID in the store order management table 258 or delivery order management table 259 (step S45), and proceeds to step S35.

[0226] By performing the above process, the server device 20 can display the order history of each user on a sub-screen corresponding to the user indicating the ordering destination.

[0227] Fig. 34 is a flow chart showing an example of the flow of transaction processing executed by the server device of the embodiment. In Fig. 29, it is assumed that the order history information related to the order received from the terminal device has already been registered in the store order management table 258 and the delivery order management table 259.

[0228] The accounting processor 206 determines whether or not an instruction to pay for the remote drinking party has been issued via the above-mentioned accounting button 123. If an instruction to pay has not been accepted (step S51: No), the accounting processor 206 repeats the determination in step S51.

[0229] Furthermore, if an accounting instruction is accepted in step S51 (step S51: Yes), the accounting processor 206 calculates the total payment amount based on the remaining order history information related to the reservation ID of the accounting target, excluding order history information with a paid flag of "1" (step S52). Next, the accounting processor 206 provides an accounting screen 160 to each of the terminal devices related to the reservation ID of the accounting target, based on the calculation results of step S52, etc. (step S53).

[0230] The screen display control unit 203 displays the payment amount of each user in the food and drink bill 161 field of the sub-screen corresponding to that user (step S54).

[0231] The amount redistribution unit 208 judges whether an instruction to select a payment amount has been given (step S55). If it is judged that an instruction to select a payment amount has been given (step S55: Yes), the process proceeds to step S56. On the other hand, if it is not judged that an instruction to select a payment amount has been given (step S55: No), the process proceeds to step S57.

[0232] When it is determined in step S55 that an instruction to select the payment amount has been given, the amount redistribution unit 208 calculates the payment amount for each user based on the selected payment method. Then, the screen display control unit 203 displays the payment amount for each user based on the selected payment method in the food and drink cost 161 column of the sub screen corresponding to that user (step S56).

[0233] Next, the accounting processor 206 determines whether an instruction to execute accounting has been given (step S57). If it is determined that an instruction to execute accounting has been given (step S57: Yes), the process proceeds to step S58. On the other hand, if it is determined that an instruction to execute accounting has not been given (step S57: No), the process returns to step S55.

[0234] The accounting processor 206 uses the payment information of each user to execute accounting processing to pay the payment amount set for that user to each store 60 or delivery store 62 (step S58), and ends this processing.

[0235] In the flowchart of FIG. 34, a flow may be used in which it is determined whether or not an instruction to pay for the remote drinking party has been issued, on the condition that it is determined that the end date and time of the remote drinking party has been reached.

[0236] (Effects of the server device) As described above, the server device 20 of the embodiment includes a reservation reception unit 201 (management unit) that receives access from each of the store terminals 30, 40 or the user terminal 41 (terminal device) placed in a plurality of locations, and manages the location and terminal device from which the access originates in association with the user who operates the terminal device, an inter-terminal communication unit 202 (communication control unit) that connects the terminal devices associated by the reservation reception unit 201 so that they can communicate with each other, and a screen display control unit 203 (display control unit) that displays, on a display unit 36 ​​connected to each terminal device associated by the reservation reception unit 201, a main screen 110 in which images captured by an imaging unit 38 (imaging device) corresponding to each terminal device are arranged as sub-screens 112, 113, and 114. The system includes a GUI providing unit 204 (menu providing unit) that provides menu information showing products that can be provided at the location where the terminal device belongs, so that the menu information can be viewed by terminal devices connected to each other so as to be able to communicate with each other via the inter-terminal communication unit 202, an order receiving unit 205 (order receiving unit) that receives order information of products and delivery destinations of the products from any of the terminal devices to which the menu information has been provided, and notifies the store that provides the products of the received order information, and a screen display control unit 203 (amount display unit) that displays the payment amount for each terminal device based on the order information from each terminal device associated by the reservation receiving unit 201 on the display unit 36 ​​corresponding to each terminal device in association with an image corresponding to each terminal device. Therefore, the payment amount of each user can be easily confirmed without interrupting the conversation at the remote drinking party, thereby improving the convenience of the remote food and drink provision service.

[0237] The server device 20 of the embodiment further includes an amount redistribution unit 208 that redistributes the total amount of payment of each user to each terminal device based on an instruction from the store terminal 30, 40 or the user terminal 41 (terminal device). Therefore, it is possible to provide options for payment methods such as splitting the bill across different stores and individual payment in one lump sum, thereby improving the convenience of the remote food and drink provision service.

[0238] In the server device 20 of the embodiment, the amount redistribution unit 208 causes the display unit 36 ​​connected to the terminal device to display the redistribution method of the total payment amount and the payment amount of the user associated with the terminal device based on the redistribution method in association with each other. Therefore, the payment amount of each user according to the distribution method of the total payment amount can be immediately confirmed.

[0239] In addition, in the server device 20 of the embodiment, when some of the multiple store terminals 30, 40 or user terminals 41 (terminal devices) are disconnected, the amount redistribution unit 208 redistributes the total amount of unsettled payment amounts for each terminal device to each terminal device that is maintaining its connection, depending on whether the payment amount corresponding to the disconnected terminal device has been paid or whether the payment amount is to be left to the user operating the terminal device that is maintaining its connection. Therefore, users participating in the remote drinking party can leave the remote drinking party at their own convenience, either by completing the payment process or by leaving the payment to another user.

[0240] The above-described embodiment can be modified as appropriate by changing a part of the configuration or function of each of the above-described devices. Therefore, the following describes a modified example of the above-described embodiment as another embodiment. The following mainly describes the differences from the above-described embodiment, and a detailed description of the commonalities with the contents already described will be omitted.

[0241] (First Modification of the Embodiment) In the above embodiment, a case has been described in which each user participating in a remote drinking party uses a different terminal device (store terminal 30, 40 or user terminal 41). However, the form of a remote drinking party is not limited to this, and the above-mentioned server device 20 can also handle a case in which multiple users use the same terminal device.

[0242] Specifically, when the reservation receiving unit 201 of the server device 20 receives reservations specifying the same store ID from users with different user IDs, the reservation receiving unit 201 manages the user IDs of these users in association with the same store ID.

[0243] Furthermore, when the inter-terminal communication unit 202 of the server device 20 receives a plurality of user IDs from a terminal device having the same terminal ID, the inter-terminal communication unit 202 registers these plurality of user IDs in the reservation information in association with the same terminal ID.

[0244] Note that the ordering method of multiple users using the same terminal device is not particularly important. For example, when one of multiple users using the same terminal device places an order for a product, the GUI providing unit 204 may display a screen for selecting which of the multiple users is to be the order destination (order originator). Also, for example, when a user ID other than the multiple users is selected as the order destination by one of the multiple users using the same terminal device, the GUI providing unit 204 may display a screen for selecting which of the multiple users using the same terminal device is to be the order originator.

[0245] As described above, the server device 20 of this modified example can achieve the same effects as the above-described embodiment even when a plurality of users use the same terminal device.

[0246] (Modification 2 of the embodiment) In the above-described embodiment and the first variant of the embodiment, the terminal device (store terminal 30, 40 or user terminal 41) performs screen display or GUI display on the display unit 36 ​​in response to control instructions from the server device 20, but the terminal device may be configured to perform some of these controls itself.

[0247] In other words, the reservation reception unit 201 of the server device 20 may cause the output control unit 302 of the associated terminal device (store terminal 30, 40 or user terminal 41) to function as a display control unit, a menu providing unit, an order reception unit, and a price display unit.

[0248] The display control unit displays on the display unit 36 ​​of the terminal device a main screen 110 in which the images captured by the imaging devices corresponding to each terminal device, received from the server device 20, are aligned.

[0249] The menu providing unit provides menu information indicating products that can be provided at the location where the terminal device is located so that the menu information can be viewed by terminal devices communicatively connected to each other via the inter-terminal communication unit 202 of the server device 20.

[0250] The order receiving unit receives order information on a product and a delivery destination of the product from any of the terminal devices to which the menu information has been provided, and notifies the server device 20 of the received order information.

[0251] The amount display unit displays on the display unit 36 ​​the payment amount for each terminal device based on the order information from each terminal device associated with the server device 20, in association with an image corresponding to each terminal device.

[0252] As described above, the terminal device (store terminal 30, 40 or user terminal 41) of this modified example is communicably connected to the server device 20 that manages the location of the access source, the terminal device, and the user who operates the terminal device in association with each other. The output control unit 302 of the terminal device functions as a display control unit that displays the main screen 110 in which the images captured by the imaging devices corresponding to each terminal device and received from the server device 20 are aligned on the display unit 36 ​​connected to each associated terminal device, a menu providing unit that provides menu information indicating products that can be provided at the location to which the terminal device belongs so that the menu information can be viewed by the communicably connected terminal devices, an order receiving unit that receives order information of products and delivery destinations of the products from any of the terminal devices to which the menu information has been provided, and notifies the server device 20 of the received order information, and an amount display unit that displays the payment amount for each terminal device based on the order information from each terminal device associated with the server device 20 on the display unit 36 ​​in association with the image corresponding to each terminal device. Therefore, the amount paid by each user can be easily confirmed without interrupting the conversation at the remote drinking party, thereby improving the convenience of the remote food and beverage provision service.

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

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

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

[0256] 10. Remote Food and Beverage Delivery System 20 Server device 30, 40 Store terminal (terminal device) 41 User terminal (terminal device) 50 Ordering terminal 60 stores 61 Remote Restaurant 62 Delivery Stores 110 Main Screen 112,113,114 Sub screen 132 Menu sub-screen 142 Order icon (order information) 151 Order History Icon 152 Order Status Icon 201 Reservation Reception Department (Management Department) 202 Terminal communication unit (management unit, communication control unit) 203 Screen display control unit (display control unit, amount display unit) 204 GUI provision section (menu provision section) 205 Order Reception Department (Order Reception Department) 206 Accounting Department 207 Delivery Status Acquisition Department 208 Amount Redistribution Department 301 Communication Control Unit 302 Output control section 303 Operation reception section 501 Communication control section 502 Output control section 503 Operation reception section [Prior art documents] [Patent documents]

[0257] [Patent Document 1] JP 2015-176335 A

Claims

1. a management unit that receives access from each of terminal devices placed in a plurality of locations, and manages the location of the access source, the terminal device, and a user operating the terminal device in association with each other; a communication control unit that connects the terminal devices associated with each other by the management unit so that they can communicate with each other; a display control unit that displays a main screen on a display unit connected to each of the terminal devices associated with the management unit, the main screen displaying images captured by an imaging device corresponding to each of the terminal devices; a menu providing unit that provides menu information indicating products that can be provided at the location where the terminal device is located, so that the menu information can be viewed by the terminal devices that are communicatively connected to each other by the communication control unit; an order receiving unit that receives order information on a product and a delivery destination of the product from any one of the terminal devices to which the menu information is provided, and notifies the store that provides the product of the received order information; an amount display unit that displays, on the display unit, a payment amount for each terminal device based on order information from each terminal device associated by the management unit, in association with the image corresponding to each of the terminal devices; A server device comprising:

2. further comprising an amount redistribution unit that redistributes the total amount of the payment to each of the terminal devices based on an instruction from the terminal device; The server device according to claim 1 .

3. the amount redistribution unit causes a display unit connected to the terminal device to display a redistribution method of the total payment amount and a payment amount of the user associated with the terminal device based on the redistribution method in association with each other; The server device according to claim 2.

4. the amount redistribution unit, when some of the plurality of terminal devices are disconnected, redistributes the total amount of the unsettled payment amount for each of the terminal devices to each of the terminal devices that are maintaining a connection, depending on whether the payment amount corresponding to the disconnected terminal device has been paid or whether the payment amount is to be left to a user who operates the terminal device that is maintaining the connection; The server device according to claim 2 or 3.

5. A terminal device that is communicably connected to a server device that manages a location of an access source, a terminal device, and a user who operates the terminal device in association with each other, A communication control unit that transmits and receives various information to and from the server device; display control for displaying a main screen on a display unit connected to each associated terminal device, the main screen including images captured by imaging devices corresponding to each terminal device and received from the server device; providing menu information indicating products that can be provided at a location where the terminal device is located, so that the menu information can be viewed by the terminal devices that are communicatively connected to each other; an order reception for receiving order information on a product and a delivery destination of the product from any one of the terminal devices to which the menu information has been provided, and notifying the server device of the received order information; an output control unit that controls the display unit to display a payment amount for each terminal device based on order information from each terminal device associated with the server device in association with the image corresponding to each terminal device; A terminal device comprising:

6. The computer of the server device, a management unit that receives access from each of terminal devices placed in a plurality of locations, and manages the location of the access source, the terminal device, and a user operating the terminal device in association with each other; a communication control unit that connects the terminal devices associated with each other by the management unit so that they can communicate with each other; a display control unit that displays a main screen on a display unit connected to each of the terminal devices associated with the management unit, the main screen displaying images captured by an imaging device corresponding to each of the terminal devices; a menu providing unit that provides menu information indicating products that can be provided at the location where the terminal device is located, so that the menu information can be viewed by the terminal devices that are communicatively connected to each other by the communication control unit; an order receiving unit that receives an order for a product and a delivery address of the product from any one of the terminal devices to which the menu information has been provided, and notifies the store that provides the product of the received order; an amount display unit that displays a payment amount for each terminal device based on order information from each terminal device associated with the management unit in association with the image corresponding to each of the terminal devices; A program to make it function as such.

Images