JP7633831B2 - Server device, terminal device and program - Google Patents

Description

Embodiments of the present invention relate to a server device, a terminal device, and a program.

As telework and remote work become more widespread, web conferencing systems that hold conferences over a network are becoming more 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.

Meanwhile, ordering systems for brick-and-mortar stores have been proposed in the past (for example, Patent Literature 1). However, the conventional technology is based on the assumption that orders are placed at the same store, and does not anticipate remote drinking parties. As a result, when holding a remote drinking party, the process of checking the ordered menu or reordering the same menu is cumbersome, and there is an issue that conversations between participants are interrupted when performing these operations.

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 beverage delivery services.

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 order history display unit. The management unit receives access from each of terminal devices placed in multiple locations, and manages the location of the access source, the terminal device, and the user operating 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 on a display unit connected to each terminal device associated by the management unit, in which images captured by an imaging device corresponding to each terminal device are aligned. 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 by the communication control unit to each other. The order receiving unit receives order information of the product and the delivery destination of the product from any of the terminal devices to which the menu information has been provided, and notifies the store that provides the product of the received order information. The order history display unit displays the order information received by the order receiving unit in association with the delivery destination of the ordered product on the main screen.

FIG. 1 is a block diagram showing an example of a system configuration of a remote food and drink serving system according to an embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. FIG. 3 is a diagram illustrating an example of a hardware configuration of a store terminal and a user terminal according to the embodiment. FIG. 4 is a diagram illustrating an example of a hardware configuration of the order receiving terminal according to the embodiment. FIG. 5 is a diagram illustrating an example of a data configuration of a store management table according to the embodiment. FIG. 6 is a diagram illustrating an example of a data configuration of a remote run management table according to the embodiment. FIG. 7 is a diagram illustrating an example of a data configuration of a delivery store management table according to the embodiment. FIG. 8 is a diagram illustrating an example of a data configuration of a store menu management table according to the embodiment. FIG. 9 is a diagram illustrating an example of a data configuration of a delivery menu management table according to the embodiment. FIG. 10 is a diagram illustrating an example of a data configuration of a user management table according to the embodiment. FIG. 11 is a diagram illustrating an example of a data configuration of a reservation management table according to the embodiment. FIG. 12 is a diagram illustrating an example of a data configuration of a store order management table according to the embodiment. FIG. 13 is a diagram illustrating an example of a data configuration of a delivery order management table according to the embodiment. FIG. 14 is a functional block diagram showing an example of the functional configuration of a remote food and drink providing system according to an embodiment. 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. 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. FIG. 17 is a first diagram showing an example of a menu selection screen displayed on a store terminal or a user terminal. FIG. 18 is a second diagram showing an example of a menu selection result displayed on the store terminal or the user terminal. FIG. 19 is a diagram showing an example of a confirmation screen displayed when presenting a menu to another participant. FIG. 20 is a diagram showing an example of a confirmation screen that is displayed when a menu is provided by another participant. FIG. 21 is a diagram showing an example of an order history displayed on a store terminal or a user terminal. FIG. 22 is a diagram showing another example of an order history displayed on a store terminal or a user terminal. FIG. 23 is a first diagram showing an example of a checkout screen displayed on a store terminal or a user terminal. FIG. 24 is a diagram showing an example of an amount input screen displayed on a store terminal or a user terminal. FIG. 25 is a second diagram showing an example of the accounting screen displayed on the store terminal or user terminal. FIG. 26 is a diagram showing an example of the operation of accounting processing executed by the accounting processing unit. FIG. 27 is a flowchart illustrating an example of the flow of a login process executed by the server device of the embodiment. FIG. 28 is a flowchart illustrating an example of the flow of a menu selection screen providing process executed by the server device of the embodiment. FIG. 29 is a flowchart showing an example of the flow of an order process executed by the server device of the embodiment. FIG. 30 is a flow chart showing an example of the flow of transaction processing executed by the server device of the embodiment.

The following describes the embodiments in detail with reference to the drawings. Note that the present invention is not limited to the embodiments described below.

