JP2024163271A - Meal service provision support system - Google Patents

Abstract

[Problem] To enable users to reserve and order any meal service without going to a food service facility, to arbitrarily set the location and time for receiving the meal service, and to eliminate the need for payment processing via cash or card, thereby eliminating congestion at food service facilities and effectively avoiding the concentration of users and contact between people.
[Solution] This is a support system 1 for providing a specified meal service desired by a user at a specified location desired by the user, and is configured to include a menu selection information generation means for generating menu selection information indicating the content and service location of the available meal services, which is displayed on a user terminal 40 that can be operated by the user, a delivery service unit 10A and a mobile check service unit 10B which are equipped with a usage information generation means for generating specified usage information when the meal service prepared corresponding to the menu selection information is received at the service location, and a payment processing unit 11 which executes specified payment processing based on the usage information.
[Selected figure] Figure 2

Description

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, takeaway bento boxes, and takeout menus, provided at various eating and drinking facilities, such as university cafeterias (school cafeterias) for students, corporate cafeterias (corporate cafeterias) for employees, cafeterias operated by businesses, and food courts in commercial facilities.

Generally, food and beverage facilities such as university cafeterias for students and corporate cafeterias for employees provide a variety of meal services every day, such as set meals, a la carte dishes, lunch menus, takeaway bento boxes, and takeout menus.
At locations where this type of meal service is provided, customers tend to concentrate at lunchtime, and problems have been pointed out, particularly at cafeteria-style eating and drinking establishments such as school and company cafeterias, where customers have to wait long lines to receive their meal, have to wait to pay and settle the bill, and take a long time to finally receive their meal.
Furthermore, especially in recent years, there has been a desire to provide safe and comfortable meal services that minimize crowding and human contact as much as possible, in order to prevent viral infections, and cafeteria-style eating and drinking facilities such as university cafeterias are being called upon to take on new initiatives and make improvements.

Technologies for supporting the provision of meal services in such dining facilities include those proposed in Patent Documents 1 and 2, for example.
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, etc., by attaching an RFID tag to each of the multiple dishes (menus) that they pick up.
Patent Document 2 proposes a "restaurant management system" in which IC tags are attached to tableware in an employee cafeteria, the data from the IC tags is read to automatically calculate the total amount, and the payment is automatically made at a payment machine using an IC card held by the customer, thereby preventing eating and drinking without paying and enabling smooth, unmanned checkout.

JP 2004-102563 A JP 2004-145470 A

However, all of the technologies proposed thus far 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 and refinement, 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.

The present invention has been proposed to solve the problems described above, and aims to provide a meal service provision support system that allows users to reserve and order any meal service without going to the dining facility, allows them to freely set the location and time for receiving the meal service, and eliminates the need for payment processing via cash or card, thereby eliminating congestion at the dining facility and effectively avoiding the concentration of users and contact between people, and 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.

To achieve the above 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, comprising: a usage information generation means for generating specified usage information indicating that the meal service provided to the user has been received at the location where the meal service is provided; and a payment processing means for executing a specified payment process based on the usage information, and the usage information generation means is configured to generate the usage information based on image data of the meal service received at the store, which is taken on a user terminal operable by the user who visits the store where the meal service is provided.

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 of the present invention as described above.

According to the present invention, users can make reservations and orders for any meal service without going to a food service facility, can freely set the location and time for picking up the meal service, and do not need to process payments via cash or card, thereby eliminating 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 or employee cafeterias run by universities or companies, or food courts in commercial facilities.

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. FIG. 2 is a functional block diagram showing the configuration of each part in the present system. FIG. 2 is a functional block diagram showing the configuration of a delivery service unit of the present system. 2 is an explanatory diagram illustrating a schematic diagram of the flow of data between the delivery service unit of the system and the user terminal and store terminal. FIG. FIG. 2 is a functional block diagram showing the configuration of a mobile check service unit of the present system. 2 is an explanatory diagram showing a schematic diagram of the flow of data between the mobile check service unit of the present system and the user terminal and store terminal. FIG. 2 is a diagram showing a maintenance screen (input screen) for product master data of the present system. FIG. 2 is a diagram showing a maintenance screen (input screen) for the delivery destination master data of the present system. FIG. 13 is a diagram showing a maintenance screen (input screen) for the order information master of the present system. 1A and 1B are diagrams showing maintenance screens (input screens) for the reservation reception information master of the present system, in which (a) shows an input screen for performance management information, and (b) shows an input screen for registration information. FIG. 1 is an explanatory diagram illustrating the concept of "delivery of lunch boxes" in the delivery service section of the present system. FIG. 2 is an explanatory diagram illustrating the concept of an "off-store receiving location" in the delivery service section of the present system. FIG. 1 is an explanatory diagram illustrating the concept of "congestion alleviation" by the delivery service unit of the present system. FIG. 2 is an explanatory diagram illustrating a schematic diagram of the "systemized area" by the delivery service unit of the present system. FIG. 2 is an explanatory diagram illustrating a schematic flow of processing in a delivery service unit of the present system. 11 is an explanatory diagram showing the transition of the display screen of a user terminal during processing by the delivery service unit of the present system. FIG. FIG. 2 is an explanatory diagram showing a schematic overview of the "usage flow" in the mobile check service section of the present system. FIG. 2 is an explanatory diagram showing a schematic flow of processing in the mobile check service unit of the present system. 18, this is an explanatory diagram showing a schematic flow of processing in the mobile check service unit of this system. 1 is 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. FIG. FIG. 13 is an explanatory diagram showing a modified example of the processing in the mobile check service section of the present system, and is an example of "product selection and confirmation using QR/barcode." FIG. 13 is an explanatory diagram showing a modified example of the processing in the mobile check-in service unit of the present system, which is an example of "completion of use by photographing a meal image." FIG. 13 is an explanatory diagram showing a schematic diagram of a modified example of the processing in the mobile check service unit of the present system, and is an example of "real-time reservation/contactless ordering between users and stores." FIG. 13 is an explanatory diagram showing a schematic diagram of a modified example of the processing in the delivery service unit/mobile check service unit of the present system, and is an example of "checking congestion status using a user terminal." FIG. 13 is an explanatory diagram showing a schematic diagram of a modified example of the processing in the delivery service section/mobile check service section of the present system, and is an example of "visualization of nutritional value information/distribution of recommended menu items and coupons." FIG. 13 is an explanatory diagram showing a schematic diagram of a modified example of the processing in the delivery service section/mobile check service section of the present system, and is an example of "visualization of nutritional value information to persons other than the person in question." FIG. 13 is an explanatory diagram showing a schematic diagram of 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." FIG. 13 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." FIG. 13 is an explanatory diagram showing a schematic diagram of 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." FIG. 13 is an explanatory diagram showing a modified example of the processing in the delivery service unit/mobile check service unit of the present system, and is an example of the "feedback function to the user."

