Server device and program

Abstract

To provide a server device and program configured to improve convenience related to remote food and drink providing service using a plurality of stores.SOLUTION: In a remote food and drink providing system configured by connecting a store terminal and a user terminal over a network so as to communicate with a server device, the server device 30 includes: a store management table 351 which stores store information on stores SP corresponding to store IDs, in association with the store IDs of each stores SP; a menu management table 352 which stores menu information on each commodity which can be served in the stores SP corresponding to the store IDs, in association with the store IDs of each stores SP; a user management table 353 which stores user information on users corresponding to user IDs, in association with the user IDs of each users; and an order management table 355 which stores order history information on a commodity ordered for a remote drinking party corresponding to a reservation ID, in association with the reservation ID.SELECTED DRAWING: Figure 3

Description

[Technical field]

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

[0002] As teleworking 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.

[0003] Meanwhile, in the past, a 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.

[0004] However, conventional technology assumes that orders are placed within the same store, and does not assume the above-mentioned form of web conference across multiple stores. Therefore, even if a remote drinking party is held using a store, the product orders and payments are handled individually by users at each store, and there is room for improvement in terms of convenience. Summary of the Invention [Problem to be solved by the invention]

[0005] The problem that the present invention aims to solve is to provide a server device and a program that can improve the convenience of a remote food and drink provision service that uses multiple stores. [Means for solving the problem]

[0006] The server device of the embodiment includes a management means, a communication control means, a provision means, and an order receiving means. The management means receives access from each of terminals installed in a plurality of stores, and manages the store and terminal from which the access originates in association with the user who operates the terminal. The communication control means connects the terminals of users belonging to the same group so that they can communicate with each other. The provision means A screen displaying, for each store, menu information of products common to each of the stores among menu information representing products that can be provided in the stores to which each of the terminals communicably connected by the communication control means belongs is displayed on each of the terminals. The order receiving means receives an order for a product from any of the terminals to which the menu information has been provided, and notifies a store that provides the product of information related to the ordered product. In addition, when the ordering user of the terminal that placed the order is different from the ordering user of the store that provides the ordered product, the order receiving means confirms with the ordering user's terminal whether or not the order can be accepted, and notifies the store of the terminal that has been instructed to accept the ordered product of information regarding the ordered product, and the providing means displays, on the screen provided to the ordering user's terminal, the confirmation result of the ordering user's whether or not the order can be accepted, in association with the menu information of the store to which the ordering user belongs. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating a configuration example of a remote food and drink providing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a store terminal according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of the server device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a data configuration of a store management table according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a data configuration of the menu management table according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a data configuration of a user management table according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of a reservation management table according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a data configuration of an order management table according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a functional configuration of the store terminal and the server device according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a screen displayed on the store terminal according to the embodiment. [Figure 11]FIG. 11 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 15] FIG. 15 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 16] FIG. 16 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 17] FIG. 17 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 18] FIG. 18 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 19] FIG. 19 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 20] FIG. 20 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 21] FIG. 21 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 22] FIG. 22 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Diagram 23] FIG. 23 is a diagram illustrating another example of a screen displayed on the store terminal according to the embodiment. [Figure 24] FIG. 24 is a flowchart illustrating an example of the login process executed by the server device of the embodiment. [Diagram 25] FIG. 25 is a flowchart illustrating an example of a menu providing process executed by the server device of the embodiment. [Figure 26] FIG. 26 is a flowchart illustrating an example of an order process executed by the server device according to the embodiment. [Figure 27]FIG. 27 is a flowchart illustrating an example of a transaction process executed by the server device according to the embodiment. [Figure 28] FIG. 28 is a diagram for explaining an example of the operation of accounting processing executed by the accounting processing unit of the embodiment. [Figure 29] FIG. 29 is a diagram showing an example of a screen displayed on the store terminal in the first modification. [Diagram 30] FIG. 30 is a diagram showing another example of a screen displayed on the shop terminal in the first modification. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0009] Fig. 1 is a diagram showing an example of the system configuration of a remote food and drink provision service according to an embodiment. As shown in Fig. 1, a remote food and drink provision system 1 includes a store terminal 10, a user terminal 20, and a server device 30. The store terminal 10 and the user terminal 20 are communicatively connected to the server device 30 via a network N such as the Internet or a mobile phone network.

[0010] The store terminal 10 is a terminal device provided in each store SP, which is a restaurant such as an izakaya. The store terminal 10 is, for example, an ordering terminal for self-ordering provided at each seat in the store SP, and is realized by a tablet terminal or the like. There is no particular limit to the number of store terminals 10 provided in the store SP, and there may be more than one.

[0011] Each store SP also includes a store server (not shown) for receiving order information sent from the store terminal 10 and the server device 30. Each store SP may be an affiliated store of a chain store or the like, or each store may be an independent store.

[0012] The user terminal 20 is a terminal device used by a user who uses the remote food and drink providing system 1. The user terminal 20 can be realized by a portable terminal device such as a smartphone or a tablet terminal.

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

[0014] The server device 30 cooperates with the store terminal 10 of each store SP to provide a remote food and drink provision service using the store terminal 10. More specifically, the server device 30 controls communication between the store terminals 10 installed in each of the multiple store SPs to provide a service (remote food and drink provision service) in which users at different store SPs can talk to each other and share screens. Hereinafter, the remote food and drink provision service using the store terminal 10, or providing (receiving) the remote food and drink provision service using the store terminal 10, is also referred to as a "remote drinking party."

[0015] Next, the configuration of the main devices of remote food and drink supply system 1 will be described.

[0016] Fig. 2 is a diagram showing an example of a hardware configuration of the store terminal 10. As shown in Fig. 2, the store 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.

[0017] The CPU 11 is an example of a processor, and performs overall control of each unit of the store terminal 10. The ROM 12 stores various programs. The RAM 13 is a workspace in which programs and various data are expanded.

[0018] The store terminal 10 also includes a communication unit 14 , a storage unit 15 , a display unit 16 , an operation unit 17 , an imaging unit 18 , and an audio input / output unit 19 .

[0019] The communication unit 14 is a communication interface connectable to a network N. The communication unit 14 communicates with external devices such as a server device 30 via the network N. The communication unit 14 also communicates with a store server in its own store and other store terminals 10.

[0020] The storage unit 15 is composed of a storage medium such as a hard disk drive (HDD) or a flash memory, and maintains the stored contents even when the power is cut off. The storage unit 15 stores programs that the CPU 11 can execute and various setting information. For example, the storage unit 15 stores programs (client programs) prepared for a remote drinking party and contents related to GUI display. The CPU 11 executes various processes by operating according to the programs stored in the ROM 12 or the storage unit 15 and expanded in the RAM 13.

[0021] The display unit 16 is a display device such as an LCD (Liquid Crystal Display), and displays various information and screens under 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.

[0022] 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 who operates the store terminal 10, thereby acquiring image data (still image, video) of the user, and outputs the acquired image data to the CPU 11.

[0023] 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's 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.

[0024] It should be noted that the hardware configuration of the store terminal 10 is not limited to the configuration shown in Fig. 2. Also, the following description will be given on the assumption that the user terminal 20 has the same hardware configuration as the store terminal 10.

[0025] Fig. 3 is a diagram showing an example of a hardware configuration of the server device 30. As shown in Fig. 3, the server device 30 includes a computer configuration including a CPU 31, a ROM 32, and a RAM 33.

[0026] The CPU 31 is an example of a processor, and performs overall control of each unit of the server device 30. The ROM 32 stores various programs. The RAM 33 is a workspace in which programs and various data are expanded.

[0027] The server device 30 also includes a communication unit 34 and a storage unit 35. The communication unit 34 is a communication interface connectable to a network N. The communication unit 34 communicates with external devices such as the store terminal 10 and the user terminal 20 via the network N.

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

[0029] The storage unit 35 also stores a store management table 351, a menu management table 352, a user management table 353, a reservation management table 354, and an order management table 355.

[0030] Fig. 4 is a diagram showing an example of the data configuration of the store management table 351. As shown in Fig. 4, the store management table 351 stores store information on the store SP corresponding to the store ID in association with the store ID of each store SP.

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