(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, the 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.

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.

Each of the stores 60 also includes 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.

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 the 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.

Product order information 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 multiple delivery stores 62, the delivery store 62 that is considered to be able to deliver the ordered product to the order destination most quickly, and transmits the delivery order to the order receiving terminal 50 of the selected delivery store 62.

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, for example, by 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 multiple units. The order receiving terminal 50 also communicates with a handheld terminal (not shown) carried by a delivery person at the delivery store 62, making it possible to check the delivery status of the ordered items at any time.

The user terminal 41 is a terminal device used by a user who uses the remote food and beverage provision system 10. The user terminal 41 can be realized, for example, as 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.

The server device 20 is realized by, for example, an information processing device such as a workstation. Note that in this embodiment, the server device 20 is described as a single device, but this 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.

The server device 20 provides a remote food and drink delivery service by working 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 provides a service (remote food and drink delivery service) that allows multiple users in different locations to talk to each other and share screens by controlling 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.

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."

The system configuration of the remote food and drink delivery system 10 is not limited to the example shown in FIG. 1. For example, a server device other than the server device 20 may be provided to manage multiple delivery stores 62, 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.

(Hardware configuration of server device)
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.

The server device 20 has a computer configuration including a CPU (Central Processing Circuit) 21, a ROM (Read Only Memory) 22, and a RAM (Random Access Memory) 23.

The CPU 21 is an example of a processor, and controls each part of the server device 20. The ROM 22 stores various programs and data. The RAM 23 is a workspace in which the programs and data are deployed.

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

The memory unit 25 is composed of storage media such as a hard disk drive (HDD) or flash memory, and maintains its stored contents even when the power is cut off. The memory unit 25 stores programs that the CPU 21 can execute and various setting information. For example, the memory unit 25 stores programs (server programs) prepared for remote drinking parties and content 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 and the memory unit 25 into the RAM 23 and running them.

The memory unit 25 also stores various data necessary for executing a remote drinking party. Specifically, the memory 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.

(Hardware configuration of store terminal and user terminal)
Next, the hardware configuration of the store terminals 30 and 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.

The store terminal 30 has 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 part 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 deployed.

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

The communication unit 34 is a communication interface that can be connected 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 the store server in the store itself, other store terminals 30, 40, or user terminals 41.

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

The display unit 36 is a display device such as an LCD (Liquid Crystal Display), and displays various information and screens according to 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.

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.

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 the 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.

The hardware configuration of the store terminal 30 is not limited to the configuration shown in FIG. 3. The following description will be given assuming that the store terminal 40 and the user terminal 41 have the same hardware configuration as the store terminal 30.

(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.

The order receiving terminal 50 has 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 deployed.

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

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.

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

The display unit 56 is a display device such as an LCD, and displays various information and screens according to 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.

Note that the hardware configuration of the order receiving terminal 50 is not limited to the configuration shown in FIG. 4.

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

FIG. 5 is a diagram illustrating an example of the data configuration of a store management table according to an embodiment. The store management table 251 stores store information about the store 60 corresponding to the store ID in association with the store ID of each store 60.

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. Note that the data configuration of the store management table 251 is not limited to the example in FIG. 5.

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

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 the 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 that represents the remote restaurant 61 corresponding to the remote restaurant ID. Note that the data configuration of the remote restaurant management table 252 is not limited to the example shown in FIG. 6.

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

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 that represents the delivery store 62 corresponding to the delivery store ID. Note that the data configuration of the delivery store management table 253 is not limited to the example in FIG. 7.

Figure 8 is a diagram showing an example of the 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) that can be consumed at the store 60 corresponding to the store ID, in association with the store ID of each store 60. The server device 20 obtains menu information from, for example, the store server of each store 60, and stores the information in the store menu management table 254.

Menu information includes, for example, the product (menu) product ID, product name, generic name, price, product image, and description.

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 large beer" and "A medium beer", and the "beer" sold at store B is "B beer". In this case, the product ID and product name indicating "A large beer" and "A medium beer" 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.

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.

The data structure of the store menu management table 254 is not limited to the example shown in FIG. 8. The server device 20 may also update the menu information in the store menu management table 254 at a predetermined timing by periodically or at any time acquiring the menu information from the store server of each store 60.

Figure 9 is a diagram showing an example of the data configuration of a delivery menu management table according to an embodiment. The delivery menu management table 255 stores menu information about 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, obtains menu information from each delivery store 62 and stores it in the delivery menu management table 255.

The menu information includes, for example, the product (menu) product ID, product name, generic name, price, product image, and description. The content of each item is the same as the data stored in the store menu management table 254 described above. Note that the server device 20 may manage the store menu and delivery menu together as a single menu management table rather than separating them into the store menu management table 254 and the delivery menu management table 255.

FIG. 10 is a diagram showing an example of the data configuration of a user management table according to an embodiment. The user management table 256 stores user information about 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.

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 along with the user name. The address is information indicating the address or whereabouts 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 payments such as credit card payments and electronic money payments. 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.

The data configuration of the user management table 256 is not limited to the example of 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. In addition, the host of a remote drinking party may be assigned a flag indicating that he or she is the host.

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

The reservation ID is identification information for identifying a reservation for a remote drinking party. The server device 20 issues a unique reservation ID (e.g., an ascending number) each time it accepts a reservation for a remote drinking party from a user via the user terminal 41 or the like.

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

The reservation date and time is information that indicates the date and time when the remote drinking party is scheduled to take place. The reservation date and time is expressed, for example, as a period between a start date and time and an end date and time.

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, etc.

The location of participation in the 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.

The terminal ID is registered with the identification information of the store terminal 30, 40 or the user terminal 41 used in the remote drinking party. 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.

In this embodiment, among the information included in the reservation information, the reservation date and time, user ID, and participation location are assumed to be registered before the remote drinking party is held. Furthermore, among the information included in the reservation information, the terminal ID and login date and time are assumed to be registered on the day the remote drinking party is held, that is, when the user corresponding to the user ID arrives at the participation location. Note that the participation location may be registered when the user arrives at the participation location on the day the remote drinking party is held. Alternatively, the user and the user's participation location may be associated and registered. 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.

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 and organizer of the remote drinking party in association with a user ID.

Figure 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 related to products ordered from the store 60 for the remote drinking party corresponding to the reservation ID, in association with the reservation ID. That is, when a menu item offered by the store 60 is ordered at the store 60, the order history of that order is recorded in the store order management table 258.

The order history information includes, for example, the order ID, the ordering user ID, the ordering user ID, the participating location, the product ID, the quantity, and a payment completion flag. In addition, the participating location records the store ID from which the menu item is ordered.

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

The ordering user ID is registered with the user ID of the user who ordered the product. The order recipient user ID is registered with the user ID of the user to whom the ordered product will be provided. For example, if a user orders a product to be consumed by 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 a product to be consumed by another user, different user IDs are registered as the ordering user ID and the order recipient user ID.

In the participation location, information that identifies the location where the user of the ordering user ID is located is registered, for example, 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 that identifies the user's own home. In the product ID, the product ID of the product that is the subject of the order is registered. In the quantity, the quantity of the product that is the subject of the order is registered.

In the paid flag, flag information is registered that indicates whether the payment for the product that was the subject of the order has been made. In this embodiment, as described below, 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 reorder"), 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 a treat order has been made. Note that in FIG. 12, unpaid is defined as a flag "0" and paid is defined as a flag "1".

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 the order.

Figure 13 is a diagram showing an example of the 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 the 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. That is, when the order destination is the store 60, the server device 20 records the order information in the store order management table 258, and when the order destination is the delivery store 62, the server device 20 records the order information in the delivery order management table 259.

The delivery status information includes, for example, the order ID, the ordering user ID, the ordering 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, a delivery status flag, etc.

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

The ordering user ID is registered with the user ID of the user who ordered the delivery of the product. The order recipient user ID is registered with the user ID of the user to whom the ordered product will be provided. 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.

The delivery store ID records the delivery store ID of the delivery store 62 that is the order destination.

Information specifying the delivery destination of the product is registered in the delivery location. Specifically, information specifying the location of the user of the ordering user ID is registered, for example, the store ID of store 60 used for the remote drinking party, the remote restaurant ID of remote restaurant 61, or identification information specifying the user's own home.

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.

In the paid flag, flag information is registered that indicates whether or not the payment for the product to be delivered has been made. In this embodiment, as described below, 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 reorder"), 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. Note that in FIG. 13, unpaid is defined as a flag "0" and paid is defined as a flag "1".

The delivery status flag registers information indicating the preparation status of the product to be delivered. Examples of the preparation status of the product to be delivered include "preparing to cook," "cooking," "delivering," "delivery completed," "serving," etc.

The data configuration of the delivery order management table 259 is not limited to the example shown in FIG. 13. For example, the delivery order management table 259 may store information indicating the current location of the delivery person and the estimated delivery time. In addition, the server device 20 may manage the store order management table 258 and the delivery order management table 259 together as a single order management table, rather than separating them.

(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.

The server device 20 has the following functional units: a reservation reception unit 201, a terminal-to-terminal communication unit 202, a screen display control unit 203, a GUI provision unit 204, an order reception unit 205, an accounting processing unit 206, and a delivery status acquisition unit 207.

Some or all of the functional units of the server device 20 may be software configurations realized by cooperation between the 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, some or all of the functional units of the server device 20 may be hardware configurations realized by a dedicated circuit or the like mounted on the server device 20.

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

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, the host or organizer user (hereinafter also referred to as the organizer) accesses the website using a 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, the user's user ID, the store SP (store ID) to be used, etc.

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 entered details. The reservation reception unit 201 also notifies the user's user terminal 41 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.

Meanwhile, other users who have been notified of the reservation ID use their own user terminals 41 to access the above website specifying the reservation ID. When the reservation reception unit 201 receives an access specifying a reservation ID, it reads the reservation information (date and time of the event, etc.) corresponding to the reservation ID from the reservation management table 257 and provides it visibly to the user terminal 41 from which the access originated. The other users then make a reservation (additional reservation) for a remote drinking party by inputting their own user ID, the store 60 (store ID) that they will be using, the remote restaurant 61 (remote restaurant ID), etc. When the reservation reception unit 201 receives the additional reservation, it additionally registers the items of the additional reservation to the reservation information for the previously input reservation ID.

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 that are located within a predetermined range (e.g., within 3 km) of the user's address as candidates for use for the remote drinking party.

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 this. For example, if the representative has acquired the user IDs of the participants in advance, the representative may register the user IDs of the participants collectively. In addition, 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 who has completed the user ID registration. 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 to execute 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 from which the access originates, the terminal device, and the user who operates the terminal device in association with each other. Note that the reservation reception unit 201 is an example of a management unit.

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) from which the access originates, in association with the user (user ID) operating the terminal device.

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, i.e., users belonging to the same group, so that they can communicate with each other.

Specifically, when the inter-terminal communication unit 202 receives 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 the identified reservation information includes the specified user ID. 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.

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 each of the terminal devices they operate.

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

In addition, the inter-terminal communication unit 202 may be configured to deny access if the user ID received from the terminal device is not included in the reservation information for the corresponding reservation ID, or may be configured to add the user ID to the reservation information.

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, where sub-screens displaying images captured by the imaging units 38 (imaging devices) corresponding to the respective terminal devices are aligned. The screen display control unit 203 displays the order information received by the order reception unit in association with the delivery address of the ordered product on the main screen displayed on the display unit 36. The screen display control unit 203 is an example of a display control unit and an order history display unit. The sub-screens and main screens will be described later (see FIG. 16).

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.

The order receiving unit 205 is an example of an order receiving unit and an order information selection 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.

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). Then, the order receiving unit 205 registers the identified user ID, ordering store ID or delivery store ID, product ID, and other information in association with the newly issued order ID in the order history information in the store order management table 258 corresponding to the reservation ID corresponding to the identified user ID or in the delivery order history information in the delivery order management table 259.

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

