JP7650163B2 - Server device and program - Google Patents

Description

An embodiment of the present invention relates to a server 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 using web conferencing systems. For example, users can visit different stores and hold a web conference using terminals installed in the stores, allowing them to communicate with users in other stores while eating and drinking food and beverages (products) provided by the stores.

Meanwhile, in the past, technology has been proposed for ordering systems in brick-and-mortar stores that calculates the amount to be paid per person based on the number of people in a customer group (for example, Patent Document 1). In this conventional technology, in order to calculate the amount to be paid per person based on the actual eating and drinking behavior, the order history of the group is identified, the products included in the order history are classified into categories, and the number of customers who are said to have eaten or drunk products from each category is identified.

However, conventional technology is based on the assumption that orders are placed within the store where users gather to eat and drink, and does not anticipate the above-mentioned remote drinking party format in which users participate in multiple locations, such as a store or their home, or the continued remote drinking party format in which food and drink are ordered from outside the store or home. As a result, there is room for improvement in terms of convenience.

The problem that this invention aims to solve is to provide a server device and program that can simultaneously provide a form of communication in which people can participate from multiple locations and order food and drink.

The server device of the embodiment comprises a management means for accepting access from a plurality of terminals, and for managing the terminal from which the access originates , the user operating the terminal, the user's participation location, and the end time in association with each other, a communication control means for connecting the terminals of users belonging to the same group so that they can communicate with each other, a provision means for providing menu information including information on products that can be delivered to the participation location so that it can be viewed by the terminals connected to each other so that they can communicate with each other by the communication control means, and an order acceptance means for accepting an order for a product from any of the terminals to which the menu information has been provided, and notifying a store that handles the product of information regarding the ordered product, wherein the provision means displays the menu information on a display device of the terminal, overlapping it so as to cover a portion of a main display screen, and displays an captured image sent from the terminal of a user belonging to the same group on the main display screen, and when there is no operation to select the captured image, the menu information includes information on products that can be delivered to the participation location of the user of the terminal from which the access originates, and when there is an operation to select the captured image, the menu information includes information on products that can be delivered to the participation location of the user of the terminal from which the selected captured image was sent .

FIG. 1 is a diagram illustrating an example of the configuration of a remote food and drink providing system according to an embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a seat terminal according to the embodiment. FIG. 3 is a diagram illustrating an example of a hardware configuration of the order receiving terminal according to the embodiment. FIG. 4 is a diagram illustrating an example of a hardware configuration of a server device according to the embodiment. FIG. 5 is a diagram illustrating an example of a data configuration of a remote restaurant management table according to the embodiment. FIG. 6 is a diagram illustrating an example of a data configuration of a delivery store management table according to the embodiment. FIG. 7 is a diagram illustrating an example of a data configuration of a menu management table according to the embodiment. FIG. 8 is a diagram illustrating an example of a data configuration of a user management table according to the embodiment. FIG. 9 is a diagram illustrating an example of a data configuration of a reservation management table according to the embodiment. FIG. 10 is a diagram illustrating an example of a data configuration of an order management table according to the embodiment. FIG. 11 is a diagram illustrating an example of a data configuration of a delivery status management table according to the embodiment. FIG. 12 is a diagram showing an example of the functional configuration of the server device, the seat terminal or user terminal, and the order receiving terminal according to the embodiment. FIG. 13 is a diagram illustrating an example of data transmission and reception between devices according to the embodiment. FIG. 14 is a diagram illustrating an example of a screen displayed on a desk terminal or a user terminal according to the embodiment. FIG. 15 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 16 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 17 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 18 is an enlarged view of an example of a portion of a screen displayed on a desk terminal or a user terminal according to the embodiment. FIG. 19 is a diagram for explaining the determination of whether an order is possible or not in this embodiment. FIG. 20 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 21 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 22 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 23 is a diagram showing another example of a screen displayed on the desk terminal or the user terminal according to the embodiment. FIG. 24 is a flowchart illustrating an example of a login process executed by the server device according to the embodiment. FIG. 25 is a flowchart illustrating an example of a menu providing process executed by the server device of the embodiment. FIG. 26 is a flowchart illustrating an example of an order process executed by the server device according to the embodiment. FIG. 27 is a flowchart illustrating an example of a transaction process 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.

Fig. 1 is a diagram showing an example of the configuration of a remote food and drink provision system 1 according to an embodiment. The remote food and drink provision system 1 includes a seat terminal 10, a user terminal 20, a server device 30, an order receiving terminal 40, an external service server 50, a driver terminal 60, a kitchen terminal 70, etc. The server device 30 is communicatively connected to each of the other terminals (the seat terminal 10, the user terminal 20, the order receiving terminal 40, the external service server 50, the driver terminal 60, the kitchen terminal 70, etc.) via a network N such as the Internet or a mobile phone line network. In addition, the external service server 50 is communicatively connected to the order receiving terminal 40, the driver terminal 60, and the server device 30 via the network N.

The seat terminal 10 is a terminal device provided in each of the remote restaurants 91. The remote restaurants 91 are stores that provide a place to eat food and drink that has been prepared outside and delivered. By their very nature, the remote restaurants 91 do not need to have kitchens. In this embodiment, the remote restaurants 91 are capable of providing drink menus within the store. Each of the remote restaurants 91 may be affiliated with a chain store or the like, or each may be an independent store.

The seat terminal 10 is, for example, an ordering terminal for self-ordering provided at each seat in the remote restaurant 91, and is realized by a tablet terminal or the like. Note that there is no particular limit to the number of seat terminals 10 provided in the remote restaurant 91, and there may be more than one.

Each of the remote restaurants 91 also includes a kitchen terminal 70 for displaying order information notified from the server device 30. Each of the remote restaurants 91 also includes a store server (not shown) that manages the seat terminals 10 and the kitchen terminals 70.

The user terminal 20 is a terminal device used by a user who uses the remote food and beverage provision system 1. The user terminal 20 can be realized by a portable terminal device such as a smartphone or a tablet terminal. Note that in this embodiment, for the sake of convenience, an example will be described in which the user terminal 20 is connected to the remote food and beverage provision system 1 from the user's home 92, but this is not limited to this. For example, a user who uses the user terminal 20 may use the remote food and beverage provision system 1 at a location other than the user's home 92.

The server device 30 is an example of a server device in this embodiment. The server device 30 is realized by, for example, an information processing device such as a workstation. Note that, in this embodiment, the server device 30 is described as a single device, but this is not limited thereto. For example, the server device 30 may be configured to operate functions in a distributed manner across multiple server devices.

The server device 30 cooperates with the other terminals included in the remote food and drink provision system 1 to provide a remote food and drink provision service to users using the seat terminal 10 and the user terminal 20. More specifically, the server device 30 controls communication between the seat terminal 10 and the user terminal 20 provided in each of the multiple remote restaurants 91 to provide a service (remote food and drink provision service) that mediates conversations and shares screens between users in different locations. Hereinafter, the remote food and drink provision service using the seat terminal 10, or providing (receiving) the remote food and drink provision service using the seat terminal 10, is also referred to as a "remote drinking party."

The server device 30 also accepts orders for delivery items from the seat terminal 10 and the user terminal 20 and manages the process until delivery is completed.

The order receiving terminal 40 is a terminal device provided in each of the delivery stores 93. The order receiving terminal 40 is realized, for example, by a tablet terminal. The delivery store 93 may be a store that has both a kitchen where cooking staff cooks and a dining area where customers eat and drink, or it may be a take-out or made-to-order store that has only a kitchen and no dining area. The order receiving terminal 40 notifies the cooking staff in the kitchen of information related to product orders.

The external service server 50 is, for example, a server device provided by a business operator that provides an existing delivery service, and provides the server device 30 with information (menus) of products provided by each delivery store 93 and the operating status of each driver 94.

The driver terminal 60 is a terminal device carried by each driver 94. The driver terminal 60 can be realized as a portable terminal device such as a smartphone or tablet terminal.

The kitchen terminal 70 is a terminal device provided in the back yard of each remote restaurant 91. The kitchen terminal 70 is realized, for example, by a tablet terminal or the like. The kitchen terminal 70 notifies the wait staff of information related to the products ordered by users in the remote restaurant 91. The contents of the notification include, for example, the scheduled delivery time, images of the products, the shape and size of suitable tableware, and information for identifying the seat of the orderer.

Next, we will explain the configuration of the main devices in the remote food and beverage provision system 1.

