JP7727236B2 - Information processing system, information processing method and program - Google Patents

Description

The present invention relates to an information processing system, information processing method, and program capable of processing order information sent from a user terminal at a restaurant.

Traditionally, restaurants have used mobile ordering systems in which customers place orders by sending order information from their mobile devices, such as smartphones, to the restaurant's server, rather than placing the order face-to-face with a waiter.

For example, Patent Document 1 below discloses that a customer's mobile device reads a two-dimensional code attached to a table and transmits the acquired table number to a server device via the Internet. The server device then transmits table confirmation information to an in-store system in response. Once a connection with the server device is established, the customer operates a function menu displayed on the mobile device to input order data (food name, quantity, etc.) and transmits the order information along with the table number to the server device, which then transmits it to the in-store system.

Patent No. 6598249

However, with the above technology, orders are made solely based on customer selection, meaning that employees miss out on opportunities to conduct sales promotions with customers.

In light of the above circumstances, the object of the present invention is to provide an information processing device, information processing method, and program that enables employees in a mobile ordering system to carry out sales promotion activities tailored to a customer's table without having to visit that table.

To achieve the above object, an information processing system according to one embodiment of the present invention has a communication unit and a control unit. The communication unit receives received information from a user terminal, including table identification information that identifies tables placed in a restaurant and order information. The control unit analyzes the received information for each piece of table identification information to determine user attributes for each piece of table identification information, and generates notification information for the user according to the determined attributes.

In this way, the information processing system can analyze information received from user terminals and generate notification information according to determined attributes, enabling employees in a mobile ordering system to carry out sales promotion activities tailored to each table without having to visit the customer's table. The information processing system can be composed of one or more information processing devices.

The communication unit may receive the table identification information from the user terminal by the user terminal reading code information associated with each table as the table identification information.

The control unit may be able to receive the order information from the user terminal when the table identification information is read by the user terminal.

This allows the information processing system to accept orders from user terminals simply by having the user terminal read the table identification information for each table.

The control unit may transmit the generated notification information to a store terminal of the restaurant, and may also transmit the notification information to the user terminal in response to an operation input from the user of the store terminal in response to the notification information.

This allows the information processing system to have restaurant employees send the notification information they desire to customers.

The control unit may classify all tables at the restaurant according to the determined attributes and generate the same notification information for each table classification.

This allows the information processing system to avoid the waste of generating duplicate notification information for tables with the same attributes, compared to when generating notification information for each table.

The control unit may generate an operation screen having different areas for each of the attributes, and arrange a user interface for sending the notification information in each of those areas.

This allows the information processing system to allow restaurant employees to simultaneously send notification information to one or multiple tables for each attribute via the operation screen.

The control unit may also display history information indicating the transmission history of the notification information to the user terminal for each area.

This allows the information processing system to allow restaurant employees to check the past sending history of notification information and send notification information that is more effective in promoting sales.

The control unit may determine user attributes for each of the table identification information by analyzing the order information.

This allows the information processing system to generate appropriate notification information based on the order information for each table.

The control unit may determine the attributes based on information acquired by accepting orders from the user terminal between the time the table identification information is first acquired and the time payment is made for the table.

This allows the information processing system to use all information from the time the customer sits down at the table until payment to generate notification information.

The control unit may obtain user identification information that identifies the user of the user terminal included in the received information, and determine the attributes based on personal information linked to the user identification information.

This allows the information processing system to generate more personalized notification information based on the customer's personal information.

The control unit may determine the attributes based on information that is common to a predetermined percentage or more of the personal information of users of multiple user terminals that have acquired the same table identification information. In this case, common information may be, for example, female (gender), elderly (age group), or members of the same family (relationship between users).

This allows the information processing system to determine attributes common to each customer at the same table, allowing it to generate notification information appropriate for each customer at that table.

The control unit may determine the attribute based on the number of user terminals or user identification information included in the received information.

This allows the information processing system to change notification information depending on the number of customers at a table.

The control unit may generate, as the notification information, information suggesting the number or amount of food or drink corresponding to the number for each attribute.

This allows the information processing system to automatically suggest food and drink options for the number of people at a table.