The payment method for 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 for the product price has been completed together with the user ID from a device such as the user terminal 41 or the store server.

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 items 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.

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

In addition, 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 the memory (e.g., ROM 32, storage unit 35).In addition, 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.

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. Also, for example, the communication control unit 301 receives image data and audio data transmitted from other store terminals 30, 40 or user terminals 41 via the server device 20.

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 other store terminals 30, 40 or the user terminal 41. The output control unit 302 also works in cooperation with the server device 20 to display various GUIs on the display unit 36. 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 other store terminals 30, 40 or the user terminal 41.

The operation reception unit 303 receives the user's operation content input via the operation unit 37. For example, the operation reception unit 303 receives an operation on the GUI displayed on the display unit 36. In this embodiment, the store terminal 30, 40 or the user terminal 41 (terminal device) functions as an input/output interface of the server device 20.

The order receiving terminal 50 has a communication control unit 501, an output control unit 502, and an operation reception unit 503 as functional units.

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 obtains the delivery status of the ordered menu item by communicating with a handheld terminal (not shown) carried by the delivery person.

The output control unit 502 controls the display unit 56 to output the received order information. 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. The output control unit 502 also outputs the delivery status of the ordered menu to the server device 20.

The operation reception unit 503 receives the operation contents of the staff of the delivery store 62 inputted via the operation unit 57. For example, the operation reception unit 503 receives operations 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.