Figure 2 is a diagram showing an example of the hardware configuration of the seat terminal 10 according to the embodiment. The seat terminal 10 includes a computer configuration including a CPU (Central Processing Circuit) 11, a ROM (Read Only Memory) 12, and a RAM (Random Access Memory) 13.

The CPU 11 is an example of a processor, and controls each part of the seat terminal 10. The ROM 12 stores various programs. The RAM 13 is a workspace in which programs and various data are expanded.

The seat terminal 10 also includes a communication unit 14, a memory unit 15, a display unit 16, an operation unit 17, an imaging unit 18, and an audio input/output unit 19.

The communication unit 14 is a communication interface that can be connected to the network N. The communication unit 14 communicates with external devices such as the server device 30 via the network N. The communication unit 14 also communicates with the store server and other seat terminals 10 within the store.

The memory unit 15 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 15 stores programs that the CPU 11 can execute and various setting information. For example, the memory unit 15 stores programs (client programs) prepared for remote drinking parties and content related to the display of a GUI (Graphical User Interface). The CPU 11 executes various processes by operating according to the programs stored in the ROM 12 or the memory unit 15 and deployed in the RAM 13.

The display unit 16 is a display device such as an LCD (Liquid Crystal Display), and displays various information and screens according to the control of the CPU 11. The operation unit 17 has various operation keys, and outputs operation contents according to user operations to the CPU 11. The operation unit 17 may be a touch panel provided on the surface of the display unit 16.

The imaging unit 18 is an imaging device equipped with an imaging element such as a CCD (Charge Coupled Device). The imaging unit 18, for example, captures an image of a user operating the seat terminal 10 to obtain image data (still images, video) of the user, and outputs the obtained image data to the CPU 11.

The audio input/output unit 19 includes an audio input device such as a microphone, and an audio output device such as a speaker. The audio input/output unit 19 acquires user audio data and outputs the acquired audio data to the CPU 11. The audio input/output unit 19 also outputs the audio data input from the CPU 11 as audio.

The hardware configuration of the seat terminal 10 is not limited to the configuration shown in FIG. 2. The following description will be given assuming that the user terminal 20 has the same hardware configuration as the seat terminal 10.

Figure 3 is a diagram showing an example of the hardware configuration of the order receiving terminal 40 according to the embodiment. The order receiving terminal 40 has a computer configuration including a CPU 41, a ROM 42, and a RAM 43.

The CPU 41 is an example of a processor, and controls each part of the order receiving terminal 40. The ROM 42 stores various programs. The RAM 43 is a workspace in which programs and various data are expanded.

The order receiving terminal 40 also includes a communication unit 44, a memory unit 45, a display unit 46, and an operation unit 47.

The communication unit 44 is a communication interface that can be connected to the network N. The communication unit 44 communicates with external devices such as the server device 30 and the external service server 50 via the network N.

The memory unit 45 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 45 stores programs that the CPU 41 can execute and various setting information. For example, the memory unit 45 stores content related to GUI display. The CPU 41 executes various processes by operating according to programs stored in the ROM 42 or the memory unit 45 and deployed in the RAM 43.

The display unit 46 is a display device such as an LCD, and displays various information and screens according to the control of the CPU 41. The operation unit 47 has various operation keys, and outputs operation contents according to user operations to the CPU 41. The operation unit 47 may be a touch panel provided on the surface of the display unit 46.

The hardware configuration of the order receiving terminal 40 is not limited to the configuration shown in FIG. 3. The driver terminal 60 and the kitchen terminal 70 will be described as having the same hardware configuration as the order receiving terminal 40.

FIG. 4 is a diagram showing an example of the hardware configuration of the server device 30 according to the embodiment. As shown in FIG. 4, the server device 30 includes a computer configuration including a CPU 31, a ROM 32, and a RAM 33.

The CPU 31 is an example of a processor, and controls each part of the server device 30. The ROM 32 stores various programs. The RAM 33 is a workspace in which programs and various data are deployed.

The server device 30 also includes a communication unit 34 and a storage unit 35. 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 seat terminal 10 and the user terminal 20 via the network N.

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 (server programs) prepared for remote drinking parties and content related to GUI display. The CPU 31 executes various processes by operating according to the programs stored in the ROM 32 or the memory unit 35 and deployed in the RAM 33.

The hardware configuration of the server device 30 is not limited to the configuration shown in FIG. 4. In addition, the following description will be given assuming that the external service server 50 has the same hardware configuration as the server device 30.

The memory unit 35 of the server device 30 also stores a remote restaurant management table 351, a delivery store management table 352, a delivery menu management table 353, a user management table 354, a reservation management table 355, an order management table 356, and a delivery status management table 357.

Figure 5 is a diagram showing an example of the data configuration of the remote restaurant management table 351 according to the embodiment. The remote restaurant management table 351 stores information (remote restaurant information) about the remote restaurant 91 corresponding to the ID (remote restaurant ID) of each remote restaurant 91 in association with the ID of the remote restaurant 91.

The remote restaurant ID is identification information for identifying each remote restaurant 91. The remote restaurant information includes items such as the name (remote restaurant name), address, contact information, and image (remote restaurant image) of the remote restaurant 91. The remote restaurant name is the trade name or branch name of the remote restaurant 91. The address refers to the address indicating the location of the remote restaurant 91. The contact information refers to address information such as the address or IP address of the remote restaurant 91. The remote restaurant image is image information such as an icon or logo mark representing the remote restaurant 91 corresponding to the remote restaurant ID. Note that the data configuration of the remote restaurant management table 351 is not limited to the example shown in FIG. 5.

Figure 6 is a diagram showing an example of the data configuration of the delivery store management table 352 according to the embodiment. The delivery store management table 352 stores information (delivery store information) about the delivery store 93 corresponding to the delivery store ID in association with the ID of each delivery store 93 (delivery store ID).

The delivery store ID is identification information for identifying each delivery store 93. The delivery store information includes items such as the name (delivery store name), address, contact information, and image (delivery store image) of the delivery store 93. The delivery store name is the trade name or branch name of the delivery store 93. The address refers to the address indicating the location of the delivery store 93. The contact information refers to address information such as the address or IP address of the delivery store 93. The delivery store image is image information such as an icon or logo that represents the delivery store 93 corresponding to the delivery store ID. Note that the data configuration of the delivery store management table 352 is not limited to the example shown in FIG. 6.

Figure 7 is a diagram showing an example of the data configuration of the delivery menu management table 353 according to an embodiment. The delivery menu management table 353 stores menu information about each product (menu) that can be provided (cooked) by the delivery store 93 corresponding to the delivery store ID, in association with the delivery store ID of each delivery store 93. The server device 30 stores the menu information of each delivery store 93 obtained via the external service server 50, for example, in the delivery menu management table 353.

Menu information includes, for example, the product (menu) product ID, product name, general name, price, product image, description, cooking time, and serving time.

The product ID is identification information for identifying the product sold at each delivery store 93. 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 delivery store A, which is one of the delivery stores 93, is "Large A Beer" and "Medium A Beer", and the "beer" sold at delivery store B, which is another delivery store 93, is "B Beer". In this case, the product ID and product name indicating "Large A Beer" and "Medium A Beer" are registered in association with the delivery store ID of delivery 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 delivery store ID of delivery 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 delivery store ID, etc.

The cooking time is the estimated time required for cooking at the delivery store 93. The serving time is the estimated time required for serving at the remote restaurant 91.

The data structure of the delivery menu management table 353 is not limited to the example shown in FIG. 7. The server device 30 may also update the menu information in the delivery menu management table 353 at a predetermined timing by periodically or at any time acquiring the menu information from the external service server 50.

FIG. 8 is a diagram showing an example of the data configuration of the user management table 354 according to the embodiment. The user management table 354 stores user information about the user corresponding to the 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, user name, address, contact information, and payment information. User name is information indicating the name of the user corresponding to the user ID. Address is information indicating the address or whereabouts of the user corresponding to the user ID. 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 20 possessed by the user is registered in the contact information. Payment information is information related to electronic payments such as credit card payment and electronic money payment. 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 354 is not limited to the example shown in FIG. 6. For example, the user management table 354 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.

Here, the server device 30 may store an icon image of the user in association with the user ID of the user managed in the user management table 354. The icon image is displayed alongside various information on the screen displayed on each terminal during the remote drinking party, thereby modifying the information (i.e., indicating that the user of the icon image is related to the information). The icon image is stored, for example, in the user management table 354. In the following, in this embodiment, it is assumed that the user management table 354 stores the icon image.

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