Hereinafter, an embodiment of the 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 according to instructions from a program (software). The program can send commands to each component of the computer to cause it to perform the specified processes, functions, etc. according to the present invention described below. In other words, each process, means, and function in the present invention is realized by a specific means in which the program and the computer work together.

The whole or part of the program may be provided by a computer-readable recording medium, such as a magnetic disk, an optical disk, a semiconductor memory, or any other recording medium, and the program may be read from the recording medium and installed on a computer for execution. The program may also be directly loaded into a computer via a communication line and executed without using a recording medium.
Furthermore, the present system can be configured with a single information processing device (such as one personal computer) or with a plurality of information processing devices (such as a group of a plurality of server computers).

Although not shown in the figure, the hardware configuration of this system 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, and data is exchanged via the system bus. The CPU (Central Processing Unit), also known as the central processing unit, is the part that performs the central processing 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, and ROM (Read Only Memory) is a type of memory device that uses semiconductors, etc., and data is written only once during manufacturing, and the recorded data 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 the user to give operational instructions to the computer or to input characters, etc., and specifically consists of a keyboard, mouse, etc. The display device consists of, for example, a liquid crystal display, etc., and may have a touch panel function. In addition, it may also have a communication function that enables communication with other terminals, information processing devices, etc.

[System configuration]
As shown in FIG. 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 data communication with each other.

Here, the meal service provision support server 10, the user terminal 40, and the store terminal 50 can each be configured using information processing devices belonging to different organizations, companies, etc.
In this case, the meal service provision support server 10 is configured as an information processing device operated by a company or the like that provides services to customers who operate, for example, school or corporate cafeterias as a service using the present system 1. The 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 the present 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.

On the other hand, the meal service provision support server 10, the user terminal 40, and the store terminal 50 may also be configured using information processing devices belonging to, for example, the same organization, company, business operator, etc.
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.

[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 specified program (software) is implemented, such as one or more server computers or personal computers, or a server system consisting of one or more virtual servers built on a cloud computing service.

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 implemented with software that runs on middleware such as a web server program.
This software publishes and provides applications that can be used by one or more user terminals 40 and store terminals 50 via a network such as the Internet 100 in the form of, for example, an API (Application Programming Interface).

As a result, each user terminal 40 and store terminal 50 can call up and log in to 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 thereby be able to 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 response to the menu selection information is received, and specified payment processing based on the usage information.

In addition, the meal service provision support server 10 has a predetermined database for meal service provision support (delivery service section 10A/mobile check service section 10B) and is equipped with a memory means in which various information necessary for the operation of 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 in 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 at any time as this system 1 is operated.

The meal service provision support server 10 in 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.
Below, we will explain in detail each part that is configured and functions as the meal service provision support server 10.

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 location where the meal service is provided, as 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).

The mobile check service unit 10B is a means (mobile check system) for executing and completing mobile check services such as preparation, serving, delivery, and payment for the selected meal service when the location where the meal service is provided, as indicated by 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).

The meal services handled by the delivery service unit 10A include, for example, takeaway lunches and takeout menus prepared and served at food and beverage facilities such as university cafeterias for students, corporate cafeterias for employees, cafeterias operated by businesses, and food courts in commercial facilities.
In addition, the meal services handled by the mobile check service unit 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 school cafeterias, company cafeterias, and food courts mentioned above.
The specific configurations and functions of the delivery service section 10A/mobile check service section 10B will be described later with reference to FIGS. 3-4/5-6, and the specific processing operations will be described later with reference to FIGS. 11-16/17-20.

The payment processing unit 11 is a means for executing a predetermined payment processing based on the usage information regarding 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 "dining hall 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 "canteen card payment" system is a service that allows users to freely use a canteen (store) up to a daily maximum amount for a specified period (e.g., one year) using a designated card in advance, enabling users such as university students to dine and pay without worrying about the money they have on hand.

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) to execute the 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, IC card, etc.

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 payment means other than the ``dining hall card payment'' system described above, 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 will be described later together with the delivery service unit 10A/mobile check service unit 10B with reference to FIGS. 11-16/17-20.

The reservation status information generating unit 12 is a means for generating predetermined reservation status information regarding the content of the meal service to be provided and the location of the service 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 so as to be viewable on the user terminal 40 .
This allows users to check and understand on the user terminal 40 the usage status and congestion status of the store or pick-up location where they are receiving the meal service (see Figure 24).

