Meal service provision support system

Abstract

To enable a user to reserve and order optional meal service without going to eating and drinking facilities, to optionally set the reception place and reception time of the meal service, to eliminate the need of settlement processing through cash and a card or the like, to dissolve the congestion of the eating and drinking facilities and to effectively evade the concentration of users and contact between persons.SOLUTION: The support system 1 includes a delivery service division 10A and a mobile check service division 10B, each of which includes a menu selection information generating means for generating menu selection information which is displayed on user-operable user terminals 40 and which selectably indicates contents of a meal service which can be provided and a providing place, and a use information generating means for generating predetermined use information when the meal service prepared corresponding to the menu selection information is received at the providing place, and a settlement processing unit 11 for executing predetermined settlement processing based on the use information.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to technology for supporting the provision and operation of various meal services such as set meals, a la carte dishes, lunch menus, take-out bento boxes, and takeout menus provided at various eating and drinking establishments, such as cafeterias for students (school cafeterias) in universities, cafeterias for employees in companies (corporate cafeterias), cafeterias run by businesses, and food courts in commercial facilities. [Background technology]

[0002] Generally, dining facilities such as cafeterias for students (school cafeterias) operated within universities and cafeterias for employees (corporate cafeterias) within companies offer a variety of meal services every day, including set meals, a la carte dishes, lunch menus, takeaway bento boxes, and takeout menus. In places where this type of meal service is provided, customers tend to gather at lunchtimes, and problems have been pointed out, particularly in cafeteria-style eating and drinking establishments such as school cafeterias and company cafeterias, where customers have to wait in long lines to receive their meal service, have to wait to pay, and take a long time to finally receive their meal. In addition, especially in recent years, from the perspective of preventing viral infections, it has become desirable to provide safe and comfortable meal services that minimize crowding and human contact, and new initiatives and improvements are being called for in cafeteria-style dining facilities such as university cafeterias.

[0003] Technologies for supporting the provision of meal services in such eating and drinking establishments are proposed in, for example, Patent Document 1 and Patent Document 2. Patent document 1 proposes a "payment system" that enables customers to quickly and reliably confirm and pay for the menu they have selected in a self-service employee cafeteria or the like by attaching an RFID tag to each of the multiple dishes (menus) that they pick up. Patent Document 2 proposes a "restaurant management system" that attaches IC tags to tableware in employee cafeterias, reads the data on the IC tags to automatically calculate the total amount, and automatically settles the bill at a cash register using an IC card held by the customer, thereby preventing eating and drinking without paying and enabling smooth, unmanned checkout. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-102563 [Patent Document 2] Japanese Patent Application Laid-Open No. 2004-145470 Summary of the Invention [Problem to be solved by the invention]

[0005] However, all of the technologies proposed to date to support the provision of meal services, including the systems disclosed in Patent Documents 1 and 2, are limited to automating and unmanning payment and settlement, and there is room for further improvement, particularly in terms of eliminating congestion when receiving meal services at food and beverage establishments, the concentration of users at certain times of the day, and new measures to avoid contact between people.

[0006] The present invention has been proposed to solve the above-mentioned problems, and aims to provide a meal service provision support system that allows users to reserve and order any meal service without going to the food and beverage facility, and can freely set the location and time for receiving the meal service, without the need for payment processing via cash or card, thereby alleviating congestion at the food and beverage facility and effectively avoiding the concentration of users and contact between people, and is particularly suitable for cafeteria-style food and beverage facilities such as student cafeterias and employee cafeterias operated by universities and companies, and food courts in commercial facilities. [Means for solving the problem]

[0007] In order to achieve the above-mentioned object, the present invention is a support system for providing a specified meal service desired by a user at a specified location desired by the user, and comprises a usage information generation means for generating specified usage information indicating that the meal service provided to the user has been received at the meal service providing location, and a payment processing means for executing specified payment processing based on the usage information, wherein the usage information generation means is configured to generate the usage information based on image data of the actual menu received by the user, which is photographed on a user terminal that the user can operate.

[0008] Furthermore, the present invention can be configured as a program executed in the meal service provision support system according to the present invention as described above. Furthermore, the present invention can also be implemented as a method that can be implemented by the meal service provision support system and program according to the present invention as described above. [Effects of the Invention]

[0009] According to the present invention, users can reserve and order any meal service without going to a food service facility, and can also set the location and time of collection of the meal service as they wish, eliminating the need for payment processing via cash or card, thereby alleviating congestion in food service facilities and effectively avoiding the concentration of users and contact between people. This makes it possible to provide a meal service provision support system, program, and method that is particularly suitable for cafeteria-style dining facilities such as student cafeterias and employee cafeterias operated by universities and companies, and food courts in commercial facilities. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is an explanatory diagram showing a schematic diagram of the overall configuration of a meal service provision support system (this system) according to one embodiment of the present invention. [Figure 2] FIG. 2 is a functional block diagram showing the configuration of each part in the system. [Figure 3] FIG. 2 is a functional block diagram showing the configuration of a delivery service unit of the present system. [Figure 4] This is an explanatory diagram that shows a schematic diagram of the flow of data between the delivery service unit of this system and the user terminal and store terminal. [Figure 5] FIG. 2 is a functional block diagram showing the configuration of the mobile check service unit of the present system. [Figure 6] This is an explanatory diagram that shows a schematic diagram of the data flow between the mobile check service unit of this system and the user terminal and store terminal. [Figure 7] FIG. 10 is a diagram showing a maintenance screen (input screen) for the product master of the present system. [Figure 8] FIG. 10 is a diagram showing a maintenance screen (input screen) for the delivery destination master data of the present system. [Figure 9] FIG. 10 is a diagram showing a maintenance screen (input screen) for the order information master of the present system. [Figure 10] 1A and 1B are diagrams showing maintenance screens (input screens) for the reservation reception information master of the present system, where (a) shows the input screen for performance management information, and (b) shows the input screen for registration information. [Figure 11] This is an explanatory diagram that schematically shows the concept of "delivering lunch boxes" in the delivery service section of this system. [Figure 12] FIG. 10 is an explanatory diagram illustrating the concept of an "off-store pickup location" in the delivery service section of the system. [Figure 13] FIG. 1 is an explanatory diagram that schematically illustrates the concept of "congestion relief" by the delivery service unit of the present system. [Figure 14] FIG. 1 is an explanatory diagram showing a schematic diagram of the "systemized area" of the delivery service department of the present system. [Figure 15] FIG. 2 is an explanatory diagram illustrating a process flow in the delivery service unit of the present system. [Figure 16] FIG. 10 is an explanatory diagram showing the transition of the display screen of the user terminal during processing by the delivery service unit of the system. [Figure 17]FIG. 1 is an explanatory diagram showing a schematic overview of the "usage flow" in the mobile check service section of the present system. [Figure 18] FIG. 2 is an explanatory diagram showing a schematic flow of processing in the mobile check service unit of the present system. [Figure 19] Continuing from FIG. 18, this is an explanatory diagram schematically showing the flow of processing in the mobile check service unit of this system. [Figure 20] An explanatory diagram showing the transition of the display screen of a user terminal during processing by the mobile check service unit of this system. [Figure 21] This is an explanatory diagram that shows a modified example of the processing in the mobile check service unit of the present system, and is an example of "product selection and confirmation using QR / barcode." [Figure 22] FIG. 10 is an explanatory diagram showing a modified example of the processing in the mobile check service unit of the present system, and is an example of "completion of use by photographing a meal image." [Figure 23] This is an explanatory diagram that shows a schematic diagram of a modified example of the processing in the mobile check service section of this system, and is an example of "real-time reservations / contactless ordering between users and stores." [Figure 24] FIG. 10 is an explanatory diagram showing a modified example of the processing in the delivery service section / mobile check service section of the present system, and is an example of "checking congestion status using a user terminal." [Figure 25] This is an explanatory diagram that shows a schematic diagram of a modified example of the processing in the delivery service section / mobile check service section of this system, and is an example of "visualization of nutritional value information / distribution of recommended menus and coupons." [Figure 26] This is an explanatory diagram that shows a modified example of the processing in the delivery service section / mobile check service section of this system, and is an example of ``visualizing nutritional value information to people other than the person concerned.'' [Figure 27] This is an explanatory diagram that shows a modified example of the processing in the delivery service section / mobile check service section of the present system, and is an example of "adding barrier-free information for various foods." [Figure 28] FIG. 10 is an explanatory diagram showing a modified example of the processing in the delivery service section / mobile check service section of the present system, and is an example of "order handling by voice." [Figure 29] This is an explanatory diagram that shows a modified example of the processing in the delivery service section / mobile check service section of the present system, and is an example of "audio-based meal response." [Figure 30] FIG. 10 is an explanatory diagram showing a modified example of the processing in the delivery service section / mobile check service section of the present system, and is an example of the "feedback function to the user." DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of a meal service provision support system according to the present invention will be described with reference to the drawings. The meal service provision support system (this system) of the present invention described below is realized by processes, means, and functions executed by a computer in accordance with instructions from a program (software). The program sends commands to each component of the computer, causing it to perform the specified processes, functions, etc. described below according to the present invention. In other words, each process, means, and function in the present invention is realized by specific means in which the program and the computer work together.