[0032] Fig. 5 is a diagram showing an example of the data configuration of the menu management table 352. As shown in Fig. 5, the menu management table 352 stores menu information about each product (menu) available at the store SP corresponding to the store ID in association with the store ID of each store SP. The server device 30 acquires the menu information from, for example, a store server of each store SP and stores it in the menu management table 352.

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

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

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

[0036] The data configuration of the menu management table 352 is not limited to the example in Fig. 5. The server device 30 may acquire the menu information in the menu management table 352 from a store server of each store SP periodically or as needed, thereby updating the menu information at a predetermined timing.

[0037] Fig. 6 is a diagram showing an example of the data configuration of user management table 353. As shown in Fig. 6, user management table 353 stores user information on a user corresponding to a user ID in association with the user ID of each user. Here, the user ID is identification information for identifying each user.

[0038] The user information includes, for example, a user name, an address, contact information, and payment information. The user name is information indicating the name of a user corresponding to a user ID. The address is information indicating the address or whereabouts of a user corresponding to a user ID. The contact information is information indicating the contact information of a user corresponding to a 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. The payment information is information related to electronic payment such as credit card payment and electronic money payment. The payment information holds one or more pieces of information such as a credit card number, and is used when paying for a product by electronic payment.

[0039] The data configuration of the user management table 353 is not limited to the example in Fig. 6. For example, the user management table 353 may store information such as the gender, age, and preferences of each user corresponding to the user ID in association with the user ID of the user.

[0040] Fig. 7 is a diagram showing an example of the data configuration of the reservation management table 354. As shown in Fig. 7, the reservation management table 354 stores reservation information related to the reservation ID in association with the reservation ID.

[0041] 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) every time the server device 30 accepts a reservation for a remote drinking party from a user via the user terminal 20 or the like.

[0042] The reservation information includes, for example, information such as reservation date and time, user ID, store ID, terminal ID, and login date and time.

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

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

[0045] The terminal ID is registered with identification information of the store terminal 10 used in the remote drinking party. Moreover, the login date and time is registered with the date and time when the use of the store terminal 10 corresponding to the terminal ID started.

[0046] In this embodiment, among the information included in the reservation information, the reservation date and time, the user ID, and the store ID are assumed to be registered before the remote drinking party is held. Also, among the information included in the reservation information, the terminal ID and the login date and time are assumed to be registered on the day of the remote drinking party, that is, when the user corresponding to the user ID visits the store SP. Note that the store ID may be registered as the store ID of the store SP when the user visits the store SP on the day of the remote drinking party. Alternatively, the user and the store SP that the user visits may be registered in association with each other. For example, the store ID may be registered in advance in association with the user ID registered in the reservation information of the reservation ID.

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

[0048] Fig. 8 is a diagram showing an example of the data configuration of the order management table 355. As shown in Fig. 8, the order management table 355 stores order history information on products ordered at a remote drinking party corresponding to a reservation ID in association with the reservation ID.

[0049] The order history information includes, for example, an order ID, an ordering user ID, an order destination user ID, a store ID, a product ID, a quantity, and a payment completed flag.

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

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

[0052] The store ID of the order destination is registered in the store ID. In other words, the store ID of the store SP where the user with the order destination user ID exists is registered in the store ID. The product ID of the product that is the subject of the order is registered in the product ID. The quantity is registered with the quantity of the product that is the subject of the order.

[0053] Moreover, the paid flag registers flag information indicating whether or not the payment for the ordered product has been made. In this embodiment, as described below, when a user wants to give a product as a gift to another user (hereinafter, this ordering method is also referred to as a "treat re-order"), 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. FIG. 8 shows a case where unpaid is flagged as "0" and paid is flagged as "1".

[0054] The data configuration of the order management table 355 is not limited to the example shown in Fig. 8. For example, the order management table 355 may store information indicating the date and time of an order.

[0055] Next, the functional configurations of the store terminal 10 and the server device 30 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the functional configurations of the store terminal 10 and the server device 30.

[0056] As shown in FIG. 9, the store terminal 10 includes a communication control unit 21, an output control unit 22, and an operation reception unit 23 as functional units.

[0057] Some or all of the functional units of the store terminal 10 may be software configurations realized by cooperation between a processor (e.g., CPU 11) of the store 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 store terminal 10 may be hardware configurations realized by a dedicated circuit or the like mounted on the store terminal 10.

[0058] The communication control unit 21 of the store 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 store terminals 10 via the server device 30.

[0059] 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 store terminals 10. The output control unit 22 also causes the display unit 16 to display various GUIs (Graphical User Interfaces) by working in cooperation with the server device 30. 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 store terminals 10.

[0060] The operation reception unit 23 receives the operation content of the user inputted 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 store terminal 10 functions as an input / output interface of the server device 30.

[0061] On the other hand, the server device 30 includes a reservation receiving unit 311, an inter-terminal communication unit 312, a GUI providing unit 313, an order receiving unit 314, and an accounting processing unit 315 as functional units.

[0062] A part or all of the functional units of the server device 30 may be a software configuration realized by cooperation between a 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, a part or all of the functional units of the server device 30 may be a hardware configuration realized by a dedicated circuit or the like mounted on the server device 30.

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

[0064] For example, a website that allows a user to specify the date and time of the remote drinking party and the store to be used may be published on the network N, and reservations may be accepted via the website. In this case, a user who is a host or organizer (hereinafter also referred to as an organizer) accesses the website using the user terminal 20 and makes a reservation (new reservation) for the remote drinking party by inputting the date and time of the remote drinking party, his / her own user ID, the store SP (store ID) to be used by the user, and the like. When accepting a new reservation, the reservation acceptance unit 311 issues a reservation ID and registers it in the reservation management table 354 together with the input items. In addition, the reservation acceptance unit 311 notifies the user terminal 20 of the user of the issued reservation ID. Then, the organizer notifies the user ID to other users who will be participating members of the remote drinking party. Note that when making a new reservation, the user ID of a user other than the organizer may be input.

[0065] Meanwhile, the other user who has been notified of the reservation ID uses his / her own user terminal 20 to access the above-mentioned website specifying the reservation ID. When the reservation reception unit 311 receives the access specifying the reservation ID, it reads the reservation information (date and time of the event, etc.) corresponding to the reservation ID from the reservation management table 354 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, the store SP (store ID) that he / she will use, etc. When the reservation reception unit 311 receives the additional reservation, it additionally registers the items of the additional reservation to the reservation information of the reservation ID that was previously input.

[0066] In addition, the reservation reception unit 311 may compare the address stored in the user information with the address stored in the store information of each store SP, and present to the user store SPs that are within a predetermined range (e.g., within 3 km) of the user's address as candidates for use.

[0067] By performing the above process (reservation process), the reservation reception unit 311 stores a pair of the user ID and the store ID used by each user participating in the same remote drinking party in the reservation management table 354 in association with a common reservation ID. In the above description, the other users who received the notification of the reservation ID individually register their own user IDs, etc., in the reservation information of the reservation ID, and register them additionally, but this is not limited to the above. For example, if a representative has acquired the user IDs of the participants in advance, the representative may register the user IDs of the participants collectively. After the reservation process is completed, the user terminal 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 user whose user ID has been registered. For example, the user terminal 20 may display the two-dimensional code information on the day of the reservation, and the store terminal 10 may read the displayed two-dimensional code information to execute the login process.

[0068] 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 store terminal 10 of the store SP, and manages the store SP (store ID) and store terminal 10 (terminal ID) of the access source, in association with the user (user ID) operating the store terminal 10.

[0069] The inter-terminal communication unit 312 is an example of a communication control means. The inter-terminal communication unit 312 connects the shop terminals 10 of users associated with the same reservation ID, that is, users belonging to the same group, so that they can communicate with each other.

[0070] Specifically, when the inter-terminal communication unit 312 receives an access from the store 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 354. 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 accessing store terminal 10 and the current date and time (login date and time) in association with the user ID to the reservation information.

[0071] 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 user terminals 20 having the terminal ID registered in the reservation information so that they can communicate with each other. This allows data sharing between the store terminals 10 associated with the same reservation ID, so that users belonging to the same group can talk with other users while looking at images (face images) captured by each of the store terminals 10.

[0072] The inter-terminal communication unit 312 may be configured to register, when accessed from a store terminal 10, the terminal ID of the store terminal 10 and the store ID of the store SP to which the store terminal 10 belongs in the reservation information.