(Operation of the 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.

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 the remote drinking party, by the organizer sending an invitation or the like that specifies the reservation ID and 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 user terminal 41 in the identified reservation information.

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

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 the user that the start date and time has not been reached. On such a standby screen, for example, a countdown to the start date and time may be displayed.

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 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 start screen 100 that allows the user to instruct the start of a remote drinking party.

Figure 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 Figure 15, the start screen 100 has a start button 101, which is an operator for instructing the start of a remote drinking party.

When the inter-terminal communication unit 202 receives an 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.

In addition, when the GUI providing unit 204 accepts an operation of the start button 101 from the store terminal 30, 40 or the user terminal 41 by working together with the screen display control unit 203, the GUI providing unit 204 causes the display unit 36 of the store terminal 30, 40 or the user terminal 41 to display a main screen 110 for displaying data (image data) shared between the store terminals 30, 40 or the user terminal 41.

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, the main screen 110 has a plurality of sub-screens 112, 113, and 114 divided according to the number of participants in 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, 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 obtains the 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 obtained screen title 111 on the main screen 110. Note that the following explanation will be given assuming that Figure 15 shows the main screen 110 displayed on the terminal device operated by Person A.

Each of the sub-screens 112, 113, and 114 is associated with the terminal ID of the store terminal 30, 40 or user terminal 41 (terminal device) operated by each user, the user ID of the user operating the terminal device, the store ID of the store 60 to which the store terminal 30 belongs, the store ID of the remote restaurant 61 to which the store terminal 40 belongs, etc. In addition, 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. In addition, 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.

This allows users of each terminal device to view the main screen 110 and talk to each participant in the remote drinking party while looking at each other's faces.

In addition, each of the sub-screens 112, 113, and 114 displays a user name and user icon 117 corresponding to the user ID associated with that sub-screen 112, 113, and 114. Specifically, the GUI provision unit 204 reads out the user name and user icon corresponding to the user ID from the user management table 256. Then, the screen display control unit 203 superimposes the read out user name and user icon 117 on the sub-screens 112, 113, and 114.

In addition, each of the sub-screens 112, 113, and 114 displays the user's participation location 115 associated with the sub-screen 112, 113, and 114. Specifically, the GUI provision unit 204 reads out the user's participation location from the reservation management table 257. Then, the screen display control unit 203 superimposes the read out user's participation location 115 on the sub-screens 112, 113, and 114. The number of sub-screens is appropriately set by the action of the screen display control unit 203 according to the number of terminal devices connected to each other.

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). Note that since Mr. A is the host of the remote drinking party, the host icon 116 may be displayed on the sub-screen 112.

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

In addition, various operation buttons are displayed on the main screen 110. In the example of FIG. 16, a call button 120, an order button 121, an order status check button 122, a checkout button 123, a microphone control button 124, a camera control button 125, and an end remote drinking party button 126 are displayed.

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 Mr. 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.

The order button 121 is an operation button that calls 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 place an order for 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, remote restaurant 61, or user's home associated with the terminal device on which the order button 121 is operated from the store menu management table 254 or delivery menu management table 255. The GUI providing unit 204 then displays a menu subscreen 132 (see FIG. 17) based on the read menu information on the display unit 36 of the operating terminal device. The user then operates the displayed menu subscreen 132 to place an order. This will be described in detail later.

The order status confirmation button 122 is an operation button for confirming the order status of the menu ordered from the delivery store 62. When the server device 20 accepts the operation of the order status confirmation 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 placed the delivery order from the terminal device where the order status confirmation button 122 was operated. The server device 20 then inquires of the identified delivery store 62 about the delivery status of the menu ordered for delivery. The order receiving terminal 50 that receives the inquiry acquires information related to the progress of cooking at the delivery store 62 and information related to the delivery status of the delivery staff. The order receiving terminal 50 then transmits the acquired information to the server device 20. The server device 20 then replies to the terminal device that made the inquiry with the contents received from the order receiving terminal 50. Information indicating the order status is then displayed on the main screen 110 of the terminal device. Details will be described later (see Figs. 21 and 22).

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 the 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.

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. In other words, each time the microphone control button 124 is pressed, the microphone is alternately turned on and off (toggle operation).

The camera control button 125 is an operation button for temporarily stopping the operation of the imaging device provided in the imaging unit 38 of the terminal device on which the camera control button 125 is displayed. In other words, each time the camera control button 125 is pressed, the imaging device is alternately operated and stopped (toggle operation).

The end remote drinking party 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 end remote drinking party button 126. At this time, the sub-screen on which the withdrawing user was displayed transitions to a black screen, for example. 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 payment for any menu items that the user has ordered up to that point may be processed.

Figure 17 is a first diagram showing an example of a menu selection screen displayed on a store terminal or a user terminal. Note that Figure 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.

When the order button 121 is pressed, the screen title 111 changes 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, we will explain the case where person A, who is displayed on the sub-screen 112, selects "Recommended Menu".

The menu selection screen 130 includes a number 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.

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 the 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.

The multiple menu sub-screens 132 are displayed aligned horizontally on the screen. Scroll buttons 138 are displayed on the left and right edges of the screen. By pressing the scroll buttons 138, the menu sub-screens 132 can be scrolled left and right. The menu sub-screens 132 may also be scrolled left and right by flicking a finger over the area in which the menu sub-screens 132 are displayed.

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 operating terminal device to display menu information showing products that can be provided at the location where the terminal device corresponding to the operated order button 121 is located.

Figure 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 for himself or herself or a menu to give as a gift to another user from among multiple menu subscreens 132.

When selecting a menu item to order, the user presses and holds down the menu sub-screen 132 that shows the menu item to be ordered, and swipes to the sub-screen 112 for the order recipient (Mr. A). 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. When the user releases the finger from the menu sub-screen 132, the menu on the menu sub-screen 132 becomes selected. In this way, the menu sub-screen 132 functions as an operator for accepting product orders.