[0012] The whole or part of the program may be provided on a computer-readable recording medium, such as a magnetic disk, optical disk, semiconductor memory, or any other suitable medium, and the program may be read from the recording medium, installed on a computer, and executed. Alternatively, the program may be directly loaded onto a computer via a communication line and executed without using a recording medium. Furthermore, this system can be configured with a single information processing device (for example, one personal computer, etc.), or can be configured with multiple information processing devices (for example, a group of multiple server computers, etc.).

[0013] The hardware configuration of this system, although not specifically illustrated, is composed of information processing devices including a CPU, RAM, ROM, HDD, input device, display device, etc. These components are connected by a system bus, through which data is exchanged. The CPU (Central Processing Unit), also known as the central processing unit, is the central processing part of the computer, controlling each device and calculating / processing data. RAM (Random Access Memory) is a type of memory device that allows data to be erased and rewritten. ROM (Read Only Memory) is a type of memory device that uses semiconductors, etc., and data is written only once during manufacturing and can only be read when used. HDD (Hard Disk Drive) is an auxiliary storage device that uses the properties of magnetic materials to record and read information. The input device is used by users to give operating instructions to the computer or to input characters, etc., and specifically consists of a keyboard, mouse, etc. The display device is composed of, for example, an LCD display, and may have a touch panel function. In addition, the computer may also be equipped with communication functions that enable communication with other terminals, information processing devices, etc.

[0014] [System Configuration] As shown in Figure 1, a meal service provision support system 1 (hereinafter referred to as "this system 1") according to one embodiment of the present invention is configured to include a meal service provision support server 10, one or more user terminals 40 (40a to 40n), and one or more store terminals 50 (50a to 50n). The meal service provision support server 10, user terminal 40, and store terminal 50 are connected via the Internet 100, which includes networks such as LAN and WAN, and are capable of mutual data communication.

[0015] Here, the meal service provision support server 10, the user terminal 40, and the store terminal 50 can be configured by information processing devices belonging to different organizations, companies, etc. In this case, meal service provision support server 10 is configured as an information processing device operated by a company that provides services to customers, such as those that operate school cafeterias or corporate cafeterias, using this system 1 as a service. User terminal 40 and store terminal 50 are then configured as information processing devices provided at one or more universities, companies, organizations, businesses, etc. that receive support for meal service provision via this system 1. Therefore, in this case, the user terminal 40 and the store terminal 50 will function as external devices connected to the present system 1 via a network, and the present system 1 will be composed only of the meal service provision support server 10.

[0016] On the other hand, the meal service provision support server 10, the user terminal 40, and the store terminal 50 may be configured by information processing devices belonging to the same organization, company, business, or the like. In this case, the system 1 will be composed of three components: a meal service provision support server 10, a user terminal 40, and a store terminal 50, and the system 1 will function as an internal system operated, for example, by the same university, company, organization, business operator, etc.

[0017] [Meal service provision support server] The meal service provision support server 10 is an information processing device that serves as the core of the system 1, for providing the specified meal service desired by the user at the specified location desired by the user, and constitutes the meal service provision support system of the present invention. This meal service provision support server 10 can be configured, for example, by an information processing device on which a predetermined program (software) is implemented, such as one or more server computers, personal computers, or a server system consisting of one or more virtual servers built on a cloud computing service.

[0018] The meal service provision support server 10 is also equipped with an OS (Operating System) and a DBMS (DataBase Management System), not shown, and is operated as a server computer. The meal service provision support server 10 is configured to have software that runs on middleware such as a web server program installed. This software publishes and provides applications that can be used in the form of, for example, an API (Application Programming Interface) to one or more user terminals 40 and store terminals 50 via a network such as the Internet 100 .

[0019] As a result, each user terminal 40 and store terminal 50 can log in by calling up a dedicated application program or web browser operated to support the provision of meal services executed by the meal service provision support server 10, and can use and execute the functions of the meal service provision support system of the present invention, such as the generation process of specified menu selection information that selectably indicates the contents and locations of meal services that can be provided by the store terminal 50, the generation process of usage information when a meal service prepared in accordance with the menu selection information is received, and specified payment processing based on the usage information.

[0020] In addition, the meal service provision support server 10 has a predetermined database (delivery service section 10A / mobile check service section 10B) for meal service provision support, and is equipped with a storage means in which various information necessary for operating the meal service provision support system of the present invention is accumulated and stored (see Figures 3 and 5). The storage means stores various information resources, such as user information and store information to be managed by this system 1, and specified user data and master data for identifying various meal services, as well as transaction data such as specified reservation acceptance information and usage information input and transmitted from each user terminal 40 and store terminal 50 described below, and necessary information is read out, stored, and updated as needed in accordance with the operation of this system 1.

[0021] The meal service provision support server 10 of this embodiment is configured to function as each of the following parts, as shown in Figure 2: a delivery service unit 10A, a mobile check service unit 10B, a payment processing unit 11, a reservation status information generation unit 12, and a usage history information generation unit 13. Each component that constitutes and functions as the meal service provision support server 10 will be specifically described below.

[0022] The delivery service unit 10A is a means (delivery service system) for executing and completing delivery services such as preparation, delivery, handover, and payment for the reserved meal service when the meal service provision location indicated in the reservation acceptance information generated and displayed on the user terminal 40 is one or more specified pick-up locations other than the store that provides the meal service (see Figures 3-4 and 11-16 described below).

[0023] The mobile check service unit 10B is a means (mobile check system) for executing and completing mobile check services such as preparing, serving, delivering, and paying for the selected meal service when the location where the meal service is provided, indicated in the menu selection information generated and displayed on the user terminal 40, is a store that provides the meal service (see Figures 5-6 and 17-20 described below).

[0024] Here, the meal services that are handled by the delivery service unit 10A include, for example, takeaway lunches and takeout menus prepared and served at eating and drinking facilities such as cafeterias for students at universities, cafeterias for employees at companies, cafeterias operated by businesses, and food courts in commercial facilities. In addition, the meal services that are handled by the mobile check service department 10B include meals, dishes, drinks, and side dishes such as set meals, a la carte dishes, and lunch menus that are prepared and served at eating and drinking facilities such as the above-mentioned school cafeterias, company cafeterias, and food courts. The specific configurations and functions of the delivery service unit 10A / mobile check service unit 10B will be described further below with reference to Figures 3-4 / Figures 5-6, and the specific processing operations with reference to Figures 11-16 / Figures 17-20.

[0025] The payment processing unit 11 is a means for executing a predetermined payment process based on usage information about a meal service when the meal service is provided to a user via the delivery service unit 10A / mobile check service unit 10B. In this system 1, a "canteen card payment" system that is stored and managed in association with the user terminal 40 can be used as the payment processing unit 11. The "Cafeteria Card Payment" system is a service that allows users to freely use cafeterias (stores) using a designated card, up to a daily limit, for a designated period (for example, one year) on a prepaid basis. This allows users, such as university students, to eat and pay without worrying about the amount of money they have on hand.

[0026] The payment processing unit 11 of this system 1 constitutes an automatic payment processing system that, when a user receives a meal service via a user terminal 40 based on user information registered in association with the user terminal 40, debits the amount indicated in the meal service usage information from the user's prepaid account (e.g., a prepaid account) and executes payment processing. This allows users of this system 1 to pay for meal services through automatic payment processing based on usage information generated and processed by this system 1, without having to pay in cash or present a credit card or IC card when using or receiving meal services.

[0027] Details of such a "canteen card payment" system are disclosed in "Canteen Card Payment Device" in Japanese Patent No. 4169749, which is held by the applicant of the present application as the patent owner. In addition, the payment processing unit 11 of this system 1 can also adopt payment methods and means other than the above-mentioned "cafeteria card payment" system, and can also use the configurations and functions of existing payment means, such as credit cards, IC cards, prepaid cards, and smartphone payments. The specific processing operations of the payment processing unit 11 as described above, along with the delivery service unit 10A and the mobile check service unit 10B, will be described later with reference to FIGS. 11-16 and 17-20.

[0028] The reservation status information generating unit 12 is a means for generating predetermined reservation status information regarding the contents of the meal service to be provided and the location where the meal service is to be provided, based on the menu selection information transmitted from the user terminal 40. The reservation status information generated by the reservation status information generating unit 12 is output and displayed on the user terminal 40 so as to be viewable. This allows the user to check and understand on the user terminal 40 the usage status and congestion status of the store or pick-up location where the user is going to receive the meal service (see FIG. 24).