The usage history information generation unit 13 is a means for generating specified 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.
This will enable users, their families, and other related parties to obtain and manage useful information on what type of meal services each user has received in the past, and in what tendency, frequency, and manner (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 and the mobile check service unit 10B with reference to FIGS. 11-16 and 17-20.

[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 shows a schematic diagram of data flow between the delivery service unit 10A of the system 1 and the user terminal 40 and store terminal 50. As shown in FIG.
As shown in FIG. 3, the delivery service section 10A includes a menu selection information generating section 10A-1, a reservation acceptance information generating section 10A-2, a usage information generating section 10A-3, and also includes a predetermined database (DB20-26).

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 in a selectable manner, and 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 specified 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.

The usage information generating unit 10A-3 is a means for generating predetermined usage information when a meal service prepared in accordance with the menu selection information is received at the service location, and constitutes the usage information generating means of the present invention.
In the delivery service unit 10A, when 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).

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 transmitted and received, thereby executing the specified delivery service.
Specifically, as shown in FIG. 4, each user terminal 40 and store terminal 50 can execute 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.

First, the user terminal 40 can execute functions such as advance reservation for meal services and confirmation of reservation information between the user terminal 40 and the delivery service unit 10A.
In addition, the store terminal 50 can execute functions such as master registration of specific information and data regarding 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 is capable of outputting 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, thereby allowing automatic payment processing to be performed.
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 as described above will be described later in more detail with reference to FIG.

The DBs 20-26 provided in the delivery service section 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 section 10A as a database.
Specifically, in the delivery service department 10A, as shown in FIG. 3, various information and data are stored and managed in each of the databases, namely, an account master DB 20, a product master DB 21, an area master DB 22, a delivery destination master DB 23, an order information master DB 24, a reservation reception information DB 25, and a usage information DB 26.

7 to 10 show examples of the maintenance screens (input screens) for the product master DB 21, the delivery destination master DB 23, the order information master DB 24, and the 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 database 20-26 of delivery service unit 10A shown in Figures 7-10 and below is an example of information to be processed in this system 1, and is not limited to only the information below. It goes without saying that this system 1 can add, delete, change, etc. any information required.

[Account Master DB]
The account master DB 20 is configured to register and manage information on 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 upper limit

[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 present system 1 and can be provided to users, as master data, such as the following data (see FIG. 7).
1: App ID
2: Product name 3: Receipt product name 4: Product code 5: JAN code 6: Major category 7: Medium category 8: Product category 9: Tax category 10: Tax rate 11: Reduced tax category 12: Nutritional value information 13: Price

[Area Master DB]
The area master DB 22 is configured to register and manage information about areas (delivery areas) in which users can receive meal services 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

[Delivery destination master DB]
The delivery destination master DB23 is configured to register and manage information about the delivery destination (pick-up location) where a user can receive a meal service in this system 1 as master data, such as the following data (see Figure 8).
1: App ID
2: Delivery destination name 3: Delivery destination address 4: Delivery destination postal code 5: Delivery start time 6: Delivery end time 7: Delivery destination description information (notes)
8: Store code 9: Terminal ID

[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 accepting orders 5: Product for sale 6: Delivery address 7: Sales price 8: Quantity for sale 9: Sales information explanation column

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

[Usage Information DB]
The usage information DB 26 is configured to register and manage usage information when a user actually receives a meal service in the present system 1 as transaction data, such as the following data:
1: Payment number
2: Store used 3: Date and time of use 4: Product used 5: Number used 6: Amount used 7: User ID
The specific processing operations of the delivery service unit 10A as described above will be described later with reference to FIGS.

[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 figure, the mobile check service unit 10B is configured similarly to the delivery service unit 10A described above, and includes 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 specified database (DB30-36).

The menu selection information generation unit 10B-1, similar to the menu selection information generation unit 10A-1, generates predetermined menu selection information that indicates the selectable contents and service locations of the meal services that can be provided, and is displayed on a user terminal 40 that can be operated by the user.
The reservation acceptance information generating unit 10B-2, like the reservation acceptance information generating unit 10A-2, generates specific reservation acceptance information indicating the content of the meal service to be provided and the location where it will be provided, based on the menu selection information transmitted from the user terminal 40.

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, as indicated in the menu selection information, is a store that provides the meal service (see Figures 17-20).

The user terminal 40 and store terminal 50 are communicatively connected to the mobile check service unit 10B described above via a 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 FIG. 6, each user terminal 40 and store terminal 50 can execute 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.

First, the user terminal 40 can execute functions such as mobile checks for meal services and confirmation of usage history between the user terminal 40 and the mobile check service unit 10B.
In addition, the store terminal 50 is 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.
And, in the mobile check service unit 10B, similar to the delivery service unit 10A described above, it is possible to output 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 allowing automatic payment processing to be performed.
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.

The DB30-36 provided in the mobile check service unit 10B is similar to the DB20-26 of the delivery service unit 10 described above, in that it stores, manages, updates, etc. as a database specific 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, namely, an account master DB 30, a product master DB 31, a store master DB 32, a classification master DB 33, a classification tax rate master DB 34, a reservation reception information DB 35, and a usage information DB 36.

Of these DBs 30-36 of the mobile check service unit 10B, the information and data stored and managed in the account master DB 30, product master DB 31, reservation reception information DB 35, and usage information DB 36 are basically the same as those in the account master DB 20, product master DB 21, reservation reception information DB 25, and usage information DB 26 of the delivery service unit 10A described above, so explanations 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 unique to the mobile check service unit 10B and different from the delivery service unit 10A.

[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 as master data, such as the following data.
1: App ID
2: Store code 3: Store name 4: Terminal ID

[Classification Master DB]
The classification master DB 33 is configured to register and manage information regarding 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 category

[Classification tax rate master DB]
The classified tax rate master DB 34 is configured to register and manage information regarding the classified tax rates of meal services that can be provided in this system 1 as master data, such as the following 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 Figures 17-20.

[User terminal]
The user terminal 40 (40a to 40n) can be composed of one or more information processing devices, such as a smartphone, tablet terminal, or notebook PC, carried and operated by a user who receives meal services via this system 1, such as a university student using a university cafeteria or an employee using a company cafeteria.
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 various information and data necessary to receive the meal service, and output/display them via APIs provided by this system 1.

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

[Action]
Next, the specific processing and operation (implementation of the meal service provision support method) in the above-described system 1 will be described with reference to Figures 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 above-mentioned meal service provision support server 10, 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 a safe, secure and comfortable meal service.

[Delivery service system]
First, the processing operation (delivery service system) by the delivery service unit 10A will be described with reference to FIGS.
11-13 are explanatory diagrams that 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 in which users of this system 1 (e.g., university students) can 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 users themselves own and operate.

Specifically, in the delivery service system that constitutes this system 1, a user desiring a meal service can receive their desired meal service, such as a bento box or take-out food, at their desired date and time at a desired collection location other than the store providing the meal service, via a user terminal 40 that they carry and operate themselves, without having to go to a dining facility such as a cafeteria, thereby minimizing crowding and contact with others and allowing them 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 locations for meal services (sales areas, pick-up locations, etc.) that can be located both on and off university campuses.
2) When receiving the meal service, no payment is required on-site.
3) The scope of meal service can be expanded widely outside the store.

First, in this system 1, as a usage case (1), as shown in FIG. 11, it is possible to provide and deliver meal services at, for example, a "dormitory" or a specified location outside a university campus (in the example in the figure, there are three locations: "dormitory", "A (northern area)", and "B (southern area)"). In this case, payment of the fee, etc. is automatically processed by the payment processing unit 11 (see FIG. 2) described above, so there is no need for the user to pay or make an account.

In addition, as a usage case (2) of this system 1, as shown in FIG. 12, it becomes 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 will eliminate the need for users to make payments or accounts.

Furthermore, as a usage case (3) of this system 1, as shown in FIG. 13, even in an "existing store" such as a campus cafeteria, the meal service can be completed by simply handing over the menu reserved on a smartphone or the like to a customer who visits the store, with advance reservation and no payment required via a user terminal 40, thereby reducing the time required for menu selection and payment and alleviating congestion in the store.
In particular, operating dedicated lanes during the busiest lunch hours, or limiting operation to times when usage is high, such as in the mornings and evenings, is effective, and it also enables flexible responses and operations that take into account the characteristics of each store, such as usage trends and reception capabilities.

In this way, the delivery service implemented by this system 1 makes it possible to deliver to facilities outside the university and set up collection points on campus, thereby enabling meal services such as boxed lunches to be delivered to dormitory residents and nearby students, and also to be provided and handed over at collection points on campus other than the cafeteria.
Therefore, students who are users can easily use the meal service they desire even if they are not on campus (university) or do not have to take the trouble to go to campus just to eat, and even if they are on campus (university), they can easily use the meal service they desire.

This will allow, for example, each university campus to set up an on-campus sales outlet outside of existing stores and carry out meal delivery without the need for on-site payment (payment-less), providing a new sales area and on-site payment-less service that avoids "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, "systematizes" the "reservations" and "payments" of the meal service provision operations in a manner that can handle them, thereby enabling each of the operations in the delivery service, namely "sales, reservations, meal planning, cooking, receipt (delivery), and payment," to be carried out smoothly.

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

FIG. 15 shows an example in which a user uses a cafeteria operated by a business operator (eg, a university co-op).
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 a meal service ("reserve/receive lunch box") operated by a business equipped with a store terminal 50 via the delivery service system.

Specifically, as shown in FIG. 16(a), a user can log in to the present system 1 from, for example, a banner placed on the HOME page of an existing application on the display screen of the user terminal 40, and then, for example, as shown in FIG. 16(b) and (c), the user can select the "pre-reservation area" from the "pre-reservation/reservation information confirmation" screen.
For "advance reservation," as shown in Figures 16(d) and (e), for example, by following the "reservation form" displayed on the screen, the user can enter the desired details and content regarding the specified "order details" and "pickup location" (e.g., the orderer, the type of order (lunch box), delivery destination, delivery date and time, etc.), and then place and confirm the order.
In addition, the entered/ordered details can be checked at any time on a "confirm reservation information" screen, as shown in FIG. 16(f), for example.

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

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 the 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 on the store terminal 50 on the business operator's side as "(2) Check lunch box reservation status."
Based on this output information, the business operator performs the cooking and work of “(3) Lunch box preparation” as the meal service to be provided, prepares the lunch box ordered by the user, and delivers it to the “designated recipient (delivery destination)” indicated in the reservation reception information.

Thereafter, when the prepared meal service (lunch) is received by the user at the receiving destination (delivery destination), which is the place of provision, as “(4) Receiving lunch box”, the business operator inputs and generates specific usage information indicating “(5) Confirmation of lunch box reservation history” at the store terminal 50, and the information is recorded and updated as reservation acceptance information for 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. This allows the payment processing unit 11 to execute automatic payment processing at a predetermined timing (for example, "reflected the next day = the same timing as POS") and execute and complete the payment processing by automatically withdrawing the fee for the meal service from the above-mentioned prepaid account of the user, etc.

In this manner, according to the delivery service unit 10A (delivery service system), a user can receive the desired lunch box or take-out meal, etc., selected and ordered on the user terminal 40 that the user carries and operates, at the desired delivery destination and pick-up location, on the desired date and time, without having to go to the restaurant.
In addition, the store offering the meal service can plan and prepare lunch boxes and other meals well in advance based on the order information sent from the user terminal 40 via the store terminal 50, and since delivery is made at a receiving 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.

In addition, delivery at a receiving location outside the store does not have to be performed by a person, but may be performed unmanned. For example, a locker with an authentication function installed by a store or the like that provides meal services may be used as the receiving location.
In this case, the store offering the meal service prepares lunch boxes and the like based on the order information sent from the user terminal 40, stores the lunch boxes and the like 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 character string, or may be a two-dimensional code such as an automatically generated QR code (registered trademark). The authentication data may also be IC card information (such as a student ID or employee ID) owned by the user that is associated with the user information in advance, and in that case, the locker may be opened and the food may be received by touching the associated IC card. The authentication data may also be biometric authentication data (such as one or more fingerprint data) that is associated with the user information in advance, or may be numbers or a character string that the user has set in advance.

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 a notification that pickup is complete.
If the customer specifies a locker as the pick-up location when placing an order, the customer may specify a specific locker number, or may simply specify the location where the locker is installed (e.g., 1st floor, Building 6). In that case, the store may include the specific locker number in the preparation completion notification sent by the store.
When a locker is used as a receiving location, a status notification means may be provided to notify the terminal 40 of a prospective user of the locker (a person who ordered the stored lunch box or the like) of the unreceived status when authentication processing has not been performed even after a predetermined time has elapsed. The locker may be a locker that is fixedly installed at a predetermined location, or may be 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 function.

[Mobile Check System]
Next, the processing operation (mobile check system) by the mobile check service unit 10B will be described with reference to FIGS.
FIG. 17 is an explanatory diagram that shows a schematic diagram of 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 in which a user of this system 1 (e.g., a university student) can order and make payments when visiting a store such as a school cafeteria using a smartphone app that serves as a user terminal 40 that the user carries and operates.

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

In this system 1, as shown in FIG. 17, meal services are provided to users via a mobile check service in accordance with the flow and procedures outlined below.
1) A user uses a user terminal 40 such as a smartphone to launch an app for using the present system 1, and selects the store (shop) 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 screen of the app.
3) The user then visits the store selected on the app and picks up the menu item they selected on the app from the menu items on display.

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 emit a sound indicating "confirmation complete." This sound allows both the user and the store to confirm that the check (payment) has been completed.
In addition, in this case, as in the case of the delivery service described above, payment etc. will be automatically processed by the payment processing unit 11 (see Figure 2), eliminating the need for the user to make payment or settle the account.
5) Once customers have been verified by the restaurant, they can continue eating at any seat inside or outside the restaurant.