Here, the reservation ID is identification information for identifying a reservation for a remote drinking party. The server device 30 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 20 or the like.

The reservation information includes, for example, information such as the reservation date and time, user ID, participation location (remote restaurant ID or home), 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 the 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.

When a user joins a remote drinking party from a remote restaurant 91, the identification information of the seat terminal 10 used at the remote restaurant 91 is registered as the terminal ID. In this case, the date and time when the user started using the seat terminal 10 corresponding to the terminal ID is registered as the login date and time. On the other hand, when a user joins a remote drinking party from home, the identification information of the user terminal 20 is registered as the terminal ID. In this case, the date and time when the user logged in to the remote food and beverage providing system 1 with the user terminal 20 is registered as the login date and time.

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. Also, 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 logs into the remote food and beverage provision system 1 from the participation location.

If the location of participation is not the user's home, the remote restaurant ID of the remote restaurant 91 may be registered when the user visits the remote restaurant 91 on the day of the remote drinking party. Alternatively, the user and the remote restaurant 91 that the user will visit may be registered in association with each other. For example, the remote restaurant 91 may be registered in advance in association with the user ID registered in the reservation information of the reservation ID. If the location of participation is the user's home, information indicating that the location is the user's home is registered. The information indicating that the location is the user's home is, for example, a value that uses the same code system as the remote restaurant ID and does not overlap with all remote restaurant IDs.

The data configuration of the reservation management table 355 is not limited to the example in FIG. 9. For example, the reservation management table 355 may store information indicating the name and subject of the remote drinking party in association with a reservation ID. The reservation management table 355 may also store information indicating the host or organizer of the remote drinking party in association with a user ID. In the following, in this embodiment, it is assumed that the reservation management table 355 stores information indicating the host in association with a user ID.

FIG. 10 is a diagram illustrating an example of the data configuration of the order management table 356 according to an embodiment. The order management table 356 stores order history information about products ordered at a remote drinking party corresponding to a reservation ID, in association with the reservation ID.

Order history information includes, for example, order ID, ordering user ID, ordering user ID, participating location (remote restaurant ID or home), product ID, quantity, and payment flag.

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

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 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 a product that another user will consume, different user IDs are registered as the ordering user ID and the order recipient user ID.

The participating location is registered with the remote restaurant ID of the order destination or information indicating that it is the user's home (as described above). In other words, if the user with the order destination user ID is present in the remote restaurant 91, the participating location is registered with the remote restaurant ID of the remote restaurant 91 in which the user with the order destination user ID is present. Also, if the user with the order destination user ID is present at home, information indicating that it is the user's home is registered as the participating location.

The product ID of the product that is the subject of the order is registered in the product ID field. The quantity of the product that is the subject of the order is registered in the quantity field.

In addition, the paid flag registers flag information indicating whether or not the product that was the subject of the order has been paid for. In this embodiment, as described below, when a user wants to give a product as a gift to another user (hereinafter, this ordering method will be referred to as a "treat reorder"), the payment for the product is made 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 pays 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. Figure 10 shows a case where unpaid is flagged as "0" and paid is flagged as "1".

The data configuration of the order management table 356 is not limited to the example shown in FIG. 10. For example, the order management table 356 may store information indicating the date and time of an order.

Figure 11 is a diagram showing an example of the data configuration of the delivery status management table 357 according to the embodiment. The delivery status management table 357 stores delivery status information about products ordered at a remote drinking party corresponding to a delivery order ID, in association with the delivery order ID.

Here, the delivery order ID is identification information for identifying each delivery order. The server device 30 issues a unique delivery order ID (e.g., an ascending number) each time an order ID is issued for an order received from a user (seat terminal 10 or user terminal 20).

The delivery status information includes, for example, the order ID, ordering user ID, order recipient user ID, participating location (remote restaurant ID or home), product ID, quantity, delivery status flag, driver contact information, etc. The order ID, ordering user ID, order recipient user ID, participating location, product ID, and quantity are transcribed to be the same as those in the order management table 356.

The delivery status flag registers flag information indicating whether the delivery status of the ordered item has been delivered or not. Figure 11 shows a case where the flag is set to "0" for undelivered and "1" for delivered.

The driver contact information is information for communicating with the driver terminal 60, and may be, for example, ID information in a system that provides an application specifically for drivers, or an email address or telephone number. For each order, the server device 30 requests the external service server 50 to assign a driver 94, receives contact information for the assigned driver 94 from the external service server 50, and stores the provided contact information in the delivery status management table 357. The server device 30 also obtains information for understanding the delivery status by communicating with the driver terminal 60 using the driver contact information.

The data configuration of the delivery status management table 357 is not limited to the example shown in FIG. 11. For example, the delivery status management table 357 may store information indicating the date and time of the order.

Next, the functional configuration of the server device 30, the seat terminal 10 or the user terminal 20, and the order receiving terminal 40 will be described with reference to FIG. 12. FIG. 12 is a diagram showing an example of the functional configuration of the server device 30, the seat terminal 10 or the user terminal 20, and the order receiving terminal 40 according to the embodiment.

First, the seat terminal 10 (user terminal 20) has a communication control unit 21, an output control unit 22, and an operation reception unit 23 as functional units.

Some or all of the functional units of the seat terminal 10 may be software configurations realized by cooperation between the processor (e.g., CPU 11) of the seat terminal 10 and a program stored in a memory (e.g., ROM 12, storage unit 15). Also, some or all of the functional units of the seat terminal 10 may be hardware configurations realized by a dedicated circuit or the like mounted on the seat terminal 10.

The communication control unit 21 of the seat terminal 10 controls the communication unit 14 to exchange various information (data) with the server device 30 and the store server. For example, the communication control unit 21 transmits image data and audio data acquired by the imaging unit 18 and audio input/output unit 19 to the server device 30. Also, for example, the communication control unit 21 receives image data and audio data transmitted from other seat terminals 10 and user terminals 20 via the server device 30.

The output control unit 22 controls the display unit 16 and the audio input/output unit 19 to output various information (data). For example, the output control unit 22 causes the display unit 16 to display image data acquired by the imaging unit 18 and image data transmitted from other seat terminals 10 or user terminals 20. The output control unit 22 also works in cooperation with the server device 30 to display various GUIs on the display unit 16. The output control unit 22 also causes the audio input/output unit 19 to output audio data acquired by the audio input/output unit 19 and audio data transmitted from other seat terminals 10 or user terminals 20.

The operation reception unit 23 receives the user's operation content input via the operation unit 17. For example, the operation reception unit 23 receives an operation on the GUI displayed on the display unit 16. In this embodiment, the seat terminal 10 and the user terminal 20 function as an input/output interface of the server device 30.

Next, the order receiving terminal 40 has a communication control unit 411, an output control unit 412, and an operation reception unit 413 as functional units.

Some or all of the functional units of the order receiving terminal 40 may be software configurations realized by cooperation between the processor (e.g., CPU 41) of the order receiving terminal 40 and a program stored in a memory (e.g., ROM 42, storage unit 45). Also, some or all of the functional units of the order receiving terminal 40 may be hardware configurations realized by a dedicated circuit or the like mounted on the order receiving terminal 40.

The communication control unit 411 of the order receiving terminal 40 controls the communication unit 44 to exchange various information (data) with the server device 30 and the external service server 50. For example, the communication control unit 411 receives order information sent to the seat terminal 10 and the user terminal 20 via the server device 30.

The output control unit 412 outputs various information (data) by controlling the display unit 46. For example, the output control unit 22 causes the display unit 46 to display order information received from the server device 30. The output control unit 412 also cooperates with the server device 30 to cause the display unit 46 to display various GUIs.

The operation reception unit 413 receives the operation content of the cooking staff input via the operation unit 47. For example, the operation reception unit 413 receives an operation on the GUI displayed on the display unit 46.

The server device 30 has a reservation reception unit 311, a terminal-to-terminal communication unit 312, a GUI provision unit 313, an order reception unit 314, and an accounting processing unit 315 as functional units.

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

The reservation reception unit 311 receives reservations for remote drinking parties and registers the details of the received reservations in the reservation management table 355. 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 restaurant to be used may be published on the network N, and reservations may be accepted through the website. In this case, the user who will be the host or organizer (hereinafter also referred to as the organizer) uses the user terminal 20 to access the website and make 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 ID of the remote restaurant 91 to be used by the user (remote restaurant ID), etc. When the reservation acceptance unit 311 accepts a new reservation, it issues a reservation ID and registers it in the reservation management table 355 together with the input information. In addition, the reservation acceptance unit 311 notifies the user terminal 20 of the user of the issued reservation ID. The organizer then notifies the user IDs of the other users who will be participating in the remote drinking party. Note that when making a new reservation, the user ID of a user other than the organizer may be entered.