[0029] The usage history information generation unit 13 is a means for generating predetermined usage history information for each user terminal 40 (each user) based on the meal service usage information of each user generated and output by the delivery service unit 10A / mobile check service unit 10B. The usage history information generated by the usage history information generating unit 13 is output and displayed so as to be viewable on the user terminal 40 of the corresponding user. This will enable users and their families and other related parties to obtain and manage useful information on the type of meal service each user has received in the past, as well as the trends, frequency, and manner in which the service has been provided (see Figures 25-26). Specific processing operations of the reservation status information generating unit 12 and the usage history information generating unit 13 as described above will be described later together with the delivery service unit 10A / mobile check service unit 10B with reference to FIGS. 11-16 / 17-20.

[0030] [Delivery Service Department] FIG. 3 is a functional block diagram showing a specific configuration of the delivery service section 10A of the present system 1. As shown in FIG. FIG. 4 is an explanatory diagram that schematically shows the flow of data between the delivery service unit 10A of the system 1 and the user terminal 40 and store terminal 50. As shown in FIG. 3, the delivery service unit 10A includes a menu selection information generation unit 10A-1, a reservation acceptance information generation unit 10A-2, a usage information generation unit 10A-3, and also includes a predetermined database (DB20-26).

[0031] The menu selection information generation unit 10A-1 is a means for generating predetermined menu selection information that indicates the content and location of the meal services that can be provided, which is displayed on a user terminal 40 that can be operated by the user, and constitutes the menu selection information generation means of the present invention. The reservation acceptance information generation unit 10A-2 is a means for generating predetermined reservation acceptance information indicating the content and location of the meal service to be provided based on the menu selection information transmitted from the user terminal 40, and constitutes the reservation acceptance information generation means of the present invention.

[0032] The usage information generation unit 10A-3 is a means for generating predetermined usage information when the meal service prepared in accordance with the menu selection information is received at the service location, and constitutes the usage information generation means of the present invention. In the delivery service unit 10A, if the location where the meal service is provided indicated in the reservation acceptance information is one or more specified pick-up locations other than the store that provides the meal service, the usage information generation unit 10A-3 generates usage information after the meal service is received by the user at the specified pick-up location (see Figure 11-16).

[0033] The user terminal 40 and the store terminal 50 are communicatively connected to the delivery service unit 10A described above via a network, and the necessary information and data related to the provision of the meal service are sent and received, thereby enabling the specified delivery service to be carried out. Specifically, as shown in FIG. 4, each user terminal 40 and store terminal 50 can execute the specified functions provided by the delivery service unit 10A by calling up a dedicated application program or web browser operated in this system 1 and logging in.

[0034] First, the user terminal 40 can execute functions such as advance reservation for meal service and confirmation of reservation information between the user terminal 40 and the delivery service unit 10A. Furthermore, the store terminal 50 can execute functions such as master registration of predetermined information and data about meal services, reservation acceptance and performance management, and reservation acceptance registration between the store terminal 50 and the delivery service unit 10A. The delivery service unit 10A outputs predetermined payment data such as receipt data to the payment processing unit 11 based on the information and data transmitted and received between the user terminal 40 and the store terminal 50, and is able to perform automatic payment processing. The specific contents of the information and data transmitted and received between the delivery service unit 10A and the user terminal 40 / store terminal 50 will be described further below with reference to FIG.

[0035] The DBs 20-26 provided in the delivery service unit 10A are configured to store, manage, update, etc. predetermined master data and transaction data relating to users and delivery services to be managed by the delivery service unit 10A as a database. Specifically, in the delivery service unit 10A, as shown in FIG. 3, various information and data are stored and managed in the following databases: account master DB20, product master DB21, area master DB22, delivery destination master DB23, order information master DB24, reservation reception information DB25, and usage information DB26.

[0036] 7-10 show examples of maintenance screens (input screens) for the product master DB 21, delivery destination master DB 23, order information master DB 24, and reservation reception information DB 25, respectively. These input screens are output and displayed on a display or the like provided in the system 1, and input and correction can be performed as appropriate using input means such as a keyboard or pointing device. Note that the information stored in the databases 20-26 of the delivery service unit 10A shown in Figures 7-10 and below is an example of information to be processed in the present system 1, and is not limited to the information below. It goes without saying that the present system 1 can add, delete, change, etc. any information required.

[0037] [Account Master DB] The account master DB 20 is configured to register and manage information about users of the system 1 as master data, such as the following data: 1: App ID 2: User name 3:User ID 4: Meal service usage category 5: Daily maximum amount

[0038] [Product Master DB] The product master DB 21 is configured to register and manage information about meal services, which are products prepared in each store in the system 1 and can be provided to users, such as the following data as master data (see FIG. 7). 1: App ID 2:Product name 3: Receipt product name 4: Product code 5:JAN code 6: Major classification 7: Middle classification 8: Product classification 9:Tax category 10:Tax rate 11: Reduced tax category 12: Nutritional Information 13: Amount

[0039] [Area Master DB] The area master DB 22 is configured to register and manage information about areas in which users can receive meal services (delivery areas) in this system 1, such as the following data as master data. 1: App ID 2: Area ID 3: Area name 4: Area description information

[0040] [Delivery destination master DB] The delivery destination master DB 23 is configured to register and manage information about delivery destinations (receiving locations) where users can receive meal services in the system 1, such as the following data as master data (see FIG. 8). 1: App ID 2: Delivery address 3: Delivery address 4: Delivery destination postal code 5: Delivery start time 6: Delivery end time 7: Delivery destination information (notes) 8: Store code 9: Device ID

[0041] [Order information master DB] The order information master DB 24 is configured to register and manage the order information transmitted from the user terminal 40 and accepted in the present system 1 as master data, such as the following data (see FIG. 9). 1: App ID 2: Area ID 3: Delivery date 4: Deadline for applications 5: Products for sale 6: Delivery destination 7:Sales price 8: Number of units sold 9: Sales information description

[0042] [Reservation reception information DB] The reservation acceptance information DB 25 is configured to register and manage reservation acceptance information sent from the user terminal 40 and accepted in this system 1 as transaction data, such as the following data (see Figures 10(a) and (b)). 1: Reservation number 2: Delivery date 3: Area ID 4: Delivery destination 5: Product 6: Number of items 7:User ID 8: User contact information 9: Delivery destination postal code 10: Delivery address 11: Status

[0043] [Usage information DB] The usage information DB 26 is configured to register and manage usage information of users who have actually received meal services in the present system 1 as transaction data, such as the following data. 1: Payment number 2: Stores used 3: Date and time of use 4: Products used 5: Number of uses 6: Usage amount 7:User ID The specific processing operations of the delivery service unit 10A as described above will be described later with reference to FIGS.

[0044] [Mobile Check Service Department] FIG. 5 is a functional block diagram showing a specific configuration of the mobile check service unit 10B of the present system 1. As shown in FIG. As shown in the same figure, the mobile check service unit 10B is configured in a similar manner to the delivery service unit 10A described above, including a menu selection information generation unit 10B-1, a reservation acceptance information generation unit 10B-2, and a usage information generation unit 10B-3, as well as a predetermined database (DB30-36).

[0045] Similar to the menu selection information generation unit 10A-1, the menu selection information generation unit 10B-1 generates predetermined menu selection information that indicates the contents and locations of the meal services that can be provided, and is displayed on a user terminal 40 that can be operated by the user. Similar to the reservation acceptance information generation unit 10A-2, the reservation acceptance information generation unit 10B-2 generates predetermined reservation acceptance information indicating the content and location of the meal service to be provided based on the menu selection information transmitted from the user terminal 40.

[0046] The usage information generating unit 10B-3, like the usage information generating unit 10A-3, generates predetermined usage information when the meal service prepared in accordance with the menu selection information is received at the service location. In the mobile check service unit 10B, the usage information generation unit 10A-3 generates usage information based on the menu selection information displayed on the user terminal 40 presented by the user at the store when the location where the meal service is provided indicated in the menu selection information is a store that provides the meal service (see Figures 17-20).

[0047] The user terminal 40 and the store terminal 50 are communicatively connected to the mobile check service unit 10B via the network, and the necessary information and data related to the provision of the meal service are sent and received, thereby executing the specified mobile check service. Specifically, as shown in Figure 6, each user terminal 40 and store terminal 50 can execute the specified functions provided by the mobile check service unit 10B by calling up a dedicated application program or web browser operated in this system 1 and logging in.

[0048] First, the user terminal 40 can execute functions such as mobile check and usage history confirmation for the meal service in conjunction with the mobile check service unit 10B. The store terminal 50 is also capable of transmitting and receiving predetermined information and data regarding the provision of meal services to and from the mobile check service unit 10B, and storing and managing the information and data. Similarly to the delivery service unit 10A described above, the mobile check service unit 10B outputs predetermined payment data such as accounting data and usage history data to the payment processing unit 11 based on the information and data transmitted and received between the user terminal 40 and the store terminal 50, thereby enabling automatic payment processing. The specific contents of the information and data transmitted and received between the mobile check service unit 10B and the user terminal 40 / store terminal 50 as described above will be described further below with reference to FIGS. 18-19.