When a menu is selected on the menu sub-screen 132, 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 a reduced image of the entire menu image 136 displayed on the menu sub-screen 132, or an image of a portion of the menu image 136. The generated order icon 142 is displayed inside an order menu display area 141 that is 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.

When selecting a menu to present to another user, the user simply swipes the selected menu sub-screen 132 to the sub-screen of the recipient user. For example, if Person A wishes to present Menu C to Person C, Person A simply swipes 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 will be presented to Person C. The generated order icon 142 is displayed within the order menu display area 141, as shown in FIG. 18.

In addition, an order button 144 is displayed inside the order menu display area 141. The order button 144 is an operator for sending the contents of the order icon 142 to the server device 20.

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

The confirmation screen 140 also displays an operation button 146 for instructing the user to place an order and an operation button 147 for instructing the user to cancel the order. After checking the message 145, the ordering user responds by operating either the operation button 146 or the operation button 147 as to whether or not to place the order.

When the order receiving unit 205 receives an operation of the operation button 147 from the terminal device of the order originator, it erases the confirmation screen 140. In addition, when the order receiving unit 205 receives an operation of the operation button 146 from the terminal device of the order originator, it cooperates with the GUI providing unit 204 to display the order icon 142 shown in FIG. 18.

Figure 20 is a diagram showing an example of a confirmation screen that is displayed when a menu is provided by another participant. Figure 20 shows an example of a confirmation screen 148. As shown in Figure 20, confirmation screen 148 displays a message 149 for confirming whether or not to accept the order. Note that Figure 20 shows an example of message 149 that also displays the product name and price of the product to be ordered, and the user name of the user who placed the order.

The confirmation screen 148 also displays an operation button 146 for instructing the user to accept the order and an operation button 147 for instructing the user to reject the order. After checking the message 149, the user who is to receive the order operates either the operation button 146 or the operation button 147 to respond as to whether or not to accept the order.

Here, when the order receiving unit 205 receives an operation of the operation button 147 from a terminal device, it displays information (not shown) on the terminal device from which the order was placed indicating that the user to whom the order was placed has rejected the order.

In addition, when the order receiving unit 205 receives an operation of the operation button 146 from the terminal device of the order destination, the order receiving unit 205 cooperates with the GUI providing unit 204 to generate the order icon 142 shown in FIG. 18 and display it in the order menu display area 141.

Figure 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 Figure 21, the order history icon 151 is displayed superimposed on the sub-screen of the user corresponding to the order destination (delivery destination) of each menu.

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 further be 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 from 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 then transmits the information read from each table to the terminal device to display it. Alternatively, information recorded in a related table may be read, and the server device 20 may process the read information and transmit it 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 by the server device 20 from the delivery order management table 259 to the terminal device for display.

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 accepts 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 accepts a selection operation.

Figure 22 is a diagram showing another example of an order history displayed on a store terminal or a user terminal. As shown in Figure 22, an order history icon 161 may be displayed superimposed on a sub-screen of a user corresponding to the order destination (delivery destination) of each menu. The order history icon 161 includes a store icon 135, a menu image 143, and an order status icon 162.

The order status icon 162 includes graphic information indicating the status of the ordered item until it is delivered. The order status icon 162 is stored in advance in the server device 20 in the form of graphic information corresponding to the delivery status flag. The server device 20 then reads out the graphic information corresponding to the delivery status flag read out from the delivery order management table 259, and transmits it to the terminal device for display. The user can reorder the same menu by selecting the order history icon 161. In other words, the order history icon 161 also functions as an operator that accepts selection operations.

Next, the accounting process will be described with reference to FIG. 23. FIG. 23 is a first diagram showing an example of an accounting screen displayed on a store terminal or a user terminal. As shown in FIG. 23, the accounting screen 170 displays payment information 171 indicating the total amount to be paid for the products and the remaining balance. Note that when the accounting screen 170 is displayed, no payment operation has been performed, so the total amount to be paid and the remaining balance displayed in the payment information 171 are the same amount.

The accounting screen 170 also displays a total amount 172 calculated for each user. The total amount 172 is displayed, for example, in correspondence with the user name. The accounting screen 170 also displays a split amount 173. The split amount 173 is the total amount to be paid for the products shown in the payment information 171 divided by the number of users who participated in the remote drinking party. The accounting screen 170 may be freely operated by any user who participated in the remote drinking party, or may be operated only by a representative of the users who participated in the remote drinking party (for example, the organizer of the remote drinking party).

As a result, each user operating a terminal device can easily check the total amount to be paid for the products ordered at the remote drinking party and the total amount of the products consumed by each person by looking at the accounting screen 170 displayed on the display unit 36 of the terminal device.

The accounting screen 170 also has an individual button 174 and a split-the-bill button 175 as controls for specifying the payment method. The individual button 174 is provided for each user, and is used when the user pays an amount of their choice (hereinafter also referred to as "individual payment").

Specifically, when the accounting processing unit 206 receives an operation of the individual button 174 from the terminal device, it cooperates with the GUI provision unit 204 to cause the display unit 36 of the terminal device to display the amount input screen 180 shown in FIG. 24.

Figure 24 is a diagram showing an example of an amount input screen displayed on a store terminal or a user terminal. Figure 24 shows an example of the display of an amount input screen 180. As shown in Figure 24, the amount input screen 180 is provided with operation buttons 181 such as numeric keys, and a display area 182. When a user operating the terminal device inputs a desired amount via the operation buttons 181, the input amount is displayed in the display area 182. The clear button included in the operation buttons 181 is an operator for clearing the input amount. The full amount button included in the operation buttons 181 is an operator for inputting the remaining amount displayed on the accounting screen 170.

The amount input screen 180 also has an OK button 183 and a cancel button 184. When the accounting processing unit 206 receives an operation of the cancel button 184 from the terminal device, it erases the amount input screen 180 and displays the accounting screen 170 again.