The control unit may generate, as the notification information, information for each attribute that suggests food and drink according to the amount of time that has elapsed since the table identification information was received.

This allows the information processing system to generate notification information that suggests different foods and drinks depending on the amount of time that has elapsed since the customer began their meal.

If the elapsed time exceeds a predetermined time, the control unit may generate information suggesting takeaway food and beverages for each of the attributes.

This allows the information processing system to suggest takeaway food and drinks if customers are unable to finish their ordered food and drinks based on the remaining available time, thereby further increasing sales.

The control unit may generate information suggesting additional or takeaway food and drink options for each attribute when the restaurant is unlikely to achieve its sales target for the day or for that time period.

This allows the information processing system to proactively generate promotional notification information if sales are not meeting the day's target, thereby helping to achieve the day's sales target as much as possible.

An information processing method according to another aspect of the present invention includes:
receiving, from a user terminal, reception information including table identification information for identifying a table placed at the restaurant and order information;
Analyzing the received information for each of the table identification information to determine a user attribute for each of the table identification information;
and generating notification information for the user in accordance with the determined attribute.

A program according to another aspect of the present invention is a program for executing the following on an information processing device:
receiving, from a user terminal, received information including table identification information for identifying a table placed at the restaurant and order information;
determining a user attribute for each of the table identification information by analyzing the received information for each of the table identification information;
and generating notification information for the user in accordance with the determined attribute.

As described above, the present invention makes it possible for a mobile ordering system to carry out sales promotion activities tailored to a customer's table without an employee having to visit the table. However, this effect does not limit the present invention.

1 is a diagram showing a configuration of an order receiving system according to an embodiment of the present invention. 1 is a diagram showing a hardware configuration of a restaurant information providing server according to an embodiment of the present invention. 2 is a diagram showing the configuration of a database included in a restaurant information providing server according to an embodiment of the present invention. FIG. 10 is a flowchart showing the flow of an order receiving process, a user attribute determining process, and a notification information generating process performed by a restaurant information providing server according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of a transmission screen for notification information generated by the restaurant information providing server according to one embodiment of the present invention.

Embodiments of the present invention will be described below with reference to the drawings.

[System configuration]
FIG. 1 is a diagram showing the configuration of a mobile order system according to this embodiment.

As shown in the figure, this system includes a restaurant information providing server 100 on the Internet 50, multiple user terminals 200, and multiple restaurant terminals 300.

The restaurant information providing server 100 is a web server that operates a portal site that lists information about restaurants. The restaurant information providing server 100 is connected to multiple user terminals 200 and multiple restaurant terminals 300 of restaurants via the Internet 50.

The restaurant information providing server 100 provides a restaurant information search system for users of user terminals 200 on the portal site. Specifically, the restaurant information providing server 100 searches for restaurant information that matches the search criteria based on a search request from the user terminal 200, generates a web page listing the search results, and transmits it to the user terminal 200. The restaurant information providing server 100 also handles the reservation process for any restaurant from the user terminal 200 of the user who viewed the restaurant information.

The restaurant information providing server 100 also provides a restaurant information management screen (web page) for restaurants (affiliated restaurants) listed on the portal site. Through this management screen, users of the restaurant terminal 300 can edit and update the restaurant information (content) on the web page provided to general users as the search results, and upload the web page to the portal site.

User terminal 200 (200A, 200B, 200C, etc.) is a terminal used by a user, such as a smartphone, mobile phone, or tablet PC (Personal Computer). User terminal 200 accesses restaurant information providing server 100, receives the above-mentioned web page, and displays it on a screen using a browser or the like.

The user terminal 200 determines restaurant search conditions based on user operation and transmits a restaurant search request based on those search conditions to the restaurant information providing server 100. In this embodiment, the user of the user terminal 200 can transmit a search request for restaurants that can be reserved by selecting pre-set search conditions such as the restaurant's location area (nearest station), genre, price range, etc. Then, based on user operation, the user terminal 200 can transmit a reservation request for one of the restaurants displayed as the search results to the restaurant information providing server 100.

The restaurant terminal 300 is a terminal installed in each restaurant, and may be a tablet PC, notebook PC, desktop PC, etc. Based on the administrator's operation, the restaurant terminal 300 can perform processing related to its own restaurant information, such as editing and updating the restaurant information, by communicating with the restaurant information providing server 100.