[0049] The DB30-36 provided in the mobile check service unit 10B, similar to the DB20-26 of the delivery service unit 10 described above, is designed to store, manage, update, etc. as a database certain master data and transaction data relating to the users and mobile check services managed by the mobile check service unit 10B. Specifically, in the mobile check service unit 10B, as shown in FIG. 5, various information and data are stored and managed in each of the databases: account master DB30, product master DB31, store master DB32, classification master DB33, classification tax rate master DB34, reservation reception information DB35, and usage information DB36.

[0050] Of these DBs 30-36 of the mobile check service unit 10B, the account master DB 30, the product master DB 31, the reservation reception information DB 35, and the usage information DB 36 store and manage information and data that are basically the same as those of the account master DB 20, the product master DB 21, the reservation reception information DB 25, and the usage information DB 26 of the delivery service unit 10A described above, so a description thereof will be omitted. The following describes an example of data stored and managed in the store master DB 32, the classification master DB 33, and the classification tax rate master DB 34, which are specific to the mobile check service unit 10B and different from the delivery service unit 10A.

[0051] [Store Master DB] The store master DB 32 is configured to register and manage information about stores where users can receive meal services in this system 1, such as the following data, as master data. 1: App ID 2: Store code 3: Store name 4: Device ID

[0052] [Classification Master DB] The classification master DB 33 is configured to register and manage information about the classification of meal services that can be provided in the present system 1 as master data, such as the following data. 1: Classification name 2: Classification code 3: Department code 4: Tax classification

[0053] [Classification tax rate master DB] The classification tax rate master DB 34 is configured to register and manage information about classification tax rates for meal services that can be provided in this system 1, such as the following data as master data. 1: Classification code 2:Tax rate 3: Reduced tax rate category The specific processing operations of the mobile check service unit 10B as described above will be described further below with reference to FIGS.

[0054] [User terminal] The user terminal 40 (40a to 40n) can be configured as one or more information processing devices, such as a smartphone, tablet terminal, or notebook PC, which are carried and operated by users of this system 1, such as university students using a university cafeteria or employees using a company cafeteria, who receive meal services via this system 1. By connecting and accessing this user terminal 40 to the meal service provision support server 10 and the store terminal 50 via the Internet 100, the user can send / receive, and output / display various information and data required to receive meal services via the API provided by this system 1.

[0055] [Store terminal] The store terminal 50 (50a to 50n) can be configured as one or more information processing devices, such as a POS terminal, desktop PC, tablet terminal, or smartphone, which is installed in a store (dining establishment / eating facility) that is a user of this system 1, such as a university or company cafeteria, or a cafeteria or cafeteria restaurant run by a business, and which provides meal services via this system 1. When this store terminal 50 connects to and accesses the meal service provision support server 10 and the user terminal 40 via the Internet 100, store staff and employees can send / receive, output, and display various information and data necessary to provide meal services via the API provided by this system 1.

[0056] [Operation] Next, specific processing and operations (implementation of the meal service provision support method) in the system 1 as described above will be described with reference to FIGS. 11-15 and 17-20. In this system 1, a series of processing operations are automatically executed in each of the delivery service unit 10A, mobile check service unit 10B, payment processing unit 11, reservation status information generation unit 12, and usage history information generation unit 13 of the meal service provision support server 10 described above, thereby alleviating congestion in dining facilities and effectively avoiding or eliminating the concentration of users and contact between people, thereby enabling the smooth provision of safe, secure, and comfortable meal services.

[0057] [Delivery Service System] First, the processing operation (delivery service system) by the delivery service unit 10A will be described with reference to FIGS. 11-16. 11-13 are explanatory diagrams that schematically show the concept of meal service provision in the delivery service section 10A of the present system 1. FIG. The delivery service system is a service that allows users of this system 1 (e.g., university students) to use and receive meal services by pre-ordering ingredients, mainly for lunch boxes, in an easy, convenient, and safe manner using a smartphone app, which serves as the user terminal 40 that the user owns and operates.

[0058] Specifically, in the delivery service system that constitutes this system 1, users who wish to receive a meal service can use a user terminal 40 that they carry and operate themselves to receive their desired meal service, such as a bento box or takeout food, at a desired date and time at a desired pickup location other than the store that provides the meal service, without having to go to a dining facility such as a cafeteria, thereby minimizing crowding and contact with people and allowing users to receive a safe and comfortable meal service. In particular, the delivery service realized by this system 1 has the following features: 1) For example, it will be possible to provide new meal service locations (sales areas, pick-up locations, etc.) both on and off university campuses. 2) When receiving meal service, payment is not required on-site. 3) The scope of meal service can be expanded widely outside the store.

[0059] First, in this system 1, as a use case (1), it is possible to provide and deliver meal services at, for example, a "dormitory" or a predetermined location (in the example of the figure, three locations: "dormitory," "A (north area)," and "B (south area)") located outside the university campus, as shown in Fig. 11. In this case, payment etc. is automatically processed by the payment processing unit 11 (see Fig. 2) described above, so the user does not need to pay or handle the accounting etc.

[0060] In addition, as a use case (2) of this system 1, as shown in Figure 12, it is possible to provide and deliver meal services at "on-campus pick-up points" outside existing stores, for example, set up on a university campus (in the example shown in the figure, there are two locations: "Campus A Pick-up Point" and "Campus B Pick-up Point"). In addition, automatic payment processing eliminates the need for users to make payments or make payments.

[0061] Furthermore, in this system 1, as a use case (3), as shown in Figure 13, even in "existing stores" such as campus cafeterias, meal service can be completed by simply handing over the menu reserved on a smartphone or the like to the customer when they visit the store, with advance reservations and no payment required via the user terminal 40, thereby reducing the time required for menu selection and payment and alleviating congestion in the store. In particular, it is effective to operate dedicated lanes during busy lunch hours, or to operate them only during times when usage is high, such as in the morning or evening, and it also enables flexible responses and operations based on the characteristics of each store, such as usage trends and reception readiness.

[0062] In this way, the delivery service implemented by this system 1 makes it possible to deliver meal services such as boxed lunches to dormitory residents and nearby students by setting up deliveries to facilities outside the university and collection points on campus, and also makes it possible to provide and collect meal services at collection points other than the cafeteria on campus. Therefore, students who use the service can easily use the meal service they want even if they are not on campus (university) or do not have to go to campus specifically for meals, and even if they are on campus (university).

[0063] This will allow, for example, each university campus to set up an on-campus sales outlet outside of existing stores, allowing meal services to be delivered without the need for on-site payment (payment-less), providing a new sales area and on-site payment-less service that can avoid "crowding" (contact between people and congestion) as much as possible. In this way, the delivery service system of this system 1, as shown in Figure 14, "systemizes" the "reservations" and "payments" of the meal service provision operations, thereby enabling each of the delivery service operations of "sales, reservations, meal planning, cooking, receipt (delivery), and payment" to be carried out smoothly.

[0064] Specific processing and data flows in the delivery service unit 10A of the system 1 will be described below with reference to FIGS. 15 and 16. FIG. FIG. 15 shows a schematic diagram of the flow of processing (data) in the delivery service section 10A. FIG. 16 shows the transition of screens output and displayed on the user terminal 40 during the processing of the delivery service section 10A.

[0065] FIG. 15 shows an example in which a user uses a cafeteria operated by a business (for example, a university cooperative). As shown in the figure, in the delivery service system, a user (e.g., a student) accesses and logs into the system 1 via a user terminal 40 that he or she owns and operates, and is then able to receive meal services ("reserving / receiving lunch boxes") operated by a business operator with a store terminal 50 via the delivery service system.

[0066] Specifically, as shown in Figure 16(a), a user can log in to the system 1 from a banner displayed on the display screen of the user terminal 40, for example, on the HOME page of an existing app, and then can select an advance reservation area from the "Advance reservation / reservation information confirmation" screen, for example, as shown in Figures 16(b) and (c). For "advance reservations," as shown in Figures 16(d) and (e), the user can enter desired details and information about the specified "order details" and "pick-up location" (e.g., the person placing the order, the type of order (lunch box), the delivery address, the delivery date and time, etc.) by following the input operations in the "reservation form" displayed on the screen, and then place and confirm the order. Furthermore, the entered / ordered details can be checked at any time on the "Confirm Reservation Information" screen, as shown in FIG. 16(f), for example.

[0067] In this way, predetermined menu selection information is generated and output from the delivery service unit 10A to the user terminal 40 (menu selection information generation unit 10A-1), which indicates the contents and locations of meal services available at each store in a selectable manner, and the menu selection information selected in response to the user's input operation is sent to the system 1. In the example shown in FIG. 15, menu selection information indicating "(1) Lunch box reservation" selected and generated at user terminal 40 is transmitted and received by delivery service unit 10A. In the delivery service unit 10A, based on the menu selection information sent from the user terminal 40, predetermined reservation acceptance information indicating the content of the meal service to be provided and the location of the service is generated and stored in a database (reservation acceptance information generation unit 10A-2 / reservation acceptance information DB25: see Figure 3).