When the accounting processing unit 206 receives an 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) of the user of the terminal device. Then, as shown in FIG. 25, the accounting processing unit 206 displays the accounting screen 170 with the updated payment information 171, etc., on the display unit 36 of the terminal device operated by each user in the same group.

Figure 25 is a second diagram showing an example of an accounting screen displayed on a store terminal or a user terminal. Figure 25 shows the updated state of the accounting screen 170 described in Figure 23. As shown in Figure 25, the accounting screen 170 displays input amount information 177 indicating the payment amount entered on the amount input screen 180 in association with the username (individual button 174) of the user who performed the input operation. In addition, the remaining balance in the payment information 171 is updated to a value obtained by subtracting the payment amount indicated by the input amount information 177 from the total payment amount.

Furthermore, the updated remaining amount divided by the number of users who have not yet entered an amount on the amount input screen 180 is displayed as a reference value 178. In FIG. 25, two users, User B and User D, have not yet entered an amount, so the remaining amount of "4000 yen" divided by the two users to get "2000 yen" is displayed as the reference value 178.

On the other hand, the "Split the Bill" button 175 is used when each user pays an equal amount (hereinafter referred to as "Split the Bill payment"). When the accounting processing unit 206 receives an operation of the "Split the Bill" button 175, it sets the "Split the Bill" amount displayed on the accounting screen 170 as the amount to be paid by each user.

For example, when the accounting screen 170 shown in FIG. 23 accepts an operation of the Split button 175, the accounting processing unit 206 sets the payment amount for each of users A, B, and C to 4,340 yen. Also, when the accounting screen 170 shown in FIG. 25 accepts an operation of the Split button 175, the accounting processing unit 206 sets the payment amount for each of users B and C, who have not yet entered an amount, to 2,000 yen, as shown in the reference value 178.

When the balance becomes "0", the accounting processing unit 206 activates the payment button 176 located in the bottom right of the accounting screen 170 so that it can be operated. The payment button 176 is an operator for instructing the execution of accounting processing.

When the accounting processing unit 206 accepts the operation of the payment button 176 from any of the terminal devices operated by users A to C, it executes accounting processing to pay the payment amount set for each user using the payment information of that user. Specifically, the accounting processing unit 206 executes accounting processing to pay the amount of the product ordered from the store 60 or delivery store 62 used by each user.

Then, when the accounting process is completed, the reservation reception unit 201 determines that the remote drinking party for the corresponding reservation ID has ended, and invalidates the data entry for that reservation ID. For example, the reservation reception unit 201 deletes the data entry for the reservation ID for which the remote drinking party has ended, or moves it to another data table.

When the end date and time of the reservation date and time is reached, the reservation reception unit 201 (or the accounting processing unit 206, etc.) may cooperate with the GUI provision unit 204 to cause the display unit 36 of the terminal device operated by each user to display an end notification screen (not shown) that notifies the user that the end date and time has been reached.

Figure 26 is a diagram showing an example of the accounting process executed by the accounting processing unit. Figure 26 shows a schematic diagram of a case in which users A to C use stores A to C, respectively.

More specifically, it is assumed that the total price of the products consumed by user A at store A is 4,920 yen, the total price of the products consumed by user B at store B is 5,080 yen, and the total price of the products consumed by user C at store C is 3,020 yen. It is also assumed that each user pays a flat rate of 4,340 yen by splitting the bill.

In this case, the accounting processing unit 206 uses the payment information of each of users A to C to perform accounting processing to pay the total amount for food and drink to each of stores A to C. First, the accounting processing unit 206 uses the payment information of each individual user to perform accounting processing to pay the amount to be paid to the store used by that user.

For example, in the case of user A, the total amount at store A (4,920 yen) is equal to or greater than the payment amount (4,340 yen). In this case, the accounting processing unit 206 uses user A's payment information to execute processing to pay the payment amount to store A. In the case of user B, the total amount at store B (5,080 yen) is equal to or greater than the payment amount (4,340 yen). In this case, the accounting processing unit 206 uses user B's payment information to execute processing to pay the payment amount to store B. Also, in the case of user C, the total amount at store C (3,020 yen) is less than the payment amount (4,340 yen). In this case, the accounting processing unit 206 uses user C's payment information to execute processing to pay the total amount to store C.

In addition, in the above payments, there may be cases where some stores do not pay the full total amount. For example, at store A, user A's payment amount is short by 580 yen. At store B, user B's payment amount is short by 740 yen.

Therefore, the accounting processing unit 206 executes a process to compensate for the shortfall that occurred between store A and store B, using the payment information of user C, who paid the total amount in the previous accounting process.

For example, the accounting processing unit 206 executes processing to pay 580 yen to store A and 740 yen to store B based on the difference of 1,320 yen between the 3,020 yen paid by user C to store C and the payment amount of 4,340 yen.

This makes it possible to compensate for any shortfalls that occur at store A 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 stores where the orders were placed without any overage or shortfall.

The accounting method (payment method) executed by the accounting processor 206 is not limited to the example shown in FIG. 26. For example, the payment information of users A to C may be used to make payments in order starting from store A to fill the total amount. In this case, the payment amount of user A's payment of 4,340 yen leaves store A short of 580 yen, so the payment information of user B is used to make a payment of 580 yen to store A. Next, a process is executed to pay store B the remaining amount of 3,760 yen, which is the amount obtained by subtracting the 580 yen previously paid from the payment amount of user B's payment of 4,340 yen. Then, if a shortfall occurs, the payment information of user C is used to make up the shortfall, and the price of the products ordered at the remote drinking party can be paid to each store, as described above.

(Flow of processing performed by the server device)
The flow of the processes performed by the server device 20 will be described below with reference to the flowcharts of FIGS.

Figure 27 is a flowchart showing an example of the flow of login processing executed by the server device of the embodiment. Note that this processing is premised on the assumption that a reservation for a remote drinking party has already been made.