[0073] Furthermore, the inter-terminal communication unit 312 may be configured to reject access if the user ID received from the store terminal 10 is not included in the reservation information for the corresponding reservation ID, or may be configured to additionally register the user ID in the reservation information.

[0074] The GUI providing unit 313 is an example of a providing means. The GUI providing unit 313 provides various GUIs to the store terminal 10. Specifically, the GUI providing unit 313 provides a screen that allows the store terminals 10 connected to each other so as to be able to communicate with each other via the inter-terminal communication unit 312 to view menu information showing products that can be provided at the store SP to which the store terminal 10 belongs. The GUI providing unit 313 also provides each of the store terminals 10 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.

[0075] 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 any of the store terminals 10 to which menu information has been provided, and notifies the store SP that provides the product of information (order information) related to the ordered product.

[0076] Furthermore, each time an order for a product is received, the order receiving unit 314 identifies the user ID of the user of the store terminal 10 that placed the order (ordering user ID) and the user ID of the user of the store SP that provides the ordered product (order destination user ID).The order receiving unit 314 then registers information such as the identified user ID, ordering store ID, and product ID as order history information in the order management table 355, in association with a newly issued order ID under a reservation ID corresponding to the identified user ID.

[0077] The accounting processor 315 is an example of an accounting unit. The accounting processor 315 executes accounting processing to pay the price of the product accepted by the order accepting unit 314 to the store SP that provides the product. Specifically, the accounting processor 315 executes accounting processing to pay the price of the ordered product using the payment information stored in the user management table 353.

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

[0079] The operation of the server device 30 will be described below. The server device 30 executes various processes in response to operations based on the screen provided to the store terminal 10 by the GUI providing unit 313. Therefore, the operation of the server device 30 will be described below based on the screen displayed on the display unit 16 of the store terminal 10. It is assumed that the reservation for the remote drinking party has been made in advance.

[0080] First, when the inter-terminal communication unit 312 receives an access from the store terminal 10 specifying a reservation ID and a user ID, it executes the login process described above to identify the reservation information. Note that the login process may involve a code reader (not shown) of the store terminal reading 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 accessing store terminal 10 and the login date and time in the identified reservation information.

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

[0082] 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 store terminal 10 to display a standby screen (not shown) notifying that the start date and time has not been reached. For example, such a standby screen may display a countdown to the start date and time.

[0083] 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 store terminal 10 to display a start screen (see Figure 10) that allows the user to instruct the start of the remote drinking party.

[0084] Fig. 10 is a diagram showing an example of a screen displayed on the store terminal 10. Here, Fig. 10 shows an example of a display of a start screen. As shown in Fig. 10, a start screen 100 has a start button 101 which is an operator for instructing the start of a remote drinking party.

[0085] When the inter-terminal communication unit 312 accepts an operation of the start button 101 from the store terminal 10, it establishes communication between the store terminals 10 having the terminal IDs registered in the reservation information, and realizes a state in which data can be shared between the store terminals 10.

[0086] Furthermore, when the GUI providing unit 313 receives an operation of the start button 101 from the shop terminal 10, it causes the display unit 16 of the shop terminal 10 to display a main screen 110 for displaying data (image data) shared between the shop terminals 10.

[0087] Fig. 11 is a diagram showing another example of a screen displayed on the shop terminal 10. Fig. 11 shows a display example of a main screen 110. As shown in Fig. 11, the main screen 110 has a plurality of sub-screens divided according to the number of participants in the remote drinking party. Fig. 11 shows an example in which the main screen 110 is divided into four sub-screens according to the four users, user A to user D.

[0088] Each sub-screen is associated with the terminal ID of the store terminal 10 operated by each user, the user ID of the user operating the store terminal 10, the store ID of the store SP to which the store terminal 10 belongs, etc. Also, each sub-screen displays image data acquired (captured) by the store terminal 10 of the corresponding terminal ID. Also, audio data acquired by the store terminal 10 is provided from the server device 30 to each store terminal 10, and output from the audio input / output unit 19 by the output control unit 22.

[0089] This allows the user of the shop terminal 10 to view the main screen 110 and talk with each of the participants of the remote drinking party while looking at each other's faces.

[0090] Furthermore, on each sub-screen, a user name 111 of a user ID associated with the sub-screen and a store image 112 of the store SP are displayed. Specifically, the GUI providing unit 313 reads out a user name corresponding to the user ID from the user management table 353. Furthermore, the GUI providing unit 313 reads out a store image of the store SP from the store management table 351. Then, the GUI providing unit 313 displays the read out user name and store image as the user name 111 and the store image 112, superimposed on the sub-screen.

[0091] FIG. 11 shows an example in which the upper left sub-screen displays a user name "User A" and a store image 112 of store A used by user A. Also, an example in which the upper right sub-screen displays a user name "User B" and a store image 112 of store B used by user B. Also, an example in which the lower right sub-screen displays a user name "User C" and a store image 112 of store C used by user C. Also, an example in which the lower left sub-screen displays a user name "User D" and a store image 112 of store D used by user D.

[0092] This allows the user of the store terminal 10 to easily check the user name of each user who has participated in the remote drinking party and the store SP used by each user by looking at the main screen 110. Note that in this embodiment, a GUI screen on which a user C operates the store terminal 10 of a store C will be described as an example. Also, the main screen 110 may be set to display an image of a person other than the user who operates the store terminal 10.

[0093] Furthermore, each sub-screen is provided with a menu button 113 for instructing the display of a menu for each store SP. When the GUI providing unit 313 accepts an operation of the menu button 113 from the store terminal 10, it reads out menu information from the menu management table 352 based on the store ID of the store SP corresponding to the sub-screen on which the menu button 113 is provided. Then, the GUI providing unit 313 displays the menu screen 120 based on the read out menu information on the display unit 16 of the operating store terminal 10.

[0094] FIG. 12 is a diagram showing another example of a screen displayed on the shop terminal 10. FIG. 12 shows a display example of a menu screen 120. As shown in FIG. 12, the menu screen 120 displays a shop name 121 and a shop image 122 of the shop SP corresponding to the operated menu button 113. The menu screen 120 also displays information such as a product name 123, a price 124, and a product image 125 of each product included in the menu information. The menu screen 120 also displays a reduced screen 126, which is a reduced version of the main screen 110 in FIG. 11, superimposed thereon. Therefore, while the user is viewing and operating the menu screen 120, the user can continue a conversation with other users. The size and display position of the reduced screen 126 are not limited to those shown in FIG. 12 and can be adjusted arbitrarily.

[0095] In this way, in response to the operation of the menu button 113 displayed on each sub-screen, the GUI providing unit 313 causes the display unit 16 of the operating store terminal 10 to display menu information (menu screen) showing products available at the store SP corresponding to the operated menu button 113. In this way, the GUI providing unit 313 can provide the menu screen of the store to which the store terminal 10 belongs so that it can be viewed by the store terminals 10 in the same group.

[0096] Furthermore, on the menu screen 120, the product name 123, price 124, and product image 125 of each product function as controls for accepting an order for the product. Specifically, the product name 123, price 124, and product image 125 are associated with the product ID of the corresponding product, the store ID of the store SP that provides the product, etc. When a product is selected, the product ID and store ID associated with the selected product, as well as the terminal ID of the store terminal 10 itself and the user ID of the user operating the store terminal 10 are notified to the server device 30. When the order acceptance unit 314 accepts a product selection operation from the store terminal 10, it executes a process related to the order for the selected product.

[0097] Here, the order receiving unit 314 determines whether the user ID of the user who performed the selection operation on the store terminal 10, i.e., the user who placed the order, matches the user ID of the user of the store SP that provides the selected product, i.e., the user who received the order.

[0098] If the two user IDs match, the order receiving unit 314 determines that the user has ordered a product to be consumed by the user himself / herself. In this case, the order receiving unit 314 notifies the store server of the store SP corresponding to the store ID of the order destination of order information including the product ID of the ordered product, the user ID of the order destination user, the terminal ID of the store terminal 10 operated by the user, etc.

[0099] The order receiving unit 314 also associates the user ID of the user who performed the selection operation with the newly issued order ID and registers the order history information in the reservation management table 354, with the ordering user ID and order destination user ID set. The order receiving unit 314 also registers the store ID of the order destination, the product ID of the ordered product, the quantity, etc. in the order history information. The paid flag is set to "0" by default, indicating unpaid.