[0068] The reservation reception information generated and stored in the delivery service unit 10A is output and displayed on the store terminal 50 of the business providing the meal service that is logged in to this system 1, and can be viewed and confirmed by the business's staff, employees, etc. In the example shown in FIG. 15, the menu selection information generated and output by the delivery service unit 10A is output and displayed as "(2) Check lunch box reservation status" on the store terminal 50 on the business side. Based on this output information, the business operator will then carry out the cooking and work of "(3) Lunch Box Preparation" as the meal service to be provided, prepare the lunch box ordered by the user, and deliver it to the "designated recipient (delivery destination)" indicated in the reservation acceptance information.

[0069] Thereafter, when the prepared meal service (lunch box) is received by the user at the receiving destination (delivery destination) which is the service location as "(4) Receiving lunch box," the business operator inputs and generates specified usage information indicating "(5) Confirming lunch box reservation history" at the store terminal 50, and the information is recorded and updated as reservation acceptance information in the delivery service unit 10A (usage information generation unit 10A-3 / usage information DB26: see Figure 3). Then, the delivery service unit 10A executes the "(6) Automatic Receipt Data Creation & Linkage" process based on the reservation acceptance information received from the store terminal 50, and outputs and transmits predetermined payment data such as receipt data to the payment processing unit 11. As a result, the payment processing unit 11 executes automatic payment processing at a predetermined timing (for example, "reflected the next day = the same timing as POS"), and can execute and complete the payment processing by automatically withdrawing the fee for the meal service from the user's prepaid account or the like as described above.

[0070] As described above, the delivery service unit 10A (delivery service system) enables users to receive their desired lunch boxes, take-out meals, etc., selected and ordered on the user terminal 40 that they carry and operate themselves, at their desired delivery destination and pick-up location on their desired date and time, without having to go to the restaurant. In addition, the store providing the meal service can prepare and prepare lunch boxes and other dishes in a well-planned manner based on the order information sent from the user terminal 40 via the store terminal 50, and since the delivery is made at a pick-up location outside the store, there is no need for customers to gather in the store, especially at lunchtime. Therefore, according to the present system 1, it is possible to provide a safe and comfortable meal service by minimizing congestion and contact with people.

[0071] The delivery at the pick-up location outside the store does not have to be manned, but may be unmanned. For example, a locker with an authentication function installed by a store or the like that provides meal service may be used as the pick-up location. In this case, the store offering the meal service prepares the lunch box or other items based on the order information transmitted from the user terminal 40, stores the lunch box or other items in the receiving locker specified in the order information, and then transmits a preparation completion notification to the user terminal 40. The preparation completion notification includes authentication data for opening the receiving locker. The authentication data may be numbers or a string of characters, or may be an automatically generated two-dimensional code such as a QR code (registered trademark). The authentication data may also be information about the user's IC card (such as a student ID or employee ID) that is associated with the user information in advance. In this case, the locker may be opened and the item may be picked up by touching the associated IC card. The authentication data may also be biometric authentication data (such as one or more fingerprint data) associated with the user information in advance, or may be numbers or a string of characters that the user has set in advance.

[0072] In addition, the store may be configured to recognize that pickup is complete when the user enters the authentication data, or the locker may be equipped with a separate confirmation means for receiving notification of pickup completion. If a customer specifies a locker as the pickup location when placing an order, they may specify a specific locker number, or simply the location where the locker is installed (for example, 1st floor, Building 6). In this case, the store can include the specific locker number in the preparation completion notification sent by the store. When a locker is used as a pickup location, a status notification means may be provided to notify the terminal 40 of the intended user of the locker (the person who ordered the stored lunch box, etc.) of the unpicked status if the authentication process has not been performed after a predetermined time has elapsed. The locker may be a locker that is fixedly installed in a predetermined location, or a locker that can move autonomously based on set time and route information, and may be realized in any form as long as it has storage space and authentication functionality.

[0073] [Mobile Check System] Next, the processing operation (mobile check system) by the mobile check service unit 10B will be described with reference to FIGS. 17-20. FIG. 17 is an explanatory diagram that schematically shows the concept of meal service provision in the mobile check service section 10B of the present system 1. The mobile check system is a service that allows users of this system 1 (e.g., university students) to place orders and make payments when they visit a store such as a school cafeteria using a smartphone app that serves as the user terminal 40 that they carry and operate themselves.

[0074] Specifically, the mobile check system that constitutes this system 1 allows users who visit a store such as a school cafeteria hoping to receive a meal service to use the user terminal 40 that they carry and operate themselves to order and pay for meal services such as set meals, a la carte dishes, and lunch menus prepared and served at the store, and even to "check" the management of the meal service usage history information themselves, thereby realizing a new store usage experience. In particular, the mobile check service realized by this system 1 allows users such as students to complete the process of enjoying meal services at a store using just one smartphone, which is almost always carried by the user, providing attractive value that can only be experienced by visiting the store.

[0075] In this system 1, as shown in FIG. 17, meal service is provided to users via the mobile check service according to the following outline of the flow and procedure. 1) The user uses a user terminal 40 such as their smartphone to launch an app for using the system 1, and selects the store (store) they wish to visit from the store display (menu selection information) displayed on the screen of the app. 2) Next, select a menu (meal service) from the menu display (menu selection information) displayed on the app screen. 3) The user then visits the store selected in the app and picks up the menu item selected in the app from the menus on display.

[0076] 4) After receiving the menu, the user shows the confirmation screen on their smartphone (user terminal 40) to a store staff member or employee, and the check (payment) is completed. At this time, for example, the smartphone can be set to play a sound indicating "confirmation complete." This sound allows both the customer and the store to confirm that the check (payment) is complete. In addition, in this case, as in the case of the delivery service described above, payment etc. is automatically processed by the payment processing unit 11 (see Figure 2), eliminating the need for the user to make payment or accounting. 5) Once the restaurant has confirmed the customer's identity, they can continue to eat at any seat inside or outside the restaurant.

[0077] In this way, with the mobile check service implemented by this system 1, when receiving meal service at the university's dining facilities, such as cafeterias and cafeterias, a user can reserve the restaurant and menu in advance from their own smartphone (user terminal 40), and at the restaurant, they can simply receive the desired menu and present the "confirmation screen" displayed on their smartphone to the restaurant, and then they can immediately eat without having to make any payment. This allows, for example, in stores such as campus cafeterias, to make advance reservations and make payments via user terminal 40, and when customers arrive at the store, they can simply receive the menu they reserved on their smartphone or other device and show the confirmation screen to receive and enjoy the desired meal service, reducing the time it takes to select a menu and make payments and alleviating congestion in the store.

[0078] In this way, the mobile check system related to this system 1, like the delivery service system shown in Figure 14, can be "systematized" in a way that can handle the "reservations" and "payments" of the meal service provision operations, thereby enabling each operation related to the provision of meal services at the store to be carried out smoothly. In particular, it is effective to operate dedicated lanes during busy lunch hours, or to operate them only during times when usage is high, such as in the morning or evening, and it also enables flexible responses and operations based on the characteristics of each store, such as usage trends and reception readiness.

[0079] The specific processing and data flow in the mobile check service unit 10B of the present system 1 will be described below with reference to FIGS. 18-20. 18-19 show a schematic diagram of the flow of processing (data) in the mobile check service unit 10B. FIG. 20 shows the transition of screens output and displayed on the user terminal 40 during the processing of the mobile check service unit 10B.

[0080] Figures 18-19 show an example in which customers go to eat at a restaurant or other food service facility operated by a business (such as a university cafeteria, a company cafeteria, a local restaurant, cafeteria, or food court). As shown in the figure, in the mobile check system, users can access and log in to the system 1 via a user terminal 40 that they carry and operate themselves, and receive meal service at a food and beverage establishment operated by a business that has a store terminal 50 via the mobile check system.

[0081] Specifically, as shown in Figure 20(a), a user can first log in to the system 1 by touching "Mobile Check Service" on the "HOME screen" displayed on the display screen of the user terminal 40, and then, for example, as shown in Figures 20(b) and 20(c), from the "Mobile Check Screen" to "Product Selection Screen," the user can select and specify the "store" to visit and the desired "product" (menu). These selection and input operations are performed by following the input screen displayed on the user terminal 40, allowing the user to select and set the desired "store" and "product" (menu). In addition, the entered information can be checked at any time on the "confirmation screen," as shown in, for example, Figure 20(d), and past meal service usage history information can also be checked and referenced on the "usage history screen," as shown in, for example, Figure 20(e) (usage information generation unit 10B-3 / usage information DB36: see Figure 5).

[0082] In this way, predetermined menu selection information is generated and output from the mobile check service unit 10B to the user terminal 40, which indicates each store where the meal service is provided and the contents of the meal service that can be provided at that store in a selectable manner (menu selection information generation unit 10B-1), and the menu selection information selected in accordance with the user's input operation is sent to the system 1. In the example shown in Figure 18, first, the mobile check system (mobile check service unit 10B) sends to the user terminal 40 specified information (menu selection information) for each store registered in the store master DB32 (see Figure 5), and the user terminal 40 becomes able to perform "(1) Store selection."