In this way, with the mobile check-in service implemented by this system 1, when receiving meal service at the university dining facilities such as cafeterias and cafeterias, a user can reserve the store and menu in advance from their own smartphone (user terminal 40). At the store, they simply receive the desired menu item and show the store the "confirmation screen" displayed on their smartphone, and can immediately eat without having to make a payment, etc.
This allows, for example, in a school cafeteria or other store on campus, to make a reservation in advance via user terminal 40 and make no payment, and when a customer comes to the store, they can simply receive the menu reserved on a smartphone or other device and show the confirmation screen, completing the provision and enjoyment of the desired meal service, reducing the time required for menu selection and payment and alleviating congestion in the store.

In this way, the mobile check system of the present system 1, like the delivery service system shown in Figure 14, can "systematize" the "reservations" and "payments" involved in the provision of meal services in a manner that can handle them, thereby enabling each task related to the provision of meal services in the store to be carried out smoothly.
In particular, operating dedicated lanes during the busiest lunch hours, or limiting operation to times when usage is high, such as in the mornings and evenings, is effective, and it also enables flexible responses and operations that take into account the characteristics of each store, such as usage trends and reception capabilities.

The specific process and data flow in the mobile check service section 10B of the present system 1 will be described below with reference to FIGS.
18-19 show schematic diagrams of the process (data) flow 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.