Meanwhile, the other user who has been notified of the reservation ID uses his/her own user terminal 20 to access the above website specifying the reservation ID. When the reservation reception unit 311 accepts that an access specifying a reservation ID has been made, it reads the reservation information (date and time of the event, etc.) corresponding to that reservation ID from the reservation management table 355 and provides it visibly to the user terminal 20 from which the access originated. The other user then makes a reservation (additional reservation) for a remote drinking party by inputting his/her own user ID and the ID (remote restaurant ID) of the remote restaurant 91 that he/she will be using. When the reservation reception unit 311 accepts the additional reservation, it additionally registers the items of the additional reservation to the reservation information of the reservation ID that was previously input.

The reservation reception unit 311 may compare the address stored in the user information with the address stored in the remote restaurant information of each remote restaurant 91, and present to the user remote restaurants 91 that are within a predetermined range (e.g., within 3 km) of the user's address as candidates for use.

By performing the above process (reservation process), the reservation reception unit 311 stores a pair of the user ID and the remote restaurant ID used by each user participating in the same remote drinking party in the reservation management table 355 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 additionally register them, 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 20 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 users whose user IDs have been registered. For example, the user terminal 20 may display the two-dimensional code information on the day of the reservation, and the seat terminal 10 may read the displayed two-dimensional code information to execute the login process.

The inter-terminal communication unit 312 functions as an example of a management means together with the reservation reception unit 311. The inter-terminal communication unit 312 receives access from the seat terminal 10 of the remote restaurant 91, and manages the remote restaurant 91 (remote restaurant ID) and seat terminal 10 (terminal ID) from which the access originates, in association with the user (user ID) operating the seat terminal 10. The inter-terminal communication unit 312 also receives access from a user terminal 20, and manages the contact information (identification information such as a telephone number or terminal ID) of the access source user terminal 20, in association with the user (user ID) operating the user terminal 20.

The inter-terminal communication unit 312 is an example of a communication control means. The inter-terminal communication unit 312 connects the seat terminals 10 and the user terminals 20 of users associated with the same reservation ID, that is, users who belong to the same group, so that they can communicate with each other.

Specifically, when the inter-terminal communication unit 312 receives access from a seat terminal 10 specifying participation information such as a reservation ID and a user ID, it identifies reservation information corresponding to the specified reservation ID from the reservation management table 355. The inter-terminal communication unit 312 executes a login process to determine whether the specified user ID is included in the identified reservation information. If the specified user ID is included in the reservation information, the inter-terminal communication unit 312 additionally registers the terminal ID of the seat terminal 10 from which the access originated and the current date and time (login date and time) in association with the user ID to the reservation information.

Similarly, when a user participates using a user terminal 20, when the inter-terminal communication unit 312 receives access from the user terminal 20 specifying participation information such as a reservation ID and a user ID, it identifies the reservation information corresponding to the specified reservation ID from the reservation management table 355. The inter-terminal communication unit 312 executes a login process to determine whether the specified user ID is included in the identified reservation information. When the specified user ID is included in the reservation information, the inter-terminal communication unit 312 additionally registers the contact information (identification information such as a telephone number or terminal ID) of the accessing user terminal 20 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 312 registers the terminal ID and the login date and time in the reservation information, it performs control to connect the seat terminals 10 (or user terminals 20) with the terminal IDs (or contact information) registered in the reservation information so that they can communicate with each other. This allows data sharing between the seat terminals 10 and user terminals 20 associated with the same reservation ID, so that users belonging to the same group can converse with other users while looking at images (face images) captured by each of the seat terminals 10.

The inter-terminal communication unit 312 may be configured to register the terminal ID of the seat terminal 10 and the remote restaurant ID of the remote restaurant 91 to which the seat terminal 10 belongs in the reservation information when the seat terminal 10 accesses the inter-terminal communication unit 312.