[0083] In addition, the mobile check system (mobile check service unit 10B) sends to the user terminal 40 predetermined information (menu selection information) about products available at each store registered in the product master DB31 (see Figure 5), allowing the user terminal 40 to perform "(2) Product selection." In the example shown in the same figure, the mobile check system extracts two types of product information, "1) Selection of product for the day" and "2) Recommended product," for "products available on that day" from the product information registered in the product master DB31, and transmits this information to the user terminal 40.

[0084] Next, the user goes to the store selected on the user terminal 40, as shown in FIG. At the store, the specified meal service that will be the "product of the day" that is sent and provided to the user terminal 40 is prepared at the "order and serving counter" and is displayed and served in a cafeteria-style manner, for example in an "unmanned corner," so that customers can freely pick up the meal. When a user visits a store, they receive the product they selected on the user terminal 40 through "(3) Menu Receipt (Serving)," and then, as "(4) Menu Confirmation," the "app screen and menu" displayed on the user terminal 40 is visually confirmed by store staff, employees, etc. in a "confirmation corner" or similar location within the store.

[0085] The provision of the meal service is completed when the store staff or employees click "(5) Confirmation Complete" on the confirmation screen of the user terminal 40. At this time, for example, a predetermined sound can be emitted from the smartphone constituting the user terminal 40 to indicate that the confirmation has been "confirmed," thereby allowing both the user and the store to confirm that "confirmation has been completed" via the user terminal 40. In addition, in this case, as in the case of the delivery service described above, payment etc. is automatically processed by the payment processing unit 11 (see Figure 2), eliminating the need for the user to make payment or accounting.

[0086] This allows customers to eat the products they receive at any seat they like, for example, inside or outside the store. Thereafter, the user terminal 40 sends predetermined usage information, including information on the store and product for which "confirmation has been completed," to the mobile check service unit 10B, which records and updates the information (usage information generation unit 10B-3 / usage information DB36: see Figure 5). Then, the mobile check service unit 10B executes the "(6) Automatic Receipt Data Creation & Linkage" process based on the usage information received from the user terminal 40, and outputs and transmits predetermined payment data such as receipt data to the payment processing unit 11. As a result, the payment processing unit 11 executes automatic payment processing at a predetermined timing (for example, "reflected the next day = the same timing as POS"), and can execute and complete the payment processing by automatically withdrawing the fee for the meal service from the user's prepaid account or the like as described above.

[0087] In this way, with the mobile check service unit 10B (mobile check system), a user who intends to use a food and beverage facility such as a university or company cafeteria can select the desired meal service for the desired store in advance using their own user terminal 40, and when they actually visit the store, they can simply receive the selected meal service and present the confirmation screen on the user terminal 40, and begin eating immediately. In addition, stores offering meal services can plan and prepare the "same-day products" (meal services) that have been distributed and registered in advance, and stores will no longer need to handle accounting other than handing over the products to customers and confirming them. This means that even during busy times such as lunchtime, customers will not have to concentrate at the cash register to pay, allowing for smooth store operations. Therefore, this system 1 also makes it possible to provide a safe and comfortable meal service by minimizing crowding and contact with people.

[0088] [Modifications / Application Examples] The above describes the basic configuration and processing operations of the delivery service unit 10A (delivery service system) and the mobile check service unit 10B (mobile check system) of this system 1, but this system 1 can be implemented as various modified and applied examples in addition to the above. Modifications and applications of the present system 1 will be described below with reference to FIGS.

[0089] [Product selection and usage confirmation via QR / barcode] FIG. 21 is an explanatory diagram that schematically shows a modified example of the processing in the mobile check service unit 10B of the present system 1, and is an example of "product selection and confirmation using QR / barcode." In the embodiment of the mobile check service unit 10B described above, as shown in Figures 17-18, the user performs a predetermined input operation on their user terminal 40 to select and set the desired store and product in advance before actually going to the store. In contrast, in this modified example, as shown in Figure 21, a user can receive meal service by going to a desired store where the system 1 can be used and then reading a barcode or QR code provided at the store with the user terminal 40.

[0090] Specifically, in this modified example, the menu selection information generation unit 10B-1 of the mobile check service unit 10B generates menu selection information by reading the barcode or two-dimensional code attached to the menu provided in the store on the user terminal 40. The usage information generating unit 10B-3 of the mobile check service unit 10B generates usage information when the barcode or two-dimensional code displayed on the user terminal 40 is read in the store. According to this modified example, as shown in FIG. 21, meal service is provided to users in accordance with the following general flow and procedure.

[0091] 1) The user goes to the desired store and reads (scans) a barcode displayed on the store's menu, for example, using the camera function or scanning function of the user terminal 40, such as the user's smartphone. 2) Next, the customer scans the barcode and picks up the menu from the counter or other area in the store. 3) After receiving the menu, the user shows the confirmation screen on their smartphone (user terminal 40) to a store staff member or employee for confirmation and approval. 4) The user then uses the camera or scanning function of their smartphone (user terminal 40) to read the payment QR code displayed near the store staff member or employee who approved the confirmation screen, and the check (payment) is completed.

[0092] At this time, for example, a sound can be made to sound when the "payment QR code" is read from the smartphone. This sound allows both the user and the store to confirm that the check (payment) has been completed. Furthermore, by reading this payment QR code, the payment processing unit 11 (see Figure 2) automatically processes the payment, eliminating the need for the user to make payments or accounting, as in the case of the mobile check system shown in Figure 16 above. 5) Once the payment QR code has been scanned, customers can then dine at any seat inside or outside the store.

[0093] According to this modified example, users who visit the store in person can view the menu and recommended products at the store and make a selection when they arrive, which meets the needs of users who want to select products on the spot.In addition, by providing a function that allows users to specify and select products by scanning the menus available in the store or the barcodes attached to the products, convenience for users can be improved. Furthermore, by installing a QR code for payment, it becomes possible to easily and reliably confirm that the product has been received, and by sounding a sound when the code is read, it becomes possible to prevent non-payment and to effectively deter and prevent fraudulent activities (eating and drinking without paying, etc.). The barcode (one-dimensional code) and QR code (two-dimensional code) used in this modified example are examples of using identification information that can be read by a terminal, etc., and other means such as an IC chip or RFID may be used as long as they can perform similar processing and functions.

[0094] [Complete use by taking photos of your food] FIG. 22 is an explanatory diagram that schematically shows a modified example of the processing in the mobile check service unit 10B of the present system 1, and is an example of "use completed by photographing a meal image." In the embodiment of the mobile check service unit 10B described above, as shown in Figures 17 and 19, after the user receives the desired menu at the store they visit, they can complete and enjoy the meal service by showing the confirmation screen displayed on the user terminal 40 to a store staff member or employee, etc., and obtaining confirmation. In contrast, in this modified example, as shown in Figure 22, a user can go to a desired store that can use this system 1, receive the desired menu, and then take a photo of the received menu (food) using a camera or other photography function on the user terminal 40, and send the image data to the store terminal, thereby receiving the meal service.

[0095] Specifically, in this modified example, the menu selection information generation unit 10B-1 of the mobile check service unit 10B generates menu selection information at the user terminal 40 based on the imaging data of the meal service received at the store. According to this modified example, as shown in FIG. 22, meal service is provided to users through the following general flow and procedure.

[0096] 1) A user selects the restaurant to visit and the desired menu (meal) from the application of this system 1 on their user terminal 40. Menu selection information indicating the entered and selected restaurant and menu is sent to the restaurant terminal 50 as order data via this system 1 or directly. 2) The user then visits the store selected in the app and picks up the menu item selected in the app from the menus on display. 3) After receiving the menu, the user takes a seat and takes a photo of the actual menu (meal) they received using the camera or video function of the user terminal 40, and then sends the image data to the store terminal 50 via this system 1 or directly. 4) The procedure is now complete and the user can proceed to eat their meal.

[0097] At the store, the order data and photographed data sent from the user terminal 40 are received at the store terminal 50 via this system 1 or directly, and by comparing and confirming this data, it is registered and managed as meal service usage information and used for automatic payment processing by the payment processing unit 11 and as usage history information by the usage history information generation unit 13. In the above example, the store performs confirmation, payment, and other processing by comparing the order data sent from the user terminal 40 with the photographed data, but it is also possible to perform confirmation, payment, and other processing based solely on the photographed data of the menu (meal) that the user generates and obtains on the user terminal 40. In this case, the user does not need to input or send the order data, and the store does not need to compare the two data, which has the advantage that processing can be completed using the photographed data alone.