Figures 18 and 19 show an example in which a user goes to a dining facility such as a cafeteria operated by a business operator (a university cafeteria, a company cafeteria, a local restaurant, cafeteria, food court, etc.) to eat.
As shown in the figure, in the mobile check system, a user accesses and logs in to the system 1 via a user terminal 40 that the user carries and operates, and is then able to receive meal service via the mobile check system at a food and beverage establishment operated by an operator equipped with a store terminal 50.

Specifically, first, as shown in Fig. 20(a), a user can log in to the present 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 Fig. 20(b) and (c), the user can select and specify the "store" to visit and the desired "product" (menu) from the "Mobile Check Screen" to "Product Selection Screen." These selection and input operations are performed by performing input operations according to the input screen displayed on the user terminal 40, allowing the user to select and set a desired "store" and "product" (menu).
In addition, the input information can be checked at any time on a "confirmation screen," as shown in, for example, FIG. 20(d), and past meal service usage history information can be checked and referenced on a "usage history screen," as shown in, for example, FIG. 20(e) (usage information generation unit 10B-3/usage information DB36: see FIG. 5).

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

In addition, the mobile check system (mobile check service unit 10B) transmits to the user terminal 40 specific information (menu selection information) about products that can be provided at each store and that are registered in the product master DB 31 (see Figure 5), enabling "(2) Product selection" to be performed on the user terminal 40.
In the example shown in the figure, from the product information registered in the product master DB 31, two types of product information, "1) product selection for that day" and "2) recommended products," are extracted from the mobile check system for "products available on that day" and are transmitted to the user terminal 40.