Furthermore, in this embodiment, at each restaurant, users who visit and sit at each table T (T1, T2, ...) can order food and drink using their own user terminal 200. Specifically, each table T is provided with a printed material (plate, card, etc.) on which a two-dimensional code C (C1, C2, ...) that stores a table ID that identifies the table is printed. By reading the two-dimensional code C with the user terminal 200, users can access the restaurant's food and drink ordering page, and can order food and drink by sending order information along with the table ID to the restaurant information providing server 100 via the order page.

In other words, the restaurant information providing server 100 functions as a web server that accepts reservations from customers via a website, and also functions as a POS (Point of Sales) server that manages order information and sales information for each table T in the restaurant, sending order information from each user terminal 200 to the restaurant terminal 300 and performing accounting for each table T based on the order information.

Furthermore, the restaurant information providing server 100 can determine the user attributes for each table ID based on the information acquired by accepting orders from the user terminal 200 between the time the table ID is acquired and the time the payment for that table is made, and generate notification information (e.g., promotional information such as recommended menu items) for the user at each table according to the user attributes. Details of this user attribute determination process and the notification information generation process will be described later.

[Hardware configuration of restaurant information server]
2 is a diagram showing the hardware configuration of the restaurant information providing server 100. As shown in the figure, the restaurant information providing server 100 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an input/output interface 15, and a bus 14 connecting these components to one another.

The CPU 11 accesses the RAM 13 and other memory as needed, and performs various calculation processes while providing overall control over each block of the restaurant information providing server 100. The ROM 12 is a non-volatile memory that permanently stores firmware such as the OS, programs, and various parameters executed by the CPU 11. The RAM 13 is used as a working area for the CPU 11, and temporarily stores the OS, various applications currently being executed, and various data being processed.

The input/output interface 15 is connected to a display unit 16, an operation reception unit 17, a memory unit 18, a communication unit 19, etc.

The display unit 16 is a display device that uses, for example, an LCD (Liquid Crystal Display), an OELD (Organic ElectroLuminescence Display), or a CRT (Cathode Ray Tube).

The operation reception unit 17 is, for example, a pointing device such as a mouse, a keyboard, a touch panel, or other input device. If the operation reception unit 17 is a touch panel, the touch panel may be integrated with the display unit 16.

The storage unit 18 is a non-volatile memory such as a hard disk drive (HDD), flash memory (SSD; solid state drive), or other solid-state memory. The storage unit 18 stores the OS, various applications, and various data.

In particular, in this embodiment, the storage unit 18 stores applications and other programs that enable the restaurant information providing server 100 to execute the order acceptance process, user attribute determination process, and notification information generation process described below. As will be described later, the storage unit 18 has databases containing such data, including a restaurant information database, a user information database, a POS information database, and a notification information database.

The communication unit 19 is, for example, a NIC (Network Interface Card) for Ethernet or various modules for wireless communication such as wireless LAN, and is responsible for communication processing with the user terminal 200.

Although not shown, the hardware configuration of the user terminal 200 and restaurant terminal 300 is basically the same as that of the restaurant information providing server 100.

[Database configuration of restaurant information server]
FIG. 3 is a diagram showing the configuration of a database included in the restaurant information providing server 100. As shown in FIG.

As shown in the figure, the restaurant information providing server 100 has a restaurant information database 31, a user information database 32, a POS information database 33, and a notification information database 34 in the memory unit 18.