[0098] According to this modified example, when a customer visits a store, they can complete the provision and use of the meal service related to this system 1 simply by taking and sending an image of the meal they have received, thereby providing a smoother process and a new user experience that has never been seen before. Furthermore, meal service providers can complete the process by comparing and approving the order data and photographed data after the fact, which reduces the workload at the store and also makes it possible to carry out confirmation work remotely, for example in an office other than the store. This provides a means of confirmation that does not require face-to-face contact regardless of location, making it possible to propose and reform new ways of working that are suited to virus and infection control measures, known as "with corona."

[0099] [Real-time booking] FIG. 23 is an explanatory diagram that schematically shows a modified example of the processing in the mobile check service unit 10B of the present system 1, and is an example of "real-time reservation / contactless ordering between a user and a store." In the embodiment of the mobile check service unit 10B described above, as shown in FIG. 17, the menu selection information selected and input by the user via the user terminal 40 is used as confirmation screen information to be presented to staff, employees, etc. at the store visited. In contrast to this, in this modified example, as shown in Figure 23, the menu selection information entered at the user terminal 40 is sent as reservation acceptance information to the store terminal 50 via this system 1 or directly, so that the user can use and utilize it as a real-time "same-day order" to use on the day.

[0100] Specifically, in this modified example, the reservation acceptance information generation unit 10B-2 of the mobile check service unit 10B generates, based on the menu selection information sent from the user terminal 40, specified reservation acceptance information indicating the content and location of the meal service to be provided as real-time same-day order information indicating the user's use on that day. The usage information generation unit 10B-3 of the mobile check service unit 10B generates usage information based on the menu selection information (order for the day) displayed on the user terminal 40 presented by the user who visited the store on the day and the reservation acceptance information sent in advance, and can be used for food delivery processing at the store, automatic payment processing, management of usage history information, etc. According to this modified example, as shown in FIG. 23, meal service is provided to users through the following general flow and procedure.

[0101] [Before receiving] 1) A user can use his / her user terminal 40 to make advance reservations for meals on the day at various locations and times of his / her choice. Specifically, a customer selects the restaurant (store) they wish to use, as well as the "lane" and desired menu item at that store, via the app of this system 1. Once the store, lane, and menu item are selected, an order number, indicated by, for example, a QR code, that identifies this information is generated and issued, and is sent to the store terminal 50 via this system 1 or directly as menu selection information indicating "order for the day." 2) The store can grasp the orders for the day in real time based on the menu selection information received by the store terminal 50, which can be used for preparing meals (preparing for meal service). For example, by installing a dedicated tablet or the like as the store terminal 50 that can be seen by the staff and employees who cook at each food serving lane, the cooking staff can directly check and grasp the orders for the day in real time.

[0102] [When receiving] 3) The user then visits the restaurant selected in the app, goes to the restaurant's food serving lane that has been reserved and transmitted in advance, and presents the order number, such as a QR code, generated and displayed on the user terminal 40. The restaurant reads the QR code displayed on the user terminal 40 using a dedicated tablet or the like provided for each lane, and compares it with the menu selection information indicating the day's order that has been received in advance. 4) Once the QR code on the user terminal 40 is matched with the menu selection information received by the store terminal 50, the meal ordered that day is delivered to the user, completing the provision of the meal delivery service. This completes the procedure and the customer can then proceed to eat their meal.

[0103] According to this modified example described above, by placing dedicated terminals that can receive orders directly from user terminals 40 at each food delivery lane at the store, it is possible to automate the process of confirming usage, particularly in cafeteria-style settings, thereby improving operational efficiency. In addition, by being able to reserve and keep track of orders from customers visiting on the day in real time, efficiency in hall operations will also be improved. In addition, users can simply place their order in advance using the user terminal 40, and then when they visit a store, they can simply present the user terminal 40 to receive the meal service.This means that there is no need to converse with store staff or employees, and users can enjoy safe and secure contactless ordering and meal service. In this modification, a barcode (one-dimensional code) or other identification information can also be used instead of the QR code (two-dimensional code).

[0104] [Checking the congestion situation based on the number of orders] FIG. 24 is an explanatory diagram that schematically shows an application example of the processing in the delivery service unit 10A / mobile check service unit 10B of the present system 1, and is an example of "checking the congestion situation by a user terminal." In this system 1, as described above, the reservation status information generating unit 12 generates predetermined reservation status information regarding the content of the meal service to be provided and the location where it will be provided, based on the menu selection information sent from the user terminal 40. The reservation status information generated by the reservation status information generating unit 12 is output and displayed on the user terminal 40 so as to be viewable.

[0105] Specifically, as shown in Figure 24, users of this system 1 can set and input the time period during which they would like to use the desired dining facility, as well as the menu and products they would like to use, via user terminal 40, and can therefore ascertain the reservation status and congestion level for that time period before visiting the store, which can be used as a guide to the congestion level when using the store. This allows users to check and understand the usage and congestion status of the store or pick-up location where they are planning to receive the meal service on the user terminal 40, and by avoiding busy times when they visit the store, they can avoid contact with people and being in a "crowded" situation, and receive the meal service safely and securely.

[0106] [Usage history information (nutritional information, coupons, information provided to family)] Figures 25-26 are explanatory diagrams that schematically show examples of application of processing in the delivery service unit 10A / mobile check service unit 10B of this system 1, where Figure 25 is an example of "visualizing nutritional value information / delivering recommended menus and coupons" and Figure 26 is an example of "visualizing nutritional value information to persons other than the individual concerned." In this system 1, as described above, the usage history information generation unit 13 generates predetermined usage history information for each user terminal 40 (for each user) based on the meal service usage information of each user generated and output by the delivery service unit 10A / mobile check service unit 10B. The usage history information generated by the usage history information generating unit 13 is output and displayed so as to be viewable on the user terminal 40 of the corresponding user.

[0107] Specifically, in this system 1, as shown in Figure 25, (1) when a user eats a meal using a service provided through this system 1, (2) information about that meal, such as information about nutritional value, is generated and stored as usage history information and is visualized and provided to the user via the user terminal 40. In addition, (3) the stores and businesses that provide meal services will utilize the usage history information as usage data, and will use it to plan and set up recommended menus based on nutritional value and distribute coupons, for example, and (4) users will be able to receive information such as recommended menus and coupons via their user terminals 40.

[0108] Furthermore, in this system 1, the user's usage history information can be sent and provided to other people besides the user, such as parents or family members. Specifically, as shown in Figure 26, (1) when a user eats a meal using the service provided through this system 1, (2) information about the meal, such as information about nutritional value, is generated and stored and visualized and provided to the user via the user terminal 40, and further, (3) the information can be provided and viewed not only by the user but also on smartphones, tablet devices, PCs, etc. owned by, for example, parents or family members. In this case, the smartphones of parents or family members, etc., to which the usage history information of users other than the user himself / herself is transmitted and output, also constitute user terminals 40 related to the present system 1.

[0109] In this way, by using the services related to this system 1, users can check not only their usage history of meals, etc., but also information regarding nutritional value as usage history information, and as users, they can receive recommended news and coupons based on the nutritional value of the food they have consumed. Furthermore, it is possible to provide information on the user's usage history not only to the user but also to the user's parents, for example, so that users who live far away from their parents can be informed through this system 1 that they are eating regular meals and consuming sufficient nutritional value.

[0110] [Barrier-free information for various dietary needs (allergies / halal / vegetarian, etc.)] FIG. 27 is an explanatory diagram that schematically shows an application example of the processing in the delivery service section 10A / mobile check service section 10B of the present system 1, and is an example of "adding barrier-free information for various foods." As described above, in this system 1, the menu selection information generation unit 10A-1 / 10B-1 generates predetermined menu selection information that indicates the contents and locations of the meal services that can be provided, and is displayed on a user terminal 40 that can be operated by the user. This menu selection information can include predetermined additional information related to the contents of the meal services that can be provided by this system 1, and as shown in Figure 27, barrier-free information for various foods, such as allergen information and halal information, can be generated and provided as additional information.

[0111] Such barrier-free information for various meals can be stored and managed in the product master DBs 21, 31 of the system 1 as menu selection information and as additional information related to each meal service. This allows users with allergies or halal requirements to be presented with allergen and halal information along with the products (meal services) that can be provided through this system 1, and allows them to select a dedicated menu when selecting a menu, thereby helping to provide a safer and more secure meal service. It goes without saying that in addition to the barrier-free information for various foods such as allergen information and halal information shown in this application example, any information that is useful to users, such as calorie information and nutritional value information, can be generated and displayed as menu selection information in this system 1.

[0112] [Voice response] Figures 28-29 are explanatory diagrams that schematically show examples of application of processing in the delivery service unit 10A / mobile check service unit 10B of this system 1, where Figure 28 is an example of "order handling by voice" and Figure 29 is an example of "meal delivery handling by voice." As described above, in this system 1, predetermined input operations are performed on the user terminal 40 that can be operated by the user, thereby selecting, inputting, transmitting, etc., predetermined menu selection information that selectably indicates the contents and locations of meal services available in this system 1. In the present system 1, by using the audio input / output functions of the user terminal 40, such as a microphone and speaker, it becomes possible to input and / or output the above-mentioned menu selection information by voice.