Similarly, when accessed from a user terminal 20, the inter-terminal communication unit 312 may register the contact information of the user terminal 20 (identification information such as a telephone number or terminal ID) and the participation location of the user who possesses the user terminal 20 (e.g., information indicating that the location is the user's home) in the reservation information.

In addition, the inter-terminal communication unit 312 may be configured to deny access or to add the user ID to the reservation information if the user ID received from the seat terminal 10 (or the user terminal 20) is not included in the reservation information for the corresponding reservation ID.

The GUI providing unit 313 is an example of a providing means. The GUI providing unit 313 provides various GUIs to the seat terminal 10 and the user terminal 20. Specifically, the GUI providing unit 313 provides a screen including menu information indicating products that can be delivered to the participating location (remote restaurant 91 or user home 92) of each terminal (seat terminal 10 and user terminal 20). In addition, on this menu information screen, the GUI providing unit 313 provides the menu information of each member to be mutually viewable between terminals of the same group that are communicatively connected via the inter-terminal communication unit 312.

The GUI providing unit 313 also provides each of the seat terminal 10 and the user terminal 20 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 313 will be described later.

The order receiving unit 314 is an example of an order receiving means. The order receiving unit 314 receives an order for a product from either the seat terminal 10 or the user terminal 20 to which the menu information has been provided, and notifies the order receiving terminal 40 of the delivery store 93 that provides the product of information related to the ordered product (order information).

In addition, each time an order for a product is received, the order receiving unit 314 identifies the user ID (ordering user ID) of the user of the seat terminal 10 or user terminal 20 that placed the order, and the user ID (order destination user ID) of the user to whom the ordered product will be provided. The order receiving unit 314 then registers information such as the identified user ID, the store ID of the order destination, and the product ID as order history information in the order management table 356, in association with the newly issued order ID under the reservation ID corresponding to the identified user ID.

The accounting processing unit 315 is an example of an accounting means. The accounting processing unit 315 executes accounting processing to pay the price of the product accepted by the order acceptance unit 314 to the delivery store 93 that provides the product. Specifically, the accounting processing unit 315 executes accounting processing to pay the price of the ordered product using the payment information stored in the user management table 354.

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 315 determines that the user's payment is complete when 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 20 or the store server.

In the remote food and drink provision system 1 configured as described above, each device included in the system (seat terminal 10, user terminal 20, server device 30, order receiving terminal 40, external service server 50, driver terminal 60, kitchen terminal 70) transmits and receives data as shown in FIG. 13. This allows the remote food and drink provision system 1 to function. FIG. 13 is a diagram showing an example of data transmission and reception between each device according to an embodiment. The example shown in FIG. 13 is simplified to help understand the overview of the system. It is assumed that reservations for the remote drinking party are made in advance.

First, the external service server 50 acquires information on the products provided by each delivery store 93 (menu information) from the order receiving terminal 40 of the store and stores it (step S501). The external service server 50 also accesses the driver terminal 60 of each driver 94 to acquire information on the operating status of each driver 94 (operation information) and stores it (step S502). These steps (steps S501, S502) are performed as needed.

The server device 30 accesses the external service server 50 to obtain menu information, and stores it in the delivery menu management table 353 of the storage unit 35 (step S301). This process is performed as needed.

When the seat terminal 10 and the user terminal 20 start using the remote food and drink provision service (i.e., when the remote drinking party starts), they perform a login operation on the server device 30 (step S101). In response to this, the server device 30 performs a predetermined process (described below) for the start of the remote drinking party (step S302).

The seat terminal 10 and the user terminal 20 order products by selecting from the displayed menu (step S102). When the server device 30 accepts an order, it first transmits information about the order to the order receiving terminal 40 (step S303). The order receiving terminal 40, which has received the order information, displays the information about the order on a screen for the cook at the delivery store 93 to see (step S401). The cook operates the order receiving terminal 40 to accept the order, and prepares the ordered products.

Next, the server device 30 requests the external service server 50 to assign a driver 94 (step S304). Upon receiving the assignment request, the external service server 50 selects a driver 94 that is suitable for the contents of the order (step S503) and transmits the contact information of the driver 94 to the server device 30 (step S504).

When the server device 30 receives the contact information of the driver 94 from the external service server 50, it contacts the contact information of the driver 94 and requests delivery of the ordered product (step S305). When the driver terminal 60 carried by the driver 94 receives the request from the server device 30 (step S601), it replies that the request has been accepted (step S602).

When the order receiving terminal 40 receives an operation indicating that the product is ready, it transmits a predetermined signal to the server device 30 (step S402). The server device 30, which receives this signal, notifies the terminal that placed the order (the seat terminal 10 or the user terminal 20) that cooking is complete (step S306).

If the ordering user's participating location is a remote restaurant 91, the server device 30 notifies the kitchen terminal 70 of the participating location, the remote restaurant 91, of information for serving the food (step S307). The information to be notified may include, for example, the scheduled delivery time, an image of the product, the shape and size of suitable tableware, and information for identifying the seat of the orderer. When the kitchen terminal 70 receives the information for serving the food from the server device 30, it notifies the received information to the food serving staff by displaying it on the screen or by voice (step S701).

Although not shown in FIG. 13, the driver terminal 60 reports the delivery status to the server device 30 as needed. The server device 30, which receives the report from the driver terminal 60, reports the delivery status to the terminal that placed the order (the seat terminal 10 or the user terminal 20) as needed.

The server device 30 executes various processes according to operations corresponding to the screens provided by the GUI providing unit 313 to the seat terminal 10 and the user terminal 20. Therefore, hereinafter, the operation of the server device 30 will be explained with reference to the screens (FIGS. 14 to 22, 23) displayed on the display unit 16 of the seat terminal 10 and the user terminal 20. It is assumed that the reservation for the remote drinking party has been made in advance.

First, the predetermined process (step S302 described above) when starting a remote drinking party will be described. When the inter-terminal communication unit 312 receives access from the seat terminal 10 or the user terminal 20 specifying a reservation ID and a user ID, it executes the login process described above to identify the reservation information. Note that when the participation location is a remote restaurant 91, the login process may involve the seat terminal 10's code reader (not shown) reading the two-dimensional code information displayed on the user terminal 20, acquiring the reservation ID and user ID associated with the two-dimensional code information, and identifying the reservation information. The inter-terminal communication unit 312 also registers the terminal ID of the seat terminal 10 from which the access originated and the login date and time in the identified reservation information.

Next, the inter-terminal communication unit 312 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 312 cooperates with the GUI provision unit 313 to cause the display unit 16 of the seat terminal 10 (or the user terminal 20 in the case of a user whose participation location is the user's home 92) 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 312 cooperates with the GUI provision unit 313 to cause the display unit 16 of the seat terminal 10 (or the user terminal 20 in the case of a user whose participating location is the user's home 92) to display a start screen (see FIG. 14) that allows the user to instruct the start of the remote drinking party.

FIG. 14 is a diagram showing an example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. FIG. 14 shows a display example of a start screen 100. As shown in FIG. 14, 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 312 receives an operation of the start button 101 from the seat terminal 10 or the user terminal 20, it establishes communication between the seat terminal 10 and the user terminal 20 of the terminal ID registered in the reservation information, and realizes a state in which data can be shared between the seat terminals 10 and the user terminals 20 of the same group.

In addition, when the GUI providing unit 313 receives an operation of the start button 101 from the seat terminal 10 or the user terminal 20, it causes the display unit 16 of the seat terminal 10 and the user terminal 20 to display a main screen 110 (see FIG. 15) for displaying data (image data) shared between the seat terminal 10 and the user terminal 20.

Figure 15 is a diagram showing another example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. Figure 15 shows an example of the display of the main screen 110. Here, the main screen 110 is an example of a main display screen.

As shown in FIG. 15, the main screen 110 has a title display field 111 and multiple sub-screens divided according to the number of participants in the remote drinking party. FIG. 15 shows an example in which the main screen 110 is divided into three sub-screens 112, 113, and 114 according to three users, User A to User C.

Each of the sub-screens 112, 113, and 114 is associated with the terminal ID of the terminal (seat terminal 10 or user terminal 20) operated by each user, the user ID of the user operating the terminal, the remote restaurant ID of the remote restaurant 91 to which the seat terminal 10 belongs, etc. Also, each of the sub-screens 112, 113, and 114 displays image data acquired (captured) by the terminal (seat terminal 10 or user terminal 20) of the corresponding terminal ID. Also, the server device 30 provides each of the seat terminal 10 and the user terminal 20 with audio data acquired by the seat terminal 10 and the user terminal 20, and the audio data is output from the audio input/output unit 19 by the output control unit 22.

As a result, the user of the seat terminal 10 or the user terminal 20 can watch the main screen 110 and talk to each participant of the remote drinking party while looking at each other's faces.

In addition, each of the sub-screens 112, 113, and 114 displays the participation location 115 and icon image 117 of the user whose user ID is associated with the sub-screen 112, 113, or 114. Specifically, the GUI providing unit 313 reads out the icon image corresponding to the user ID from the user management table 354. In addition, the GUI providing unit 313 reads out the participation location of each user from the reservation management table 355. Then, the GUI providing unit 313 displays the read-out icon image and participation location as the icon image 117 and participation location 115 superimposed on the sub-screens 112, 113, and 114.

The organizer label 116 is also displayed superimposed on one of the sub-screens 112, 113, and 114. Specifically, the GUI providing unit 313 reads out the user ID associated with the information indicating the organizer from the reservation management table 355. Then, the GUI providing unit 313 displays the organizer label 116 superimposed on the sub-screen 112 on which the user with the read user ID is displayed.

In FIG. 15, an example is shown in which the left sub-screen 112 displays "Mr. A" based on the user name, and the remote restaurant name of remote restaurant A used by user A as the participation location 115 for user A. The center sub-screen displays "Mr. B" based on the user name, and the remote restaurant name of remote restaurant B used by user B as the participation location 115 for user B. The right sub-screen displays "Mr. C" based on the user name, and "home" as the participation location 115 for user C.

As a result, the users of the seat terminal 10 and the user terminal 20 can easily check the icon images 117 of each user who participated in the remote drinking party and each user's participation location 115 by looking at the main screen 110. In addition, each participant can recognize the organizer by the organizer label 116.

The main screen 110 may be configured to display an image of someone other than the user operating the seat terminal 10 or user terminal 20.

The main screen 110 is provided with an order button 121 for instructing the display of menu information showing items that can be delivered to each participating location 115. When the GUI providing unit 313 accepts the operation of the order button 121 from the seat terminal 10 or the user terminal 20, it reads out the deliverable menu information from the delivery menu management table 353. Here, the initial state of the above-mentioned "deliverable menu information" shows the items that can be delivered to the participating location of the operator, i.e., the ordering user. Then, the GUI providing unit 313 displays a menu screen 130 (described later, FIG. 16) based on the read out menu information on the display unit 16 of the operating terminal (seat terminal 10 or user terminal 20).

After operating the order button 121, if an operation to select a sub-screen is performed, such as by touching the display area of one of the sub-screens 112, 113, or 114, the GUI providing unit 313 recognizes that the user displayed on the selected sub-screen has been specified as the delivery destination of the product. For example, if the order button 121 is operated on a seat terminal 10 used by user A and then sub-screen 114 displaying user C is selected, the GUI providing unit 313 recognizes that user A is about to order a product to be given as a gift to user C. In other words, in this case, the GUI providing unit 313 recognizes that in the subsequent operation, an order will be placed by user A and the order destination will be user C.

The GUI providing unit 313 then displays a menu screen 130 (described later, FIG. 16) corresponding to the order destination recognized as described above on the display unit 16 of the operating terminal (the seat terminal 10 or the user terminal 20). In other words, in the above example, menu information that can be delivered to the home of user C is displayed on the seat terminal 10 of user A. Of course, if no selection operation is performed on any of the sub-screens 112, 113, 114 after the operation of the order button 121, the GUI providing unit 313 recognizes that both the order originator and the order destination are the same as the operating source, and displays menu information showing products that can be delivered to the participating location of the ordering user.

An example of the flow of the process of extracting "menu information available for delivery" performed by the GUI providing unit 313 is as follows. When the GUI providing unit 313 accepts an operation, it first checks the participating location associated with the user ID of the user who is the order destination in the reservation management table 355, and temporarily stores this in the RAM 33 as the delivery location.

Next, the GUI providing unit 313 calculates the time required to travel from each delivery store 93 to the delivery location (travel time) from the address of each delivery store 93 stored in the delivery store management table 352 and the delivery location, and temporarily stores these in the RAM 33. Next, the GUI providing unit 313 obtains the cooking time and serving time of each product stored in the delivery menu management table 353, and temporarily stores these in the RAM 33. Next, the GUI providing unit 313 calculates the total time of the travel time, cooking time, and serving time. Then, the GUI providing unit 313 includes products whose time that has elapsed from the current time by the above total time is a time before a predetermined time before the end time of the remote drinking party (hereinafter referred to as the service completion time) in the "menu information indicating deliverable products". In addition, the GUI providing unit 313 recognizes the time that is backdated by the above total time from the above service completion time as the reception end time. The reception end time is the so-called last order time. Products that have passed the deadline for accepting orders will not be displayed in the menu because the time that the above total time has passed from the current time will exceed the time that the product will be delivered.

The above-mentioned "predetermined time" is, for example, the minimum time required to consume the product, such as 20 minutes, but may be determined at the discretion of the remote restaurant 91, and may be, for example, 5 minutes or 0 minutes. In the following, in this embodiment, the predetermined time is set to 20 minutes. In other words, if the end time of the remote drinking party is 10 p.m. as shown in FIG. 15, the GUI provision unit 313 includes in the menu information products that can be completed to the ordering party by 9:40 p.m.

This is how the "menu information available for delivery" is extracted. Note that the above procedure is just one example that prioritizes ease of understanding, and menu information can be extracted using a more efficient extraction method.

For example, in the above example, the travel time from the delivery store 93 to the delivery location is used to extract the deliverable menu information, but in practice, instead of the travel time, for example, the distance between the delivery store 93 and the delivery location may be used to extract the menu information. In this case, for example, in the first stage, delivery stores 93 whose distance from the delivery location is equal to or less than a first threshold are extracted. Next, in the second stage, from among the products handled by the delivery stores 93 extracted in the first stage, products whose total time of cooking time, serving time, and the above-mentioned "predetermined time" is equal to or less than a second threshold are extracted and included in the menu information. In this case, the second threshold is, for example, a value obtained by subtracting the time required to travel the distance of the first threshold from the time from the current time to the end time of the remote drinking party.

Figure 16 is a diagram showing another example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. Figure 16 shows an example of the display of a menu screen 130. The menu screen 130 is configured by overlapping a menu display area 131 that displays menu information so as to cover a portion of the main screen 110, which is the primary display screen.

As shown in FIG. 16, the GUI providing unit 313 displays the menu display area 131 on the menu screen 130, superimposed on the sub-screens 112, 113, and 114. The menu display area 131 displays menu information indicating products that can be delivered to the order destination.

The menu display area 131 includes one or more rectangular display columns 132 that display information about one product. In the illustrated menu display area 131, the GUI providing unit 313 arranges the multiple display columns 132 in a horizontal row in accordance with the arrangement direction of the sub-screens 112, 113, and 114. Furthermore, when the GUI providing unit 313 detects an operation of sliding a finger in accordance with the arrangement direction of the display columns 132 in the illustrated menu display area 131, it scrolls the display columns 132. Note that the GUI providing unit 313 also scrolls the display columns 132 when buttons 138 provided on both the left and right ends of the menu display area 131 are operated.

The GUI providing unit 313 includes a product name column 133, a price column 134, a store image column 135, a product image column 136, a delivery time column 137, etc. in the display column 132. The GUI providing unit 313 displays the product name, price, and product image obtained from the delivery menu management table 353 in each of the product name column 133, price column 134, and product image column 136. The GUI providing unit 313 also displays a delivery store image obtained from the delivery store management table 352 in the store image column 135. The delivery time column 137 is a column that indicates the time required until delivery, and the GUI providing unit 313 displays in this column the total time of the cooking time and serving time obtained from the delivery menu management table 353, and the above-mentioned travel time.

With a menu screen 130 having a menu display area 131 as shown in the example, a user can continue a conversation with other users while viewing and operating the menu screen 130.

Figure 17 is a diagram showing another example of a screen displayed on the seat terminal 10 or user terminal 20 of the embodiment. Figure 17 shows an example of a display when one or more products are selected on the menu screen 130 and before the order is sent. As shown in Figure 17, when one or more products are selected on the menu screen 130, the GUI providing unit 313 displays a pending order display area 141 superimposed on the sub-screens 112, 113, and 114. The pending order display area 141 includes a product display column 142 and an order confirmation button 144.

The product display field 142 has a product image field 143 that displays a product image of the product selected in the menu display area 131, and a store image field 135 that displays a store image of the delivery store 93 that provides the product displayed in the product image field 143.

The product display column 142 increases each time a product is selected in the menu display area 131. In the example shown in FIG. 17, the product display column 142 is displayed on the menu screen 130 below the menu display area 131 together with the menu display area 131. This makes it easy for the user to view the menu information and check the product selection status while continuing a conversation with the participants.

The example shown in FIG. 17 is a display example on user A's seat terminal 10, and the GUI providing unit 313 displays the icon image 117 of the ordering user in the product display area 142. This allows user A to easily distinguish between the product he or she has selected for his or her own consumption and the product to be given as a gift to user C.

The order confirmation button 144 accepts an operation to confirm an order for a product displayed in the product display field 142 included in the unconfirmed order display area 141 (step S102 above). When the GUI providing unit 313 detects that the order confirmation button 144 has been operated, it transmits the product displayed in the product display field 142 included in the unconfirmed order display area 141 to the order receiving terminal 40 of each delivery store 93 (step S303 above).

When the order confirmation button 144 is operated, the GUI provision unit 313 erases the unconfirmed order display area 141 and the menu display area 131, displays a simple dialogue for a predetermined period of time informing the user that the order has been accepted, and then returns the display to the main screen 110 (see FIG. 15).

Figure 18 is an enlarged view of an example of a portion of a screen displayed on the display unit 16 of the seat terminal 10 or the user terminal 20 of the embodiment. Figure 18 shows an example of the display state of the above-mentioned display field 132. When the following specific condition is met, the GUI providing unit 313 includes the acceptance end notice 139 in the display field 132. The above specific condition is, for example, "the time remaining until the end of order acceptance is 10 minutes or less." In other words, in this case, when the time remaining until the end of order acceptance is 10 minutes or less, the GUI providing unit 313 includes the acceptance end notice 139 in the display field 132 and notifies the user of information that allows the user to recognize the time remaining until the end of order acceptance (i.e., the remaining time during which the product can be ordered).

Figure 19 is a diagram for explaining the determination of whether an order can be placed in an embodiment. If the end time of a remote drinking party is, for example, 10 p.m., the GUI provision unit 313 subtracts a predetermined time of 20 minutes and recognizes the completion time of service as 9:40 p.m. Furthermore, the total time for a menu E product is 15 minutes, with 8 minutes of cooking time, 5 minutes of travel time, and 2 minutes of serving time, meaning that the time required from order confirmation to service is 15 minutes.

In this case, when displaying the menu display area 131 at 9:15 p.m., the GUI providing unit 313 includes the display column 132 for menu E in the menu display area 131 because there are 25 minutes remaining until the time of completion of provision. Also, at this point, for a product that takes 15 minutes from order confirmation to provision, there is 25 minutes remaining until the time of completion of provision, with a difference between the two being 10 minutes. In other words, there are 10 minutes remaining until the time of order acceptance is terminated, so a notice of acceptance termination 139 indicating this is included in the display column 132. At this point, the notice of acceptance termination 139 displays, for example, "10 minutes remaining until acceptance is terminated." Note that FIG. 18 shows an example of the display column 132 at 9:20 p.m., 5 minutes further ahead in the current time.

The remaining time shown in the reception end notice 139 may be a countdown display in one-minute intervals, for example, or a countdown display in finer time intervals. The reception end notice 139 may also be displayed in a color, shape, or movement that is more eye-catching than its surroundings.

Furthermore, the order acceptance deadline notice 139 may display, for example, the order acceptance deadline, instead of the remaining time until the order acceptance deadline, as information that allows the user to recognize the remaining time during which the product can be ordered.

In this way, when the acceptance end notice 139 is displayed, the user can know in advance that the product will soon no longer be displayed on the menu, which is highly convenient and preferable.

Fig. 20 is a diagram showing another example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. Fig. 20 shows an example of a confirmation screen 161 that the GUI providing unit 313 displays on the display unit 16 of the seat terminal 10 of user A, superimposed on the menu screen 130. As shown in Fig. 20, the confirmation screen 161 displays the user name of the ordering user (user C) and a message 145 for confirming with the ordering user (user A) that the product will be given as a gift to that user. The confirmation screen 161 also includes buttons 146 and 147 operated by the ordering user (user A). The "Yes" button 146 accepts an operation to instruct the user to place an order. The "No" button 147 accepts an operation to instruct the user to cancel the order.

The user who placed the order (user A) checks message 145, and if he or she determines that there is no problem, operates the "Yes" button 146. The user who placed the order (user A) checks message 145, and if he or she determines that the order will not be placed, operates the "No" button 147. When the "Yes" button 146 is operated, the server device 30 causes the user terminal 20 used by user C to display a notification screen 162 (see FIG. 21), which will be described next.

Fig. 21 is a diagram showing another example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. Fig. 21 shows an example of a notification screen 162 that the GUI providing unit 313 displays on the display unit 16 of the user terminal 20 of user C, superimposed on the menu screen 130. As shown in Fig. 21, the notification screen 162 displays a message 148 for confirming with the user name of the order destination user (user C) that the product will be presented by the ordering user (user A). The notification screen 162 also includes buttons 146, 147 operated by the order destination user (user C). The "Yes" button 146 accepts an operation to instruct the order to be placed. The "No" button 147 accepts an operation to instruct the order to be cancelled.

The user to whom the order is to be placed (user C) checks message 148, and if it is determined that there is no problem, it operates the "Yes" button 146. The user to whom the order is to be placed (user C) checks message 148, and if it is determined that there is a problem, it operates the "No" button 147. When the "Yes" button 146 is operated, the server device 30 transmits and receives data related to the payment to and from the seat terminal 10 used by user A.

22 is a diagram showing another example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. FIG. 22 is a display example on the seat terminal 10 of user A. As shown in this figure, for example, the main screen 110 displays an order history icon 151 showing information and status of products ordered by the user (here, user A) of the terminal (seat terminal 10 or user terminal 20) displaying the main screen 110, which has not yet been provided, on the sub-screens 112 and 114 of the order destination user of each product. The order history icon 151 has a product image column 143 and a store image column 135 showing product information. The order history icon 151 also has status icons 152 and 153 showing the status of the product. The status icons 152 and 153 may be text such as "delivery in progress" or "cooking in progress", or may be illustrations conveying the same meaning. This allows each user to easily know the status of the products they have ordered.

As shown in Figs. 15 to 17, the main screen 110 and the menu screen 130 have an order status button 122. When the order status button 122 is operated, the GUI providing unit 313 causes the display unit 16 of the terminal that received the operation (the seat terminal 10 or the user terminal 20) to display an order status screen (see Fig. 23) showing the status of the ordered product.

FIG. 23 is a diagram showing another example of a screen displayed on the seat terminal 10 or the user terminal 20 of the embodiment. The order status screen may be displayed overlaid on the main screen 110 or as a separate screen. In the illustrated example, the product name, orderer, delivery destination, status, and estimated time of serving for each order of all orderers are displayed in a list. For example, the status is displayed as "Not yet", "Medium", "Done" and the like for each of the "Cooking", "Delivery", and "Plating" columns. In this example, "Done" in the "Cooking" column means "cooked", "Medium" in the "Delivery" column means "being delivered", and "Not yet" in the "Plating" column means "not plated". The estimated time of serving may be displayed with a range. In the illustrated example, the status of the ordered products is shown all in text, but each may be shown as an image such as an icon.

Below, an example of the operation of the server device 30 described above will be described with reference to the flowcharts in Figures 24 to 27.

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

First, when participation information including the user ID of the user operating the seat terminal 10 at the remote restaurant 91 or the user terminal 20 at the user's home 92 where the participation location is, a reservation ID for the remote drinking party, etc. is transmitted from the seat terminal 10 at the remote restaurant 91 or the user terminal 20, the inter-terminal communication unit 312 receives the participation information (step S11). Next, the inter-terminal communication unit 312 refers to the reservation management table 355 and identifies reservation information that meets the conditions of the participation information (step S12).

Then, the inter-terminal communication unit 312 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 the reservation date and time has not been reached (step S13; No), the inter-terminal communication unit 312 cooperates with the GUI provision unit 313 to provide a standby screen to the seat terminal 10 or the user terminal 20 (step S14), and returns the process to step S13.

Also, when the reservation date and time arrives (step S13; Yes), the inter-terminal communication unit 312 cooperates with the GUI provision unit 313 to provide the start screen 100 of the remote drinking party to the seat terminal 10 or the user terminal 20 (step S15).

Next, the inter-terminal communication unit 312 waits until a start instruction is received from the seat terminal 10 or the user terminal 20 (step S16; No). When the inter-terminal communication unit 312 receives a start instruction from the seat terminal 10 or the user terminal 20 (step S16; Yes), it establishes communication between the seat terminal 10 or the user terminal 20 that sent the participation information and the seat terminal 10 or the user terminal 20 of the other user registered in the reservation information (step S17), and starts data sharing between the terminals (step S18).

Then, the GUI providing unit 313 provides the main screen 110 to the seat terminal 10 or user terminal 20 that sent the participation information (step S19), and ends this process.

By performing the above processing, the server device 30 can create an environment in which a remote drinking party can be held on the user terminal 20, where the participation location is the user's home 92.

Figure 25 is a flowchart showing an example of a menu provision process executed by the server device 30 of the embodiment. In this process, when the order button 121 is operated (step S21), the GUI provision unit 313 identifies the participation location of the ordering user (step S22). Next, the GUI provision unit 313 displays the menu that can be provided to the location identified in step S22 on the terminal of the ordering user (the seat terminal 10 or the user terminal 20) (step S23). Here, the above-mentioned available menu (product) is displayed for each product in the display field 132 of the menu display area 131 of the menu screen 130 shown in Figure 16.

When the GUI providing unit 313 detects an operation on the order confirmation button 144, it determines that the order has been accepted (Yes in step S24), and performs order processing (step S25). This step S25 corresponds to steps S303 to S305 in FIG. 13.

Furthermore, when there is no operation on the order confirmation button 144 (No in step S24), the GUI providing unit 313 judges whether or not a delivery destination has been specified (step S26). In other words, when an operation to select a subscreen has been performed, such as by touching a display area of any of the subscreens 112, 113, and 114, the GUI providing unit 313 judges that the user displayed on the selected subscreen has been specified as the delivery destination of the product.
If a delivery destination has not been specified in step S26 (No in step S26), the GUI providing unit 313 returns the process to step S24. If a delivery destination has been specified in step S26 (Yes in step S26), the GUI providing unit 313 displays a menu that can be provided to the specified delivery destination (step S27), and returns the process to step S24.

Figure 26 is a flowchart showing an example of an order process executed by the server device 30 of the embodiment. Note that Figure 26 shows an example of a process when an order operation based on the menu screen 130 is received from the seat terminal 10.

First, the order receiving unit 314 receives an order for a product from the seat terminal 10 (step S31). Next, the order receiving unit 314 determines whether the user ID of the orderer matches the user ID of the order recipient (step S32). If the two user IDs match, the order receiving unit 314 determines that the user has ordered a product to be consumed by himself/herself. In this case, the order receiving unit 314 notifies the order receiving terminal 40 of the delivery store 93 of the order recipient of the order contents (product ID, user ID of the orderer, etc.) (step S33). The order receiving unit 314 also registers the order history information including the received order contents in association with the corresponding reservation ID in the order management table 356 (step S34). The GUI providing unit 313 also displays the order history icon 151 on the sub-screens 112, 113, and 114 of the order recipient (step S35), and ends this process.

If it is determined in step S32 that the two user IDs are different (step S32; No), the order receiving unit 314 determines whether a method (treat) in which the user who placed the order pays for the product has been instructed (step S36).

If a payment method has been specified for the order recipient user (step S36; No), the order receiving unit 314 displays a confirmation screen for confirming the order details on the terminal operated by the order recipient user (seat terminal 10 or user terminal 20) (step S37). Next, the order receiving unit 314 waits until it receives a response from the order recipient user.

If a response rejecting the order is received (step S38; No), the order receiving unit 314 ends this process without placing an order for the product. In this case, the order receiving unit 314 may provide result information indicating this to the seat terminal 10 operated by the user who placed the order.

If an answer indicating consent to accept the order contents is obtained in step S38 (step S38; Yes), the order receiving unit 314 notifies the order contents (product ID, order recipient's user ID, etc.) to the order receiving terminal 40 of the delivery store 93 of the order recipient (step S39). The order receiving unit 314 also registers the order history information including the accepted order contents in association with the corresponding reservation ID in the order management table 356 (step S40). The GUI providing unit 313 also displays the order history icon 151 on the order recipient's sub-screens 112, 113, and 114 (step S35), and ends this process.

On the other hand, if a payment method is specified by the ordering user in step S36 (step S36; Yes), the order receiving unit 314 causes the terminal operated by the ordering user (seat terminal 10 or user terminal 20) to display a confirmation screen 161 for confirming the order details (step S40). The order receiving unit 314 also causes the terminal operated by the ordering user (seat terminal 10 or user terminal 20) to display a notification screen 162 for confirming the order details (step S41). The order receiving unit 314 then waits until it receives a response from each user.

If a response rejecting the order is received from either or both of the ordering user and the order recipient user (step S42; No), the order receiving unit 314 ends this process without placing an order for the product. Note that if the order recipient user rejects the order, the order receiving unit 314 may provide result information indicating this to the seat terminal 10 operated by the ordering user.

If both the orderer and order recipient users respond with consent to accept the order contents (step S42; Yes), the order acceptance unit 314 notifies the order contents (product ID, order recipient user ID, etc.) to the order receiving terminal 40 of the order recipient's delivery store 93 (step S44). The order acceptance unit 314 also registers the order history information including the accepted order contents in association with the corresponding reservation ID in the order management table 356 (step S45). The GUI provision unit 313 also displays the order history icon 151 on the order recipient's sub-screens 112, 113, and 114 (step S35), and ends this process.

If both the ordering user and the order recipient user respond with consent to accept the order contents (step S42; Yes), the accounting processing unit 315 executes accounting (payment) for the ordered product based on the ordering user's payment information, etc. The accounting processing unit 315 also sets the paid flag of the order history information registered in step S45 to "1" (paid).

Figure 27 is a flowchart showing an example of accounting processing executed by the server device 30 of the embodiment. In Figure 27, it is assumed that order history information related to an order received from the seat terminal 10 or the user terminal 20 has already been registered in the order management table 356.

First, the reservation reception unit 311 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 355 (step S51). If there is a reservation ID whose end date and time has been reached (step S51; Yes), the reservation reception unit 311 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 311 also proceeds to step S53.

In step S53, the accounting processor 315 determines whether or not an instruction to pay for the remote drinking party has been issued via the accounting button 123 (see Figures 15 to 17) provided on the main screen 110 or the menu screen 130 (step S53). If an instruction to pay has not been accepted (step S53; No), the accounting processor 315 returns to step S51.

If an accounting instruction is received in step S53 (step S53; Yes), the accounting processor 315 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 315 provides an accounting screen to each terminal (seat terminal 10 or user terminal 20) 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 315 receives an operation to specify a payment method from either the seat terminal 10 or the user terminal 20 that provided the accounting screen (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 315 sets the specified amount as the payment amount for 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 315 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 315 determines whether the remaining balance obtained by subtracting the payment amount from the total payment amount is zero (step S60). If the remaining balance is not zero (step S60; No), the process returns to step S55, and an accounting screen with updated remaining balance etc. is provided to the seat terminal 10 or user terminal 20.

Also, if it is determined in step S60 that the remaining balance is zero (step S60; Yes), the accounting processing unit 315 executes accounting processing to obtain the payment amount set for each user using the payment information of that user (step S61), and ends this processing.

As described above, the server device 30 of this embodiment and the program executed by the computer equipped with the server device 30 can provide a form of communication in which participants can participate from multiple locations, while also allowing food and drink to be ordered. In other words, at a remote drinking party, information about products that can be delivered to the order destination can be displayed on the display unit 16 of the terminal being used (the seat terminal 10 or the user terminal 20) and products can be ordered without interrupting communication with the participants.

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, some modified examples of the above-described embodiment will be described below as other embodiments. Note that the following will mainly describe the differences from the above-described embodiment, and detailed descriptions of the points in common with the contents already described will be omitted. The modified examples described below may be implemented individually or in appropriate combination.

The programs executed by each device in the above-described embodiments are provided in a state where they are pre-installed in a ROM, a storage unit, etc. The programs executed by each device in the above-described embodiments may be provided by being recorded in 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 digital versatile disk (DVD).

Furthermore, the programs executed by each device in the above-mentioned embodiments 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 in the above-mentioned embodiments 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.

1. Remote food and beverage supply system,
10 ... seat terminal,
11...CPU, 12...ROM, 13...RAM, 14...Communication unit, 15...Storage unit,
16: display unit, 17: operation unit, 18: imaging unit, 19: audio input/output unit,
20...user terminal,
21: communication control unit, 22: output control unit, 23: operation reception unit,
30 ... server device,
31...CPU, 32...ROM, 33...RAM, 34...Communication section, 35...Storage section,
311... reservation reception unit (constituting an example of a management means);
312...Terminal communication unit (constituting an example of a management means, an example of a communication control means),
313...GUI providing unit (an example of a providing means),
314: order receiving unit (an example of an order receiving means);
315...accounting processing section,
351...Remote restaurant management table,
352...Delivery store management table,
353...Delivery menu management table,
354...user management table,
355...Reservation management table,
356...Order management table,
357...Delivery status management table,
40 ... order receiving terminal,
41...CPU, 42...ROM, 43...RAM,
44...Communication section, 45...Storage section, 46...Display section, 47...Operation section,
411: communication control unit, 412: output control unit, 413: operation reception unit,
50 ... external service server,
60 ... Driver terminal,
70... Kitchen terminal,
91 ...Remote restaurant, 92 ...User's home,
93 ... Delivery store, 94 ... Driver,
100...Start screen, 101...Start button,
110: main screen (main display screen), 111: title display field,
112, 113, 114...Sub screen, 115...Participation location,
116...Organizer label, 117...Icon image,
121...Order button, 122...Order status button, 123...Checkout button,
130... Menu screen,
131... menu display area, 132... display column,
133 ... product name column, 134 ... price column, 135 ... store image column,
136 ... product image column, 137 ... provision time column, 138 ... button,
139...Notice of end of registration,
141: Unconfirmed order display area; 142: Product display area; 143: Product image area;
144...Order confirmation button,
151...order history icon, 152...status icon,
161: confirmation screen; 145: message; 146, 147: buttons;
162...notification screen, 148...message.

JP 2015-176335 A

Claims (5)

a management means for receiving access from a plurality of terminals and managing the terminal from which the access originates , the user who operates the terminal, the user's participation location, and the end time in association with each other;
A communication control means for connecting the terminals of users belonging to the same group so that they can communicate with each other;
a provision means for providing menu information including information on products that can be delivered to the participating locations so that the menu information can be viewed between the terminals communicatively connected by the communication control means;
an order receiving means for receiving an order for a product from any one of the terminals to which the menu information is provided, and notifying a store that handles the product of information related to the ordered product;
Equipped with
the providing means displays the menu information on a display device of the terminal so as to overlap and cover a portion of a main display screen;
displaying on the main display screen captured images transmitted from the terminals of the users belonging to the same group;
When there is no operation to select the captured image, the menu information includes information on products that can be delivered to the participating location of the user of the terminal that has accessed the menu information,
When an operation for selecting the captured image is performed, the server device includes information on products that can be delivered to the participating location of the user of the terminal that is the transmission source of the selected captured image . The providing means includes a required time from cooking to delivery of the product as information on the product included in the menu information.
The server device according to claim 1 . The server device according to claim 2 , wherein the providing means provides, as the menu information, information on a product whose required time is equal to or less than a difference between a provision completion time that is 0 minutes or more before the end time and a current time. The server device according to claim 3, wherein the provision means includes, as information about the product included in the menu information, a difference between a time that is the time prior to the completion of provision by the required time and a current time , in a manner that can be recognized as a remaining time during which the product can be ordered. The computer of the server device,
a management means for receiving access from a plurality of terminals and managing the terminal from which the access originates , the user who operates the terminal, the user's participation location, and the end time in association with each other;
A communication control means for connecting the terminals of users belonging to the same group so that they can communicate with each other;
a provision means for providing menu information including information on products that can be delivered to the participating locations so that the menu information can be viewed between the terminals communicatively connected by the communication control means;
an order receiving means for receiving an order for a product from any one of the terminals to which the menu information is provided, and notifying a store that handles the product of information related to the ordered product;
Function as a
the providing means displays the menu information on a display device of the terminal so as to overlap and cover a portion of a main display screen;
displaying on the main display screen captured images transmitted from the terminals of the users belonging to the same group;
When there is no operation to select the captured image, the menu information includes information on products that can be delivered to the participating location of the user of the terminal that has accessed the menu information,
and a program for including, when an operation for selecting the captured image is performed, information on products that can be delivered to the participating location of the user of the terminal that is the transmission source of the selected captured image .

Images