[0100] On the other hand, if the two user IDs are different, the order receiving unit 314 determines that the ordering user has ordered a product to be consumed by another user. In this case, the order receiving unit 314 cooperates with the GUI providing unit 313 to display a confirmation screen (not shown) on the display unit 16 of the store terminal 10 operated by the ordering user to confirm whether the ordered product is a "treat order" in which the ordering user pays for the product.

[0101] Here, if the store terminal 10 indicates that the order is not a "treat order," the order receiving unit 314 notifies the store server of the store SP corresponding to the store ID of the order recipient of order information including the product ID of the ordered product, the user ID of the order recipient user, the terminal ID of the store terminal 10 operated by that user, etc.

[0102] Then, the order receiving unit 314 associates the newly issued order ID with the order history information that sets the different user ID of the orderer and the user ID of the order recipient, and registers this information in the reservation management table 354. The order receiving unit 314 also registers the store ID of the order recipient, the product ID of the ordered product, the quantity, etc. in the order history information.

[0103] In addition, when a "treat order" is indicated from the store terminal 10, the order receiving unit 314 cooperates with the GUI providing unit 313 to display a payment screen 127 for making payment for the product on the display unit 16 of the store terminal 10 that placed the order.

[0104] Fig. 13 is a diagram showing another example of a screen displayed on the store terminal 10. Fig. 13 shows an example in which a prepayment screen 127 is superimposed on the menu screen 120. As shown in Fig. 13, the prepayment screen 127 displays the user name of the ordering user (user D) and a message 1271 for confirming that the product will be given as a gift to that user. Fig. 13 shows an example in which image data acquired by the store terminal 10 operated by the ordering user is displayed together with the message 1271.

[0105] The advance payment screen 127 also displays the name, price, and product image of the product to be ordered as order target information 1272. The advance payment screen 127 also displays a first payment method 1273 using code payment and a second payment method 1274 using payment information as information to guide the payment method for the product.

[0106] The ordering user checks the message 1271 and the order target information 1272, and if they determine that there are no problems, they pay for the product using either the first payment method 1273 or the second payment method 1274. For example, when paying using the first payment method 1273, the user pays for the product shown in the order target information 1272 by reading the two-dimensional code information displayed below the first payment method 1273 using their own user terminal 20.

[0107] For example, the GUI providing unit 313 displays two-dimensional code information on the advance payment screen 127, which holds the price of the product, the payment destination store SP, the ordering user ID, the notification destination when the payment is completed (the address of the server device 30), and the like. Then, the user terminal 20 performs code payment based on the two-dimensional code information, and then notifies the server device 30 of the various information contained in the two-dimensional code information. This allows the server device 30 to know that the product has been paid for by code payment. Note that known technology is used for code payment.

[0108] When paying using the second payment method 1274, the user can pay for the product by operating the second payment method 1274 displayed as an operator. When the accounting processing unit 315 of the server device 30 accepts the operation of the second payment method 1274, it executes accounting processing to pay for the product indicated in the order target information 1272, using the payment information of the ordering user registered in the user management table 353.

[0109] When the accounting process is completed, the accounting processor 315 cooperates with the order receiver 314 to change the paid flag included in the order history information to "1." The order receiver 314 then notifies the store server of the store SP corresponding to the store ID of the order destination of order information including the product ID of the ordered product, the user ID of the order destination user, the terminal ID of the store terminal 10 operated by that user, etc.

[0110] Then, the order receiving unit 314 associates the newly issued order ID with the order history information that sets the different user ID of the orderer and the user ID of the order recipient, and registers this information in the reservation management table 354. The order receiving unit 314 also registers the store ID of the order recipient, the product ID of the ordered product, the quantity, etc. in the order history information.

[0111] The store server that receives the order information from the server device 30 notifies the store clerk or the like of the notified item, thereby encouraging the ordered item to be cooked. Then, the store clerk or the like carries the cooked item to the user with the ordering user ID, thereby completing the delivery of the ordered item.

[0112] When the users (user IDs) of the order origin and the order destination are different, the order receiving unit 314 may perform control so as to notify the order information after obtaining consent from the user of the order destination.

[0113] Returning to FIG. 12, the menu screen 120 is provided with a close button 128 for returning to the main screen 110. When the GUI providing unit 313 accepts an operation of the close button 128 via the shop terminal 10, it erases the menu screen 120 and causes the display unit 16 of the shop terminal 10 to display the main screen 110 again. Note that returning to the main screen 110 is not limited to the operation of the close button 128. For example, the GUI providing unit 313 may be configured to return the display to the main screen 110 when an operation of double-tapping the reduced screen 126 is accepted.

[0114] 11, a general menu button 114 is provided in the center of the main screen 110. When the GUI providing unit 313 accepts an operation of the general menu button 114 from the store terminal 10, it causes the display unit 16 of the store terminal 10 to display a general menu screen 115 shown in FIG.

[0115] Fig. 14 is a diagram showing another example of a screen displayed on the shop terminal 10. Fig. 14 shows an example in which a general menu screen 115 is superimposed on a main screen 110. As shown in Fig. 14, a first operation button 1151 and a second operation button 1152 provided for each user are displayed on the general menu screen 115.

[0116] Here, the first operation button 1151 is provided for each user belonging to the same group or for each store SP used by the user. Also, the first operation button 1151 is an operator for instructing the display of a menu of the corresponding store SP.

[0117] For example, the first operation button 1151 labeled "User A" is an operator for displaying a menu of a store SP used by user A. Also, the first operation button 1151 labeled "me" is an operator for displaying a menu of a store SP used by a user (user C) who operates this store terminal 10.

[0118] When the GUI providing unit 313 receives an operation of the first operation button 1151 from the store terminal 10, it displays the above-mentioned menu screen 120 on the display unit 16 of the store terminal 10 based on the menu information of the store SP corresponding to the operated first operation button 1151.

[0119] On the other hand, the second operation button 1152 is an operation button for instructing the display of a menu common to all stores SP used by each user in the same group.

[0120] When the GUI providing unit 313 receives an operation of the second operation button 1152 from the store terminal 10, it extracts product information (product name, price, etc.) of products with a common general name from the menu information of the store SP used by each user belonging to the same group. Next, the GUI providing unit 313 displays the common product menu screen 130 based on the extracted product information on the display unit 16 of the store terminal 10.

[0121] When the menu screen 120, the general menu screen 115, or the menu screen including the common product menu screen 130 described later or the checkout screen 170 (hereinafter, operation screen) is displayed on the main screen 110, the sizes of the main screen 110 and the operation screen may be adjusted so that both the main screen 110 and the operation screen are displayed. Alternatively, when the operation screen is displayed superimposed on the main screen 110, the size of the operation screen may be adjusted to be small, or the background of the operation screen other than the operation buttons (operators) may be made a "watermark" so that the facial expression of the user of the main screen 110 can be seen. This allows the user operating the store terminal 10 to continue a conversation with other users without feeling awkward while viewing and operating the operation screen including the menu screen 120, the general menu screen 115, or the checkout screen 170.

[0122] Fig. 15 is a diagram showing another example of a screen displayed on the store terminal 10. Fig. 15 shows a display example of a common product menu screen 130. As shown in Fig. 15, the common product menu screen 130 displays user ID information 131 indicating the user IDs of each user belonging to the same group in association with a store image 132 of the store SP used by the user. Here, the user ID information 131 written as "me" refers to the user (user C) who operates this store terminal 10.

[0123] Furthermore, on the common product menu screen 130, operation buttons 133 indicating products related to generic names P and Q common to each store SP are displayed vertically for each store SP that sells the products. Furthermore, the operation buttons 133 are displayed horizontally for each generic name P. Each of the operation buttons 133 displays the product name, price, etc. of the corresponding product.

[0124] This allows the user of the store terminal 10 to easily check the common menu at each store SP used by the users of the remote drinking party by looking at the common product menu screen 130. Therefore, for example, when all users who participated in the remote drinking party order a common product such as beer, by looking at the common product menu screen 130, the user can easily select a product common to each store SP.

[0125] Here, the operation buttons 133 function as an operator for selecting the products to be ordered. Specifically, the operation buttons 133 are associated with the product IDs of the corresponding products, and after selecting one or more operation buttons 133, it is possible to order the selected products by operating the order only button 134 or the treat button 135 provided at the bottom of the screen.