[0113] For example, as shown in FIG. 28, "recommended menu items" and "orders" can be selected by voice from the application of this system 1, which can further improve user convenience. Specifically, the functions of the smartphone that constitutes the user terminal 40 automatically convert the voice information uttered by the user into data, allowing for the output of, for example, "display recommendations" or the input of "orders," and makes it possible to input data into product master DBs 21, 31, etc., and to send order data to the store terminal 50. Furthermore, as shown in Figure 29, restaurants can also voice their orders when serving food, which means that, for example, cooking staff can understand the orders from a distance without having to speak, which is expected to be an effective infection prevention measure.

[0114] [Feedback function for users] FIG. 30 is an explanatory diagram that schematically shows an application example of the processing in the delivery service section 10A / mobile check service section 10B of the present system 1, and is an example of the "feedback function to the user." As described above, in this system 1, the usage history information generation unit 13 is capable of generating and managing the usage information of each user's meal service generated and output by the delivery service unit 10A / mobile check service unit 10B as usage history information on a per-user basis. Furthermore, as shown in Figure 30, such user-specific usage history information can also be used to allow users who have used meal services through this system 1 to optionally provide feedback on information such as their impressions and satisfaction with the meal they have consumed.

[0115] Such feedback information from users can be accumulated and managed in the product master DBs 21 and 31 of the system 1 as satisfaction level data associated with order data. This will enable stores and businesses, for example, to use the information as a reference for future planning and consideration, and users themselves will be able to effectively use it as reference information when selecting menu items.

[0116] As described above, according to this system 1, users can make reservations and orders for any meal service in advance without going to the dining facility, and can also freely set the store to visit, the location and time to pick up the meal service, etc. Furthermore, payment processing via cash or card can be eliminated. Therefore, according to the present system 1, it is possible to eliminate congestion in food and beverage facilities, effectively avoid the concentration of users and contact between people, and realize the provision and enjoyment of safe and secure meal services. This will enable support for providing meal services that are particularly suitable for cafeteria-style eating and drinking establishments, such as student cafeterias and employee cafeterias run by universities and companies, restaurants and cafeterias run by businesses, and food courts in commercial facilities.

[0117] More specifically, the present system 1 has the following advantages. Point 1: Contactless and hygienic The user terminal 40 is configured using a smartphone that each user has and owns, so there is no need to share the store's cash register or tablet terminal, and there is no need to handle cash, making it a very hygienic system that is particularly suitable for use in food and beverage establishments. Point 2: No need to install a dedicated terminal The user terminal 40 is configured using a smartphone that each user owns, and there is no need to prepare or purchase any dedicated hardware such as a terminal or device when using this system 1. Point 3: No maintenance required Since the user terminal 40 is configured using a smartphone that the user has and owns, the user can always use the latest smartphone, for example, and there is no need for any interaction with vendors on the store side. Point 4: No initial costs or electricity fees Since the user terminal 40 is configured using a smartphone that the user has or owns, the store's cash registers, tablet terminals, etc. can be used as is, and no new investment or electricity costs are required to start using this system 1. Point 5: No installation work required To start using this system 1, no installation work, electrical or wiring work, etc. is required for system implementation, and it can be used immediately. Point 6: Analysis from the user's perspective Customer data can be obtained from the user's smartphone, which constitutes the user terminal 40, and analysis can be performed by combining it with order / payment data, for example. Point 7: Meal service available anytime, anywhere The user's smartphone is used as the user terminal 40, and the user can view the menu and choose what they like anytime, anywhere, not just when they visit the store, but also while they are on the move or at home. Point 8: Recommended menu items In traditional school or company cafeterias, even though there are a wide variety of menus available, the combinations and menu choices tend to be monotonous. However, with this system, it is possible to notify and suggest to users, for example, combinations of standard menu items as recommended menus. Point 9: Integration with existing cafeteria card payments As described above, the present system 1 is capable of processing payments using an automatic payment processing system based on the "cafeteria card payment" disclosed in Patent Publication No. 4169749, which is held by the applicant of the present application as the patent holder. Point 10: Can be used in conjunction with or substituted for existing carrier-specific IC cards As described above, the present system 1 can be used in combination with or in place of an existing business's own IC card (such as FeliCa (registered trademark)). Point 11: Customer experience and store management reform For users, using this system 1 allows them to complete the process using just their smartphone, creating value that can only be experienced by visiting a store. For stores and businesses, this will make it possible to eliminate the division of labor between dining hall work and cashier work in food and beverage establishments, and also to transform the way cashier work is done into a job that focuses on "hospitality" and "maintaining hygiene within the store." Point 12: Contributing to SDGs efforts This system 1 will also be able to contribute to efforts toward the SDGs (Sustainable Development Goals) as follows: (1) Both customers (users) and store staff can spend time in the store in a hygienic manner. ⇒ "3: Good health and well-being" (2) Creating a safe working environment in restaurants during the COVID-19 era ⇒ "8: Decent work and economic growth" (3) Reducing food waste ⇒ "12: Responsible Consumption and Production"

[0118] Although the present invention has been described above by showing preferred embodiments thereof, it goes without saying that the present invention is not limited to the above-described embodiments, and various modifications can be made within the scope of the present invention. For example, in the above-described embodiment, the meal service providing facilities that are supported by the present invention have been described using cafeterias such as those operated by universities and cafeterias set up in companies and organizations, but the facilities to which the present invention can be applied are not limited to cafeterias or cafeterias.

[0119] The present invention is not limited to any particular organization, company, business operator, or group of any size or type, as long as it is a food and beverage establishment or the like that requires the provision of safe and comfortable meal services while easing congestion. Therefore, the present invention can be applied to, for example, small and medium-sized enterprises, privately run local restaurants, dining facilities installed in hospitals and medical care facilities, food and beverage facilities operated in sports facilities, amusement facilities, movie theaters, ski resorts, etc., to support the provision of safe and comfortable meal services. [Industrial Applicability]

[0120] The present invention can be suitably used as a technology and system for supporting the provision and operation of various meal services provided at various food and beverage facilities, such as cafeterias (school cafeterias) for students at universities, cafeterias (corporate cafeterias) for employees at companies, and cafeterias and food courts in commercial facilities. [Explanation of symbols]

[0121] 1. Meal service provision support system 10 Meal service provision support server 10A Delivery Service Department 10A-1 Menu selection information generation unit 10A-2 Reservation reception information generation unit 10A-3 Usage information generation section 10B Mobile Check Service Department 10B-1 Menu selection information generation unit 10B-2 Reservation reception information generation unit 10B-3 Usage information generation section 11 Payment processing section 12 Reservation status information generation unit 13. Usage history information generation unit 20 Account Master DB 21 Product master database 22 Area Master DB 23 Delivery destination master database 24 Order information master database 25 Reservation reception information DB 26 Usage information DB 30 Account Master DB 31 Product master database 32 Store master database 33 Classification Master DB 34 Classification tax rate master database 35 Reservation reception information DB 36 Usage information DB 40 User terminal 50 store terminals

Claims

1. A support system for providing a specified meal service desired by a user at a specified location desired by the user, a usage information generating means for generating predetermined usage information indicating that the meal service provided to the user has been received at the meal service providing location; a payment processing means for executing a predetermined payment process based on the usage information, The usage information generating means The usage information is generated based on image data of the actual menu received by the user, the image data being captured on a user terminal operable by the user. A meal service provision support system characterized by:

2. The usage information generating means The image data of the actual menu photographed by the user terminal is transmitted to a provider terminal operable by a provider providing the meal service.

2. The meal service provision support system according to claim 1.

3. The payment processing means Based on the usage information, a predetermined payment process is executed based on the user information registered in association with the user terminal.

3. The meal service provision support system according to claim 1 or 2.

4. The system further includes a menu selection information generating means for generating predetermined menu selection information that can be displayed on the user terminal and that selectably indicates the contents and locations of meal services that can be provided to the user. A meal service provision support system according to any one of claims 1 to 3.

5. a reservation status information generating means for generating predetermined reservation status information regarding the content and location of the meal service to be provided based on the menu selection information transmitted from the user terminal; The reservation status information is output so as to be viewable on the user terminal. The meal service provision support system according to claim 4.

6. a usage history information generating means for generating predetermined usage history information for each of the users based on the usage information; The usage history information is output so as to be viewable on the user terminal. A meal service provision support system according to any one of claims 1 to 5.

7. The usage history information includes predetermined additional information related to the content of the meal service that can be provided. The meal service provision support system according to claim 6.

8. An information processing device that constitutes a support system for providing a predetermined meal service desired by a user at a predetermined location desired by the user, a usage information generating means for generating predetermined usage information indicating that the meal service provided to the user has been received at the meal service providing location; functioning as a payment processing means for executing a predetermined payment process based on the usage information; The usage information generating means The usage information is generated based on image data of the actual menu received by the user, the image data being taken by the user terminal operable by the user. A meal service provision support program characterized by:

Images