Next, the user goes to the store selected on the user terminal 40 as shown in FIG.
At the store, a specified meal service that is the "same day product" is sent and provided to the user terminal 40 and prepared at the "order and serving counter", and is displayed and served in a cafeteria style, for example in an "unmanned corner", so that the customers can freely pick up the food.
When a user visits the store, the user receives the product 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 viewed and confirmed by the store’s staff, employees, etc. in, for example, a “confirmation corner” on the store side.

When the store staff or employees select “(5) Confirmation Complete” on the confirmation screen of the user terminal 40, the provision of the meal service is completed.
At this time, for example, a specified sound can be played 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. will be automatically processed by the payment processing unit 11 (see Figure 2), eliminating the need for the user to make payment or settle the account.

This allows the customer to eat the product they receive at any seat inside or outside the store.
Thereafter, the user terminal 40 transmits specific usage information, including information on the store and product for which "confirmation has been completed," to the mobile check service unit 10B, where it is recorded and updated (usage information generation unit 10B-3/usage information DB 36: see FIG. 5).
Then, in the mobile check service unit 10B, based on the usage information received from the user terminal 40, the "(6) Automatic receipt data creation &linking" process is executed, and predetermined payment data such as receipt data is output and transmitted 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 prepaid account of the user described above, or the like.

In this manner, according to the mobile check service unit 10B (mobile check system), a user who wishes to use an eating facility such as a university or company cafeteria can select the desired meal service for the desired store in advance using his or her own user terminal 40, and when the user actually visits the store, he or she can simply receive the selected meal service and present the confirmation screen of 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 the stores will not need to handle accounting or other procedures other than handing them over 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 the store to operate smoothly.
Therefore, this system 1 also makes it possible to provide a safe and comfortable meal service by minimizing congestion and contact with people.

[Modifications/Applications]
The above describes the basic configurations 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. However, in addition to the above, this system 1 can be implemented as various modified examples and application examples.
Modifications and applications of the present system 1 will be described below with reference to FIGS.

[Product selection and usage confirmation using QR/barcode]
FIG. 21 is an explanatory diagram that shows a schematic diagram of a modified example of the processing in the above-mentioned 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, a user performs a predetermined input operation on his/her 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 a user terminal 40.

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 a barcode or two-dimensional code attached to a menu provided in the store on the user terminal 40.
The usage information generating section 10B-3 of the mobile check service section 10B generates usage information by reading the barcode or two-dimensional code displayed on the user terminal 40 at the store.
According to this modified example, as shown in FIG. 21, meal service is provided to users in accordance with the flow and procedures outlined below.

1) A user goes to a desired store and reads (scans) a barcode displayed, for example, on a menu at the store, using the camera function, scanning function, etc. of a user terminal 40 such as the user's smartphone.
2) Next, the customer scans the barcode of the menu and picks it up 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 to confirm and approve it.
4) After that, the user uses the camera function, scanning function, etc. of their smartphone (user terminal 40) to read the payment QR code posted near the store staff member or employee who approved the confirmation screen, and the check (payment) is completed.

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 FIG. 2) automatically processes the payment, as in the case of the mobile check system shown in FIG. 16 above, eliminating the need for the user to make payment, accounting, etc.
5) Once the payment QR code has been scanned, customers can begin eating at any seat inside or outside the store.

According to this modified example, users who visit the store in person can view the menu and recommended items at the store and make a selection when they arrive, thereby meeting the needs of users who want to select items on the spot. In addition, by providing a function that allows users to specify and select items by scanning the menus provided in the store or barcodes attached to the items, convenience for users can be improved.
Furthermore, by installing a QR code for payment, it is possible to easily and reliably confirm that the product has been received, and by playing a sound when the code is read, it is possible to prevent non-processing and effectively deter and prevent fraudulent activities (eating and drinking without paying, etc.).
It should be noted that 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.

[Use is completed by taking a picture of the food]
FIG. 22 is an explanatory diagram that shows a schematic diagram of 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 a 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 staff member or employee of the store and obtaining confirmation.
In contrast, in this modified example, as shown in FIG. 22, a user can go to a desired store that can use this system 1, receive the desired menu, and then take a picture of the received menu (food) using a photographing function such as a camera on the user terminal 40 and send the image data to the store terminal, thereby receiving the meal service.

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 in accordance with the following general flow and procedures.

1) A user selects the store to visit and the desired menu (meal) from the application of this system 1 on his/her user terminal 40. Menu selection information indicating the store and menu that have been input and selected is sent as order data to the store terminal 50 via this system 1 or directly.
2) The user then visits the store selected on the app and picks up the menu item they selected on the app from the menu items on display.
3) After receiving the menu, the user takes a seat, etc., and takes a picture of the actual menu (meal) they received using the camera, video, or other photography function of the user terminal 40, and transmits 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.

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 the data is compared and confirmed, 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 processes 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 processes based only 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 and transmit order data, and the store does not need to compare two pieces of data, which has the advantage that processing can be completed using the photographed data alone.

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 receive, providing smoother processing and a new, unprecedented user experience.
In addition, meal service providers can complete the process by comparing and approving the order data and photo data after the fact, reducing the workload at the store and making 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 in line with virus and infection control measures known as "with Corona."