When participation information including the user ID of the user operating the terminal device, a reservation ID for a remote drinking party, etc. is transmitted from a terminal device (store terminal 30, 40 or 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).

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 been reached (step S13). If it is determined that the reservation date and time has been reached (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 been reached (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 the process returns to step S13.

If it is determined in step S13 that the reservation 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).

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

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

By performing the above processing, the server device 20 can create an environment on the terminal device where a remote drinking party can be held.

Figure 28 is a flowchart showing an example of the flow of a process for providing a menu selection screen executed by the server device of the embodiment. Note that Figure 28 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.

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.

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 a 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.

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 provision unit 204 reads out menu information of the delivery store that can provide delivery at 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.

By performing the above processing, the server device 20 can display the menu selection screen 130 on the display unit 36 of the terminal device.

Figure 29 is a flowchart showing an example of the order processing flow executed by the server device of the embodiment.

First, the order receiving unit 205 receives an order for a product from a terminal device (step S31). Next, the order receiving unit 205 determines 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 determines that the user has ordered a product to be consumed by himself/herself, and notifies the order recipient store 60 or delivery store 62 of the order details (product ID, orderer user ID, etc.) (step S33). The order receiving unit 205 also registers order history information including the received order details in association with the corresponding reservation ID in the store order management table 258 or delivery order management table 259 (step S34).

Next, the inter-terminal communication unit 202 cooperates with the GUI provision unit 204 and the screen display control unit 203 to display the order history icons 151, 161 on the display unit 36 of the terminal device (step S35). Note that the order history icons 151, 161 are displayed on a sub-screen corresponding to the user who is the order destination. After that, the server device 20 ends this process.

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 (treat) in which the user who placed the order pays for the product has been instructed (step S36).

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). The order receiving unit 205 then waits until it receives a confirmation result from the order destination user (step S38).

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 this to the terminal device operated by the user who placed the order.