[0126] Further, the operation button 133 is associated with the user ID of the corresponding user ID information 131 and the store ID of the store SP corresponding to the store image 132. For example, when the operation button 133 labeled "Product PA" is operated, the user ID of user A corresponding to the operation button 133 and the store ID of store A are selected as the order destination together with the product ID of the product "Product PA."

[0127] The order only button 134 is an operator for instructing the ordering method in which the order destination user pays for the ordered product. When the order receiving unit 314 receives the operation of the order only button 134 via the store terminal 10, it judges whether the user ID of the order source user who performed the operation matches the user ID of the order destination user selected by the operation button 133.

[0128] If the two user IDs match, the order receiving unit 314 determines that the user has ordered a product to be consumed by the user himself / herself, and similarly to the above, notifies the store server of the store SP where the order was placed of the order information, and registers the order history information in the order management table 355.

[0129] On the other hand, if the two user IDs are different, the order receiving unit 314 determines that the ordering user has ordered a product that another user will consume. In this case, the order receiving unit 314 displays a confirmation screen 140 on the display unit 16 of the store terminal 10 operated by the ordering user, to allow the user to confirm whether or not to accept the order.

[0130] Fig. 16 is a diagram showing another example of a screen displayed on the store terminal 10. Fig. 16 shows an example of a confirmation screen 140. As shown in Fig. 16, the confirmation screen 140 displays a message 141 for confirming whether or not to accept the order. Fig. 16 shows an example in which the message 141 displays the product name and price of the product to be ordered, as well as the user name of the user who placed the order.

[0131] Furthermore, an operation button 142 for instructing to accept the order and an operation button 143 for instructing to reject the order are displayed on the confirmation screen 140. After checking the message 141, the user of the order destination operates either the operation button 142 or the operation button 143 to respond as to whether or not to accept the order.

[0132] Here, when the order receiving unit 314 receives an operation of the operation button 143 from the store terminal 10, it displays result information 136 indicating that the order recipient user has rejected the order on the common product menu screen 130 displayed on the order originating store terminal 10 (see FIG. 17).

[0133] Furthermore, when the order receiving unit 314 receives an operation of the operation button 142 from the store terminal 10 of the order destination, it notifies the store server of the store SP corresponding to the store ID of the order destination of the order information. The order receiving unit 314 also registers order history information on the ordered product in the order management table 355. Then, the order receiving unit 314 displays result information 136 indicating that the order has been received by the user of the order destination on the common product menu screen 130 displayed on the store terminal 10 of the order originator (see FIG. 17).

[0134] Fig. 17 is a diagram showing another example of a screen displayed on the store terminal 10. Fig. 17 shows an example of a common product menu screen 130 on which result information 136 is displayed. Here, a state is shown in which each product with a general name Q is selected with the operation button 133, and then the order only button 134 is operated.

[0135] As described above, the order receiving unit 314 confirms with each of the order destination users whether or not to accept the order, and displays the confirmation result as result information 136 on the common product menu screen 130. For example, the order receiving unit 314 cooperates with the GUI providing unit 313 to superimpose the result information 136 on the selected operation button 133, as shown in FIG.

[0136] Here, for example, for user A, an "OK" mark is displayed as result information 136 indicating that the order has been accepted. Also, for example, for user D, an "NG" mark is displayed as result information 136 indicating that the order has been rejected. Note that Fig. 17 shows an example in which result information 136 is also displayed for me (user C), the user who placed the order.

[0137] In this way, when a user orders a product that another user will consume, the server device 30 checks with the order-recipient user whether or not the order can be accepted, and executes the product order if the order is accepted. The server device 30 also provides the ordering user with result information 136 indicating the confirmation result of the order-recipient user's acceptance or rejection. This allows the ordering user to easily check the acceptance status of the order-recipient user, thereby improving convenience.

[0138] In addition, on the common product menu screen 130, the Treat button 135 is an operator for instructing an ordering method (treat order) in which the ordering user pays for the product ordered by an order recipient user different from the ordering user. When the order receiving unit 314 receives an operation of the Treat button 135 from the store terminal 10, it judges whether the user ID of the ordering user who performed the operation matches the user ID of the order recipient user selected by the operation button 133.

[0139] If the two user IDs match, the order receiving unit 314 disables the operation of the treat button 135. On the other hand, if the two user IDs are different, the order receiving unit 314, in cooperation with the GUI providing unit 313, causes the display unit 16 of the store terminal 10 operated by the ordering user to display a confirmation screen 150 for confirming that a treat order is to be placed.

[0140] Fig. 18 is a diagram showing another example of a screen displayed on the store terminal 10. Fig. 18 shows an example of a display of a confirmation screen 150. As shown in Fig. 18, the confirmation screen 150 displays the user name of the order destination user ID (user D) and a message 151 for confirming that a present will be given to the user. Note that when multiple order destination users are selected, that is, when multiple products are selected, the selections are displayed in the message 151.

[0141] Furthermore, an operation button 152 for instructing to place an order and an operation button 153 for instructing to cancel the order are displayed on the confirmation screen 150. After checking the message 151, the ordering user operates either the operation button 152 or the operation button 153 to respond as to whether or not to place the order.

[0142] When the order receiving unit 314 receives an operation of the operation button 153 from the store terminal 10 that placed the order, it erases the confirmation screen 150 and returns the screen to the common product menu screen 130. On the other hand, when the order receiving unit 314 receives an operation of the operation button 152 from the store terminal 10 that placed the order, it cooperates with the GUI providing unit 313 to cause the display unit 16 of the store terminal 10 to display a prepayment screen 160 for making payment for the product price.

[0143] Fig. 19 is a diagram showing another example of a screen displayed on the store terminal 10. Fig. 19 shows an example of a prepayment screen 160. As shown in Fig. 19, the prepayment screen 160 displays a total price 156 of the products to be paid by the ordering user. This total price 161 is calculated by adding up the unit prices of the products selected by the operation button 133.

[0144] In addition, the advance payment screen 160 displays a first payment method 162 using code payment and a second payment method 163 using payment information as information to guide the payment method of the product. The first payment method 162 and the second payment method 163 are the same as the first payment method 1273 and the second payment method 1274 described above, and it is possible to pay for the product using either one of them.

[0145] When payment for the product is completed using either the first payment method 162 or the second payment method 163, the order receiving unit 314 notifies the store server of the order destination store SP of the order information in the same manner as described above. The order receiving unit 314 also registers the order history information with the payment completion flag set to "1" in the order management table 355.

[0146] Note that even when the ordering user places an order using the treat button 135 (treat order), the order receiving unit 314 may be configured to check whether the order is acceptable to the ordering user. In this case, it is preferable that the order receiving unit 314 displays the confirmation screen 150 of FIG. 18 on the store terminal 10 of the ordering user, and after receiving an instruction to execute the order, checks whether the ordering user is acceptable to accept. Furthermore, it is preferable that the order receiving unit 314, after receiving the confirmation of the order-receiving user's acceptance, displays the advance payment screen 160 including the total amount 161 reflecting the confirmation result on the store terminal 10 of the ordering user.

[0147] Returning to Fig. 14, the general menu screen 115 has a checkout button 1153 which instructs checkout. When the checkout processing unit 315 accepts operation of the checkout button 1153 from the store terminal 10, it executes checkout processing for the ordered items based on the order history information of the corresponding reservation ID registered in the order management table 355. The reservation ID can be identified from the terminal ID etc. of the store terminal 10 where the checkout button 1153 was operated.

[0148] Specifically, the accounting processor 315 calculates the total product price as the total payment amount based on the remaining order history information, excluding order history information with a paid flag of "1" from the order history information associated with the corresponding reservation ID. The accounting processor 315 also calculates the total amount for each user (user ID) based on the user ID of the order destination user recorded in the remaining order history information. The accounting processor 315 also calculates the split amount by dividing the total payment amount by the number of users belonging to the same group. The accounting processor 315 also derives the total product price calculated based on order history information with a paid flag of "1" as the paid amount.

[0149] The accounting processing unit 315 then cooperates with the GUI provision unit 313 to display the accounting screen 170 on the display unit 16 of the store terminal 10 operated by each user who participated in the remote drinking party.