[Real-time booking]
FIG. 23 is an explanatory diagram showing a typical modification of the processing in the mobile check service unit 10B of the present system 1, and is an example of "real-time reservation/contactless order 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 visited store.
In contrast to this, in this modified example, as shown in FIG. 23, the menu selection information entered into the user terminal 40 is sent as reservation acceptance information to the store terminal 50 via this system 1 or directly, so that it can be used and utilized as a real-time "same-day order" that the user can use on the day.

Specifically, in this modified example, the reservation acceptance information generation unit 10B-2 of the mobile check service unit 10B generates specific 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, 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 a 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 in accordance with the flow and procedures outlined below.

[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, the customer selects the restaurant (store) to be used, as well as the "lane" and desired menu at that store, via the app of this system 1. When the store, lane, and menu are selected, an order number that identifies the information, for example, indicated by a QR code, 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 useful 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/employees cooking at each food serving lane, the cooking staff can directly check and grasp the orders for the day in real time.

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

According to this modified example, by arranging 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 a cafeteria format, thereby making operations more efficient.
In addition, by being able to reserve and keep track of orders from customers visiting on the day in real time, the efficiency of hall operations will also be improved.
In addition, from the user's perspective, they can simply place their order in advance via user terminal 40, and when they visit the store, they can complete the meal service receipt by simply presenting user terminal 40. This eliminates the need to converse with store staff or employees, and allows users to enjoy contactless, safe and secure ordering and meal service.
In this modified example, a barcode (one-dimensional code) or other identification information can also be used instead of the QR code (two-dimensional code).

[Checking congestion status based on number of orders]
FIG. 24 is an explanatory diagram showing a typical 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 and location of the meal service 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 so as to be viewable on the user terminal 40 .

Specifically, as shown in FIG. 24, a user of this system 1 can set and input the time period during which they wish to use the desired dining facility, as well as the desired menu and products, via a user terminal 40, and can grasp the reservation status and congestion situation for that time period before visiting the store, and can use this information as a guide to the congestion situation when using the store.
This allows users to check and understand on the user terminal 40 the usage and congestion status of the store or pick-up point where they are trying to receive the meal service. By avoiding busy times when they visit the store, users can avoid contact with others and crowded situations, and can receive the meal service safely and securely.

[Usage history information (nutritional value information, coupons, information provided to family members)]
Figures 25-26 are explanatory diagrams showing schematic examples of application of processing in the delivery service unit 10A/mobile check service unit 10B of this system 1, with Figure 25 being an example of "visualizing nutritional value information/delivery of recommended menus and coupons" and Figure 26 being an example of "visualizing nutritional value information to persons other than the person in question."
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.

Specifically, in this system 1, first, as shown in FIG. 25, when a user takes 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 providing meal services will use the usage history information as usage data and use it to plan and set up recommended menu items based on nutritional value and distribute coupons, and (4) users will be able to receive information on such recommended menu items and coupons via their user terminals 40.

In addition, 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 FIG. 26, (1) when a user takes a meal using the service provided through the present system 1, (2) meal information, such as information regarding 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 himself/herself but also on smartphones, tablet terminals, PCs, etc. owned by, for example, parents or family members.
In this case, the smartphones of parents or family members, to which usage history information of users other than the user himself/herself is sent and output, also constitute user terminals 40 related to this system 1.

In this way, by using the services related to this system 1, the user can check not only the usage history of meals, etc., but also information regarding nutritional value as usage history information, and as a user, can receive recommended news and coupons based on the nutritional value of the food they have ingested.
Furthermore, the usage history information of the user can be provided not only to the user but also to, for example, the user's parents, so that a user who lives away from their parents can be informed via the system 1 that they are eating regular meals and consuming sufficient nutritional value.

[Barrier-free information for various dietary needs (allergies/Halal/Vegetarian, etc.)]
FIG. 27 is an explanatory diagram that shows a typical 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."
In this system 1, as described above, the menu selection information generation unit 10A-1/10B-1 generates predetermined menu selection information that indicates the selectable 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.

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 allergen and halal information to be presented to users with allergies or halal requirements along with the products (meal services) that can be provided via this system 1, allowing them to select dedicated menus when making menu selections, thereby helping to provide a safer and more secure meal service.
Needless to say, 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 for this system 1.

[Voice response]
Figures 28-29 are explanatory diagrams that show typical examples of application of processing in the delivery service unit 10A/mobile check service unit 10B of this system 1, with Figure 28 being an example of "order handling by voice" and Figure 29 being an example of "meal delivery handling by voice."
In this system 1, as described above, a specific input operation is performed on a user terminal 40 that can be operated by the user, thereby selecting, inputting, transmitting, etc., specific menu selection information that selectably indicates the content and service location of the meal services available in this system 1.
In the present system 1, by using the voice 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.

For example, as shown in FIG. 28, "recommended menu items" and "orders" can be selected by voice using the application of this system 1, which can further improve user convenience.
Specifically, the functions of the smartphone constituting the user terminal 40 automatically convert the voice information uttered by the user into data, making it possible to, for example, output "display recommendations" or input "order", and to input data into product master DBs 21, 31, etc., and to transmit order data to the store terminal 50.
In addition, as shown in Figure 29, the restaurant can also voice the "order details" when serving food. This means that, for example, cooking staff can understand the order from a distance without having to speak, which is expected to be effectively used as an infection prevention measure, etc.

[Feedback function for users]
FIG. 30 is an explanatory diagram that shows a typical 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 a "feedback function to the user."
In this system 1, as described above, 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 made available so that users who have used the meal service through this system 1 can voluntarily provide feedback on information such as their impressions and satisfaction with the meal they had.

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, for example, stores and businesses to use the information as a reference for future planning and consideration, and users themselves will also be able to effectively use the information as reference when selecting menu items.

As described above, according to the present system 1, users can make reservations and orders for any meal service in advance without going to a dining establishment, 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 cards, etc. 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 provide and enjoy a safe and secure meal service.
This will enable support for the provision of 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.

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 holds 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 installation in food and beverage facilities.
Point 2: No need to install dedicated terminals, etc. The user terminal 40 is configured using a smartphone that each user owns, so there is no need to prepare or purchase any dedicated terminals, devices, or other hardware when using this system 1.
Point 3: No maintenance required Because the user terminal 40 is configured using a smartphone that the user 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 costs required Because the user terminal 40 is configured using a smartphone that each user 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 When starting to use this system 1, no installation work, electrical or line work, etc. is required for introducing the system, 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, making it possible to perform analysis by combining this data with order/payment data, for example.
- Point 7: Meal service can be selected 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: Providing recommended menus In traditional school or company cafeterias, even though a wide variety of menu items are available, the combinations and menu choices tend to be monotonous. With this system 1, however, it is possible to notify and suggest to users, for example, combinations of standard menu items as recommended menu items.
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 for "cafeteria card payments" disclosed in Patent Publication No. 4,169,749, which is held by the applicant of this application as the patent owner.
Point 10: Can be used in conjunction with or as a substitute for an existing carrier's proprietary IC card. As described above, the present system 1 can be used in conjunction with or as a substitute for an existing carrier's proprietary IC card (such as FeliCa (registered trademark)).
- Point 11: Customer experience at the store and changes in store operations For customers, using System 1 creates value that can be experienced only by visiting the store, as it allows them to complete all operations using just their smartphone.
For stores and businesses, this will make it possible to eliminate the division of labor between dining hall work and cashier work in restaurants, and it will also be possible to transform the way cashier work is done to focus on "hospitality" and "maintaining hygiene in the store."
- Point 12: Contribution to SDGs efforts According to this system 1, it is possible to contribute to SDGs (Sustainable Development Goals) efforts as follows.
(1) Both customers (users) and store staff can spend time in the store in a hygienic manner ⇒ "3: Health and Welfare for Everyone"
(2) Creating an environment where people can work safely in restaurants in the COVID-19 era ⇒ "8: Decent work and economic growth"
(3) Reducing food waste ⇒ "12: Responsible Consumption and Production"

Although the present invention has been described above by showing preferred embodiments, 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, dining halls such as university cafeterias and corporate cafeterias set up in companies and organizations have been used as examples of facilities providing meal services that are supported by the present invention, but the facilities to which the present invention can be applied are not limited to university cafeterias and corporate cafeterias.

The present invention is applicable to any organization, company, business operator, association, etc. of any size or type, as long as it is a food and beverage facility or the like that has a demand to provide safe and comfortable meal service while alleviating congestion, and is not limited to any particular organization.
Therefore, the present invention can be applied to food and beverage establishments operated in small and medium-sized enterprises or privately run local restaurants, dining facilities installed in hospitals and medical and nursing care facilities, sports facilities, amusement facilities, movie theaters, ski resorts, etc., to help provide safe and comfortable meal services.

The present invention can be suitably used as technology and a system to support the provision and operation of various meal services provided at various food and beverage facilities, such as university cafeterias (school cafeterias) for students, corporate cafeterias (corporate cafeterias) for employees, and cafeterias and food courts in commercial facilities.

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

Claims (9)

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 a location where the meal service is provided;
a payment processing means for executing a predetermined payment process based on the usage information,
The usage information generating means
A meal service provision support system characterized in that the usage information is generated based on image data of the meal service received at a store where the meal service is provided, the image data being taken on a user terminal that can be operated by the user who visits the store where the meal service is provided. The meal service provision support system of claim 1, further comprising a menu selection information generation means for generating predetermined menu selection information which can be displayed on the user terminal and which selectably indicates the contents and service locations of meal services which can be provided to the user. The usage information generating means
Order data indicating the contents of the meal service that can be provided at the store and store information selected from the menu selection information on the user terminal in response to an input operation of the user who visits the store;
When receiving image data of the meal service received at the store, the image data is taken at the user terminal in response to an input operation of the user who visited the store,
The meal service provision support system according to claim 2 , further comprising: generating the usage information by comparing the received order data and imaging data. The menu selection information generating means
The menu selection information is generated by reading a barcode or two-dimensional code attached to a menu provided in the store at the user terminal,
The usage information generating means
The meal service provision support system according to claim 2, characterized in that the usage information is generated by reading the barcode or two-dimensional code displayed on the user terminal at the store. A reservation acceptance information generating means for generating a predetermined reservation acceptance information indicating the content and the place of the meal service to be provided based on the menu selection information transmitted from the user terminal,
The usage information generating means
The meal service provision support system described in claim 2 or 3, characterized in that the usage information is generated based on the menu selection information displayed on the user terminal presented at the store and the reservation acceptance information. A reservation status information generating means for generating predetermined reservation status information regarding the contents and service location of the meal service to be provided based on the menu selection information transmitted from the user terminal,
The meal service provision support system according to any one of claims 2 to 4, characterized in that the reservation status information is output so as to be viewable on the user terminal. a usage history information generating means for generating predetermined usage history information for each of the user terminals based on the usage information;
The meal service provision support system according to any one of claims 1 to 5, characterized in that the usage history information is output so as to be viewable on the user terminal. A meal service provision support system as described in any one of claims 2 to 4, characterized in that the menu selection 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 any one of claims 2 to 4, characterized in that the menu selection information can be input and/or output by voice at the user terminal.

Images