For each restaurant, the restaurant information database 31 stores the restaurant's name, location (address or latitude and longitude), area information, access information (nearest station information, walking distance from the nearest station), telephone number, an ID that identifies the restaurant (store ID), the restaurant's business type/service category information, information introducing the restaurant (information indicating the restaurant's characteristics such as store promotional text, information about events held by the restaurant, etc.), image data related to the restaurant (introducing the restaurant), menu information related to the menu offered by the restaurant, average budget information, business hours, website URL, etc. This information is entered from each restaurant's restaurant terminal 300 via a management screen provided by the restaurant information providing server 100.

The menu information corresponds to the menus posted on the websites of each restaurant on the portal site, and stores the names of multiple menu items that each restaurant can offer for each restaurant. The menu information may be stored by menu category, such as appetizer/main course, lunch/dinner/course, etc. The menu information may also include text information indicating the menu name, price, description, etc., as well as image information such as photographs of the menu, which are stored in association with the menu.

The area information includes information about multiple areas with different units of size. Large areas include prefectures and municipalities, small areas include areas within a few hundred meters of a station (e.g., the "Ginza area"), and areas of intermediate size include, but are not limited to, areas within 1 km of a station or areas surrounding multiple stations (e.g., the "Ginza-Shinbashi-Yurakucho area"). This means that the same restaurant can be linked to multiple areas depending on its size.

The above category information may include main categories such as Japanese, Chinese, Italian, French, and yakiniku, as well as more detailed subcategories such as yakitori and tempura in Japanese cuisine, and pasta and pizza in Italian cuisine.

The restaurant information database 31 also stores one or more email addresses for each restaurant as destination information for reservation notification emails that notify the restaurant of the receipt of a restaurant reservation request from the user terminal 200. The email address may be an email address used by email software installed on the restaurant terminal 300, an email address used by email software installed on a smartphone owned by a restaurant employee separate from the restaurant terminal 300, or a webmail email address that can be received from the restaurant terminal 300 or an employee's terminal.

For example, in response to an approval request from the restaurant information providing server 100, or voluntarily, the manager of each restaurant sends approval information to the restaurant information providing server 100 via the management screen, email, etc., acknowledging that the email address set as the destination of the reservation notification email is still in use. The restaurant information database 31 also stores the history of the received approval information (date and time of receipt, email address of the person being approved) for each restaurant.

If the above email address becomes obsolete, is changed, or a new email address is added, the administrator sends information to that effect via the above management screen or email, and the restaurant information providing server 100 updates the destination information for reservation notification emails in the restaurant information database 31 accordingly.

The user information database 32 stores information about users who own user terminals 200 and are users (members) of the restaurant information service provided by the restaurant information providing server 100 via the portal site. Specifically, the user information database 32 stores information for each user, such as user ID, password, name, email address (and other information to which messages are addressed), telephone number, address, age (group), gender, and birthday.

The POS information database 33 stores POS data based on orders received from the user terminal 200 in each table T. This POS data consists of, for example, table ID, time of entry, number of customers, ordered menu, number of orders (number of items), sales amount, order time, etc.

The notification information database 34 stores information indicating user attributes for each table ID, which is generated based on the order information stored in the POS information database 33, as well as notification information generated according to the user attributes.

Notification information includes promotional information such as information suggesting recommended menu items for each of the above user attributes and information announcing recommended campaigns, as well as information to inform users, such as information guiding them to in-store facilities and information about last order times.

Furthermore, the notification information database 34 may store transmission history information (such as transmission date and time, destination table ID, user attributes, etc.) for notification information that was generated and sent to the user terminal 200 via the restaurant terminal 300.

These databases are mutually referenced as needed during the order acceptance process, user attribute determination process, and notification information generation process by the restaurant information providing server 100, which will be described later.

[Operation of Restaurant Information Providing Server]
Next, we will explain the operation of the restaurant information providing server 100 configured as above. This operation is executed by the cooperation of hardware such as the CPU 11 and communication unit 19 of the restaurant information providing server 100 and software stored in the storage unit 18. For convenience, in the following explanation, the CPU 11 is the subject of operation.

Figure 4 is a flowchart showing the flow of the restaurant order reception process, user attribute determination process, and notification information generation process performed by the restaurant information providing server 100.

As shown in the figure, the CPU 11 of the restaurant information providing server 100 first determines whether a table ID has been received from the user terminal 200 (step 41).

As described above, the table ID is stored in a two-dimensional code C printed on a printed material placed on each table T, and the two-dimensional code C is read by the user terminal 200 using a code reader and transmitted to the restaurant information providing server 100.

In addition, when the table ID is read by the user terminal and received by the restaurant information providing server 100, an order page containing a list of the food and drink offered by the restaurant is sent to the user terminal 200 and displayed by the browser or application on the user terminal 200. This enables the restaurant information providing server 100 to receive food and drink order information from the user terminal 200 (to accept orders). In addition, when the user terminal 200 receives the order page, information identifying the user terminal 200 is stored, for example, using a cookie, allowing the restaurant information providing server 100 to identify the user terminal 200.

Multiple users using the same table T can each send order information from their own user terminal 200. Even if the user terminal 200 that sent the order information is different, the CPU 11 will treat the order information as being from the same table T if the table ID included in the order information is the same.

If it is determined that a table ID has been received from the user terminal 200 (Yes in step 41), the CPU 11 associates the table ID with the time of reception and records it as the store entry time of the user using the table identified by the table ID (step 42).

The CPU 11 then determines whether order information has been received from the user terminal 200 (step 43). The order information is sent via the order page displayed on the user terminal 200 as described above. The order information includes the menu name or menu ID of the ordered food and drink, quantity, etc., as well as the table ID of the table T used by the user terminal 200 that sent the order.

If it is determined that order information has been received from the user terminal 200 (Yes), the CPU 11 records the order information in the POS information database 33 and transmits it to the restaurant terminal 300 (step 44). An employee then checks the order information received by the restaurant terminal 300 and begins preparing the food and drink in the restaurant's kitchen according to the order information.

Next, the CPU 11 determines the user attributes for each table T (step 45). Here, the CPU 11 determines the user attributes for each table T based on information acquired by accepting orders from the user terminal 200 using that table T from the time the table ID is first acquired until payment for that table T.

Typically, the CPU 11 determines user attributes by analyzing the order information. For example, by analyzing the trends in the food and drink ordered at each table T, it is possible to determine attributes such as a high proportion of vegetable dishes ordered, a high proportion of meat dishes ordered, or a high proportion of alcoholic beverages ordered (high order frequency). Naturally, a certain amount of order information must be accumulated to determine user attributes from order information alone, and the CPU 11 may decide that attributes cannot be determined if there is too little order information for each table T.

Furthermore, if the user terminal 200 is logged in to a portal site service provided by the restaurant information providing server 100, for example, the restaurant information providing server 100 may also transmit the user ID of the user of the user terminal 200 on the service when reading the two-dimensional code C or when transmitting order information. When transmitting the order page to the user terminal 200, the CPU 11 may provide a user interface for logging in to the service on the order page to prompt the user to log in. When the user terminal 200 logs in, the table ID and user ID are associated and stored.

The CPU 11 may then determine the above attributes based on the personal information of the user linked to the user ID (such as name, gender, age, occupation, address, reservation history, etc.). For example, the CPU 11 may determine the above attributes based on information that is common to a predetermined percentage (e.g., 50%, 80%, etc.) or more of the personal information of the users of multiple user terminals 200 that are the source of the same table ID. In this case, common information may be, for example, female (gender), elderly (age group), or the same family (relationship between users), etc.

The CPU 11 may also determine attributes based on the number of user terminals or user IDs that sent the same table ID (i.e., the number of users of table T). For example, the CPU 11 may assign attributes such as group tour (10 or more people), large group (6 to 9 people), medium group (3 to 5 people), small group (2 people), or individual (1 person) depending on the number.

If the CPU 11 determines that the above user attributes have been determined for at least one table T (Yes in step 45), it classifies the tables T by the determined attributes (step 46). In other words, the CPU 11 treats multiple tables T assigned the same attribute as a single group.

The CPU 11 then generates notification information for each table classification based on the determined attributes and stores the notification information in the notification information database 34 (step 46). This eliminates the need to generate duplicate notification information for tables T with the same attributes.

The control unit may classify all tables at the restaurant by the determined attribute and generate the same notification information for each table classification. This allows the information processing system to avoid the waste of generating duplicate notification information for tables with the same attribute, compared to when notification information is generated for each table.

As mentioned above, the notification information is typically information suggesting recommended menu items for each of the above user attributes, but it may also be other sales promotion information, such as information announcing recommended campaigns, or information sent to users other than sales promotion information.

As information suggesting recommended menu items for each user attribute, for example, if a user attribute is determined to be a high rate of ordering meat dishes, notification information suggesting vegetable dishes may be generated, or if a user attribute is determined to be a high frequency of ordering sake, notification information suggesting different brands of sake recommended by the restaurant may be generated.

Furthermore, if the attribute of a group of women is determined from the above personal information, notification information suggesting healthy dishes (or dishes classified as such on the menu) may be generated, and if the attribute of a group of students is determined, notification information suggesting student discount menus or hearty dishes may be generated.

Next, the CPU 11 determines whether the notification information sending screen has been accessed from the restaurant terminal 300 (step 49).

If it is determined that the notification information sending screen has been accessed (Yes), the CPU 11 generates an operation screen (notification information sending screen) in which buttons for sending notification information are arranged in different areas for each classification (attribute) of table T, and sends it to the restaurant terminal 300 that made the access (step 50).

Figure 5 shows an example of the notification information sending screen.

As shown in the figure, the notification information transmission screen has multiple notification information display areas 51 for each of the attributes determined above. While four notification information display areas 51 are shown in the figure, in reality, five or more notification information display areas 51 may be generated, and all notification information display areas 51 may be viewable by scrolling.

Each notification information display area 51 has an attribute/table display field 52 that displays the name of the attribute determined above and the number of the table classified into that attribute, and a notification information send button 53, which is a user interface for sending the notification information generated according to that attribute to the user terminal 200 that uses the corresponding table T.

In the example shown in the figure, for example, in the notification information display area 51 in the upper left, tables 2 and 6 are associated with the attribute "Many orders for sake," and notification information to be sent to those tables is associated with information suggesting different brands of sake.

Returning to FIG. 4, the CPU 11 determines whether an operation to send notification information has been input using the notification information send button 53 on the notification information send screen displayed on the restaurant terminal 300 (step 51).

If it is determined that an operation to send notification information has been input (Yes), the CPU 11 extracts the corresponding notification information from the notification information database 34 and transmits it to the user terminal 200 linked by the table ID of the table T corresponding to the notification information and a cookie, user ID, etc. (step 52).

As shown in Figure 5 above, if notification information is associated with multiple tables T, when the notification information send button 53 is pressed, the notification information is simultaneously sent to the user terminals 200 of each user who uses all of the associated tables T.

The CPU 11 repeats the above process for each table T until it receives a payment request from the user terminal 200. If it receives a payment request from the user terminal 200 (Yes in step 53), it updates the POS information database 33, executes payment processing, for example, using a credit card or electronic money, and sends the payment information to the restaurant terminal 300, terminating the process (step 54).

[summary]
As described above, according to this embodiment, the restaurant information providing server 100 generates notification information according to attributes determined by analyzing order information from the user terminal 200, thereby enabling restaurant employees in a mobile ordering system to carry out sales promotion activities tailored to a customer's table T without having to go to that table T.

In addition, the restaurant information providing server 100 can simultaneously send the same notification information to all user terminals of multiple tables T that have been assigned the same attributes, thereby reducing the processing load and preventing network congestion compared to sending notification information individually.

[Modification]
The present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the spirit and scope of the present invention.

In the above-described embodiment, the restaurant information providing server 100 collectively sends notification information to multiple tables T with the same attributes. Alternatively, the restaurant information providing server 100 may send individual notification information for each table T. For example, the restaurant information providing server 100 may generate and send notification information suggesting the number or amount of food and drink (e.g., drinks for the same number of people as in the previous order) according to the number of user terminals or user IDs that have transmitted the same table ID (i.e., the number of users of table T).

The restaurant information providing server 100 may also generate and transmit notification information according to the attributes, suggesting food and drink according to the amount of time that has elapsed since the table ID was received. For example, the restaurant information providing server 100 may generate notification information suggesting appetizers or main dishes according to the attributes before a predetermined amount of time has elapsed, and may generate notification information suggesting rice dishes or noodles according to the attributes after the predetermined amount of time has elapsed. Also, different types of food may be associated with three or more elapsed time periods, and notification information may be generated accordingly.

Furthermore, if the elapsed time exceeds a predetermined time (for example, 30 minutes before the last order), the restaurant information providing server 100 may generate, as the notification information, information suggesting takeaway food and drink according to the attributes. This allows restaurants to further increase sales by suggesting takeaway food and drink when, for example, the user is unable to finish the food and drink they ordered based on the remaining available time.

In addition, the restaurant information providing server 100 may generate notification information suggesting additional or takeaway food and drink options according to the above attributes when a restaurant is unlikely to achieve its sales target for the day or for that time period. This allows restaurants to proactively send promotional notification information when their sales are not meeting their sales target for the day, thereby making every effort to achieve their sales target for the day.

In the above-described embodiment, the restaurant information providing server 100 may display, in each notification information display area 51 on the notification information sending screen, information indicating the sending history of the notification information in that area 51 to the user terminal 200 for each table T. The sending history is composed of, for example, the table number and the sending time. This allows restaurant staff to send more effective promotional notification information for each table T while checking the past sending history of notification information.

In the above-described embodiment, the table ID is transmitted to the restaurant information providing server 100 in the form of a two-dimensional code C, which is read by the user terminal 200. However, the method by which the restaurant information providing server 100 receives the table ID is not limited to this. For example, the user terminal 200 may receive a table ID transmitted by a beacon terminal installed on each table T, and then transmit the table ID to the restaurant information providing server 100.

In the above embodiment, an example was shown in which a cloud-based restaurant information providing server 100 performs order reception processing, user attribute determination processing, and notification information generation processing for multiple restaurants. However, a server with similar functions to the restaurant information providing server 100 may be installed for each restaurant, and the order reception processing, user attribute determination processing, and notification information generation processing may be performed.

Among the inventions described in the claims of this application, the invention described as an "information processing method" has each step performed automatically by at least one device such as a computer through software-based information processing, and is not performed by a human using a device such as a computer. In other words, the "information processing method" is an information processing method using computer software, and is not a method in which a human operates a computing tool called a computer.

11...CPU
DESCRIPTION OF SYMBOLS 18: Storage unit 19: Communication unit 31: Restaurant information database 32: User information database 33: POS information database 34: Notification information database 51: Notification information display area 52: Attribute/table display field 53: Notification information transmission button 100: Restaurant server 200: User terminal 300: Restaurant terminal

Claims (4)

a communication unit that receives table identification information that identifies a table placed at the restaurant from a user terminal, and receives reception information including order information from the user terminal during the period from the reception of the table identification information to the payment for the table;
Analyzing the received information for each of the table identification information to determine an attribute of a user group for each of the table identification information;
If the elapsed time since the reception of the table identification information does not exceed a predetermined time, first notification information is generated in accordance with the determined attribute, the first notification information suggesting food and drink to be consumed in the restaurant to a user group of the table;
and a control unit that generates second notification information suggesting takeaway food and drink to the user group at the table according to the determined attributes when the elapsed time exceeds the predetermined time. 2. The information processing system according to claim 1,
The control unit generates the second notification information when it determines that the elapsed time exceeds the predetermined time and that the user group will not be able to finish eating and drinking the food and drink they ordered within the remaining time until payment . receiving table identification information identifying a table placed at the restaurant from a user terminal;
receiving, from the user terminal, reception information including order information, during the period from receiving the table identification information to settling the table;
Analyzing the received information for each of the table identification information to determine an attribute of a user group for each of the table identification information;
If the elapsed time since the reception of the table identification information does not exceed a predetermined time, first notification information is generated in accordance with the determined attribute, the first notification information suggesting food and drink to be consumed in the restaurant to a user group of the table;
If the elapsed time exceeds the predetermined time, second notification information is generated according to the determined attribute, the second notification information suggesting takeaway food and drink to the user group at the table. In the information processing device,
receiving table identification information from a user terminal that identifies a table placed at the restaurant;
receiving, from the user terminal, reception information including order information, during the period from receiving the table identification information to settling the table;
determining an attribute of a user group for each of the table identification information by analyzing the received information for each of the table identification information;
generating first notification information, in accordance with the determined attribute, for a user group of the table, suggesting food and drink to be consumed in the restaurant, if the elapsed time from the time of receiving the table identification information does not exceed a predetermined time;
and if the elapsed time exceeds the predetermined time, generating second notification information suggesting takeaway food and drink to the user group at the table according to the determined attributes.