[0150] FIG. 20 is a diagram showing another example of a screen displayed on the store terminal 10. FIG. 20 shows an example of the display of a checkout screen 170. As shown in FIG. 20, the checkout screen 170 displays first information 171 indicating the total amount to be paid for the products and the remaining balance. The checkout screen 170 also displays second information 172 indicating the amount that has been paid. Note that when the checkout screen 170 is displayed, no payment has been made, so the total amount to be paid and the remaining balance displayed in the first information 171 are the same.

[0151] The accounting screen 170 also displays a total amount 173 calculated for each user. The total amount 173 is displayed, for example, in association with a user name. Here, the user name "me" refers to the user (user C) who is operating the store terminal 10. The accounting screen 170 also displays a split amount 174.

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

[0153] Additionally, the accounting screen 170 is provided with an individual button 175 and a split-the-bill button 176 as operators for specifying the payment method. The individual button 175 is provided for each user, and is used when the user wishes to pay an arbitrary amount (hereinafter also referred to as "individual payment").

[0154] Specifically, when the transaction processing unit 315 receives an operation of an individual button 175 from the store terminal 10, it cooperates with the GUI providing unit 313 to cause the display unit 16 of the store terminal 10 to display an amount input screen 180.

[0155] FIG. 21 is a diagram showing another example of a screen displayed on the store terminal 10. FIG. 21 shows an example of the display of an amount input screen 180. As shown in FIG. 21, the amount input screen 180 is provided with operation buttons 181 such as numeric keys, and a display area 182. When a user of the store terminal 10 inputs a desired amount via the operation buttons 181, the input amount is displayed in the display area 182. The clear button included in the operation buttons 181 is an operator for clearing the input amount. Furthermore, the full amount button included in the operation buttons 181 is an operator for inputting the remaining amount displayed on the checkout screen 170.

[0156] The amount input screen 180 also has an OK button 183 and a cancel button 184. When the transaction processing unit 315 accepts operation of the cancel button 184 from the store terminal 10, it closes the amount input screen 180 and displays the transaction screen 170 again.

[0157] Furthermore, when the accounting processor 315 accepts the operation of OK 183 from the store terminal 10, it sets the amount entered in the display area 182 as the payment amount (payment amount) of the user of the store terminal 10. Then, as shown in Figure 22, the accounting processor 315 displays the accounting screen 170 with the updated first information 171 etc. on the display units 16 of the store terminals 10 operated by each user in the same group.

[0158] FIG. 22 is a diagram showing another example of a screen displayed on the store terminal 10. FIG. 22 shows the state of the accounting screen 170 described in FIG. 20 after it has been updated. As shown in FIG. 22, the accounting screen 170 displays input amount information 178 indicating the payment amount entered on the amount input screen 180 in association with the username (individual button 175) of the user who performed the input operation. Additionally, the remaining balance in the first information 171 is updated to a value obtained by subtracting the payment amount indicated by the input amount information 178 from the total payment amount.

[0159] Furthermore, the split amount obtained by dividing the updated remaining amount by the number of users who have not yet input an amount on the amount input screen 180 is displayed as a reference value 179. In Fig. 22, since three users, User A, User B, and User D, have not yet input an amount, the remaining amount of "6000 yen" divided by the three users, resulting in "2000 yen", is displayed as the reference value 179.

[0160] On the other hand, the "Split the Bill" button 176 is used when each user pays an equal amount (hereinafter also referred to as "Split the Bill payment"). When the accounting processor 315 accepts the operation of the "Split the Bill" button 176, it sets the split amount displayed on the accounting screen 170 as the amount to be paid by each user.

[0161] For example, when the Split the Bill button 176 is operated on the accounting screen 170 shown in Fig. 20, the accounting processor 315 sets the payment amount for each of users A, B, C, and D to 4,000 yen. Also, when the Split the Bill button 176 is operated on the accounting screen 170 shown in Fig. 22, the accounting processor 315 sets the payment amount for each of users A, B, and D who have not yet entered an amount to 2,000 yen, as shown in the reference value 179.

[0162] Furthermore, when the balance becomes "0", the accounting processor 315 activates the payment button 177 located at the bottom right of the screen so that it can be operated. The payment button 177 is an operator for instructing the execution of accounting.

[0163] When the accounting processor 315 accepts operation of the payment button 177 from any of the store terminals 10 operated by users A-D, it executes accounting processing to pay the payment amount set for each user using the payment information of that user. Specifically, the accounting processor 315 executes accounting processing to pay the amount of the products ordered at each store SP used by each user.

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

[0165] In addition, when the end date and time of the reservation date and time is reached, the reservation reception unit 311 (or the accounting processing unit 315, etc.) may work in cooperation with the GUI provision unit 313 to display an end notification screen (see Figure 23) on the display unit 16 of the store terminal 10 operated by each user to notify that the end date and time has been reached.

[0166] Figure 23 is a diagram showing another example of a screen displayed on the store terminal 10. Figure 23 shows, as an example of an end notification screen, a message 116 notifying that the end date and time has been reached, superimposed on the main screen 110. In this case, a checkout button 117 similar to the checkout button 1153 described above can be displayed on the end notification screen (main screen 110) to smoothly encourage the user to move on to checkout processing.

[0167] An example of the operation of the above-mentioned server device 30 will be described below with reference to the flowcharts of FIGS.

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

[0169] First, when participation information including the user ID of the user who operates the store terminal 10, the reservation ID of the remote drinking party, etc. is transmitted from the store terminal 10 of the store SP, 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 354 and identifies reservation information that meets the conditions of the participation information (step S12).

[0170] Next, 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, and determines 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 store terminal 10 (step S14), and returns the process to step S13.

[0171] Furthermore, 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 shop terminal 10 (Step S15).

[0172] Next, the inter-terminal communication unit 312 waits until a start instruction is received from the store terminal 10 (step S16; No). When the inter-terminal communication unit 312 receives the start instruction from the store terminal 10 (step S16; Yes), the inter-terminal communication unit 312 establishes communication between the store terminal 10 that transmitted the participation information and the store terminals 10 of other users registered in the reservation information (step S17), and starts data sharing between the store terminals 10 (step S18).

[0173] Then, the GUI providing unit 313 provides the main screen 110 to the shop terminal 10 that transmitted the participation information (step S19), and ends this process.

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

[0175] Fig. 25 is a flowchart showing an example of a menu providing process executed by the server device 30. Fig. 25 shows an example of a process of the server device 30 executed when the menu button 113 or the general menu button 114 is operated on the main screen 110 displayed on the display unit 16 of the shop terminal 10.

[0176] First, the GUI providing unit 313 receives a menu display instruction from the store terminal 10 via the above-mentioned menu button 113 or general menu button 114 (step S21). The GUI providing unit 313 determines whether the received display instruction is due to an operation of the menu button 113 or the general menu button 114 (step S22). Specifically, the GUI providing unit 313 determines whether an individual display method for displaying a menu for each store SP is to be used, or an overall display method for displaying a menu common to all stores SP is to be used.

[0177] Here, if it is determined that a display instruction has been given by the menu button 113, that is, an individual display method for each store SP has been instructed (step S22; Yes), the GUI providing unit 313 identifies the store ID of the store SP specified as the target for displaying the menu (step S23). For example, the GUI providing unit 313 identifies the store ID of the store SP specified as the target for displaying the menu from information on the store ID assigned to the operated menu button 113, etc.

[0178] Next, the GUI providing unit 313 reads out the menu information of the shop ID identified in step S23 from the menu management table 352, and provides the menu screen 120 based on the menu information to the shop terminal 10 (step S24), and ends this process.

[0179] Furthermore, if it is determined in step S22 that a display instruction has been issued using the general menu button 114, that is, an instruction to display the entire store SP has been issued (step S22; No), the GUI providing unit 313 identifies the store ID of the store SP used by each user based on reservation information, etc. (step S25). Next, the GUI providing unit 313 extracts product information of products with a common generic name from the menu information corresponding to each store ID identified in step S25 (step S26).

[0180] Then, the GUI providing unit 313 provides the common product menu screen 130, which displays the product information extracted in step S26 for each store SP (for each user), to the store terminal 10 (step S27), and ends this process.

[0181] The server device 30 can display the menu screen 120 or the common product menu screen 130 on the display unit 16 of the store terminal 10 by performing the above-mentioned processing.