If an answer indicating consent to accept the order details is obtained in step S38 (step S38: 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 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.

On the other hand, if a payment method is specified by the ordering user 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 contents (step S41). The order receiving unit 205 also causes the display unit 36 of the terminal device operated by the order recipient user to display a confirmation screen for confirming the order contents (step S42). The order receiving unit 205 then waits until it receives the confirmation result from the order recipient user (step S43).

If a response rejecting the order contents is received from the order-recipient user (step S43; No), the order receiving unit 205 ends this process without placing an order for the product. Note that if the order-recipient user rejects the order contents, the order receiving unit 205 may provide result information indicating this to the terminal device operated by the ordering user.

If the order recipient user responds that they agree to accept the order details (step S43; Yes), the order receiving unit 205 notifies the order recipient store 60 or delivery store 62 of the order details (product ID, order recipient 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.

By performing the above process, the server device 20 can display each user's order history on a sub-screen corresponding to the user who is indicating the ordering destination.

Figure 30 is a flowchart showing an example of the flow of accounting processing executed by the server device of the embodiment. In Figure 30, it is assumed that order history information related to an order accepted from a terminal device has already been registered in the store order management table 258 and the delivery order management table 259.

First, the reservation reception unit 201 determines whether or not there is a reservation ID (remote drinking party) whose end date and time has been reached, based on the reservation information registered in the reservation management table 257 (step S51). If there is a reservation ID whose end date and time has been reached (step S51: Yes), the reservation reception unit 201 provides an end notification screen to each of the terminal IDs associated with that reservation ID (step S52) and proceeds to step S53. Also, if it is determined that there is no reservation ID whose end date and time has been reached (step S51: No), the reservation reception unit 201 also proceeds to step S53.

In step S53, the accounting processing unit 206 determines whether or not an instruction to pay for the remote drinking party has been received via the accounting button 123 described above. If an instruction to pay has not been received (step S53: No), the accounting processing unit 206 returns the process to step S51.

If an accounting instruction is received in step S53 (step S53: 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 S54). Next, the accounting processor 206 provides an accounting screen 170 to each of the terminal devices related to the reservation ID of the accounting target based on the calculation result in step S54, etc. (step S55).

Next, when the accounting processing unit 206 receives an operation to specify a payment method from any of the terminal devices that provided the accounting screen 170 (step S56), it determines whether the specified payment method is "individual payment" or "split payment" (step S57).

If the specified payment method is individual payment (step S57: Yes), the accounting processing unit 206 sets the specified amount as the payment amount of the user who performed the payment operation (step S58) and proceeds to step S60.

On the other hand, if the specified payment method is split payment (step S57: No), the accounting processing unit 206 sets the total payment amount, or the remainder obtained by subtracting the payment amount from the total payment amount, divided by the number of users who have not yet paid, as the payment amount for that user (step S59), and proceeds to step S60.

In step S60, the accounting processing unit 206 determines whether the remaining balance obtained by subtracting the payment amount from the total payment amount is zero. If the remaining balance is not zero (step S60: No), the process returns to step S55, and an accounting screen with updated information such as the remaining balance is provided to the terminal device.

Also, if it is determined in step S60 that the remaining balance is zero (step S60: Yes), the accounting processing unit 206 executes accounting processing to pay the payment amount set for that user to each store 60 or delivery store 62 using the payment information of that user (step S61), and ends this processing.

Note that the flowchart in FIG. 30 shows a process for determining whether or not an order for payment has been instructed for the remote drinking party on the condition that it has been determined that the end date and time of the remote drinking party has been reached, but the determination of whether or not an order for payment has been instructed may be made regardless of whether or not the end date and time of the remote drinking party has been reached.

(Functions and Effects of the Server Device)
As described above, the server device 20 of the embodiment 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, the inter-terminal communication unit 202 (communication control unit) that connects the terminal devices associated with the reservation reception unit 201 so that they can communicate with each other, and displays on the display unit 36 connected to each terminal device associated with the reservation reception unit 201 a main screen 110 in which images captured by the imaging unit 38 (imaging device) corresponding to each terminal device are arranged as sub-screens 112, 113, and 114. The system includes a screen display control unit 203 (display control unit), a GUI providing unit 204 (menu providing unit) that provides menu information representing 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 in a manner that allows communication between the terminal devices by 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 (order history display unit) that displays the order information received by the order receiving unit 205 in association with the delivery destination of the ordered products on the main screen 110. Therefore, since the ordered menu is displayed in association with each user, each user can check the order history without interrupting the conversation at the remote drinking party. This can improve the convenience of the remote food and drink provision service.

In addition, in the server device 20 of the embodiment, the screen display control unit 203 (order history display unit) displays the order information in the sub-screens 112, 113, and 114 that correspond to the delivery destination of the order information. Therefore, it is possible to immediately check which user has ordered what menu item.

The server device 20 of the embodiment further includes an order receiving unit 205 (order information selection unit) that receives a selection operation of the order information displayed by the screen display control unit 203 (order history display unit) and reorders the same product. Therefore, it is easy to reorder a menu item that has already been ordered.

In addition, in the server device 20 of the embodiment, the screen display control unit 203 (order history display unit) displays the order information in a form associated with the status of the ordered item until it is delivered. Therefore, the current status of the ordered menu can be easily confirmed. Also, it is possible to prevent forgetting to pick up the delivered item.

The above-described embodiment can be modified as appropriate by changing a portion 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 points in common with the contents already described will be omitted.

(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 (the store terminal 30, 40 or the 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.

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

In addition, when the inter-terminal communication unit 202 of the server device 20 receives multiple user IDs from terminal devices with the same terminal ID, it associates these multiple user IDs with the same terminal ID and registers them in the reservation information.

Note that there is no particular restriction on the ordering method for multiple users using the same terminal device. 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 that allows the user to select which of the multiple users to make the order destination (order originator). Also, for example, when a user ID other than that of multiple users using the same terminal device is selected as the order destination by any of the multiple users using the same terminal device, the GUI providing unit 204 may display a screen that allows the user to select which of the multiple users using the same terminal device to make the order originator.

In addition, when the accounting processing unit 206 of the server device 20 receives an operation of the accounting button 123, for example, it displays an accounting screen (not shown) on the display unit 36 of the terminal device operated by each user, which allows the user to confirm that there are multiple users in the same store 60 or remote restaurant 61. This accounting screen may be, for example, the accounting screen 170 described above, where multiple users in the same store 60 or remote restaurant 61 are grouped together by surrounding them with a dashed line, etc.

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

(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) displays a screen or a GUI on the display unit 36 in response to a control instruction from the server device 20, but the terminal device may be configured to perform some of this control itself.

In other words, the reservation reception unit 201 of the server device 20 may cause the output control unit 302 of the mutually 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 an order history display unit.

The display control unit displays a main screen 110 on the display unit 36 of the terminal device, which displays images captured by the imaging devices corresponding to each terminal device and received from the server device 20.

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 that are communicatively connected via the inter-terminal communication unit 202 of the server device 20.

The order reception unit receives an order for 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. The server device 20 notifies the store 60 that provides the product or the delivery store 62 of the order information received from each terminal device.

The order history display unit displays the order information received by the order reception unit on the main screen 110 in association with the delivery address of the ordered product.

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, which manages the location of the access source and the terminal device in association with the user who operates the terminal device. The output control unit 302 of the terminal device functions as a display control unit that displays a main screen 110 in which images captured by the imaging device 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 representing 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 in a communicable manner, an order receiving unit that receives order information of products and the delivery destination of the products from one of the terminal devices to which the menu information is provided and notifies the server device 20 of the received order information, and an order history display unit that displays the order information received by the order receiving unit in association with the delivery destination of the ordered product in the main screen 110 displayed on the display unit 36. Therefore, because the ordered menu items are displayed in association with each user, each user can check the order history without interrupting the conversation during the remote drinking party. This can improve the convenience of the remote food and drink provision service.

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 an installable or executable format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk).

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 downloading 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.

Although an 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.

10 Remote food and drink supply system 20 Server device 30, 40 Store terminal (terminal device)
41 User terminal (terminal device)
50 Order receiving terminal 60 Store 61 Remote restaurant 62 Delivery store 110 Main screen 112, 113, 114 Sub-screen 132 Menu sub-screen 142 Order icon (order information)
151, 161 Order history icon 152, 162 Order status icon 201 Reservation reception section (management section)
202 Inter-terminal communication unit (management unit, communication control unit)
203 Screen display control unit (display control unit, order history display unit)
204 GUI providing unit (menu providing unit)
205 Order reception unit (order reception unit, order information selection unit)
206 Accounting processing unit 207 Delivery status acquisition unit 301 Communication control unit 302 Output control unit 303 Operation reception unit 501 Communication control unit 502 Output control unit 503 Operation reception unit

JP 2015-176335 A

Claims (6)

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 order history display unit that displays the order information received by the order receiving unit on the main screen in association with a delivery address of the ordered product;
A server device comprising: the order history display unit displays the order information in the image corresponding to the delivery destination of the order information.
The server device according to claim 1 . an order information selection unit that accepts a selection operation of the order information displayed by the order history display unit and reorders the same product;
3. The server device according to claim 1 or 2. the order history display unit displays the order information in a form associated with the status of the ordered product until delivery;
The server device according to any one of claims 1 to 3. 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 the 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 step of receiving 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 notifying the server device of the received order;
an output control unit that controls the display unit to display an order history on the main screen of the display unit, the order information received by the order reception unit being associated with a delivery address of the ordered product;
A terminal device comprising: 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 order history display unit that displays the order information received by the order receiving unit on the main screen in association with a delivery address of the ordered product;
A program to make it function as such.

Images