[0182] Fig. 26 is a flowchart showing an example of an order process executed by the server device 30. Fig. 26 shows an example of a process when an order operation based on the menu screen 120 or the common product menu screen 130 is received from the store terminal 10.

[0183] First, the order receiving unit 314 receives an order operation for a product from the store terminal 10 (step S31). Next, the order receiving unit 314 judges 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 judges that the user has ordered a product to be consumed by himself / herself. In this case, the order receiving unit 314 notifies the order recipient store SP of the order contents (product ID, orderer user ID, 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 355 (step S34), and ends this process.

[0184] Furthermore, if it is determined in step S32 that the two user IDs are different (step S32), the order receiving unit 314 determines whether or not a method in which the user who placed the order pays for the product (treat) has been instructed (step S35).

[0185] If the payment method is specified by the order destination user (step S35; No), the order receiving unit 314 displays a confirmation screen for confirming the order contents on the store terminal 10 operated by the order destination user (step S36). Next, the order receiving unit 314 waits until it receives the confirmation result from the order destination user.

[0186] If a reply to reject the order is received (step S37; 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 that to the store terminal 10 operated by the user who placed the order.

[0187] If an agreement to accept the order details is received in step S37 (step S37; Yes), the order receiving unit 314 notifies the order details (product ID, order destination user ID, etc.) to the order destination store SP (step S38).The order receiving unit 314 also registers the order history information including the received order details in association with the corresponding reservation ID in the order management table 355 (step S39), and ends this process.

[0188] On the other hand, if a payment method by the ordering user is specified in step S35 (step S35; Yes), the order receiving unit 314 causes the store terminal 10 operated by the ordering user to display a confirmation screen for confirming the order details (step S40). The order receiving unit 314 also causes the store terminal 10 operated by the order destination to display a confirmation screen for confirming the order details (step S41). The order receiving unit 314 then waits until it receives confirmation results from each user.

[0189] If a reply to reject the order is received from either or both of the order originating user and the order destination user (step S42; No), the order receiving unit 314 ends this process without placing an order for the product. Note that if the order destination user rejects the order, the order receiving unit 314 may provide result information indicating this to the store terminal 10 operated by the order originating user.

[0190] Furthermore, 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 items based on the ordering user's payment information, etc. (step S43).

[0191] Next, the accounting processor 315 notifies the order recipient store SP of the order details (product ID, order recipient user ID, etc.) (step S44). The order receiving unit 314 also registers the order history information including the received order details in association with the corresponding reservation ID in the order management table 355 (step S45). The accounting processor 315 then sets the paid flag of the order history information registered in step S45 to "1" (paid) (step S46), and ends this process.

[0192] By performing the above processing, the server device 30 can place an order for a product with the order destination store SP by switching between a method in which the ordering user pays the price and a method in which the order destination user pays the price, depending on the order operation from the store terminal 10.

[0193] Figure 27 is a flowchart showing an example of a transaction process executed by the server device 30. In Figure 27, it is assumed that the order history information related to the order accepted from the store terminal 10 has already been registered in the order management table 355.

[0194] First, the reservation reception unit 311 judges 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 354 (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 terminal ID associated with that reservation ID (step S52) and proceeds to step S53. Also, if it is judged that there is no reservation ID whose end date and time has been reached (step S51; No), the reservation reception unit 311 proceeds to step S53.

[0195] 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 1153 or the accounting button 117 (step S53). If an instruction to pay has not been accepted (step S53; No), the accounting processor 315 returns the process to step S51.

[0196] Furthermore, if a payment instruction is accepted in step S53 (step S53; Yes), the payment processor 315 calculates the total payment amount based on the remaining order history information related to the reservation ID of the payment target, excluding order history information with a paid flag of "1" (step S54). Next, the payment processor 315 provides a payment screen 170 to each of the store terminals 10 related to the reservation ID of the payment target, based on the calculation results of step S54, etc. (step S55).

[0197] Next, when the accounting processing unit 315 receives an operation to specify a payment method from any of the store terminals 10 that provided the accounting screen 170 (step S56), it determines whether the specified payment method is "individual payment" or "split payment" (step S57).

[0198] Here, 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.

[0199] On the other hand, if the specified payment method is split payment (step S57; No), the accounting processing unit 315 sets the split amount calculated by subtracting the payment amount from the total payment amount and dividing the result by the number of users who have not yet paid as the payment amount for that user (step S59), and proceeds to step S60.

[0200] In step S60, the accounting processor 315 determines whether the balance obtained by subtracting the payment amount from the total payment amount is zero (step S60). If the balance is not zero (step S60; No), the process returns to step S55, and an accounting screen with updated balance and other information is provided to the store terminal 10.

[0201] Furthermore, if it is determined in step S60 that the balance is zero (step S60; Yes), the accounting processing unit 315 executes accounting processing to pay the payment amount set for that user to each store SP using the payment information for that user (step S61), and terminates this processing.

[0202] Here, Figure 28 is a diagram illustrating an example of the operation of the transaction processing executed by the transaction processing unit 315. Figure 28 shows a schematic diagram of a case in which users A to D each use stores A to D, respectively.

[0203] More specifically, it is assumed that the total amount of the products consumed by user A at store A is 4920 yen, the total amount of the products consumed by user B at store B is 5080 yen, the total amount of the products consumed by user C at store C is 3020 yen, and the total amount of the products consumed by user D at store D is 2980 yen. It is also assumed that each user pays a flat amount of 4000 yen by splitting the bill.

[0204] In this case, the accounting processor 315 uses the payment information of each of users A to D to execute accounting processing to pay the total amount for food and drink to each of stores A to D. First, the accounting processor 315 uses the payment information of each individual user to execute accounting processing to pay the amount due to the store SP used by that user. At this time, if the total amount at the store SP is less than the payment amount, the accounting processor 315 executes accounting processing to pay the total amount.

[0205] For example, in the case of user A, the total amount (4920 yen) at store A is equal to or greater than the payment amount (4000 yen). In this case, the accounting processor 315 executes processing to pay the payment amount to store A using the payment information of user A. In the case of user B, the total amount (5080 yen) at store B is equal to or greater than the payment amount (4000 yen). In this case, the accounting processor 315 executes processing to pay the payment amount to store B using the payment information of user B. Also, for example, in the case of user C, the total amount (3020 yen) at store C is less than the payment amount (4000 yen). In this case, the accounting processor 315 executes processing to pay the total amount to store C using the payment information of user C. Also, for example, in the case of user D, the total amount (2980 yen) at store D is less than the payment amount (4000 yen). In this case, the accounting processor 315 executes processing to pay the total amount to store D using the payment information of user D.

[0206] In addition, in the above payment, there may be cases where the total payment amount is not reached at some stores. For example, at store A, the payment amount of user A is insufficient by 920 yen. At store B, the payment amount of user B is insufficient by 1080 yen.

[0207] Therefore, the accounting processing unit 315 executes a process to compensate for the shortfall that occurred at store A and store B using the payment information of users C and D, who paid the total amount in the previous accounting process.

[0208] For example, the accounting processing unit 315 executes processing to pay 920 yen to store A and 60 yen to store B based on the 980 yen difference between the 3,020 yen that user C paid to store C and the payment amount of 4,000 yen.Furthermore, for example, the accounting processing unit 315 executes processing to pay 1,020 yen to store A based on the 1,020 yen difference between the 2,980 yen that user D paid to store D and the payment amount of 4,000 yen.

[0209] This makes it possible to compensate for the shortage that occurred at the store A and the store B. Therefore, the server device 30 can pay the prices of the products ordered at the remote drinking party to each of the order destination stores SP.

[0210] The accounting method (payment method) executed by the accounting processor 315 is not limited to the example shown in FIG. 28. For example, the payment information of users A to D may be used to make payments in order starting from store A to fill the total amount. In this case, the payment amount of user A's payment of 4000 yen leaves a shortfall of 920 yen in store A, so the payment of 920 yen is made to store A using the payment information of the next user B. Next, a process is executed to pay the remaining amount of 3080 yen, which is the amount obtained by subtracting the previously paid 920 yen from the payment amount of user B's payment of 4000 yen, to store B. Then, if a shortfall occurs, the payment information of the next user is used to make up the shortfall, so that the prices of the products ordered at the remote drinking party can be paid to each of the stores SP where the orders were placed, as described above.

[0211] As described above, when the server device 30 receives access from each of the store terminals 10 provided in a plurality of stores SP, the server device 30 manages the store SP and store terminal 10 from which the access originates, in association with the user operating the store terminal 10. The server device 30 also connects the store terminals 10 of users belonging to the same group so that they can communicate with each other, and provides menu information indicating products that can be provided at the store SP to which the store terminal 10 belongs, so that the menu information can be viewed by the store terminals 10 that are communicatively connected with each other. Then, when the server device 30 receives an order for a product from any of the store terminals 10 to which the menu information has been provided, the server device 30 notifies the store SP that provides the product of information regarding the ordered product.

[0212] In this way, the server device 30 can support the ordering method in which users belonging to the same group order products that they themselves will eat and drink, and can also support the ordering method in which other users order products that they will eat and drink. Therefore, the server device 30 can improve the convenience of the remote food and drink provision service that uses multiple stores.

[0213] In addition, the server device 30 extracts menu information of products common to each of the stores SP from the menu information of the stores SP to which each of the communicatively connected store terminals 10 belongs, and provides the extracted menu information so that it can be viewed by the store terminals 10 belonging to the same group.

[0214] In this way, for example, when all users participating in a remote drinking party order a common product such as beer, the server device 30 can support the operation related to the order. Therefore, the server device 30 can improve the convenience of the remote food and drink provision service using multiple stores.

[0215] In addition, each time the server device 30 receives an order for a product, it identifies the user who placed the order and the user who will receive the ordered product, and if the two identified users are different, it provides a confirmation screen to one or both of the users who placed the order and the user who will receive the ordered product to confirm the order details.

[0216] As a result, when an order for a product that another user will consume is made, the server device 30 can have the ordering user check whether or not the order was made by mistake, thereby preventing the occurrence of ordering mistakes, etc. In addition, the server device 30 can give the ordering user an opportunity to decide whether or not to accept the order, thereby preventing an order from being made carelessly.

[0217] The server device 30 also performs accounting to pay the price of the ordered products to the store that provides the products. The server device 30 also performs accounting for the ordered products based on an amount obtained by dividing the price of the ordered products by the number of users belonging to the same group, or on an amount to be paid designated by each user.

[0218] This allows the server device 30 to handle everything from ordering to paying for products in a remote drinking party using multiple stores SP. The server device 30 can also pay for products using a payment method based on an even split amount and a payment method based on an individually specified payment amount. Therefore, the server device 30 can improve the convenience of a remote food and drink provision service using multiple stores.

[0219] The above-described embodiment can be modified as appropriate by changing a part of the configuration or function of each of the above-described devices. Therefore, some modified examples of the above-described embodiment will be described below as other embodiments. Note that the following mainly describes the differences from the above-described embodiment, and a detailed description of the common points with the contents already described will be omitted. The modified examples described below may be implemented individually or in appropriate combination.

[0220] (Variation 1) In the above embodiment, a case has been described in which each user participating in a remote drinking party uses a different store SP and a different store terminal 10. However, the form of a remote drinking party is not limited to this, and the above-mentioned server device 30 can also handle a case in which a plurality of users use the same store SP and the same store terminal 10 in the same manner.

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

[0222] Furthermore, when the inter-terminal communication unit 312 of the server device 30 receives a plurality of user IDs from a store terminal 10 having the same terminal ID, it registers these plurality of user IDs in the reservation information in association with the same terminal ID.

[0223] In addition, when the GUI providing unit 313 of the server device 30 receives, for example, an operation of the second operation button 1152, it causes the display unit 16 of the store terminal 10 where the operation was performed to display a common product menu screen 200 that enables the user to confirm that multiple users exist in the same store SP.

[0224] Fig. 29 is a diagram showing an example of a screen displayed on the store terminal 10 of this modified example. Fig. 29 shows a display example of a common product menu screen 200. As shown in Fig. 29, the common product menu screen 200 has a screen configuration similar to that of the above-mentioned common product menu screen 130. In addition, the common product menu screen 200 indicates that user D and user E who are present in the same store SP (store D) are present in the same store by surrounding them with a dashed line 201.

[0225] Note that there is no particular restriction on the ordering method for user D and user E. For example, when user D or user E places an order for a product, the GUI providing unit 313 may display a screen for selecting whether user D or user E is to be the order destination (order originator). Also, for example, when a product to be ordered is selected for a user ID of a user other than user D and user E, the GUI providing unit 313 may display a screen for selecting whether user D or user E is to be the order originator.

[0226] In addition, when the accounting processing unit 315 of the server device 30 receives, for example, an operation of the accounting button 1153, it displays, on the display unit 16 of the store terminal 10 operated by each user, an accounting screen 210 that enables the user to confirm that multiple users exist in the same store SP.

[0227] Fig. 30 is a diagram showing another example of a screen displayed on the store terminal 10 of this modified example. Fig. 30 shows an example of the display of a checkout screen 210. As shown in Fig. 30, the checkout screen 210 has the same screen configuration as the checkout screen 170 described above. Furthermore, the checkout screen 210 indicates that users D and E, who are in the same store SP (store D), are both in the same store by encircling them with a dashed line 211. Note that the checkout process is the same as in the embodiment described above, so a description thereof will be omitted.

[0228] As described above, the server device 30 of this modified example can achieve the same effects as those of the above-described embodiment even when a plurality of users use the same store SP.

[0229] (Variation 2) In the above embodiment, a remote food and drink providing service (remote drinking party) is performed using the store terminal 10 of the store SP, but the store terminal 10 is not limited to the store terminal 10, and for example, a user terminal 20 may be used. In this case, for example, the user terminal 20 functions as an input / output interface of the server device 30 in the same way as the above-mentioned store terminal 10 by connecting to the server device 30 in the store SP.

[0230] This makes it possible to achieve the same effect as the above-described embodiment, thereby improving the convenience of remote food and beverage provision services that utilize multiple stores, even when using a user terminal 20.

[0231] The programs executed by each device of 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 of the above-described embodiments may be provided by being recorded in a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD) in the form of an installable or executable file.

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

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

[0234] 1. Remote food and beverage supply system 10 Store terminal 20 User terminal 30 Server device 311 Reservation Reception 312 Terminal Communication Unit 313 GUI provision department 314 Order Reception Department 315 Accounting Department [Prior art documents] [Patent documents]

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

Claims

1. a management means for receiving access from each of terminals installed in a plurality of stores, and managing the store and terminal from which the access originates in association with a user who operates the terminal; 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 a screen displaying, for each store, menu information of products that are common to each of the stores among menu information that indicates products that can be provided in the stores to which each of the terminals communicably connected by the communication control means belongs, so that the screen can be viewed on each of the terminals; 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 provides the product of information regarding the ordered product; Equipped with When an order source user of the terminal that placed the order is different from an order destination user of the store that provides the ordered product, the order receiving means checks with the terminal of the order destination user whether or not the order can be accepted, and notifies information about the ordered product to the store of the terminal that has been instructed to accept the order, The providing means is a server device that displays, on the screen provided to the terminal of the ordering user, the confirmation result of the acceptance of the ordering user in association with the menu information of the store to which the ordering user belongs.

2. 2. The server device according to claim 1, further comprising an accounting unit that executes an accounting process for paying the price of the product accepted by said order acceptance unit to a store that provides the product.

3. The server device according to claim 2, wherein the accounting means executes the accounting process based on a payment amount obtained by dividing the price of the product accepted by the order accepting means by the number of users belonging to the same group, or a payment amount individually specified by any of the users belonging to the same group.

4. The computer of the server device, a management means for receiving access from each of terminals installed in a plurality of stores, and managing the store and terminal from which the access originates in association with a user who operates the terminal; 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 a screen displaying, for each store, menu information of products that are common to each of the stores among menu information that indicates products that can be provided in the stores to which each of the terminals communicably connected by the communication control means belongs, so that the screen can be viewed on each of the terminals; 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 provides the product of information regarding the ordered product; and make it work. When an order source user of the terminal that placed the order is different from an order destination user of the store that provides the ordered product, the order receiving means checks with the terminal of the order destination user whether or not the order can be accepted, and notifies information about the ordered product to the store of the terminal that has been instructed to accept the order, The providing means is a program that displays, on the screen provided to the terminal of the ordering user, the confirmation result of the acceptance of the ordering user in association with the menu information of the store to which the ordering user belongs.

Images