system

Abstract

Provide a system. A means for receiving and storing user registration information; A means for receiving and storing drinking party request information; A means for searching for and providing suitable candidate stores based on the stored request information; A means for making a reservation at a store selected by the user and notifying the user of reservation confirmation information; A means for notifying participants of the drinking party information and sending reminder messages; means for receiving and aggregating participant attendance information; A means of providing necessary information on the day of the drinking party Including system.

Description

[Technical Field]

[0001] The technology of the present disclosure relates to a system. [Background technology]

[0002] Patent document 1 discloses a persona chatbot control method performed by at least one processor, the method including the steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to a description of the chatbot character, encoding the prompt, and inputting the encoded prompt into a language model to generate a chatbot utterance in response to the user utterance. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-180282 Summary of the Invention [Problem to be solved by the invention]

[0004] The work of organizing a party is burdensome and stressful due to busy schedules and complicated communication. In particular, when organizing a drinking party, the organizer must handle a wide range of tasks, such as confirming attendance, selecting a restaurant, making reservations, and communicating detailed information. Therefore, there is a need for a system that can efficiently handle these tasks on behalf of the organizer. [Means for solving the problem]

[0005] The present invention includes the following means to provide a system that smoothly performs organizing tasks.

[0006] The system is equipped with a means for receiving and saving user registration information, a means for receiving and saving drinking party request information, a means for searching for and providing suitable candidate restaurants based on the saved request information, a means for making a reservation at the restaurant selected by the user and notifying the reservation confirmation information, a means for notifying participants of the drinking party information and sending reminder messages, a means for receiving and tallying up attendance information of participants, and a means for providing information necessary on the day of the drinking party. This allows the system to efficiently handle the organizing work and significantly reduce the burden on the user.

[0007] "User registration information" refers to personal information (e.g., name, email address, telephone number) required to identify and contact users who use the system.

[0008] "Drinking party request information" refers to the details of the drinking party (e.g., date and time, location, number of participants, budget, special requests) that the user specifies to the system.

[0009] "Means for storing" refers to the function of recording received information in a database, storage device, etc. so that it can be referenced later.

[0010] "Candidate stores" refers to a list of stores suitable for hosting a drinking party suggested by the system.

[0011] "Searching means" refers to the function of searching for stores that meet specific conditions from a database or external information source based on the saved request information.

[0012] "Means for providing" refers to the function of notifying the user of a list of candidate stores obtained as a search result.

[0013] "Means for making a reservation" refers to the function by which the system automatically processes reservations for the store selected by the user.

[0014] "Reservation confirmation information" refers to the reservation confirmation information obtained by the system from the store.

[0015] "Means of notification" refers to the system's ability to communicate necessary information to users and participants via means such as email or SNS messages.

[0016] "Participants" refer to people who plan to attend a drinking party designated by the user.

[0017] A "remind message" refers to a notification message sent the day before or on the day of a drinking party to remind people to confirm or be careful.

[0018] "Attendance information" refers to information that indicates whether or not participants will attend a drinking party.

[0019] "Means of aggregating" refers to the function of compiling the total number and details of those scheduled to attend based on the attendance information received.

[0020] "Means of providing" refers to the function that makes the information necessary on the day of the drinking party (e.g., participant list, store information, contact information) available to users. [Brief explanation of the drawings]

[0021] [Figure 1] 1 is a conceptual diagram showing an example of the configuration of a data processing system according to a first embodiment. [Figure 2] 1 is a conceptual diagram showing an example of main functions of a data processing device and a smart device according to a first embodiment. [Figure 3] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a second embodiment. [Figure 4] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and smart glasses according to a second embodiment. [Figure 5] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a third embodiment. [Figure 6] FIG. 11 is a conceptual diagram showing an example of main functions of a data processing device and a headset-type terminal according to a third embodiment. [Figure 7] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a fourth embodiment. [Figure 8] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and a robot according to a fourth embodiment. [Figure 9] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 10] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 11] FIG. 3 is a sequence diagram showing a processing flow of the data processing system according to the first embodiment. [Figure 12] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 1. [Figure 13] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system according to the second embodiment when an emotion engine is combined. [Figure 14] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 2 when an emotion engine is combined. DETAILED DESCRIPTION OF THE INVENTION

[0022] An example of an embodiment of a system according to the technology of the present disclosure will be described below with reference to the accompanying drawings.

[0023] First, the terms used in the following description will be explained.

[0024] In the following embodiments, a coded processor (hereinafter simply referred to as a "processor") may be a single arithmetic device or a combination of multiple arithmetic devices. Furthermore, a processor may be a single type of arithmetic device or a combination of multiple types of arithmetic devices. Examples of arithmetic devices include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a GPGPU (General-Purpose computing on Graphics Processing Units), and an APU (Accelerated Processing Unit).

[0025] In the following embodiments, a coded RAM (Random Access Memory) is a memory in which information is temporarily stored and is used as a working memory by a processor.

[0026] In the following embodiments, the coded storage is one or more non-volatile storage devices that store various programs, various parameters, etc. Examples of non-volatile storage devices include flash memory (SSD (Solid State Drive)), magnetic disks (e.g., hard disks), and magnetic tapes.

[0027] In the following embodiments, a communication I / F (Interface) with a symbol is an interface including a communication processor, an antenna, etc. The communication I / F controls communication between multiple computers. Examples of communication standards applied to the communication I / F include wireless communication standards including 5G (5th Generation Mobile Communication System), Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.

[0028] In the following embodiments, "A and / or B" is synonymous with "at least one of A and B." In other words, "A and / or B" means that it may be only A, only B, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" is also applied when three or more things are expressed connected by "and / or."

[0029] [First embodiment]

[0030] FIG. 1 shows an example of the configuration of a data processing system 10 according to the first embodiment.

[0031] 1, a data processing system 10 includes a data processing device 12 and a smart device 14. An example of the data processing device 12 is a server.

[0032] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0033] The smart device 14 includes a computer 36, a reception device 38, an output device 40, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The reception device 38, the output device 40, and the camera 42 are also connected to the bus 52.

[0034] The reception device 38 includes a touch panel 38A, a microphone 38B, and the like, and receives user input. The touch panel 38A detects contact with an indicator (for example, a pen or a finger) to receive user input by the touch of the indicator. The microphone 38B detects the user's voice to receive user input by voice. The control unit 46A transmits data indicating the user input received by the touch panel 38A and the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the data indicating the user input.

[0035] The output device 40 includes a display 40A and a speaker 40B, and presents data to the user 20 by outputting the data in a form of expression that the user 20 can perceive (for example, audio and / or text). The display 40A displays visible information such as text and images in accordance with instructions from the processor 46. The speaker 40B outputs audio in accordance with instructions from the processor 46. The camera 42 is a compact digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor.

[0036] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54.

[0037] FIG. 2 shows an example of the main functions of the data processing device 12 and the smart device 14.

[0038] 2, in the data processing device 12, a specific process is performed by the processor 28. A specific processing program 56 is stored in the storage 32. The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific process is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0039] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0040] In the smart device 14, the processor 46 performs the reception output process. The storage 50 stores a reception output program 60. The reception output program 60 is used in conjunction with the specific processing program 56 by the data processing system 10. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0041] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0042] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[0043] Explanation of program processing

[0044] 1. User registration function

[0045] Users access the system using a terminal and enter personal information such as their name and email address.

[0046] The server receives this information and stores it in a database.

[0047] The user will receive a message confirming registration.

[0048] 2. Accepting drinking party requests

[0049] The user accesses a form for requesting a drinking party through the terminal.

[0050] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[0051] The user is notified that the request has been accepted.

[0052] 3. Proposal of candidate stores

[0053] The server searches the database for store information based on the received request information.

[0054] The server generates a list of stores that match the criteria and provides it to the user via email or notification.

[0055] The user checks the list and selects the desired store.

[0056] 4. Store reservation agent

[0057] The store information selected by the user is sent to the server.

[0058] The server performs the reservation procedure with the store and obtains confirmation information that the reservation has been completed.

[0059] The user is notified that the reservation is complete.

[0060] 5. Notification and reminders to participants

[0061] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[0062] It also sends a reminder message the day before the drinking party.

[0063] 6. Participation confirmation function

[0064] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[0065] The server receives the attendance information and stores and aggregates it in a database.

[0066] 7. Support on the day of the drinking party

[0067] The server provides users with the information they need on the day of the party (e.g., participant list, store information, contact information).

[0068] Users can use the system to receive the support they need based on their situation.

[0069] Specific examples

[0070] Example of a user registering in the system

[0071] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[0072] The server receives this information and stores it in a database.

[0073] The user will receive a message saying "Registration complete."

[0074] Example of requesting a drinking party

[0075] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food."

[0076] The server receives the request and stores it in a database.

[0077] The user will receive a notification that their request has been accepted.

[0078] Examples of proposed stores

[0079] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "budget of 5,000 yen" to generate a list of candidate restaurants, such as "Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN."

[0080] The user is notified of the list.

[0081] Store selection and reservation example

[0082] The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[0083] The server will make a reservation at Charcoal Grilled Meat ZEN.

[0084] The server receives the reservation confirmation and notifies the user.

[0085] Examples of notifications and reminders for participants

[0086] The server receives the participant list and notifies all participants of the details of the drinking party.

[0087] Send a reminder message the day before the drinking party.

[0088] Examples of support on the day of a drinking party

[0089] The server provides the user with a list of participants, store information, contact information, etc., and provides additional information as needed.

[0090] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[0091] The processing flow will be explained below.

[0092] User registration function

[0093] Step 1:

[0094] The user uses the terminal to access the URL of the user registration form.

[0095] Step 2:

[0096] The user enters personal information such as name, email address, and phone number.

[0097] Step 3:

[0098] The user presses the registration button.

[0099] Step 4:

[0100] The terminal transmits the input data to the server.

[0101] Step 5:

[0102] The server receives the data and stores it in a database.

[0103] Step 6:

[0104] The server generates a registration completion message and sends it to the terminal.

[0105] Step 7:

[0106] The user will see a message on their device confirming successful registration.

[0107] Accepting drinking party requests

[0108] Step 1:

[0109] The user uses the terminal to access the URL of the drinking party request form.

[0110] Step 2:

[0111] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[0112] Step 3:

[0113] The user presses the request button.

[0114] Step 4:

[0115] The terminal transmits the input data to the server.

[0116] Step 5:

[0117] The server receives the data and stores it in a database.

[0118] Step 6:

[0119] The server generates a message accepting the request and sends it to the terminal.

[0120] Step 7:

[0121] The user checks the message on the terminal that the request has been accepted.

[0122] Proposal of candidate stores

[0123] Step 1:

[0124] The server searches for store information in the database.

[0125] Step 2:

[0126] The server will list appropriate stores based on the request information (date, time, location, budget, special requests).

[0127] Step 3:

[0128] The server generates a list of candidate stores.

[0129] Step 4:

[0130] The server sends the list to the user's email address.

[0131] Store selection and reservation

[0132] Step 1:

[0133] The user receives a list of candidate stores and selects the store of their choice.

[0134] Step 2:

[0135] The user notifies the server of the selected store information.

[0136] Step 3:

[0137] The server then performs the reservation procedure for the selected store.

[0138] Step 4:

[0139] The server acquires reservation confirmation information from the store.

[0140] Step 5:

[0141] The server will send a notification of reservation completion to the user's email address.

[0142] Notifications and reminders to participants

[0143] Step 1:

[0144] The user inputs the participant's email address and contact information into the server and sends it.

[0145] Step 2:

[0146] The server will notify participants of details about the drinking party via email or SNS message.

[0147] Step 3:

[0148] The server sends a reminder message the day before the party.

[0149] Participation confirmation function

[0150] Step 1:

[0151] Participants will access the participation confirmation page via a link in the email.

[0152] Step 2:

[0153] Participants enter whether they will attend and press the send button.

[0154] Step 3:

[0155] The terminal transmits the attendance information to the server.

[0156] Step 4:

[0157] The server receives the attendance information and stores it in a database.

[0158] Step 5:

[0159] The server tally the stored attendance information.

[0160] Support on the day of the drinking party

[0161] Step 1:

[0162] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[0163] Step 2:

[0164] The server provides the necessary information to the user.

[0165] Step 3:

[0166] The user uses the system to check the necessary information.

[0167] Example 1

[0168] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0169] Traditionally, organizing a drinking party was a time-consuming and labor-intensive process, placing a heavy burden on users. In particular, it was difficult to efficiently organize a drinking party due to the complex and wide-ranging tasks involved, such as selecting an appropriate restaurant based on the number of people and budget, making reservations, notifying and reminding participants, and confirming attendance.

[0170] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0171] In this invention, the server includes: means for a user to access the system's "user registration" page using a terminal and input personal information such as name, email address, and password; means for the server to receive the input information and store it in a database; means for a user to input detailed information about a drinking party (date, time, location, number of people, budget, special requests); means for the server to receive the input information and store it in a database; means for the server to search the database for restaurant information matching the conditions based on the stored request information; means for the server to provide the user with the generated restaurant list; means for the user to make a reservation at a restaurant selected by the user and obtain reservation confirmation information; means for the server to notify the user of the reservation confirmation information; means for the server to notify participants of detailed information about the drinking party based on the attendee list provided by the user; means for the server to send a reminder message to participants the day before the drinking party; means for participants to access the attendance confirmation page through their terminal and input whether or not they will attend; means for the server to receive the attendance information and store and tally it in a database; and means for the server to provide users with information necessary on the day of the drinking party. This enables efficient management of drinking party events.

[0172] "User registration information" is a general term for personal information such as a user's name, email address, and password.

[0173] "Terminal" refers to an electronic device such as a computer or smartphone that a user uses to access a server via the Internet.

[0174] A "server" is a computer system that receives and processes requests from users, and provides functions such as database management and email transmission.

[0175] "Database" refers to a system for efficiently storing, managing, and retrieving information, and specifically includes relational databases such as MySQL (registered trademark).

[0176] "Drinking party request information" is a general term for detailed information necessary for hosting a drinking party, such as the date and time of the drinking party, the location, the number of people, the budget, and any special requests.

[0177] "Candidate store information" refers to a list of restaurants that meet the conditions based on the drinking party request information.

[0178] "Reservation confirmation information" refers to information indicating that the server has made a reservation with the restaurant and that the reservation has been confirmed.

[0179] "Participant list" is a general term for information provided by a user, such as names and contact information of people who plan to attend a drinking party.

[0180] A "reminder message" is a notification message sent to participants the day before a drinking party to help them remember to attend.

[0181] "Attendance confirmation information" refers to information indicating whether or not participants will be able to attend a drinking party, which is entered by participants through the attendance confirmation page.

[0182] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[0183] Specifically, the following hardware and software are used:

[0184] Hardware:

[0185] Device (PC, smartphone, etc.)

[0186] Servers (web servers, database servers, etc.)

[0187] software:

[0188] Web browser

[0189] Web Applications

[0190] Database management system (e.g. MySQL)

[0191] Mail server (e.g. SMTP server)

[0192] API connection (e.g., Google Calendar API)

[0193] User Registration

[0194] The user accesses the system's "User Registration" page using a terminal and enters personal information such as name, email address, and password. The server receives this information and stores it in a database such as MySQL. The user receives a confirmation email stating "Registration completed."

[0195] Specific examples

[0196] The user accesses "https: / / nomikai-system.com / register" on a smartphone or PC and enters information such as "Yamada Taro," "taro_yamada@example.com," and "password123." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user a confirmation email stating "Registration completed."

[0197] Accepting drinking party requests

[0198] The user accesses the "Drinking Party Request" form through their device and enters the details of the drinking party (date, time, location, number of people, budget, special requests). The server receives the entered information and stores it in a database. The user receives an email notification that the "request has been accepted."

[0199] Specific examples

[0200] The user accesses "https: / / nomikai-system.com / request" and enters the information "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user an email notification that "the request has been accepted."

[0201] Proposal of candidate stores

[0202] The server searches for restaurant information in the database based on the drinking party request information. It generates a list of restaurants that match the criteria and provides it to the user via email or notification. The user can then review the list and select the restaurant they want.

[0203] Specific examples

[0204] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "5,000 yen," and generates a list of restaurants that meet the criteria ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN"). The server then sends the list of candidate restaurants to the user via email. The user looks at the email they receive, selects the restaurant they want (for example, "Charcoal Grilled Meat ZEN"), and notifies the server.

[0205] Store reservation service

[0206] The user sends the store information they selected to the server. The server then completes the reservation procedure with the store and receives confirmation that the reservation is complete. The user receives a notification that the reservation is complete.

[0207] Specific examples

[0208] The user selects "Charcoal Grilled Meat ZEN" and notifies the server. The server processes the reservation with "Charcoal Grilled Meat ZEN" using an API call or a telephone automation system. The server obtains the reservation confirmation and stores it in a database. The user receives an email stating "Reservation completed."

[0209] Notifications and reminders to participants

[0210] The server notifies participants of the details of the drinking party based on the participant list provided by the user, and also sends a reminder message the day before the drinking party.

[0211] Specific examples

[0212] The server notifies all participants of the "Drinking Party Details" by email based on the participant list. The day before the drinking party, the server automatically sends a reminder message using the Google Calendar API.

[0213] Participation confirmation function

[0214] Participants access the attendance confirmation page via their terminal and enter whether they will attend. The server receives the attendance information and stores and compiles it in a database.

[0215] Specific examples

[0216] Participants access "https: / / nomikai-system.com / confirm" to confirm their attendance. The server receives the attendance information and stores it in a MySQL database. The server then sends the tally results to the user.

[0217] Support on the day of the drinking party

[0218] The server provides users with the necessary information on the day of the drinking party, and users use the system to receive the necessary support according to the situation.

[0219] Specific examples

[0220] On the morning of the party, the server will email the user details such as the participant list, store information, and emergency contact information. Any additional information or support the user needs will be received in real time through the system.

[0221] Prompt Sentence Examples

[0222] I want to register user information in the system. The username is "Yamada Taro" and the email address is "taro_yamada@example.com". Please explain the process for saving this information to the database.

[0223] A user fills out a form to request a drinking party with the following information: "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food." Explain the process for saving this information to a database.

[0224] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[0225] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0226] Program processing flow

[0227] Step 1: User Registration

[0228] 1. The user accesses the "User Registration" page using a terminal.

[0229] Input: The URL where users will access the registration page.

[0230] Output: Display of user registration form.

[0231] Specific operation: The user accesses "https: / / nomikai-system.com / register".

[0232] 2. The user enters personal information such as name, email address, and password.

[0233] Input: Name, Email Address, Password.

[0234] Output: The information entered.

[0235] Specific operation: The user enters "Yamada Taro", "taro_yamada@example.com", and "password123".

[0236] 3. The server receives the entered information and stores it in a database.

[0237] Input: Personal information entered by the user.

[0238] Output: User information stored in the database.

[0239] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[0240] 4. The server sends the user a message confirming registration.

[0241] Input: User information stored in the database.

[0242] Output: A confirmation email confirming successful registration.

[0243] Specific behavior: The server sends a confirmation email saying "Registration completed."

[0244] Step 2: Accepting a drinking party request

[0245] 1. The user accesses the "Drinking Party Request" form via their device.

[0246] Input: The URL where users can access the request form.

[0247] Output: Display of drinking party request form.

[0248] Specific operation: The user accesses "https: / / nomikai-system.com / request".

[0249] 2. The user enters the details of the drinking party (date, time, location, number of people, budget, special requests).

[0250] Input: date, time, location, number of people, budget, special requests.

[0251] Output: The request information entered.

[0252] Specific operation: The user enters "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food."

[0253] 3. The server receives the entered information and stores it in a database.

[0254] Input: Request information entered by the user.

[0255] Output: Request information stored in a database.

[0256] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[0257] 4. The server sends a message to the user acknowledging the request.

[0258] Input: Request information stored in the database.

[0259] Output: Email confirming acceptance of request.

[0260] Specific behavior: The server sends a confirmation email saying "your request has been accepted."

[0261] Step 3: Proposing potential stores

[0262] 1. The server searches for store information in the database based on the drinking party request information.

[0263] Input: Request details (location, budget, special requests).

[0264] Output: A list of stores that match the criteria.

[0265] Specific operation: The server searches the database for the conditions "Shinjuku," "Japanese food," and "5,000 yen."

[0266] 2. The server generates a list of stores that match the conditions.

[0267] Input: Store information as search results.

[0268] Output: The generated store list.

[0269] Specific operation: Generate a list of stores that meet the conditions ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," "Charcoal Grill Niku ZEN").

[0270] 3. The server notifies the user of the store list.

[0271] Input: Generated store list.

[0272] Output: Store list notification email.

[0273] Specific operation: The server sends the user a list of candidate stores by email.

[0274] 4. The user selects the store of their choice.

[0275] Input: Store list.

[0276] Output: Selected store information.

[0277] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[0278] Step 4: Store reservation

[0279] 1. The store information selected by the user is sent to the server.

[0280] Input: Selected store information.

[0281] Output: Store information sent to the server.

[0282] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[0283] 2. The server makes a reservation with the store.

[0284] Input: Selected store information.

[0285] Output: A reservation request to the store.

[0286] Specific operation: The server makes a reservation to "Charcoal Grilled Meat ZEN" using an API call or an automated telephone system.

[0287] 3. The server receives confirmation of the reservation.

[0288] Input: Reservation confirmation information from the store.

[0289] Output: The retrieved reservation confirmation information.

[0290] What happens: The server gets the booking confirmation and stores it in the database.

[0291] 4. The server sends a notification to the user that the reservation is complete.

[0292] Input: Retrieved reservation confirmation information.

[0293] Output: Notification email of reservation completion.

[0294] Specific behavior: Sends the user an email saying "Reservation completed."

[0295] Step 5: Notify and remind participants

[0296] 1. The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[0297] Input: Participant list, details of the drinking party.

[0298] Output: Notification email to participants.

[0299] Specific operation: Based on the participant list, the server notifies all participants of the "details of the drinking party" by email.

[0300] 2. The server sends a reminder message the day before the drinking party.

[0301] Input: Participant list.

[0302] Output: Reminder message email.

[0303] Specific operation: The server uses the Google Calendar API to automatically send a reminder message the day before the drinking party.

[0304] Step 6: Participation confirmation function

[0305] 1. Participants access the attendance confirmation page via their device.

[0306] Input: The URL of the attendance confirmation page.

[0307] Output: Display of attendance confirmation form.

[0308] Specific action: Participant accesses "https: / / nomikai-system.com / confirm".

[0309] 2. Participants enter whether they will attend.

[0310] Input: Attendance confirmation information.

[0311] Output: The attendance confirmation information entered.

[0312] Specific operation: Participants input whether they will attend or not.

[0313] 3. The server receives the attendance information and stores and aggregates it in a database.

[0314] Input: Attendance confirmation information entered by the participant.

[0315] Output: Attendance confirmation information and summary results stored in the database.

[0316] Specific operation: The server receives the attendance information, stores it in the database using SQL INSERT statements, and aggregates it.

[0317] Step 7: Support on the day of the drinking party

[0318] 1. The server provides the user with the information they need on the day of the drinking party.

[0319] Input: Party details, participant list, contact information.

[0320] Output: An email containing the required information.

[0321] Specific operation: On the morning of the drinking party, the server sends the user an email with details such as the list of participants, store information, and emergency contact information.

[0322] 2. Users use the system to receive the support they need in their context.

[0323] Input: The user's request.

[0324] Output: Supporting information provided.

[0325] Specific Action: The user receives any additional information or support they need in real time through the system.

[0326] (Application example 1)

[0327] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0328] Conventional party organizer tasks involve multiple, complicated procedures that require a great deal of time and effort when planning and running a drinking party. Tasks such as selecting potential restaurants, making reservations, and notifying participants of information are particularly complex, placing a heavy burden on organizers. Furthermore, providing necessary information in real time on the day of the party is difficult, making it difficult to respond to unforeseen circumstances. Another problem is that efficient methods for operating and managing smart devices have not yet been fully established.

[0329] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0330] In this invention, the server includes means for receiving and saving user registration information, means for receiving and saving drinking party request information, means for searching for and providing appropriate candidate restaurants based on the saved request information, means for making a reservation at a restaurant selected by the user and notifying the reservation confirmation information, means for notifying participants of drinking party information and sending reminder messages, means for receiving and compiling participant attendance information, means for providing information needed on the day of the drinking party, means for reading user registration information using a smart device when entering the restaurant and registering the user, means for displaying a list of candidate restaurants via the smart device and allowing selection, and means for visually providing information needed on the day of the drinking party using the smart device. This significantly reduces the workload involved in conventional organizing tasks and makes it possible to provide necessary information in real time.

[0331] "User registration information" refers to information including personal information such as the user's name and email address.

[0332] "Drinking party request information" refers to information such as the date and time of the drinking party, the location, the number of participants, the budget, and any special requests.

[0333] "Candidate store" refers to a store that is capable of hosting a drinking party and has been selected based on the drinking party request information.

[0334] "Reservation confirmation information" refers to the reservation confirmation information provided by the store after the reservation procedure has been completed.

[0335] "Participants" refers to people who plan to attend a drinking party.

[0336] "Information notification" refers to notifying participants of detailed information about the drinking party.

[0337] A "reminder message" refers to a confirmation message sent to participants the day before the drinking party.

[0338] "Attendance Information" refers to information regarding a participant's attendance confirmation.

[0339] "Smart device" refers to devices such as smartphones, smart glasses, or head-mounted displays.

[0340] "Visual presentation" refers to the method of displaying information directly in the user's field of vision through a smart device.

[0341] The present invention relates to a system that enables a user to efficiently perform administrative tasks using a smart device. The present invention is primarily implemented using a smart device such as a smartphone, smart glasses, or a head-mounted display.

[0342] First, the user accesses the system using a smart device. When the user enters a store, they scan a QR code (registered trademark) installed at the entrance or elsewhere. After scanning the QR code, the necessary information for user registration is displayed on the screen of the smart device. The user enters personal information such as their name and email address and presses the send button. This information is sent to the server and stored in a database.

[0343] Next, the user uses a smart device to input information about the drinking party request, such as the date, time, location, number of participants, budget, and any special requests. This information is sent to the server, and the request is saved in a database. Based on this request, the server searches the database for candidate restaurants and generates a list of restaurants that meet the user's requirements.

[0344] The generated list of stores is displayed on the screen of the smart device, and the user selects the store they want from the list. The store information selected by the user is sent to the server, which then processes the reservation. Once the reservation is complete, the server generates confirmation information and notifies the user via the smart device.

[0345] The server then notifies participants of the details of the drinking party based on the participant list provided by the user. Furthermore, a reminder message is automatically sent the day before the drinking party to prompt participants to confirm their attendance. The participants' attendance information is sent to the server and stored in a database.

[0346] On the day of the party, the server will display the necessary information (participant list, store information, contact information, etc.) on the screen of the smart device, allowing users to check the necessary information in real time and smoothly carry out their organizing duties.

[0347] Furthermore, the system significantly improves the overall efficiency of administrative work by transmitting information obtained from smart devices to a server in real time for analysis and processing. For example, by using smart glasses, users can visually obtain necessary information without using their hands, improving operability.

[0348] Hardware and software used

[0349] Hardware:

[0350] Smart glasses (e.g., Google Glass (registered trademark))

[0351] Smartphone

[0352] head-mounted display

[0353] Software and Libraries:

[0354] QRScanner: A library for reading QR codes

[0355] UserRegistryAPI: API to send user registration information to the server

[0356] PartyRequestAPI: API for managing drinking party request information

[0357] StoreDatabase: Database for searching information on potential stores

[0358] ReservationAPI: API for making store reservations

[0359] NotificationService: Service for notifying and reminding participants

[0360] AttendanceCheckAPI: API for receiving attendance confirmation information

[0361] InformationDisplayService: A service that displays information about the day of the drinking party

[0362] Examples and prompts

[0363] Examples:

[0364] A user enters a store and scans the QR code with the smart glasses. The user then enters their name and email address into the form displayed on the smart glasses screen to complete registration.

[0365] The user uses smart glasses to access a drinking party request form and enters the following: "Date and time: October 15, 2023, 7:00 PM," "Location: Commercial location," "Number of participants: 10," "Budget: 5,000 yen," and "Special request: Japanese cuisine."

[0366] The server uses this information to search for candidate stores and displays the results on the smart glasses screen. The user selects an appropriate store from the list and notifies the server.

[0367] The server makes a reservation at the selected store and notifies the user of reservation confirmation information.

[0368] The day before the drinking party, the server sends a reminder message to all participants and collects attendance confirmation information.

[0369] Prompt for the generative AI model:

[0370] - "Please explain the process of an application for smart glasses that will completely take over as organizer of a drinking party at a specific location on a specific date."

[0371] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0372] Step 1:

[0373] A user reads the QR code using a smart device. This allows the user to enter a store and scan the QR code displayed on the terminal using smart glasses or a smartphone. The input data is the content of the QR code (the URL of the user registration page), and the output is the user registration page being displayed on the smart device.

[0374] Step 2:

[0375] The user enters personal information such as name and email address into the user registration form displayed on the screen of the smart device and submits it. The input data is personal information such as name and email address, and is sent to the server. The server stores the submitted information in a database and returns a confirmation message to the user confirming completion of registration.

[0376] Step 3:

[0377] A user accesses a drinking party request form using a smart device and inputs the date, time, location, number of participants, budget, and any special requests for the drinking party. The input data is detailed information about the drinking party and is sent to the server. The server stores the received information in a database and notifies the user that the request has been accepted.

[0378] Step 4:

[0379] The server searches for candidate restaurants based on the drinking party request information it receives. The server searches the database and generates a list of suitable candidate restaurants based on the input data. The output data is the list of candidate restaurants, which is sent to the user's smart device.

[0380] Step 5:

[0381] The user selects the desired store from a list of candidate stores displayed on the screen of their smart device and sends that information to the server. The input data is the store information selected by the user, and the server processes the reservation based on this information. The server then generates reservation confirmation information and returns it to the user's smart device.

[0382] Step 6:

[0383] The server notifies participants of the details of the drinking party based on the participant list provided by the user. The input data is the participant list and drinking party details, and the output is a notification message to the participants. In addition, a reminder message is automatically sent the day before the drinking party.

[0384] Step 7:

[0385] Participants use smart devices to confirm their attendance. The input data, which indicates whether they are attending or not, is sent to the server and stored in a database. The server then compiles the attendance information and notifies the user.

[0386] Step 8:

[0387] On the day of the drinking party, users use smart devices to view the necessary information (e.g., participant list, store information, contact information). The server provides this information in real time, and users check the information displayed on the screen of their smart glasses or smartphone. The input data is the user's request, and the output data is the detailed information provided in real time.

[0388] Furthermore, an emotion engine that estimates the user's emotion may be combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59 and perform identification processing using the user's emotion.

[0389] The present invention shows a specific embodiment of a system that handles the organizing tasks of drinking parties, etc., by combining an emotion engine that recognizes the user's emotions and reflects them in the processing. This system not only smoothly performs user registration, reception of drinking party requests, proposal of candidate restaurants, restaurant reservations, notification to participants, attendance confirmation, and support on the day of the drinking party, but also provides a more appropriate and satisfying service by taking into account the emotions of the user and participants.

[0390] Explanation of program processing

[0391] 1. User registration function

[0392] Users access the system using a terminal and enter personal information such as their name and email address.

[0393] The server receives this information and stores it in a database.

[0394] A message is sent to the user indicating that registration is complete.

[0395] 2. Accepting drinking party requests

[0396] The user accesses a form for requesting a drinking party through the terminal.

[0397] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[0398] The server evaluates the user's emotional state using an emotion engine based on the request information.

[0399] The evaluation results from the emotion engine are reflected in the request information.

[0400] The user is notified that the request has been accepted.

[0401] 3. Proposal of candidate stores

[0402] The server searches the database for store information based on the emotion evaluation results included in the request information.

[0403] The server generates a list of stores that match the criteria and are appropriate for the user's emotional state.

[0404] The server sends the list to the user's email address.

[0405] The user checks the list and selects the desired store.

[0406] 4. Store reservation agent

[0407] The user notifies the server of the selected store information.

[0408] The server processes the reservation with the store.

[0409] The server acquires reservation confirmation information from the store.

[0410] The user is notified that the reservation is complete.

[0411] 5. Notification and reminders to participants

[0412] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[0413] Send a reminder message the day before the party.

[0414] 6. Participation confirmation function

[0415] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[0416] The server receives the attendance information, stores it in a database, and tally it up.

[0417] 7. Support on the day of the drinking party

[0418] The server generates the information needed on the day of the drinking party (e.g., participant list, store information, contact information).

[0419] The server provides the necessary information to the user.

[0420] The emotion engine suggests appropriate additional support in real time based on participants' reactions and feedback.

[0421] Specific examples

[0422] Example of a user registering in the system

[0423] The user accesses the "User Registration" page using a terminal and enters the name "Hanako Sato" and the email address "hanako_sato@example.com".

[0424] The server receives this information and stores it in a database.

[0425] The user will be notified with the message "Registration complete."

[0426] Example of requesting a drinking party

[0427] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: December 15, 2023, 7:00 PM," "Location: Shibuya," "Number of participants: 8," "Budget: 6,000 yen," and "Request: Western food."

[0428] The server receives the request and stores it in a database.

[0429] The emotion engine evaluates the user's emotions from the input content and obtains an evaluation result such as "I want to relax."

[0430] The server will send a notification to the user saying "your request has been accepted."

[0431] Examples of proposed stores

[0432] The server reflects the evaluation result "I want to relax" and searches the database.

[0433] The server will then provide a list of restaurants that match the criteria of "Shibuya," "Western cuisine," and "budget of 6,000 yen" and have a reputation for being relaxing. The list will include "Cafe Restaurant Hanakoji," "Shibuya Italian Restaurant La Pasta," and "French Bistro Le Petit Bar."

[0434] The server emails the list to the user.

[0435] Store selection and reservation example

[0436] The user selects "French Bistro Le Petit Bar" and notifies the server.

[0437] The server makes a reservation for French Bistro Le Petit Bar.

[0438] The server receives the booking confirmation and sends a "booking completed" notification to the user.

[0439] Examples of notifications and reminders for participants

[0440] The server receives the participant list and notifies all participants of the details of the drinking party.

[0441] Send a reminder message the day before the drinking party.

[0442] Examples of support on the day of a drinking party

[0443] The server provides users with information such as a list of participants, store information, and contact details.

[0444] The emotion engine evaluates participants' real-time reactions and suggests additional entertainment if, for example, excitement levels are low.

[0445] In this way, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[0446] The processing flow will be explained below.

[0447] User registration function

[0448] Step 1:

[0449] The user uses the terminal to access the URL of the user registration form.

[0450] Step 2:

[0451] The user enters personal information such as name, email address, and phone number.

[0452] Step 3:

[0453] The user presses the registration button.

[0454] Step 4:

[0455] The terminal transmits the input data to the server.

[0456] Step 5:

[0457] The server receives the data and stores it in a database.

[0458] Step 6:

[0459] The server generates a registration completion message and sends it to the terminal.

[0460] Step 7:

[0461] The user will see a message on their device confirming successful registration.

[0462] Accepting drinking party requests

[0463] Step 1:

[0464] The user uses the terminal to access the URL of the drinking party request form.

[0465] Step 2:

[0466] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[0467] Step 3:

[0468] The user presses the request button.

[0469] Step 4:

[0470] The terminal transmits the input data to the server.

[0471] Step 5:

[0472] The server receives the data and stores it in a database.

[0473] Step 6:

[0474] The server uses an emotion engine to evaluate the user's emotional state based on the input request information.

[0475] Step 7:

[0476] The server reflects the emotion evaluation result in the request information.

[0477] Step 8:

[0478] The server generates a message accepting the request and sends it to the terminal.

[0479] Step 9:

[0480] The user checks the message on the terminal that the request has been accepted.

[0481] Proposal of candidate stores

[0482] Step 1:

[0483] The server searches for store information in the database.

[0484] Step 2:

[0485] The server lists appropriate stores based on the request information and emotion evaluation results.

[0486] Step 3:

[0487] The server generates a list of candidate stores.

[0488] Step 4:

[0489] The server sends the list to the user's email address.

[0490] Step 5:

[0491] The user checks the list on the terminal and selects the desired store.

[0492] Store selection and reservation

[0493] Step 1:

[0494] The user notifies the server of the selected store information.

[0495] Step 2:

[0496] The server then performs the reservation procedure for the selected store.

[0497] Step 3:

[0498] The server acquires reservation confirmation information from the store.

[0499] Step 4:

[0500] The server will send a notification of reservation completion to the user's email address.

[0501] Notifications and reminders to participants

[0502] Step 1:

[0503] The user inputs the participant's email address and contact information into the server and sends it.

[0504] Step 2:

[0505] The server will notify participants of details about the drinking party via email or SNS message.

[0506] Step 3:

[0507] The server sends a reminder message the day before the party.

[0508] Participation confirmation function

[0509] Step 1:

[0510] Participants will access the participation confirmation page via a link in the email.

[0511] Step 2:

[0512] Participants enter whether they will attend and press the send button.

[0513] Step 3:

[0514] The terminal transmits the attendance information to the server.

[0515] Step 4:

[0516] The server receives the attendance information and stores it in a database.

[0517] Step 5:

[0518] The server tally the stored attendance information.

[0519] Support on the day of the drinking party

[0520] Step 1:

[0521] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[0522] Step 2:

[0523] The server provides the necessary information to the user.

[0524] Step 3:

[0525] The emotion engine evaluates participants' real-time reactions and suggests appropriate additional support.

[0526] Step 4:

[0527] Users use the system to check the necessary information and take appropriate action based on suggestions from the emotion engine.

[0528] With this specific processing flow, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[0529] Example 2

[0530] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0531] Conventional drinking party planning systems select and support restaurants without considering the user's feelings, resulting in low satisfaction for users and participants. In particular, even if there were restaurants that matched the specified location and budget, the experience was not in line with the user's feelings and expectations. In addition, support on the day of the party was limited, and real-time response was lacking.

[0532] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[0533] In this invention, the server includes a means for receiving and storing user registration information, a means for receiving and storing drinking party request information, and a means for searching for and providing suitable candidate restaurants based on the stored request information. This makes it possible to evaluate the user's emotional state, suggest suitable candidate restaurants, and provide support in real time. Furthermore, by using an emotion engine, it is possible to provide services that match the user's emotions and expectations, thereby increasing the satisfaction of the user and participants.

[0534] "User registration information" is information for identifying an individual, such as the user's name and email address.

[0535] "Drinking party request information" is information such as the date and time, location, number of participants, budget, and special requests that a user inputs to request a drinking party.

[0536] An "emotion engine" is a software or hardware system that analyzes a user's inputs and reactions to assess the user's emotional state.

[0537] An "appropriate candidate store" is a store that is likely to meet the user's requirements and provide appropriate services based on the drinking party request information and the evaluated emotional state.

[0538] "Reservation confirmation information" refers to the confirmation of the reservation made by the server to the store, and is information including details of the reservation and confirmed matters.

[0539] A "reminding message" is a message to remind participants of the planned drinking party, and is usually sent the day before the party.

[0540] "Participant attendance information" is information on whether participants invited to a drinking party will attend.

[0541] "Real-time reactions" refers to the immediate reactions and feedback of participants on the day of the drinking party, and the emotion engine makes an evaluation based on this.

[0542] This invention combines an emotion engine that recognizes the user's emotions with a system that efficiently handles the organizing tasks of drinking parties, etc. The system aims to provide appropriate and highly satisfying services by taking into consideration the emotions of the user and participants, smoothly performing user registration, accepting drinking party requests, proposing candidate restaurants, restaurant reservations, notifying participants, confirming attendance, and providing support on the day of the party.

[0543] 1. User registration function

[0544] Users access the system using a terminal and enter personal information such as their name and email address.

[0545] The server receives this information and stores it in a database.

[0546] The server notifies the user of a message that registration is complete.

[0547] 2. Accepting drinking party requests

[0548] The user accesses a form for requesting a drinking party through the terminal.

[0549] The user inputs request information such as date, time, location, number of participants, budget, and any special requests.

[0550] The server receives this request information and stores it in a database.

[0551] The server uses an emotion engine to assess the user's emotional state.

[0552] The server reflects the evaluation results in the request information and notifies the user that the request has been accepted.

[0553] 3. Proposal of candidate stores

[0554] The server searches for store information in the database based on the request information and emotion evaluation results.

[0555] The server generates a list of stores that match the criteria and are appropriate for the emotional state.

[0556] The server sends the list to the user's email address.

[0557] The user checks the list and selects the desired store.

[0558] 4. Store reservation agent

[0559] The user notifies the server of the selected store information.

[0560] The server processes the reservation with the store and obtains reservation confirmation information.

[0561] The server notifies the user that the reservation is complete.

[0562] 5. Notification and reminders to participants

[0563] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[0564] The server sends a reminder message the day before the drinking party.

[0565] 6. Participation confirmation function

[0566] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[0567] The server receives the attendance information, stores it in a database, and tally it up.

[0568] 7. Support on the day of the drinking party

[0569] The server generates and provides the information needed on the day of the drinking party (participant list, store information, contact information).

[0570] The server uses an emotion engine to evaluate participants' real-time reactions and suggest appropriate additional support.

[0571] Specific examples

[0572] Example of a user registering in the system

[0573] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[0574] The server receives this information and stores it in a database.

[0575] The server will notify the user with a message that "Registration is complete."

[0576] Example of requesting a drinking party

[0577] The user accesses the "Drinking Party Request" form and enters the request details as follows:

[0578] Date and time: December 15, 2023 19:00

[0579] Location: City center

[0580] Number of participants: 10 people

[0581] Budget: 5,000 yen

[0582] Special Request: Asian cuisine

[0583] The server receives the request and stores it in a database.

[0584] The emotion engine evaluates the user's emotions from the input content and obtains an evaluation result such as "I want to be happy."

[0585] The server will send a notification to the user saying "your request has been accepted."

[0586] Examples of proposed stores

[0587] The server reflects the evaluation result "I want to be happy" and searches the database.

[0588] The server will then list highly rated restaurants that fit the criteria of "city center," "Asian cuisine," and "budget 5,000 yen." Restaurants such as "Restaurant Yamada," "Asian Dining Nakata," and "Ethnic Gourmet Shop" will be selected.

[0589] The server emails the list to "taro_yamada@example.com".

[0590] Store selection and reservation example

[0591] The user selects "ethnic gourmet shop" and notifies the server.

[0592] The server performs the reservation procedure for the "ethnic gourmet shop."

[0593] The server receives the booking confirmation and sends a "booking completed" notification to the user.

[0594] Examples of notifications and reminders for participants

[0595] The server receives the participant list and notifies all participants of the details of the drinking party.

[0596] Send a reminder message the day before the drinking party.

[0597] Examples of support on the day of a drinking party

[0598] The server provides users with information such as a list of participants, store information, and contact details.

[0599] The emotion engine assesses participants' real-time reactions and suggests additional entertainment when "excitement levels are low."

[0600] As described above, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[0601] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0602] Step 1: Enter and save your user registration information

[0603] Input: The user uses the device to access the "User Registration" page and enters personal information such as name and email address.

[0604] Server behavior:

[0605] Data reception: The server receives the information sent by the user.

[0606] Database storage: The received information is stored in a database using an SQL query.

[0607] Generate notification: Generates a message indicating that registration is complete.

[0608] Output: The server sends the user a message saying "Registration successful."

[0609] Step 2: Enter and save the drinking party request information

[0610] Input: The user accesses a form to request a drinking party through their device and enters the date, time, location, number of people, budget, special requests, etc.

[0611] Server behavior:

[0612] Data reception: The server receives the requested information sent by the user.

[0613] Database storage: The received request information is stored in a database using an SQL query.

[0614] Emotion evaluation: Using the emotion engine, evaluate the user's emotional state based on the request information.

[0615] Reflecting evaluation results: Reflect the evaluation results in the request information and update the database.

[0616] Generate notification: Generates a message indicating that the request has been accepted.

[0617] Output: The server sends the user a message saying "Request accepted."

[0618] Step 3: Proposing potential stores

[0619] Input: The server receives the request information and the emotion evaluation result.

[0620] Server behavior:

[0621] Database search: Using an SQL query, a database is searched for store information that matches the request information and emotion evaluation results.

[0622] List generation: Organize search results into a list.

[0623] Email Creation: Create an email with your list.

[0624] Output: The server sends the generated list to the user's email address.

[0625] Step 4: Select a store and make a reservation

[0626] Input: The user selects the desired store from the received list and notifies the server.

[0627] Server behavior:

[0628] Receiving selection information: Receives store information selected by the user.

[0629] Reservation procedure: We process reservations at selected stores. We use API to access the store's reservation system and send reservation information.

[0630] Get confirmation information: Receive and parse reservation confirmation information.

[0631] Generate notification: Generates a message indicating that the reservation has been completed.

[0632] Output: The server sends the message "Reservation completed" to the user.

[0633] Step 5: Notify and remind participants

[0634] Input: Receives the attendee list and party details provided by the user.

[0635] Server behavior:

[0636] Notification Creation: Create notifications based on the participant list.

[0637] Send email: Send a notification email to all participants.

[0638] Reminder Settings: Schedule a reminder message to be sent the day before the party.

[0639] Output: The server sends notification emails and reminder messages to participants.

[0640] Step 6: Receiving and collating participation confirmation information

[0641] Input: Participants access the attendance confirmation page via their device and input whether or not they will attend.

[0642] Server behavior:

[0643] Data reception: The server receives the entered attendance information.

[0644] Save to database: Save the received attendance information to the database.

[0645] Execution of counting: Counts attendance information and generates a list of participants.

[0646] Output: The server stores the aggregated results as internal data and uses them for subsequent processing.

[0647] Step 7: Providing support on the day of the party

[0648] Input: Receive real-time reaction information from users and participants.

[0649] Server behavior:

[0650] Generate necessary information: Generate the information required on the day of the drinking party (participant list, store information, contact information).

[0651] Emotion evaluation: Evaluate participants' real-time reactions using an emotion engine.

[0652] Additional support suggestions: Generate additional support (e.g., entertainment suggestions) based on the evaluation results.

[0653] Information provision: Providing necessary information and additional support to users.

[0654] Output: The server notifies the user of the information in real time.

[0655] (Application example 2)

[0656] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0657] When organizing events such as drinking parties, simply handling procedures without considering the user's emotions can make it difficult to sufficiently increase participant satisfaction. Similarly, in factory work environments, ignoring the emotional state of workers can lead to accumulated stress and fatigue, resulting in reduced productivity. To solve these issues, a system is needed that can accurately recognize the emotions of users and workers and provide optimized services and support based on those emotions.

[0658] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0659] means for receiving and storing user registration information;

[0660] A means for receiving and storing drinking party request information;

[0661] a means for evaluating the emotions of users or participants in real time using an emotion recognition system;

[0662] A means for adjusting work schedules and suggesting breaks based on the evaluated emotional information;

[0663] A means of proposing changes to the work environment based on emotional information;

[0664] a means for searching for and providing suitable candidate locations based on the stored request information;

[0665] means for making a reservation for a location selected by the user and notifying the user of reservation confirmation information;

[0666] A means for notifying participants of the drinking party information and sending reminder messages;

[0667] means for receiving and aggregating participant attendance information;

[0668] A way to provide necessary information on the day of the drinking party,

[0669] This makes it possible to efficiently perform tasks while taking into consideration the feelings of users and workers, thereby increasing user satisfaction.

[0670] "User registration information" refers to personal information such as the user's name and email address that is registered in the system.

[0671] "Drinking party request information" is information such as the date and time, location, number of people, budget, and special requests for the drinking party that the user inputs into the system.

[0672] An "emotion recognition system" is a system that analyzes the facial expressions and voice of users or participants and evaluates their emotional state in real time.

[0673] "Work schedule adjustment" refers to changing the timing and order of work based on emotional information to optimize the workload of users or participants.

[0674] "Break suggestion" refers to recommending that a user or participant take a break by analyzing emotional information.

[0675] "Work environment modification" refers to adjusting the work environment, such as lighting, temperature, and acoustics, based on emotional information.

[0676] "Candidate locations" are candidates for drinking parties or work areas that match the user's request information, searched and provided by the system.

[0677] "Reservation confirmation information" is the result of confirmation of the reservation made by the system for the location selected by the user.

[0678] A "reminding message" is a notification sent by the system to remind participants of the specific date, time and location.

[0679] "Attendance information" is information regarding whether or not a participant will attend that is entered into the system by the participant.

[0680] This invention is a system that uses an emotion recognition system to organize drinking parties and optimize the work environment in a factory. Here, we will explain a specific embodiment including functions such as receiving and saving user registration information, receiving and saving drinking party request information, evaluating emotions in real time using the emotion recognition system, adjusting work schedules, suggesting breaks, and changing the work environment.

[0681] 1. Receiving and storing user registration information

[0682] The user accesses the system using a terminal and enters personal information such as name and email address. The server receives this information and stores it in a database. The user is then notified of the completion of registration.

[0683] 2. Receiving and storing information about drinking party requests

[0684] The user accesses a form to request a drinking party through their device and inputs the request details (date, time, location, number of people, budget, special requests). The server receives the request details and stores them in a database. Based on the request information, the emotion engine evaluates the user's emotional state and reflects the results in the request information.

[0685] 3. Real-time evaluation using emotion recognition system

[0686] The emotion recognition system analyzes the facial expressions and voice of users or participants to assess their emotional state in real time. Specifically, it uses a camera and microphone and leverages software libraries such as OpenCV and TENSORFLOW® / Keras. Using a Haar cascade for face detection, the collected data is fed into an emotion recognition model, and the resulting emotion assessment is sent to a server.

[0687] 4. Adjusting work schedules and suggesting breaks

[0688] The server then adjusts the work schedule and suggests breaks based on the emotion evaluation results obtained from the emotion recognition system. For example, if the server detects that the user is "feeling stressed," it can make suggestions to reduce the workload.

[0689] 5. Changes in work environment

[0690] The server then makes suggestions to adjust the working environment, such as lighting, temperature, and acoustics, based on the emotion evaluation results, thereby improving the comfort level of users and workers.

[0691] Specific use cases

[0692] A user is working in a factory. The robot uses a camera and microphone to collect the worker's facial expressions and voice, which are then input into an emotion recognition model. For example, if the robot detects that the worker is feeling stressed, it can suggest a break and adjust the work schedule to reduce the workload. It can also make suggestions to adjust the lighting and temperature of the work environment.

[0693] Example prompts for generative AI models

[0694] Show us how to input facial and voice data from workers, recognize their emotions, and suggest work environment optimization solutions. Please provide the following information:

[0695] 1. Detailed instructions and code examples

[0696] 2. Hardware and Software Used

[0697] 3. Practical Applications

[0698] This enables efficient task substitution and optimization of the work environment while taking emotions into consideration, thereby improving user satisfaction and productivity.

[0699] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0700] Step 1:

[0701] A user accesses the system using a terminal and enters personal information such as their name and email address. The server receives this information and stores it in a database. The input data is the user's name and email address, and the output is a message confirming registration.

[0702] Step 2:

[0703] A user inputs a request for a drinking party into a form on their device. The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database. At this time, the input data is detailed information about the drinking party, and the output is a notification that the request has been accepted.

[0704] Step 3:

[0705] The server uses an emotion recognition system to evaluate emotions based on the user's input included in the request information. Data collected from the camera and microphone is processed using OpenCV and TensorFlow / Keras to perform face detection and emotion classification. The input data is the user's facial expressions and voice, and the output is the user's emotional evaluation.

[0706] Step 4:

[0707] The server adjusts the work schedule and suggests breaks based on the emotion evaluation results. For example, if the user is evaluated as "feeling stressed," it will suggest appropriate break times and reducing the workload. The input data is the emotion evaluation results, and the output is a suggestion to adjust the work schedule.

[0708] Step 5:

[0709] The server then proposes changes to the work environment based on the emotion evaluation results. For example, if the user is rated as "I want to relax," the server will propose softening the lighting and adjusting the temperature to a comfortable range. The input data is the emotion evaluation results, and the output is specific suggestions for environmental changes.

[0710] Step 6:

[0711] The server searches for suitable candidate locations based on the stored request information and generates a list of them. The emotional evaluation results are also taken into consideration to select locations that are appropriate for the user's emotional state. The input data are the request information and the emotional evaluation results, and the output is a list of candidate locations.

[0712] Step 7:

[0713] The user uses a terminal to select a desired location from a list of candidate locations and notify the server. The server then makes a reservation for the selected location and obtains reservation confirmation information. The input data is the user-selected location information, and the output is reservation confirmation information.

[0714] Step 8:

[0715] The server receives the participant list and notifies the participants of the details of the drinking party. It also sends a reminder message the day before the drinking party. The input data is the participant list, and the output is the detailed information notification and the reminder message.

[0716] Step 9:

[0717] Participants use their devices to access the attendance confirmation page and enter whether they will attend. The server receives the attendance information, stores it in a database, and aggregates it. The input data is attendance information, and the output is the aggregated results.

[0718] Step 10:

[0719] The server generates the necessary information for the day of the drinking party (participant list, restaurant information, contact information) and provides it to the user. The emotion engine also evaluates the real-time reactions of participants and suggests appropriate additional support. The input data are the real-time reactions of participants, and the output is suggestions for additional support.

[0720] The specific processing unit 290 transmits the result of the specific processing to the smart device 14. In the smart device 14, the control unit 46A causes the output device 40 to output the result of the specific processing. The microphone 38B acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0721] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (registered trademark) (Internet search engine).<URL: https: / / openai.com / blog / chatgpt> ), Gemini (registered trademark) (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0722] In the above embodiment, an example in which the specific process is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific process may be performed by the smart device 14.

[0723] [Second embodiment]

[0724] FIG. 3 shows an example of the configuration of a data processing system 210 according to the second embodiment.

[0725] 3, the data processing system 210 includes the data processing device 12 and smart glasses 214. An example of the data processing device 12 is a server.

[0726] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0727] The smart glasses 214 include a computer 36, a microphone 238, a speaker 240, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, and the camera 42 are also connected to the bus 52.

[0728] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0729] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0730] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0731] Fig. 4 shows an example of the main functions of the data processing device 12 and the smart glasses 214. As shown in Fig. 4, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0732] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0733] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0734] In the smart glasses 214, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0735] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the smart glasses 214 will be referred to as the "terminal."

[0736] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[0737] Explanation of program processing

[0738] 1. User registration function

[0739] Users access the system using a terminal and enter personal information such as their name and email address.

[0740] The server receives this information and stores it in a database.

[0741] The user will receive a message confirming registration.

[0742] 2. Accepting drinking party requests

[0743] The user accesses a form for requesting a drinking party through the terminal.

[0744] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[0745] The user is notified that the request has been accepted.

[0746] 3. Proposal of candidate stores

[0747] The server searches the database for store information based on the received request information.

[0748] The server generates a list of stores that match the criteria and provides it to the user via email or notification.

[0749] The user checks the list and selects the desired store.

[0750] 4. Store reservation agent

[0751] The store information selected by the user is sent to the server.

[0752] The server performs the reservation procedure with the store and obtains confirmation information that the reservation has been completed.

[0753] The user is notified that the reservation is complete.

[0754] 5. Notification and reminders to participants

[0755] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[0756] It also sends a reminder message the day before the drinking party.

[0757] 6. Participation confirmation function

[0758] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[0759] The server receives the attendance information and stores and aggregates it in a database.

[0760] 7. Support on the day of the drinking party

[0761] The server provides users with the information they need on the day of the party (e.g., participant list, store information, contact information).

[0762] Users can use the system to receive the support they need based on their situation.

[0763] Specific examples

[0764] Example of a user registering in the system

[0765] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[0766] The server receives this information and stores it in a database.

[0767] The user will receive a message saying "Registration complete."

[0768] Example of requesting a drinking party

[0769] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food."

[0770] The server receives the request and stores it in a database.

[0771] The user will receive a notification that their request has been accepted.

[0772] Examples of proposed stores

[0773] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "budget of 5,000 yen" to generate a list of candidate restaurants, such as "Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN."

[0774] The user is notified of the list.

[0775] Store selection and reservation example

[0776] The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[0777] The server will make a reservation at Charcoal Grilled Meat ZEN.

[0778] The server receives the reservation confirmation and notifies the user.

[0779] Examples of notifications and reminders for participants

[0780] The server receives the participant list and notifies all participants of the details of the drinking party.

[0781] Send a reminder message the day before the drinking party.

[0782] Examples of support on the day of a drinking party

[0783] The server provides the user with a list of participants, store information, contact information, etc., and provides additional information as needed.

[0784] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[0785] The processing flow will be explained below.

[0786] User registration function

[0787] Step 1:

[0788] The user uses the terminal to access the URL of the user registration form.

[0789] Step 2:

[0790] The user enters personal information such as name, email address, and phone number.

[0791] Step 3:

[0792] The user presses the registration button.

[0793] Step 4:

[0794] The terminal transmits the input data to the server.

[0795] Step 5:

[0796] The server receives the data and stores it in a database.

[0797] Step 6:

[0798] The server generates a registration completion message and sends it to the terminal.

[0799] Step 7:

[0800] The user will see a message on their device confirming successful registration.

[0801] Accepting drinking party requests

[0802] Step 1:

[0803] The user uses the terminal to access the URL of the drinking party request form.

[0804] Step 2:

[0805] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[0806] Step 3:

[0807] The user presses the request button.

[0808] Step 4:

[0809] The terminal transmits the input data to the server.

[0810] Step 5:

[0811] The server receives the data and stores it in a database.

[0812] Step 6:

[0813] The server generates a message accepting the request and sends it to the terminal.

[0814] Step 7:

[0815] The user checks the message on the terminal that the request has been accepted.

[0816] Proposal of candidate stores

[0817] Step 1:

[0818] The server searches for store information in the database.

[0819] Step 2:

[0820] The server will list appropriate stores based on the request information (date, time, location, budget, special requests).

[0821] Step 3:

[0822] The server generates a list of candidate stores.

[0823] Step 4:

[0824] The server sends the list to the user's email address.

[0825] Store selection and reservation

[0826] Step 1:

[0827] The user receives a list of candidate stores and selects the store of their choice.

[0828] Step 2:

[0829] The user notifies the server of the selected store information.

[0830] Step 3:

[0831] The server then performs the reservation procedure for the selected store.

[0832] Step 4:

[0833] The server acquires reservation confirmation information from the store.

[0834] Step 5:

[0835] The server will send a notification of reservation completion to the user's email address.

[0836] Notifications and reminders to participants

[0837] Step 1:

[0838] The user inputs the participant's email address and contact information into the server and sends it.

[0839] Step 2:

[0840] The server will notify participants of details about the drinking party via email or SNS message.

[0841] Step 3:

[0842] The server sends a reminder message the day before the party.

[0843] Participation confirmation function

[0844] Step 1:

[0845] Participants will access the participation confirmation page via a link in the email.

[0846] Step 2:

[0847] Participants enter whether they will attend and press the send button.

[0848] Step 3:

[0849] The terminal transmits the attendance information to the server.

[0850] Step 4:

[0851] The server receives the attendance information and stores it in a database.

[0852] Step 5:

[0853] The server tally the stored attendance information.

[0854] Support on the day of the drinking party

[0855] Step 1:

[0856] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[0857] Step 2:

[0858] The server provides the necessary information to the user.

[0859] Step 3:

[0860] The user uses the system to check the necessary information.

[0861] Example 1

[0862] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0863] Traditionally, organizing a drinking party was a time-consuming and labor-intensive process, placing a heavy burden on users. In particular, it was difficult to efficiently organize a drinking party due to the complex and wide-ranging tasks involved, such as selecting an appropriate restaurant based on the number of people and budget, making reservations, notifying and reminding participants, and confirming attendance.

[0864] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0865] In this invention, the server includes: means for a user to access the system's "user registration" page using a terminal and input personal information such as name, email address, and password; means for the server to receive the input information and store it in a database; means for a user to input detailed information about a drinking party (date, time, location, number of people, budget, special requests); means for the server to receive the input information and store it in a database; means for the server to search the database for restaurant information matching the conditions based on the stored request information; means for the server to provide the user with the generated restaurant list; means for the user to make a reservation at a restaurant selected by the user and obtain reservation confirmation information; means for the server to notify the user of the reservation confirmation information; means for the server to notify participants of detailed information about the drinking party based on the attendee list provided by the user; means for the server to send a reminder message to participants the day before the drinking party; means for participants to access the attendance confirmation page through their terminal and input whether or not they will attend; means for the server to receive the attendance information and store and tally it in a database; and means for the server to provide users with information necessary on the day of the drinking party. This enables efficient management of drinking party events.

[0866] "User registration information" is a general term for personal information such as a user's name, email address, and password.

[0867] "Terminal" refers to an electronic device such as a computer or smartphone that a user uses to access a server via the Internet.

[0868] A "server" is a computer system that receives and processes requests from users, and provides functions such as database management and email transmission.

[0869] "Database" refers to a system for efficiently storing, managing, and retrieving information, and specifically includes relational databases such as MySQL.

[0870] "Drinking party request information" is a general term for detailed information necessary for hosting a drinking party, such as the date and time of the drinking party, the location, the number of people, the budget, and any special requests.

[0871] "Candidate store information" refers to a list of restaurants that meet the conditions based on the drinking party request information.

[0872] "Reservation confirmation information" refers to information indicating that the server has made a reservation with the restaurant and that the reservation has been confirmed.

[0873] "Participant list" is a general term for information provided by a user, such as names and contact information of people who plan to attend a drinking party.

[0874] A "reminder message" is a notification message sent to participants the day before a drinking party to help them remember to attend.

[0875] "Attendance confirmation information" refers to information indicating whether or not participants will be able to attend a drinking party, which is entered by participants through the attendance confirmation page.

[0876] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[0877] Specifically, the following hardware and software are used:

[0878] Hardware:

[0879] Device (PC, smartphone, etc.)

[0880] Servers (web servers, database servers, etc.)

[0881] software:

[0882] Web browser

[0883] Web Applications

[0884] Database management system (e.g. MySQL)

[0885] Mail server (e.g. SMTP server)

[0886] API connection (e.g. Google Calendar API)

[0887] User Registration

[0888] The user accesses the system's "User Registration" page using a terminal and enters personal information such as name, email address, and password. The server receives this information and stores it in a database such as MySQL. The user receives a confirmation email stating "Registration completed."

[0889] Specific examples

[0890] The user accesses "https: / / nomikai-system.com / register" on a smartphone or PC and enters information such as "Yamada Taro," "taro_yamada@example.com," and "password123." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user a confirmation email stating "Registration completed."

[0891] Accepting drinking party requests

[0892] The user accesses the "Drinking Party Request" form through their device and enters the details of the drinking party (date, time, location, number of people, budget, special requests). The server receives the entered information and stores it in a database. The user receives an email notification that the "request has been accepted."

[0893] Specific examples

[0894] The user accesses "https: / / nomikai-system.com / request" and enters the information "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user an email notification that "the request has been accepted."

[0895] Proposal of candidate stores

[0896] The server searches for restaurant information in the database based on the drinking party request information. It generates a list of restaurants that match the criteria and provides it to the user via email or notification. The user can then review the list and select the restaurant they want.

[0897] Specific examples

[0898] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "5,000 yen," and generates a list of restaurants that meet the criteria ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN"). The server then sends the list of candidate restaurants to the user via email. The user looks at the email they receive, selects the restaurant they want (for example, "Charcoal Grilled Meat ZEN"), and notifies the server.

[0899] Store reservation service

[0900] The user sends the store information they selected to the server. The server then completes the reservation procedure with the store and receives confirmation that the reservation is complete. The user receives a notification that the reservation is complete.

[0901] Specific examples

[0902] The user selects "Charcoal Grilled Meat ZEN" and notifies the server. The server processes the reservation with "Charcoal Grilled Meat ZEN" using an API call or a telephone automation system. The server obtains the reservation confirmation and stores it in a database. The user receives an email stating "Reservation completed."

[0903] Notifications and reminders to participants

[0904] The server notifies participants of the details of the drinking party based on the participant list provided by the user, and also sends a reminder message the day before the drinking party.

[0905] Specific examples

[0906] The server notifies all participants of the "Drinking Party Details" by email based on the participant list. The day before the drinking party, the server automatically sends a reminder message using the Google Calendar API.

[0907] Participation confirmation function

[0908] Participants access the attendance confirmation page via their terminal and enter whether they will attend. The server receives the attendance information and stores and compiles it in a database.

[0909] Specific examples

[0910] Participants access "https: / / nomikai-system.com / confirm" to confirm their attendance. The server receives the attendance information and stores it in a MySQL database. The server then sends the tally results to the user.

[0911] Support on the day of the drinking party

[0912] The server provides users with the necessary information on the day of the drinking party, and users use the system to receive the necessary support according to the situation.

[0913] Specific examples

[0914] On the morning of the party, the server will email the user details such as the participant list, store information, and emergency contact information. Any additional information or support the user needs will be received in real time through the system.

[0915] Prompt Sentence Examples

[0916] I want to register user information in the system. The username is "Yamada Taro" and the email address is "taro_yamada@example.com". Please explain the process for saving this information to the database.

[0917] A user fills out a form to request a drinking party with the following information: "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food." Explain the process for saving this information to a database.

[0918] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[0919] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0920] Program processing flow

[0921] Step 1: User Registration

[0922] 1. The user accesses the "User Registration" page using a terminal.

[0923] Input: The URL where users will access the registration page.

[0924] Output: Display of user registration form.

[0925] Specific operation: The user accesses "https: / / nomikai-system.com / register".

[0926] 2. The user enters personal information such as name, email address, and password.

[0927] Input: Name, Email Address, Password.

[0928] Output: The information entered.

[0929] Specific operation: The user enters "Yamada Taro", "taro_yamada@example.com", and "password123".

[0930] 3. The server receives the entered information and stores it in a database.

[0931] Input: Personal information entered by the user.

[0932] Output: User information stored in the database.

[0933] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[0934] 4. The server sends the user a message confirming registration.

[0935] Input: User information stored in the database.

[0936] Output: A confirmation email confirming successful registration.

[0937] Specific behavior: The server sends a confirmation email saying "Registration completed."

[0938] Step 2: Accepting a drinking party request

[0939] 1. The user accesses the "Drinking Party Request" form via their device.

[0940] Input: The URL where users can access the request form.

[0941] Output: Display of drinking party request form.

[0942] Specific operation: The user accesses "https: / / nomikai-system.com / request".

[0943] 2. The user enters the details of the drinking party (date, time, location, number of people, budget, special requests).

[0944] Input: date, time, location, number of people, budget, special requests.

[0945] Output: The request information entered.

[0946] Specific operation: The user enters "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food."

[0947] 3. The server receives the entered information and stores it in a database.

[0948] Input: Request information entered by the user.

[0949] Output: Request information stored in a database.

[0950] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[0951] 4. The server sends a message to the user acknowledging the request.

[0952] Input: Request information stored in the database.

[0953] Output: Email confirming acceptance of request.

[0954] Specific behavior: The server sends a confirmation email saying "your request has been accepted."

[0955] Step 3: Proposing potential stores

[0956] 1. The server searches for store information in the database based on the drinking party request information.

[0957] Input: Request details (location, budget, special requests).

[0958] Output: A list of stores that match the criteria.

[0959] Specific operation: The server searches the database for the conditions "Shinjuku," "Japanese food," and "5,000 yen."

[0960] 2. The server generates a list of stores that match the conditions.

[0961] Input: Store information as search results.

[0962] Output: The generated store list.

[0963] Specific operation: Generate a list of stores that meet the conditions ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," "Charcoal Grill Niku ZEN").

[0964] 3. The server notifies the user of the store list.

[0965] Input: Generated store list.

[0966] Output: Store list notification email.

[0967] Specific operation: The server sends the user a list of candidate stores by email.

[0968] 4. The user selects the store of their choice.

[0969] Input: Store list.

[0970] Output: Selected store information.

[0971] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[0972] Step 4: Store reservation

[0973] 1. The store information selected by the user is sent to the server.

[0974] Input: Selected store information.

[0975] Output: Store information sent to the server.

[0976] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[0977] 2. The server makes a reservation with the store.

[0978] Input: Selected store information.

[0979] Output: A reservation request to the store.

[0980] Specific operation: The server makes a reservation to "Charcoal Grilled Meat ZEN" using an API call or an automated telephone system.

[0981] 3. The server receives confirmation of the reservation.

[0982] Input: Reservation confirmation information from the store.

[0983] Output: The retrieved reservation confirmation information.

[0984] What happens: The server gets the booking confirmation and stores it in the database.

[0985] 4. The server sends a notification to the user that the reservation is complete.

[0986] Input: Retrieved reservation confirmation information.

[0987] Output: Notification email of reservation completion.

[0988] Specific behavior: Sends the user an email saying "Reservation completed."

[0989] Step 5: Notify and remind participants

[0990] 1. The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[0991] Input: Participant list, details of the drinking party.

[0992] Output: Notification email to participants.

[0993] Specific operation: Based on the participant list, the server notifies all participants of the "details of the drinking party" by email.

[0994] 2. The server sends a reminder message the day before the drinking party.

[0995] Input: Participant list.

[0996] Output: Reminder message email.

[0997] Specific operation: The server uses the Google Calendar API to automatically send a reminder message the day before the drinking party.

[0998] Step 6: Participation confirmation function

[0999] 1. Participants access the attendance confirmation page via their device.

[1000] Input: The URL of the attendance confirmation page.

[1001] Output: Display of attendance confirmation form.

[1002] Specific action: Participant accesses "https: / / nomikai-system.com / confirm".

[1003] 2. Participants enter whether they will attend.

[1004] Input: Attendance confirmation information.

[1005] Output: The attendance confirmation information entered.

[1006] Specific operation: Participants input whether they will attend or not.

[1007] 3. The server receives the attendance information and stores and aggregates it in a database.

[1008] Input: Attendance confirmation information entered by the participant.

[1009] Output: Attendance confirmation information and summary results stored in the database.

[1010] Specific operation: The server receives the attendance information, stores it in the database using SQL INSERT statements, and aggregates it.

[1011] Step 7: Support on the day of the drinking party

[1012] 1. The server provides the user with the information they need on the day of the drinking party.

[1013] Input: Party details, participant list, contact information.

[1014] Output: An email containing the required information.

[1015] Specific operation: On the morning of the drinking party, the server sends the user an email with details such as the list of participants, store information, and emergency contact information.

[1016] 2. Users use the system to receive the support they need in their context.

[1017] Input: The user's request.

[1018] Output: Supporting information provided.

[1019] Specific Action: The user receives any additional information or support they need in real time through the system.

[1020] (Application example 1)

[1021] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[1022] Conventional party organizer tasks involve multiple, complicated procedures that require a great deal of time and effort when planning and running a drinking party. Tasks such as selecting potential restaurants, making reservations, and notifying participants of information are particularly complex, placing a heavy burden on organizers. Furthermore, providing necessary information in real time on the day of the party is difficult, making it difficult to respond to unforeseen circumstances. Another problem is that efficient methods for operating and managing smart devices have not yet been fully established.

[1023] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1024] In this invention, the server includes means for receiving and saving user registration information, means for receiving and saving drinking party request information, means for searching for and providing appropriate candidate restaurants based on the saved request information, means for making a reservation at a restaurant selected by the user and notifying the reservation confirmation information, means for notifying participants of drinking party information and sending reminder messages, means for receiving and compiling participant attendance information, means for providing information needed on the day of the drinking party, means for reading user registration information using a smart device when entering the restaurant and registering the user, means for displaying a list of candidate restaurants via the smart device and allowing selection, and means for visually providing information needed on the day of the drinking party using the smart device. This significantly reduces the workload involved in conventional organizing tasks and makes it possible to provide necessary information in real time.

[1025] "User registration information" refers to information including personal information such as the user's name and email address.

[1026] "Drinking party request information" refers to information such as the date and time of the drinking party, the location, the number of participants, the budget, and any special requests.

[1027] "Candidate store" refers to a store that is capable of hosting a drinking party and has been selected based on the drinking party request information.

[1028] "Reservation confirmation information" refers to the reservation confirmation information provided by the store after the reservation procedure has been completed.

[1029] "Participants" refers to people who plan to attend a drinking party.

[1030] "Information notification" refers to notifying participants of detailed information about the drinking party.

[1031] A "reminder message" refers to a confirmation message sent to participants the day before the drinking party.

[1032] "Attendance Information" refers to information regarding a participant's attendance confirmation.

[1033] "Smart device" refers to devices such as smartphones, smart glasses, or head-mounted displays.

[1034] "Visual presentation" refers to the method of displaying information directly in the user's field of vision through a smart device.

[1035] The present invention relates to a system that enables a user to efficiently perform administrative tasks using a smart device. The present invention is primarily implemented using a smart device such as a smartphone, smart glasses, or a head-mounted display.

[1036] First, the user accesses the system using a smart device. When the user enters a store, they scan a QR code installed at the entrance or elsewhere. After scanning the QR code, the necessary information for user registration is displayed on the screen of the smart device. The user enters personal information such as their name and email address and presses the send button. This information is sent to the server and stored in a database.

[1037] Next, the user uses a smart device to input information about the drinking party request, such as the date, time, location, number of participants, budget, and any special requests. This information is sent to the server, and the request is saved in a database. Based on this request, the server searches the database for candidate restaurants and generates a list of restaurants that meet the user's requirements.

[1038] The generated list of stores is displayed on the screen of the smart device, and the user selects the store they want from the list. The store information selected by the user is sent to the server, which then processes the reservation. Once the reservation is complete, the server generates confirmation information and notifies the user via the smart device.

[1039] The server then notifies participants of the details of the drinking party based on the participant list provided by the user. Furthermore, a reminder message is automatically sent the day before the drinking party to prompt participants to confirm their attendance. The participants' attendance information is sent to the server and stored in a database.

[1040] On the day of the party, the server will display the necessary information (participant list, store information, contact information, etc.) on the screen of the smart device, allowing users to check the necessary information in real time and smoothly carry out their organizing duties.

[1041] Furthermore, the system significantly improves the overall efficiency of administrative work by transmitting information obtained from smart devices to a server in real time for analysis and processing. For example, by using smart glasses, users can visually obtain necessary information without using their hands, improving operability.

[1042] Hardware and software used

[1043] Hardware:

[1044] Smart glasses (e.g. Google Glass)

[1045] Smartphone

[1046] head-mounted display

[1047] Software and Libraries:

[1048] QRScanner: A library for reading QR codes

[1049] UserRegistryAPI: API to send user registration information to the server

[1050] PartyRequestAPI: API for managing drinking party request information

[1051] StoreDatabase: Database for searching information on potential stores

[1052] ReservationAPI: API for making store reservations

[1053] NotificationService: Service for notifying and reminding participants

[1054] AttendanceCheckAPI: API for receiving attendance confirmation information

[1055] InformationDisplayService: A service that displays information about the day of the drinking party

[1056] Examples and prompts

[1057] Examples:

[1058] A user enters a store and scans the QR code with the smart glasses. The user then enters their name and email address into the form displayed on the smart glasses screen to complete registration.

[1059] The user uses smart glasses to access a drinking party request form and enters the following: "Date and time: October 15, 2023, 7:00 PM," "Location: Commercial location," "Number of participants: 10," "Budget: 5,000 yen," and "Special request: Japanese cuisine."

[1060] The server uses this information to search for candidate stores and displays the results on the smart glasses screen. The user selects an appropriate store from the list and notifies the server.

[1061] The server makes a reservation at the selected store and notifies the user of reservation confirmation information.

[1062] The day before the drinking party, the server sends a reminder message to all participants and collects attendance confirmation information.

[1063] Prompt for the generative AI model:

[1064] - "Please explain the process of an application for smart glasses that will completely take over as organizer of a drinking party at a specific location on a specific date."

[1065] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1066] Step 1:

[1067] A user reads the QR code using a smart device. This allows the user to enter a store and scan the QR code displayed on the terminal using smart glasses or a smartphone. The input data is the content of the QR code (the URL of the user registration page), and the output is the user registration page being displayed on the smart device.

[1068] Step 2:

[1069] The user enters personal information such as name and email address into the user registration form displayed on the screen of the smart device and submits it. The input data is personal information such as name and email address, and is sent to the server. The server stores the submitted information in a database and returns a confirmation message to the user confirming completion of registration.

[1070] Step 3:

[1071] A user accesses a drinking party request form using a smart device and inputs the date, time, location, number of participants, budget, and any special requests for the drinking party. The input data is detailed information about the drinking party and is sent to the server. The server stores the received information in a database and notifies the user that the request has been accepted.

[1072] Step 4:

[1073] The server searches for candidate restaurants based on the drinking party request information it receives. The server searches the database and generates a list of suitable candidate restaurants based on the input data. The output data is the list of candidate restaurants, which is sent to the user's smart device.

[1074] Step 5:

[1075] The user selects the desired store from a list of candidate stores displayed on the screen of their smart device and sends that information to the server. The input data is the store information selected by the user, and the server processes the reservation based on this information. The server then generates reservation confirmation information and returns it to the user's smart device.

[1076] Step 6:

[1077] The server notifies participants of the details of the drinking party based on the participant list provided by the user. The input data is the participant list and drinking party details, and the output is a notification message to the participants. In addition, a reminder message is automatically sent the day before the drinking party.

[1078] Step 7:

[1079] Participants use smart devices to confirm their attendance. The input data, which indicates whether they are attending or not, is sent to the server and stored in a database. The server then compiles the attendance information and notifies the user.

[1080] Step 8:

[1081] On the day of the drinking party, users use smart devices to view the necessary information (e.g., participant list, store information, contact information). The server provides this information in real time, and users check the information displayed on the screen of their smart glasses or smartphone. The input data is the user's request, and the output data is the detailed information provided in real time.

[1082] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1083] The present invention shows a specific embodiment of a system that handles the organizing tasks of drinking parties, etc., by combining an emotion engine that recognizes the user's emotions and reflects them in the processing. This system not only smoothly performs user registration, reception of drinking party requests, proposal of candidate restaurants, restaurant reservations, notification to participants, attendance confirmation, and support on the day of the drinking party, but also provides a more appropriate and satisfying service by taking into account the emotions of the user and participants.

[1084] Explanation of program processing

[1085] 1. User registration function

[1086] Users access the system using a terminal and enter personal information such as their name and email address.

[1087] The server receives this information and stores it in a database.

[1088] A message is sent to the user indicating that registration is complete.

[1089] 2. Accepting drinking party requests

[1090] The user accesses a form for requesting a drinking party through the terminal.

[1091] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[1092] The server evaluates the user's emotional state using an emotion engine based on the request information.

[1093] The evaluation results from the emotion engine are reflected in the request information.

[1094] The user is notified that the request has been accepted.

[1095] 3. Proposal of candidate stores

[1096] The server searches the database for store information based on the emotion evaluation results included in the request information.

[1097] The server generates a list of stores that match the criteria and are appropriate for the user's emotional state.

[1098] The server sends the list to the user's email address.

[1099] The user checks the list and selects the desired store.

[1100] 4. Store reservation agent

[1101] The user notifies the server of the selected store information.

[1102] The server processes the reservation with the store.

[1103] The server acquires reservation confirmation information from the store.

[1104] The user is notified that the reservation is complete.

[1105] 5. Notification and reminders to participants

[1106] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[1107] Send a reminder message the day before the party.

[1108] 6. Participation confirmation function

[1109] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[1110] The server receives the attendance information, stores it in a database, and tally it up.

[1111] 7. Support on the day of the drinking party

[1112] The server generates the information needed on the day of the drinking party (e.g., participant list, store information, contact information).

[1113] The server provides the necessary information to the user.

[1114] The emotion engine suggests appropriate additional support in real time based on participants' reactions and feedback.

[1115] Specific examples

[1116] Example of a user registering in the system

[1117] The user accesses the "User Registration" page using a terminal and enters the name "Hanako Sato" and the email address "hanako_sato@example.com".

[1118] The server receives this information and stores it in a database.

[1119] The user will be notified with the message "Registration complete."

[1120] Example of requesting a drinking party

[1121] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: December 15, 2023, 7:00 PM," "Location: Shibuya," "Number of participants: 8," "Budget: 6,000 yen," and "Request: Western food."

[1122] The server receives the request and stores it in a database.

[1123] The emotion engine evaluates the user's emotions from the input content and obtains an evaluation result such as "I want to relax."

[1124] The server will send a notification to the user saying "your request has been accepted."

[1125] Examples of proposed stores

[1126] The server reflects the evaluation result "I want to relax" and searches the database.

[1127] The server will then provide a list of restaurants that match the criteria of "Shibuya," "Western cuisine," and "budget of 6,000 yen" and have a reputation for being relaxing. The list will include "Cafe Restaurant Hanakoji," "Shibuya Italian Restaurant La Pasta," and "French Bistro Le Petit Bar."

[1128] The server emails the list to the user.

[1129] Store selection and reservation example

[1130] The user selects "French Bistro Le Petit Bar" and notifies the server.

[1131] The server makes a reservation for French Bistro Le Petit Bar.

[1132] The server receives the booking confirmation and sends a "booking completed" notification to the user.

[1133] Examples of notifications and reminders for participants

[1134] The server receives the participant list and notifies all participants of the details of the drinking party.

[1135] Send a reminder message the day before the drinking party.

[1136] Examples of support on the day of a drinking party

[1137] The server provides users with information such as a list of participants, store information, and contact details.

[1138] The emotion engine evaluates participants' real-time reactions and suggests additional entertainment if, for example, excitement levels are low.

[1139] In this way, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[1140] The processing flow will be explained below.

[1141] User registration function

[1142] Step 1:

[1143] The user uses the terminal to access the URL of the user registration form.

[1144] Step 2:

[1145] The user enters personal information such as name, email address, and phone number.

[1146] Step 3:

[1147] The user presses the registration button.

[1148] Step 4:

[1149] The terminal transmits the input data to the server.

[1150] Step 5:

[1151] The server receives the data and stores it in a database.

[1152] Step 6:

[1153] The server generates a registration completion message and sends it to the terminal.

[1154] Step 7:

[1155] The user will see a message on their device confirming successful registration.

[1156] Accepting drinking party requests

[1157] Step 1:

[1158] The user uses the terminal to access the URL of the drinking party request form.

[1159] Step 2:

[1160] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[1161] Step 3:

[1162] The user presses the request button.

[1163] Step 4:

[1164] The terminal transmits the input data to the server.

[1165] Step 5:

[1166] The server receives the data and stores it in a database.

[1167] Step 6:

[1168] The server uses an emotion engine to evaluate the user's emotional state based on the input request information.

[1169] Step 7:

[1170] The server reflects the emotion evaluation result in the request information.

[1171] Step 8:

[1172] The server generates a message accepting the request and sends it to the terminal.

[1173] Step 9:

[1174] The user checks the message on the terminal that the request has been accepted.

[1175] Proposal of candidate stores

[1176] Step 1:

[1177] The server searches for store information in the database.

[1178] Step 2:

[1179] The server lists appropriate stores based on the request information and emotion evaluation results.

[1180] Step 3:

[1181] The server generates a list of candidate stores.

[1182] Step 4:

[1183] The server sends the list to the user's email address.

[1184] Step 5:

[1185] The user checks the list on the terminal and selects the desired store.

[1186] Store selection and reservation

[1187] Step 1:

[1188] The user notifies the server of the selected store information.

[1189] Step 2:

[1190] The server then performs the reservation procedure for the selected store.

[1191] Step 3:

[1192] The server acquires reservation confirmation information from the store.

[1193] Step 4:

[1194] The server will send a notification of reservation completion to the user's email address.

[1195] Notifications and reminders to participants

[1196] Step 1:

[1197] The user inputs the participant's email address and contact information into the server and sends it.

[1198] Step 2:

[1199] The server will notify participants of details about the drinking party via email or SNS message.

[1200] Step 3:

[1201] The server sends a reminder message the day before the party.

[1202] Participation confirmation function

[1203] Step 1:

[1204] Participants will access the participation confirmation page via a link in the email.

[1205] Step 2:

[1206] Participants enter whether they will attend and press the send button.

[1207] Step 3:

[1208] The terminal transmits the attendance information to the server.

[1209] Step 4:

[1210] The server receives the attendance information and stores it in a database.

[1211] Step 5:

[1212] The server tally the stored attendance information.

[1213] Support on the day of the drinking party

[1214] Step 1:

[1215] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[1216] Step 2:

[1217] The server provides the necessary information to the user.

[1218] Step 3:

[1219] The emotion engine evaluates participants' real-time reactions and suggests appropriate additional support.

[1220] Step 4:

[1221] Users use the system to check the necessary information and take appropriate action based on suggestions from the emotion engine.

[1222] With this specific processing flow, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[1223] Example 2

[1224] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[1225] Conventional drinking party planning systems select and support restaurants without considering the user's feelings, resulting in low satisfaction for users and participants. In particular, even if there were restaurants that matched the specified location and budget, the experience was not in line with the user's feelings and expectations. In addition, support on the day of the party was limited, and real-time response was lacking.

[1226] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[1227] In this invention, the server includes a means for receiving and storing user registration information, a means for receiving and storing drinking party request information, and a means for searching for and providing suitable candidate restaurants based on the stored request information. This makes it possible to evaluate the user's emotional state, suggest suitable candidate restaurants, and provide support in real time. Furthermore, by using an emotion engine, it is possible to provide services that match the user's emotions and expectations, thereby increasing the satisfaction of the user and participants.

[1228] "User registration information" is information for identifying an individual, such as the user's name and email address.

[1229] "Drinking party request information" is information such as the date and time, location, number of participants, budget, and special requests that a user inputs to request a drinking party.

[1230] An "emotion engine" is a software or hardware system that analyzes a user's inputs and reactions to assess the user's emotional state.

[1231] An "appropriate candidate store" is a store that is likely to meet the user's requirements and provide appropriate services based on the drinking party request information and the evaluated emotional state.

[1232] "Reservation confirmation information" refers to the confirmation of the reservation made by the server to the store, and is information including details of the reservation and confirmed matters.

[1233] A "reminding message" is a message to remind participants of the planned drinking party, and is usually sent the day before the party.

[1234] "Participant attendance information" is information on whether participants invited to a drinking party will attend.

[1235] "Real-time reactions" refers to the immediate reactions and feedback of participants on the day of the drinking party, and the emotion engine makes an evaluation based on this.

[1236] This invention combines an emotion engine that recognizes the user's emotions with a system that efficiently handles the organizing tasks of drinking parties, etc. The system aims to provide appropriate and highly satisfying services by taking into consideration the emotions of the user and participants, smoothly performing user registration, accepting drinking party requests, proposing candidate restaurants, restaurant reservations, notifying participants, confirming attendance, and providing support on the day of the party.

[1237] 1. User registration function

[1238] Users access the system using a terminal and enter personal information such as their name and email address.

[1239] The server receives this information and stores it in a database.

[1240] The server notifies the user of a message that registration is complete.

[1241] 2. Accepting drinking party requests

[1242] The user accesses a form for requesting a drinking party through the terminal.

[1243] The user inputs request information such as date, time, location, number of participants, budget, and any special requests.

[1244] The server receives this request information and stores it in a database.

[1245] The server uses an emotion engine to assess the user's emotional state.

[1246] The server reflects the evaluation results in the request information and notifies the user that the request has been accepted.

[1247] 3. Proposal of candidate stores

[1248] The server searches for store information in the database based on the request information and emotion evaluation results.

[1249] The server generates a list of stores that match the criteria and are appropriate for the emotional state.

[1250] The server sends the list to the user's email address.

[1251] The user checks the list and selects the desired store.

[1252] 4. Store reservation agent

[1253] The user notifies the server of the selected store information.

[1254] The server processes the reservation with the store and obtains reservation confirmation information.

[1255] The server notifies the user that the reservation is complete.

[1256] 5. Notification and reminders to participants

[1257] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[1258] The server sends a reminder message the day before the drinking party.

[1259] 6. Participation confirmation function

[1260] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[1261] The server receives the attendance information, stores it in a database, and tally it up.

[1262] 7. Support on the day of the drinking party

[1263] The server generates and provides the information needed on the day of the drinking party (participant list, store information, contact information).

[1264] The server uses an emotion engine to evaluate participants' real-time reactions and suggest appropriate additional support.

[1265] Specific examples

[1266] Example of a user registering in the system

[1267] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[1268] The server receives this information and stores it in a database.

[1269] The server will notify the user with a message that "Registration is complete."

[1270] Example of requesting a drinking party

[1271] The user accesses the "Drinking Party Request" form and enters the request details as follows:

[1272] Date and time: December 15, 2023 19:00

[1273] Location: City center

[1274] Number of participants: 10 people

[1275] Budget: 5,000 yen

[1276] Special Request: Asian cuisine

[1277] The server receives the request and stores it in a database.

[1278] The emotion engine evaluates the user's emotions from the input content and obtains an evaluation result such as "I want to be happy."

[1279] The server will send a notification to the user saying "your request has been accepted."

[1280] Examples of proposed stores

[1281] The server reflects the evaluation result "I want to be happy" and searches the database.

[1282] The server will then list highly rated restaurants that fit the criteria of "city center," "Asian cuisine," and "budget 5,000 yen." Restaurants such as "Restaurant Yamada," "Asian Dining Nakata," and "Ethnic Gourmet Shop" will be selected.

[1283] The server emails the list to "taro_yamada@example.com".

[1284] Store selection and reservation example

[1285] The user selects "ethnic gourmet shop" and notifies the server.

[1286] The server performs the reservation procedure for the "ethnic gourmet shop."

[1287] The server receives the booking confirmation and sends a "booking completed" notification to the user.

[1288] Examples of notifications and reminders for participants

[1289] The server receives the participant list and notifies all participants of the details of the drinking party.

[1290] Send a reminder message the day before the drinking party.

[1291] Examples of support on the day of a drinking party

[1292] The server provides users with information such as a list of participants, store information, and contact details.

[1293] The emotion engine assesses participants' real-time reactions and suggests additional entertainment when "excitement levels are low."

[1294] As described above, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[1295] The flow of the identification process in the second embodiment will be described with reference to FIG.

[1296] Step 1: Enter and save your user registration information

[1297] Input: The user uses the device to access the "User Registration" page and enters personal information such as name and email address.

[1298] Server behavior:

[1299] Data reception: The server receives the information sent by the user.

[1300] Database storage: The received information is stored in a database using an SQL query.

[1301] Generate notification: Generates a message indicating that registration is complete.

[1302] Output: The server sends the user a message saying "Registration successful."

[1303] Step 2: Enter and save the drinking party request information

[1304] Input: The user accesses a form to request a drinking party through their device and enters the date, time, location, number of people, budget, special requests, etc.

[1305] Server behavior:

[1306] Data reception: The server receives the requested information sent by the user.

[1307] Database storage: The received request information is stored in a database using an SQL query.

[1308] Emotion evaluation: Using the emotion engine, evaluate the user's emotional state based on the request information.

[1309] Reflecting evaluation results: Reflect the evaluation results in the request information and update the database.

[1310] Generate notification: Generates a message indicating that the request has been accepted.

[1311] Output: The server sends the user a message saying "Request accepted."

[1312] Step 3: Proposing potential stores

[1313] Input: The server receives the request information and the emotion evaluation result.

[1314] Server behavior:

[1315] Database search: Using an SQL query, a database is searched for store information that matches the request information and emotion evaluation results.

[1316] List generation: Organize search results into a list.

[1317] Email Creation: Create an email with your list.

[1318] Output: The server sends the generated list to the user's email address.

[1319] Step 4: Select a store and make a reservation

[1320] Input: The user selects the desired store from the received list and notifies the server.

[1321] Server behavior:

[1322] Receiving selection information: Receives store information selected by the user.

[1323] Reservation procedure: We process reservations at selected stores. We use API to access the store's reservation system and send reservation information.

[1324] Get confirmation information: Receive and parse reservation confirmation information.

[1325] Generate notification: Generates a message indicating that the reservation has been completed.

[1326] Output: The server sends the message "Reservation completed" to the user.

[1327] Step 5: Notify and remind participants

[1328] Input: Receives the attendee list and party details provided by the user.

[1329] Server behavior:

[1330] Notification Creation: Create notifications based on the participant list.

[1331] Send email: Send a notification email to all participants.

[1332] Reminder Settings: Schedule a reminder message to be sent the day before the party.

[1333] Output: The server sends notification emails and reminder messages to participants.

[1334] Step 6: Receiving and collating participation confirmation information

[1335] Input: Participants access the attendance confirmation page via their device and input whether or not they will attend.

[1336] Server behavior:

[1337] Data reception: The server receives the entered attendance information.

[1338] Save to database: Save the received attendance information to the database.

[1339] Execution of counting: Counts attendance information and generates a list of participants.

[1340] Output: The server stores the aggregated results as internal data and uses them for subsequent processing.

[1341] Step 7: Providing support on the day of the party

[1342] Input: Receive real-time reaction information from users and participants.

[1343] Server behavior:

[1344] Generate necessary information: Generate the information required on the day of the drinking party (participant list, store information, contact information).

[1345] Emotion evaluation: Evaluate participants' real-time reactions using an emotion engine.

[1346] Additional support suggestions: Generate additional support (e.g., entertainment suggestions) based on the evaluation results.

[1347] Information provision: Providing necessary information and additional support to users.

[1348] Output: The server notifies the user of the information in real time.

[1349] (Application example 2)

[1350] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[1351] When organizing events such as drinking parties, simply handling procedures without considering the user's emotions can make it difficult to sufficiently increase participant satisfaction. Similarly, in factory work environments, ignoring the emotional state of workers can lead to accumulated stress and fatigue, resulting in reduced productivity. To solve these issues, a system is needed that can accurately recognize the emotions of users and workers and provide optimized services and support based on those emotions.

[1352] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[1353] means for receiving and storing user registration information;

[1354] A means for receiving and storing drinking party request information;

[1355] a means for evaluating the emotions of users or participants in real time using an emotion recognition system;

[1356] A means for adjusting work schedules and suggesting breaks based on the evaluated emotional information;

[1357] A means of proposing changes to the work environment based on emotional information;

[1358] a means for searching for and providing suitable candidate locations based on the stored request information;

[1359] means for making a reservation for a location selected by the user and notifying the user of reservation confirmation information;

[1360] A means for notifying participants of the drinking party information and sending reminder messages;

[1361] means for receiving and aggregating participant attendance information;

[1362] A way to provide necessary information on the day of the drinking party,

[1363] This makes it possible to efficiently perform tasks while taking into consideration the feelings of users and workers, thereby increasing user satisfaction.

[1364] "User registration information" refers to personal information such as the user's name and email address that is registered in the system.

[1365] "Drinking party request information" is information such as the date and time, location, number of people, budget, and special requests for the drinking party that the user inputs into the system.

[1366] An "emotion recognition system" is a system that analyzes the facial expressions and voice of users or participants and evaluates their emotional state in real time.

[1367] "Work schedule adjustment" refers to changing the timing and order of work based on emotional information to optimize the workload of users or participants.

[1368] "Break suggestion" refers to recommending that a user or participant take a break by analyzing emotional information.

[1369] "Work environment modification" refers to adjusting the work environment, such as lighting, temperature, and acoustics, based on emotional information.

[1370] "Candidate locations" are candidates for drinking parties or work areas that match the user's request information, searched and provided by the system.

[1371] "Reservation confirmation information" is the result of confirmation of the reservation made by the system for the location selected by the user.

[1372] A "reminding message" is a notification sent by the system to remind participants of the specific date, time and location.

[1373] "Attendance information" is information regarding whether or not a participant will attend that is entered into the system by the participant.

[1374] This invention is a system that uses an emotion recognition system to organize drinking parties and optimize the work environment in a factory. Here, we will explain a specific embodiment including functions such as receiving and saving user registration information, receiving and saving drinking party request information, evaluating emotions in real time using the emotion recognition system, adjusting work schedules, suggesting breaks, and changing the work environment.

[1375] 1. Receiving and storing user registration information

[1376] The user accesses the system using a terminal and enters personal information such as name and email address. The server receives this information and stores it in a database. The user is then notified of the completion of registration.

[1377] 2. Receiving and storing information about drinking party requests

[1378] The user accesses a form to request a drinking party through their device and inputs the request details (date, time, location, number of people, budget, special requests). The server receives the request details and stores them in a database. Based on the request information, the emotion engine evaluates the user's emotional state and reflects the results in the request information.

[1379] 3. Real-time evaluation using emotion recognition system

[1380] The emotion recognition system analyzes the facial expressions and voice of the user or participant to assess their emotional state in real time. Specifically, it uses a camera and microphone and leverages software libraries such as OpenCV and TensorFlow / Keras. Using a Haar cascade for face detection, the collected data is fed into an emotion recognition model, and the resulting emotion assessment is sent to a server.

[1381] 4. Adjusting work schedules and suggesting breaks

[1382] The server then adjusts the work schedule and suggests breaks based on the emotion evaluation results obtained from the emotion recognition system. For example, if the server detects that the user is "feeling stressed," it can make suggestions to reduce the workload.

[1383] 5. Changes in work environment

[1384] The server then makes suggestions to adjust the working environment, such as lighting, temperature, and acoustics, based on the emotion evaluation results, thereby improving the comfort level of users and workers.

[1385] Specific use cases

[1386] A user is working in a factory. The robot uses a camera and microphone to collect the worker's facial expressions and voice, which are then input into an emotion recognition model. For example, if the robot detects that the worker is feeling stressed, it can suggest a break and adjust the work schedule to reduce the workload. It can also make suggestions to adjust the lighting and temperature of the work environment.

[1387] Example prompts for generative AI models

[1388] Show us how to input facial and voice data from workers, recognize their emotions, and suggest work environment optimization solutions. Please provide the following information:

[1389] 1. Detailed instructions and code examples

[1390] 2. Hardware and Software Used

[1391] 3. Practical Applications

[1392] This enables efficient task substitution and optimization of the work environment while taking emotions into consideration, thereby improving user satisfaction and productivity.

[1393] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[1394] Step 1:

[1395] A user accesses the system using a terminal and enters personal information such as their name and email address. The server receives this information and stores it in a database. The input data is the user's name and email address, and the output is a message confirming registration.

[1396] Step 2:

[1397] A user inputs a request for a drinking party into a form on their device. The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database. At this time, the input data is detailed information about the drinking party, and the output is a notification that the request has been accepted.

[1398] Step 3:

[1399] The server uses an emotion recognition system to evaluate emotions based on the user's input included in the request information. Data collected from the camera and microphone is processed using OpenCV and TensorFlow / Keras to perform face detection and emotion classification. The input data is the user's facial expressions and voice, and the output is the user's emotional evaluation.

[1400] Step 4:

[1401] The server adjusts the work schedule and suggests breaks based on the emotion evaluation results. For example, if the user is evaluated as "feeling stressed," it will suggest appropriate break times and reducing the workload. The input data is the emotion evaluation results, and the output is a suggestion to adjust the work schedule.

[1402] Step 5:

[1403] The server then proposes changes to the work environment based on the emotion evaluation results. For example, if the user is rated as "I want to relax," the server will propose softening the lighting and adjusting the temperature to a comfortable range. The input data is the emotion evaluation results, and the output is specific suggestions for environmental changes.

[1404] Step 6:

[1405] The server searches for suitable candidate locations based on the stored request information and generates a list of them. The emotional evaluation results are also taken into consideration to select locations that are appropriate for the user's emotional state. The input data are the request information and the emotional evaluation results, and the output is a list of candidate locations.

[1406] Step 7:

[1407] The user uses a terminal to select a desired location from a list of candidate locations and notify the server. The server then makes a reservation for the selected location and obtains reservation confirmation information. The input data is the user-selected location information, and the output is reservation confirmation information.

[1408] Step 8:

[1409] The server receives the participant list and notifies the participants of the details of the drinking party. It also sends a reminder message the day before the drinking party. The input data is the participant list, and the output is the detailed information notification and the reminder message.

[1410] Step 9:

[1411] Participants use their devices to access the attendance confirmation page and enter whether they will attend. The server receives the attendance information, stores it in a database, and aggregates it. The input data is attendance information, and the output is the aggregated results.

[1412] Step 10:

[1413] The server generates the necessary information for the day of the drinking party (participant list, restaurant information, contact information) and provides it to the user. The emotion engine also evaluates the real-time reactions of participants and suggests appropriate additional support. The input data are the real-time reactions of participants, and the output is suggestions for additional support.

[1414] The specific processing unit 290 transmits the result of the specific processing to the smart glasses 214. In the smart glasses 214, the control unit 46A causes the speaker 240 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[1415] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1416] In the above embodiment, an example in which the specific processing is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the smart glasses 214.

[1417] [Third embodiment]

[1418] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.

[1419] 5, the data processing system 310 includes the data processing device 12 and a headset type terminal 314. An example of the data processing device 12 is a server.

[1420] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[1421] The headset type terminal 314 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a display 343. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the display 343 are also connected to the bus 52.

[1422] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[1423] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[1424] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[1425] Fig. 6 shows an example of the main functions of the data processing device 12 and the headset type terminal 314. As shown in Fig. 6, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[1426] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[1427] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[1428] In the headset type terminal 314, a reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[1429] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the headset type terminal 314 will be referred to as the "terminal."

[1430] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[1431] Explanation of program processing

[1432] 1. User registration function

[1433] Users access the system using a terminal and enter personal information such as their name and email address.

[1434] The server receives this information and stores it in a database.

[1435] The user will receive a message confirming registration.

[1436] 2. Accepting drinking party requests

[1437] The user accesses a form for requesting a drinking party through the terminal.

[1438] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[1439] The user is notified that the request has been accepted.

[1440] 3. Proposal of candidate stores

[1441] The server searches the database for store information based on the received request information.

[1442] The server generates a list of stores that match the criteria and provides it to the user via email or notification.

[1443] The user checks the list and selects the desired store.

[1444] 4. Store reservation agent

[1445] The store information selected by the user is sent to the server.

[1446] The server performs the reservation procedure with the store and obtains confirmation information that the reservation has been completed.

[1447] The user is notified that the reservation is complete.

[1448] 5. Notification and reminders to participants

[1449] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[1450] It also sends a reminder message the day before the drinking party.

[1451] 6. Participation confirmation function

[1452] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[1453] The server receives the attendance information and stores and aggregates it in a database.

[1454] 7. Support on the day of the drinking party

[1455] The server provides users with the information they need on the day of the party (e.g., participant list, store information, contact information).

[1456] Users can use the system to receive the support they need based on their situation.

[1457] Specific examples

[1458] Example of a user registering in the system

[1459] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[1460] The server receives this information and stores it in a database.

[1461] The user will receive a message saying "Registration complete."

[1462] Example of requesting a drinking party

[1463] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food."

[1464] The server receives the request and stores it in a database.

[1465] The user will receive a notification that their request has been accepted.

[1466] Examples of proposed stores

[1467] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "budget of 5,000 yen" to generate a list of candidate restaurants, such as "Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN."

[1468] The user is notified of the list.

[1469] Store selection and reservation example

[1470] The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[1471] The server will make a reservation at Charcoal Grilled Meat ZEN.

[1472] The server receives the reservation confirmation and notifies the user.

[1473] Examples of notifications and reminders for participants

[1474] The server receives the participant list and notifies all participants of the details of the drinking party.

[1475] Send a reminder message the day before the drinking party.

[1476] Examples of support on the day of a drinking party

[1477] The server provides the user with a list of participants, store information, contact information, etc., and provides additional information as needed.

[1478] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[1479] The processing flow will be explained below.

[1480] User registration function

[1481] Step 1:

[1482] The user uses the terminal to access the URL of the user registration form.

[1483] Step 2:

[1484] The user enters personal information such as name, email address, and phone number.

[1485] Step 3:

[1486] The user presses the registration button.

[1487] Step 4:

[1488] The terminal transmits the input data to the server.

[1489] Step 5:

[1490] The server receives the data and stores it in a database.

[1491] Step 6:

[1492] The server generates a registration completion message and sends it to the terminal.

[1493] Step 7:

[1494] The user will see a message on their device confirming successful registration.

[1495] Accepting drinking party requests

[1496] Step 1:

[1497] The user uses the terminal to access the URL of the drinking party request form.

[1498] Step 2:

[1499] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[1500] Step 3:

[1501] The user presses the request button.

[1502] Step 4:

[1503] The terminal transmits the input data to the server.

[1504] Step 5:

[1505] The server receives the data and stores it in a database.

[1506] Step 6:

[1507] The server generates a message accepting the request and sends it to the terminal.

[1508] Step 7:

[1509] The user checks the message on the terminal that the request has been accepted.

[1510] Proposal of candidate stores

[1511] Step 1:

[1512] The server searches for store information in the database.

[1513] Step 2:

[1514] The server will list appropriate stores based on the request information (date, time, location, budget, special requests).

[1515] Step 3:

[1516] The server generates a list of candidate stores.

[1517] Step 4:

[1518] The server sends the list to the user's email address.

[1519] Store selection and reservation

[1520] Step 1:

[1521] The user receives a list of candidate stores and selects the store of their choice.

[1522] Step 2:

[1523] The user notifies the server of the selected store information.

[1524] Step 3:

[1525] The server then performs the reservation procedure for the selected store.

[1526] Step 4:

[1527] The server acquires reservation confirmation information from the store.

[1528] Step 5:

[1529] The server will send a notification of reservation completion to the user's email address.

[1530] Notifications and reminders to participants

[1531] Step 1:

[1532] The user inputs the participant's email address and contact information into the server and sends it.

[1533] Step 2:

[1534] The server will notify participants of details about the drinking party via email or SNS message.

[1535] Step 3:

[1536] The server sends a reminder message the day before the party.

[1537] Participation confirmation function

[1538] Step 1:

[1539] Participants will access the participation confirmation page via a link in the email.

[1540] Step 2:

[1541] Participants enter whether they will attend and press the send button.

[1542] Step 3:

[1543] The terminal transmits the attendance information to the server.

[1544] Step 4:

[1545] The server receives the attendance information and stores it in a database.

[1546] Step 5:

[1547] The server tally the stored attendance information.

[1548] Support on the day of the drinking party

[1549] Step 1:

[1550] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[1551] Step 2:

[1552] The server provides the necessary information to the user.

[1553] Step 3:

[1554] The user uses the system to check the necessary information.

[1555] Example 1

[1556] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1557] Traditionally, organizing a drinking party was a time-consuming and labor-intensive process, placing a heavy burden on users. In particular, it was difficult to efficiently organize a drinking party due to the complex and wide-ranging tasks involved, such as selecting an appropriate restaurant based on the number of people and budget, making reservations, notifying and reminding participants, and confirming attendance.

[1558] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[1559] In this invention, the server includes: means for a user to access the system's "user registration" page using a terminal and input personal information such as name, email address, and password; means for the server to receive the input information and store it in a database; means for a user to input detailed information about a drinking party (date, time, location, number of people, budget, special requests); means for the server to receive the input information and store it in a database; means for the server to search the database for restaurant information matching the conditions based on the stored request information; means for the server to provide the user with the generated restaurant list; means for the user to make a reservation at a restaurant selected by the user and obtain reservation confirmation information; means for the server to notify the user of the reservation confirmation information; means for the server to notify participants of detailed information about the drinking party based on the attendee list provided by the user; means for the server to send a reminder message to participants the day before the drinking party; means for participants to access the attendance confirmation page through their terminal and input whether or not they will attend; means for the server to receive the attendance information and store and tally it in a database; and means for the server to provide users with information necessary on the day of the drinking party. This enables efficient management of drinking party events.

[1560] "User registration information" is a general term for personal information such as a user's name, email address, and password.

[1561] "Terminal" refers to an electronic device such as a computer or smartphone that a user uses to access a server via the Internet.

[1562] A "server" is a computer system that receives and processes requests from users, and provides functions such as database management and email transmission.

[1563] "Database" refers to a system for efficiently storing, managing, and retrieving information, and specifically includes relational databases such as MySQL.

[1564] "Drinking party request information" is a general term for detailed information necessary for hosting a drinking party, such as the date and time of the drinking party, the location, the number of people, the budget, and any special requests.

[1565] "Candidate store information" refers to a list of restaurants that meet the conditions based on the drinking party request information.

[1566] "Reservation confirmation information" refers to information indicating that the server has made a reservation with the restaurant and that the reservation has been confirmed.

[1567] "Participant list" is a general term for information provided by a user, such as names and contact information of people who plan to attend a drinking party.

[1568] A "reminder message" is a notification message sent to participants the day before a drinking party to help them remember to attend.

[1569] "Attendance confirmation information" refers to information indicating whether or not participants will be able to attend a drinking party, which is entered by participants through the attendance confirmation page.

[1570] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[1571] Specifically, the following hardware and software are used:

[1572] Hardware:

[1573] Device (PC, smartphone, etc.)

[1574] Servers (web servers, database servers, etc.)

[1575] software:

[1576] Web browser

[1577] Web Applications

[1578] Database management system (e.g. MySQL)

[1579] Mail server (e.g. SMTP server)

[1580] API connection (e.g. Google Calendar API)

[1581] User Registration

[1582] The user accesses the system's "User Registration" page using a terminal and enters personal information such as name, email address, and password. The server receives this information and stores it in a database such as MySQL. The user receives a confirmation email stating "Registration completed."

[1583] Specific examples

[1584] The user accesses "https: / / nomikai-system.com / register" on a smartphone or PC and enters information such as "Yamada Taro," "taro_yamada@example.com," and "password123." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user a confirmation email stating "Registration completed."

[1585] Accepting drinking party requests

[1586] The user accesses the "Drinking Party Request" form through their device and enters the details of the drinking party (date, time, location, number of people, budget, special requests). The server receives the entered information and stores it in a database. The user receives an email notification that the "request has been accepted."

[1587] Specific examples

[1588] The user accesses "https: / / nomikai-system.com / request" and enters the information "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user an email notification that "the request has been accepted."

[1589] Proposal of candidate stores

[1590] The server searches for restaurant information in the database based on the drinking party request information. It generates a list of restaurants that match the criteria and provides it to the user via email or notification. The user can then review the list and select the restaurant they want.

[1591] Specific examples

[1592] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "5,000 yen," and generates a list of restaurants that meet the criteria ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN"). The server then sends the list of candidate restaurants to the user via email. The user looks at the email they receive, selects the restaurant they want (for example, "Charcoal Grilled Meat ZEN"), and notifies the server.

[1593] Store reservation service

[1594] The user sends the store information they selected to the server. The server then completes the reservation procedure with the store and receives confirmation that the reservation is complete. The user receives a notification that the reservation is complete.

[1595] Specific examples

[1596] The user selects "Charcoal Grilled Meat ZEN" and notifies the server. The server processes the reservation with "Charcoal Grilled Meat ZEN" using an API call or a telephone automation system. The server obtains the reservation confirmation and stores it in a database. The user receives an email stating "Reservation completed."

[1597] Notifications and reminders to participants

[1598] The server notifies participants of the details of the drinking party based on the participant list provided by the user, and also sends a reminder message the day before the drinking party.

[1599] Specific examples

[1600] The server notifies all participants of the "Drinking Party Details" by email based on the participant list. The day before the drinking party, the server automatically sends a reminder message using the Google Calendar API.

[1601] Participation confirmation function

[1602] Participants access the attendance confirmation page via their terminal and enter whether they will attend. The server receives the attendance information and stores and compiles it in a database.

[1603] Specific examples

[1604] Participants access "https: / / nomikai-system.com / confirm" to confirm their attendance. The server receives the attendance information and stores it in a MySQL database. The server then sends the tally results to the user.

[1605] Support on the day of the drinking party

[1606] The server provides users with the necessary information on the day of the drinking party, and users use the system to receive the necessary support according to the situation.

[1607] Specific examples

[1608] On the morning of the party, the server will email the user details such as the participant list, store information, and emergency contact information. Any additional information or support the user needs will be received in real time through the system.

[1609] Prompt Sentence Examples

[1610] I want to register user information in the system. The username is "Yamada Taro" and the email address is "taro_yamada@example.com". Please explain the process for saving this information to the database.

[1611] A user fills out a form to request a drinking party with the following information: "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food." Explain the process for saving this information to a database.

[1612] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[1613] The flow of the identification process in the first embodiment will be described with reference to FIG.

[1614] Program processing flow

[1615] Step 1: User Registration

[1616] 1. The user accesses the "User Registration" page using a terminal.

[1617] Input: The URL where users will access the registration page.

[1618] Output: Display of user registration form.

[1619] Specific operation: The user accesses "https: / / nomikai-system.com / register".

[1620] 2. The user enters personal information such as name, email address, and password.

[1621] Input: Name, Email Address, Password.

[1622] Output: The information entered.

[1623] Specific operation: The user enters "Yamada Taro", "taro_yamada@example.com", and "password123".

[1624] 3. The server receives the entered information and stores it in a database.

[1625] Input: Personal information entered by the user.

[1626] Output: User information stored in the database.

[1627] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[1628] 4. The server sends the user a message confirming registration.

[1629] Input: User information stored in the database.

[1630] Output: A confirmation email confirming successful registration.

[1631] Specific behavior: The server sends a confirmation email saying "Registration completed."

[1632] Step 2: Accepting a drinking party request

[1633] 1. The user accesses the "Drinking Party Request" form via their device.

[1634] Input: The URL where users can access the request form.

[1635] Output: Display of drinking party request form.

[1636] Specific operation: The user accesses "https: / / nomikai-system.com / request".

[1637] 2. The user enters the details of the drinking party (date, time, location, number of people, budget, special requests).

[1638] Input: date, time, location, number of people, budget, special requests.

[1639] Output: The request information entered.

[1640] Specific operation: The user enters "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food."

[1641] 3. The server receives the entered information and stores it in a database.

[1642] Input: Request information entered by the user.

[1643] Output: Request information stored in a database.

[1644] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[1645] 4. The server sends a message to the user acknowledging the request.

[1646] Input: Request information stored in the database.

[1647] Output: Email confirming acceptance of request.

[1648] Specific behavior: The server sends a confirmation email saying "your request has been accepted."

[1649] Step 3: Proposing potential stores

[1650] 1. The server searches for store information in the database based on the drinking party request information.

[1651] Input: Request details (location, budget, special requests).

[1652] Output: A list of stores that match the criteria.

[1653] Specific operation: The server searches the database for the conditions "Shinjuku," "Japanese food," and "5,000 yen."

[1654] 2. The server generates a list of stores that match the conditions.

[1655] Input: Store information as search results.

[1656] Output: The generated store list.

[1657] Specific operation: Generate a list of stores that meet the conditions ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," "Charcoal Grill Niku ZEN").

[1658] 3. The server notifies the user of the store list.

[1659] Input: Generated store list.

[1660] Output: Store list notification email.

[1661] Specific operation: The server sends the user a list of candidate stores by email.

[1662] 4. The user selects the store of their choice.

[1663] Input: Store list.

[1664] Output: Selected store information.

[1665] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[1666] Step 4: Store reservation

[1667] 1. The store information selected by the user is sent to the server.

[1668] Input: Selected store information.

[1669] Output: Store information sent to the server.

[1670] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[1671] 2. The server makes a reservation with the store.

[1672] Input: Selected store information.

[1673] Output: A reservation request to the store.

[1674] Specific operation: The server makes a reservation to "Charcoal Grilled Meat ZEN" using an API call or an automated telephone system.

[1675] 3. The server receives confirmation of the reservation.

[1676] Input: Reservation confirmation information from the store.

[1677] Output: The retrieved reservation confirmation information.

[1678] What happens: The server gets the booking confirmation and stores it in the database.

[1679] 4. The server sends a notification to the user that the reservation is complete.

[1680] Input: Retrieved reservation confirmation information.

[1681] Output: Notification email of reservation completion.

[1682] Specific behavior: Sends the user an email saying "Reservation completed."

[1683] Step 5: Notify and remind participants

[1684] 1. The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[1685] Input: Participant list, details of the drinking party.

[1686] Output: Notification email to participants.

[1687] Specific operation: Based on the participant list, the server notifies all participants of the "details of the drinking party" by email.

[1688] 2. The server sends a reminder message the day before the drinking party.

[1689] Input: Participant list.

[1690] Output: Reminder message email.

[1691] Specific operation: The server uses the Google Calendar API to automatically send a reminder message the day before the drinking party.

[1692] Step 6: Participation confirmation function

[1693] 1. Participants access the attendance confirmation page via their device.

[1694] Input: The URL of the attendance confirmation page.

[1695] Output: Display of attendance confirmation form.

[1696] Specific action: Participant accesses "https: / / nomikai-system.com / confirm".

[1697] 2. Participants enter whether they will attend.

[1698] Input: Attendance confirmation information.

[1699] Output: The attendance confirmation information entered.

[1700] Specific operation: Participants input whether they will attend or not.

[1701] 3. The server receives the attendance information and stores and aggregates it in a database.

[1702] Input: Attendance confirmation information entered by the participant.

[1703] Output: Attendance confirmation information and summary results stored in the database.

[1704] Specific operation: The server receives the attendance information, stores it in the database using SQL INSERT statements, and aggregates it.

[1705] Step 7: Support on the day of the drinking party

[1706] 1. The server provides the user with the information they need on the day of the drinking party.

[1707] Input: Party details, participant list, contact information.

[1708] Output: An email containing the required information.

[1709] Specific operation: On the morning of the drinking party, the server sends the user an email with details such as the list of participants, store information, and emergency contact information.

[1710] 2. Users use the system to receive the support they need in their context.

[1711] Input: The user's request.

[1712] Output: Supporting information provided.

[1713] Specific Action: The user receives any additional information or support they need in real time through the system.

[1714] (Application example 1)

[1715] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1716] Conventional party organizer tasks involve multiple, complicated procedures that require a great deal of time and effort when planning and running a drinking party. Tasks such as selecting potential restaurants, making reservations, and notifying participants of information are particularly complex, placing a heavy burden on organizers. Furthermore, providing necessary information in real time on the day of the party is difficult, making it difficult to respond to unforeseen circumstances. Another problem is that efficient methods for operating and managing smart devices have not yet been fully established.

[1717] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1718] In this invention, the server includes means for receiving and saving user registration information, means for receiving and saving drinking party request information, means for searching for and providing appropriate candidate restaurants based on the saved request information, means for making a reservation at a restaurant selected by the user and notifying the reservation confirmation information, means for notifying participants of drinking party information and sending reminder messages, means for receiving and compiling participant attendance information, means for providing information needed on the day of the drinking party, means for reading user registration information using a smart device when entering the restaurant and registering the user, means for displaying a list of candidate restaurants via the smart device and allowing selection, and means for visually providing information needed on the day of the drinking party using the smart device. This significantly reduces the workload involved in conventional organizing tasks and makes it possible to provide necessary information in real time.

[1719] "User registration information" refers to information including personal information such as the user's name and email address.

[1720] "Drinking party request information" refers to information such as the date and time of the drinking party, the location, the number of participants, the budget, and any special requests.

[1721] "Candidate store" refers to a store that is capable of hosting a drinking party and has been selected based on the drinking party request information.

[1722] "Reservation confirmation information" refers to the reservation confirmation information provided by the store after the reservation procedure has been completed.

[1723] "Participants" refers to people who plan to attend a drinking party.

[1724] "Information notification" refers to notifying participants of detailed information about the drinking party.

[1725] A "reminder message" refers to a confirmation message sent to participants the day before the drinking party.

[1726] "Attendance Information" refers to information regarding a participant's attendance confirmation.

[1727] "Smart device" refers to devices such as smartphones, smart glasses, or head-mounted displays.

[1728] "Visual presentation" refers to the method of displaying information directly in the user's field of vision through a smart device.

[1729] The present invention relates to a system that enables a user to efficiently perform administrative tasks using a smart device. The present invention is primarily implemented using a smart device such as a smartphone, smart glasses, or a head-mounted display.

[1730] First, the user accesses the system using a smart device. When the user enters a store, they scan a QR code installed at the entrance or elsewhere. After scanning the QR code, the necessary information for user registration is displayed on the screen of the smart device. The user enters personal information such as their name and email address and presses the send button. This information is sent to the server and stored in a database.

[1731] Next, the user uses a smart device to input information about the drinking party request, such as the date, time, location, number of participants, budget, and any special requests. This information is sent to the server, and the request is saved in a database. Based on this request, the server searches the database for candidate restaurants and generates a list of restaurants that meet the user's requirements.

[1732] The generated list of stores is displayed on the screen of the smart device, and the user selects the store they want from the list. The store information selected by the user is sent to the server, which then processes the reservation. Once the reservation is complete, the server generates confirmation information and notifies the user via the smart device.

[1733] The server then notifies participants of the details of the drinking party based on the participant list provided by the user. Furthermore, a reminder message is automatically sent the day before the drinking party to prompt participants to confirm their attendance. The participants' attendance information is sent to the server and stored in a database.

[1734] On the day of the party, the server will display the necessary information (participant list, store information, contact information, etc.) on the screen of the smart device, allowing users to check the necessary information in real time and smoothly carry out their organizing duties.

[1735] Furthermore, the system significantly improves the overall efficiency of administrative work by transmitting information obtained from smart devices to a server in real time for analysis and processing. For example, by using smart glasses, users can visually obtain necessary information without using their hands, improving operability.

[1736] Hardware and software used

[1737] Hardware:

[1738] Smart glasses (e.g. Google Glass)

[1739] Smartphone

[1740] head-mounted display

[1741] Software and Libraries:

[1742] QRScanner: A library for reading QR codes

[1743] UserRegistryAPI: API to send user registration information to the server

[1744] PartyRequestAPI: API for managing drinking party request information

[1745] StoreDatabase: Database for searching information on potential stores

[1746] ReservationAPI: API for making store reservations

[1747] NotificationService: Service for notifying and reminding participants

[1748] AttendanceCheckAPI: API for receiving attendance confirmation information

[1749] InformationDisplayService: A service that displays information about the day of the drinking party

[1750] Examples and prompts

[1751] Examples:

[1752] A user enters a store and scans the QR code with the smart glasses. The user then enters their name and email address into the form displayed on the smart glasses screen to complete registration.

[1753] The user uses smart glasses to access a drinking party request form and enters the following: "Date and time: October 15, 2023, 7:00 PM," "Location: Commercial location," "Number of participants: 10," "Budget: 5,000 yen," and "Special request: Japanese cuisine."

[1754] The server uses this information to search for candidate stores and displays the results on the smart glasses screen. The user selects an appropriate store from the list and notifies the server.

[1755] The server makes a reservation at the selected store and notifies the user of reservation confirmation information.

[1756] The day before the drinking party, the server sends a reminder message to all participants and collects attendance confirmation information.

[1757] Prompt for the generative AI model:

[1758] - "Please explain the process of an application for smart glasses that will completely take over as organizer of a drinking party at a specific location on a specific date."

[1759] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1760] Step 1:

[1761] A user reads the QR code using a smart device. This allows the user to enter a store and scan the QR code displayed on the terminal using smart glasses or a smartphone. The input data is the content of the QR code (the URL of the user registration page), and the output is the user registration page being displayed on the smart device.

[1762] Step 2:

[1763] The user enters personal information such as name and email address into the user registration form displayed on the screen of the smart device and submits it. The input data is personal information such as name and email address, and is sent to the server. The server stores the submitted information in a database and returns a confirmation message to the user confirming completion of registration.

[1764] Step 3:

[1765] A user accesses a drinking party request form using a smart device and inputs the date, time, location, number of participants, budget, and any special requests for the drinking party. The input data is detailed information about the drinking party and is sent to the server. The server stores the received information in a database and notifies the user that the request has been accepted.

[1766] Step 4:

[1767] The server searches for candidate restaurants based on the drinking party request information it receives. The server searches the database and generates a list of suitable candidate restaurants based on the input data. The output data is the list of candidate restaurants, which is sent to the user's smart device.

[1768] Step 5:

[1769] The user selects the desired store from a list of candidate stores displayed on the screen of their smart device and sends that information to the server. The input data is the store information selected by the user, and the server processes the reservation based on this information. The server then generates reservation confirmation information and returns it to the user's smart device.

[1770] Step 6:

[1771] The server notifies participants of the details of the drinking party based on the participant list provided by the user. The input data is the participant list and drinking party details, and the output is a notification message to the participants. In addition, a reminder message is automatically sent the day before the drinking party.

[1772] Step 7:

[1773] Participants use smart devices to confirm their attendance. The input data, which indicates whether they are attending or not, is sent to the server and stored in a database. The server then compiles the attendance information and notifies the user.

[1774] Step 8:

[1775] On the day of the drinking party, users use smart devices to view the necessary information (e.g., participant list, store information, contact information). The server provides this information in real time, and users check the information displayed on the screen of their smart glasses or smartphone. The input data is the user's request, and the output data is the detailed information provided in real time.

[1776] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1777] The present invention shows a specific embodiment of a system that handles the organizing tasks of drinking parties, etc., by combining an emotion engine that recognizes the user's emotions and reflects them in the processing. This system not only smoothly performs user registration, reception of drinking party requests, proposal of candidate restaurants, restaurant reservations, notification to participants, attendance confirmation, and support on the day of the drinking party, but also provides a more appropriate and satisfying service by taking into account the emotions of the user and participants.

[1778] Explanation of program processing

[1779] 1. User registration function

[1780] Users access the system using a terminal and enter personal information such as their name and email address.

[1781] The server receives this information and stores it in a database.

[1782] A message is sent to the user indicating that registration is complete.

[1783] 2. Accepting drinking party requests

[1784] The user accesses a form for requesting a drinking party through the terminal.

[1785] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[1786] The server evaluates the user's emotional state using an emotion engine based on the request information.

[1787] The evaluation results from the emotion engine are reflected in the request information.

[1788] The user is notified that the request has been accepted.

[1789] 3. Proposal of candidate stores

[1790] The server searches the database for store information based on the emotion evaluation results included in the request information.

[1791] The server generates a list of stores that match the criteria and are appropriate for the user's emotional state.

[1792] The server sends the list to the user's email address.

[1793] The user checks the list and selects the desired store.

[1794] 4. Store reservation agent

[1795] The user notifies the server of the selected store information.

[1796] The server processes the reservation with the store.

[1797] The server acquires reservation confirmation information from the store.

[1798] The user is notified that the reservation is complete.

[1799] 5. Notification and reminders to participants

[1800] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[1801] Send a reminder message the day before the party.

[1802] 6. Participation confirmation function

[1803] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[1804] The server receives the attendance information, stores it in a database, and tally it up.

[1805] 7. Support on the day of the drinking party

[1806] The server generates the information needed on the day of the drinking party (e.g., participant list, store information, contact information).

[1807] The server provides the necessary information to the user.

[1808] The emotion engine suggests appropriate additional support in real time based on participants' reactions and feedback.

[1809] Specific examples

[1810] Example of a user registering in the system

[1811] The user accesses the "User Registration" page using a terminal and enters the name "Hanako Sato" and the email address "hanako_sato@example.com".

[1812] The server receives this information and stores it in a database.

[1813] The user will be notified with the message "Registration complete."

[1814] Example of requesting a drinking party

[1815] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: December 15, 2023, 7:00 PM," "Location: Shibuya," "Number of participants: 8," "Budget: 6,000 yen," and "Request: Western food."

[1816] The server receives the request and stores it in a database.

[1817] The emotion engine evaluates the user's emotions from the input content and obtains an evaluation result such as "I want to relax."

[1818] The server will send a notification to the user saying "your request has been accepted."

[1819] Examples of proposed stores

[1820] The server reflects the evaluation result "I want to relax" and searches the database.

[1821] The server will then provide a list of restaurants that match the criteria of "Shibuya," "Western cuisine," and "budget of 6,000 yen" and have a reputation for being relaxing. The list will include "Cafe Restaurant Hanakoji," "Shibuya Italian Restaurant La Pasta," and "French Bistro Le Petit Bar."

[1822] The server emails the list to the user.

[1823] Store selection and reservation example

[1824] The user selects "French Bistro Le Petit Bar" and notifies the server.

[1825] The server makes a reservation for French Bistro Le Petit Bar.

[1826] The server receives the booking confirmation and sends a "booking completed" notification to the user.

[1827] Examples of notifications and reminders for participants

[1828] The server receives the participant list and notifies all participants of the details of the drinking party.

[1829] Send a reminder message the day before the drinking party.

[1830] Examples of support on the day of a drinking party

[1831] The server provides users with information such as a list of participants, store information, and contact details.

[1832] The emotion engine evaluates participants' real-time reactions and suggests additional entertainment if, for example, excitement levels are low.

[1833] In this way, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[1834] The processing flow will be explained below.

[1835] User registration function

[1836] Step 1:

[1837] The user uses the terminal to access the URL of the user registration form.

[1838] Step 2:

[1839] The user enters personal information such as name, email address, and phone number.

[1840] Step 3:

[1841] The user presses the registration button.

[1842] Step 4:

[1843] The terminal transmits the input data to the server.

[1844] Step 5:

[1845] The server receives the data and stores it in a database.

[1846] Step 6:

[1847] The server generates a registration completion message and sends it to the terminal.

[1848] Step 7:

[1849] The user will see a message on their device confirming successful registration.

[1850] Accepting drinking party requests

[1851] Step 1:

[1852] The user uses the terminal to access the URL of the drinking party request form.

[1853] Step 2:

[1854] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[1855] Step 3:

[1856] The user presses the request button.

[1857] Step 4:

[1858] The terminal transmits the input data to the server.

[1859] Step 5:

[1860] The server receives the data and stores it in a database.

[1861] Step 6:

[1862] The server uses an emotion engine to evaluate the user's emotional state based on the input request information.

[1863] Step 7:

[1864] The server reflects the emotion evaluation result in the request information.

[1865] Step 8:

[1866] The server generates a message accepting the request and sends it to the terminal.

[1867] Step 9:

[1868] The user checks the message on the terminal that the request has been accepted.

[1869] Proposal of candidate stores

[1870] Step 1:

[1871] The server searches for store information in the database.

[1872] Step 2:

[1873] The server lists appropriate stores based on the request information and emotion evaluation results.

[1874] Step 3:

[1875] The server generates a list of candidate stores.

[1876] Step 4:

[1877] The server sends the list to the user's email address.

[1878] Step 5:

[1879] The user checks the list on the terminal and selects the desired store.

[1880] Store selection and reservation

[1881] Step 1:

[1882] The user notifies the server of the selected store information.

[1883] Step 2:

[1884] The server then performs the reservation procedure for the selected store.

[1885] Step 3:

[1886] The server acquires reservation confirmation information from the store.

[1887] Step 4:

[1888] The server will send a notification of reservation completion to the user's email address.

[1889] Notifications and reminders to participants

[1890] Step 1:

[1891] The user inputs the participant's email address and contact information into the server and sends it.

[1892] Step 2:

[1893] The server will notify participants of details about the drinking party via email or SNS message.

[1894] Step 3:

[1895] The server sends a reminder message the day before the party.

[1896] Participation confirmation function

[1897] Step 1:

[1898] Participants will access the participation confirmation page via a link in the email.

[1899] Step 2:

[1900] Participants enter whether they will attend and press the send button.

[1901] Step 3:

[1902] The terminal transmits the attendance information to the server.

[1903] Step 4:

[1904] The server receives the attendance information and stores it in a database.

[1905] Step 5:

[1906] The server tally the stored attendance information.

[1907] Support on the day of the drinking party

[1908] Step 1:

[1909] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[1910] Step 2:

[1911] The server provides the necessary information to the user.

[1912] Step 3:

[1913] The emotion engine evaluates participants' real-time reactions and suggests appropriate additional support.

[1914] Step 4:

[1915] Users use the system to check the necessary information and take appropriate action based on suggestions from the emotion engine.

[1916] With this specific processing flow, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[1917] Example 2

[1918] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1919] Conventional drinking party planning systems select and support restaurants without considering the user's feelings, resulting in low satisfaction for users and participants. In particular, even if there were restaurants that matched the specified location and budget, the experience was not in line with the user's feelings and expectations. In addition, support on the day of the party was limited, and real-time response was lacking.

[1920] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[1921] In this invention, the server includes a means for receiving and storing user registration information, a means for receiving and storing drinking party request information, and a means for searching for and providing suitable candidate restaurants based on the stored request information. This makes it possible to evaluate the user's emotional state, suggest suitable candidate restaurants, and provide support in real time. Furthermore, by using an emotion engine, it is possible to provide services that match the user's emotions and expectations, thereby increasing the satisfaction of the user and participants.

[1922] "User registration information" is information for identifying an individual, such as the user's name and email address.

[1923] "Drinking party request information" is information such as the date and time, location, number of participants, budget, and special requests that a user inputs to request a drinking party.

[1924] An "emotion engine" is a software or hardware system that analyzes a user's inputs and reactions to assess the user's emotional state.

[1925] An "appropriate candidate store" is a store that is likely to meet the user's requirements and provide appropriate services based on the drinking party request information and the evaluated emotional state.

[1926] "Reservation confirmation information" refers to the confirmation of the reservation made by the server to the store, and is information including details of the reservation and confirmed matters.

[1927] A "reminding message" is a message to remind participants of the planned drinking party, and is usually sent the day before the party.

[1928] "Participant attendance information" is information on whether participants invited to a drinking party will attend.

[1929] "Real-time reactions" refers to the immediate reactions and feedback of participants on the day of the drinking party, and the emotion engine makes an evaluation based on this.

[1930] This invention combines an emotion engine that recognizes the user's emotions with a system that efficiently handles the organizing tasks of drinking parties, etc. The system aims to provide appropriate and highly satisfying services by taking into consideration the emotions of the user and participants, smoothly performing user registration, accepting drinking party requests, proposing candidate restaurants, restaurant reservations, notifying participants, confirming attendance, and providing support on the day of the party.

[1931] 1. User registration function

[1932] Users access the system using a terminal and enter personal information such as their name and email address.

[1933] The server receives this information and stores it in a database.

[1934] The server notifies the user of a message that registration is complete.

[1935] 2. Accepting drinking party requests

[1936] The user accesses a form for requesting a drinking party through the terminal.

[1937] The user inputs request information such as date, time, location, number of participants, budget, and any special requests.

[1938] The server receives this request information and stores it in a database.

[1939] The server uses an emotion engine to assess the user's emotional state.

[1940] The server reflects the evaluation results in the request information and notifies the user that the request has been accepted.

[1941] 3. Proposal of candidate stores

[1942] The server searches for store information in the database based on the request information and emotion evaluation results.

[1943] The server generates a list of stores that match the criteria and are appropriate for the emotional state.

[1944] The server sends the list to the user's email address.

[1945] The user checks the list and selects the desired store.

[1946] 4. Store reservation agent

[1947] The user notifies the server of the selected store information.

[1948] The server processes the reservation with the store and obtains reservation confirmation information.

[1949] The server notifies the user that the reservation is complete.

[1950] 5. Notification and reminders to participants

[1951] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[1952] The server sends a reminder message the day before the drinking party.

[1953] 6. Participation confirmation function

[1954] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[1955] The server receives the attendance information, stores it in a database, and tally it up.

[1956] 7. Support on the day of the drinking party

[1957] The server generates and provides the information needed on the day of the drinking party (participant list, store information, contact information).

[1958] The server uses an emotion engine to evaluate participants' real-time reactions and suggest appropriate additional support.

[1959] Specific examples

[1960] Example of a user registering in the system

[1961] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[1962] The server receives this information and stores it in a database.

[1963] The server will notify the user with a message that "Registration is complete."

[1964] Example of requesting a drinking party

[1965] The user accesses the "Drinking Party Request" form and enters the request details as follows:

[1966] Date and time: December 15, 2023 19:00

[1967] Location: City center

[1968] Number of participants: 10 people

[1969] Budget: 5,000 yen

[1970] Special Request: Asian cuisine

[1971] The server receives the request and stores it in a database.

[1972] The emotion engine evaluates the user's emotions from the input content and obtains an evaluation result such as "I want to be happy."

[1973] The server will send a notification to the user saying "your request has been accepted."

[1974] Examples of proposed stores

[1975] The server reflects the evaluation result "I want to be happy" and searches the database.

[1976] The server will then list highly rated restaurants that fit the criteria of "city center," "Asian cuisine," and "budget 5,000 yen." Restaurants such as "Restaurant Yamada," "Asian Dining Nakata," and "Ethnic Gourmet Shop" will be selected.

[1977] The server emails the list to "taro_yamada@example.com".

[1978] Store selection and reservation example

[1979] The user selects "ethnic gourmet shop" and notifies the server.

[1980] The server performs the reservation procedure for the "ethnic gourmet shop."

[1981] The server receives the booking confirmation and sends a "booking completed" notification to the user.

[1982] Examples of notifications and reminders for participants

[1983] The server receives the participant list and notifies all participants of the details of the drinking party.

[1984] Send a reminder message the day before the drinking party.

[1985] Examples of support on the day of a drinking party

[1986] The server provides users with information such as a list of participants, store information, and contact details.

[1987] The emotion engine assesses participants' real-time reactions and suggests additional entertainment when "excitement levels are low."

[1988] As described above, the system of the present invention can efficiently act as a party organizer while taking into consideration the feelings of the user and participants, thereby increasing user satisfaction.

[1989] The flow of the identification process in the second embodiment will be described with reference to FIG.

[1990] Step 1: Enter and save your user registration information

[1991] Input: The user uses the device to access the "User Registration" page and enters personal information such as name and email address.

[1992] Server behavior:

[1993] Data reception: The server receives the information sent by the user.

[1994] Database storage: The received information is stored in a database using an SQL query.

[1995] Generate notification: Generates a message indicating that registration is complete.

[1996] Output: The server sends the user a message saying "Registration successful."

[1997] Step 2: Enter and save the drinking party request information

[1998] Input: The user accesses a form to request a drinking party through their device and enters the date, time, location, number of people, budget, special requests, etc.

[1999] Server behavior:

[2000] Data reception: The server receives the requested information sent by the user.

[2001] Database storage: The received request information is stored in a database using an SQL query.

[2002] Emotion evaluation: Using the emotion engine, evaluate the user's emotional state based on the request information.

[2003] Reflecting evaluation results: Reflect the evaluation results in the request information and update the database.

[2004] Generate notification: Generates a message indicating that the request has been accepted.

[2005] Output: The server sends the user a message saying "Request accepted."

[2006] Step 3: Proposing potential stores

[2007] Input: The server receives the request information and the emotion evaluation result.

[2008] Server behavior:

[2009] Database search: Using an SQL query, a database is searched for store information that matches the request information and emotion evaluation results.

[2010] List generation: Organize search results into a list.

[2011] Email Creation: Create an email with your list.

[2012] Output: The server sends the generated list to the user's email address.

[2013] Step 4: Select a store and make a reservation

[2014] Input: The user selects the desired store from the received list and notifies the server.

[2015] Server behavior:

[2016] Receiving selection information: Receives store information selected by the user.

[2017] Reservation procedure: We process reservations at selected stores. We use API to access the store's reservation system and send reservation information.

[2018] Get confirmation information: Receive and parse reservation confirmation information.

[2019] Generate notification: Generates a message indicating that the reservation has been completed.

[2020] Output: The server sends the message "Reservation completed" to the user.

[2021] Step 5: Notify and remind participants

[2022] Input: Receives the attendee list and party details provided by the user.

[2023] Server behavior:

[2024] Notification Creation: Create notifications based on the participant list.

[2025] Send email: Send a notification email to all participants.

[2026] Reminder Settings: Schedule a reminder message to be sent the day before the party.

[2027] Output: The server sends notification emails and reminder messages to participants.

[2028] Step 6: Receiving and collating participation confirmation information

[2029] Input: Participants access the attendance confirmation page via their device and input whether or not they will attend.

[2030] Server behavior:

[2031] Data reception: The server receives the entered attendance information.

[2032] Save to database: Save the received attendance information to the database.

[2033] Execution of counting: Counts attendance information and generates a list of participants.

[2034] Output: The server stores the aggregated results as internal data and uses them for subsequent processing.

[2035] Step 7: Providing support on the day of the party

[2036] Input: Receive real-time reaction information from users and participants.

[2037] Server behavior:

[2038] Generate necessary information: Generate the information required on the day of the drinking party (participant list, store information, contact information).

[2039] Emotion evaluation: Evaluate participants' real-time reactions using an emotion engine.

[2040] Additional support suggestions: Generate additional support (e.g., entertainment suggestions) based on the evaluation results.

[2041] Information provision: Providing necessary information and additional support to users.

[2042] Output: The server notifies the user of the information in real time.

[2043] (Application example 2)

[2044] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[2045] When organizing events such as drinking parties, simply handling procedures without considering the user's emotions can make it difficult to sufficiently increase participant satisfaction. Similarly, in factory work environments, ignoring the emotional state of workers can lead to accumulated stress and fatigue, resulting in reduced productivity. To solve these issues, a system is needed that can accurately recognize the emotions of users and workers and provide optimized services and support based on those emotions.

[2046] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[2047] means for receiving and storing user registration information;

[2048] A means for receiving and storing drinking party request information;

[2049] a means for evaluating the emotions of users or participants in real time using an emotion recognition system;

[2050] A means for adjusting work schedules and suggesting breaks based on the evaluated emotional information;

[2051] A means of proposing changes to the work environment based on emotional information;

[2052] a means for searching for and providing suitable candidate locations based on the stored request information;

[2053] means for making a reservation for a location selected by the user and notifying the user of reservation confirmation information;

[2054] A means for notifying participants of the drinking party information and sending reminder messages;

[2055] means for receiving and aggregating participant attendance information;

[2056] A way to provide necessary information on the day of the drinking party,

[2057] This makes it possible to efficiently perform tasks while taking into consideration the feelings of users and workers, thereby increasing user satisfaction.

[2058] "User registration information" refers to personal information such as the user's name and email address that is registered in the system.

[2059] "Drinking party request information" is information such as the date and time, location, number of people, budget, and special requests for the drinking party that the user inputs into the system.

[2060] An "emotion recognition system" is a system that analyzes the facial expressions and voice of users or participants and evaluates their emotional state in real time.

[2061] "Work schedule adjustment" refers to changing the timing and order of work based on emotional information to optimize the workload of users or participants.

[2062] "Break suggestion" refers to recommending that a user or participant take a break by analyzing emotional information.

[2063] "Work environment modification" refers to adjusting the work environment, such as lighting, temperature, and acoustics, based on emotional information.

[2064] "Candidate locations" are candidates for drinking parties or work areas that match the user's request information, searched and provided by the system.

[2065] "Reservation confirmation information" is the result of confirmation of the reservation made by the system for the location selected by the user.

[2066] A "reminding message" is a notification sent by the system to remind participants of the specific date, time and location.

[2067] "Attendance information" is information regarding whether or not a participant will attend that is entered into the system by the participant.

[2068] This invention is a system that uses an emotion recognition system to organize drinking parties and optimize the work environment in a factory. Here, we will explain a specific embodiment including functions such as receiving and saving user registration information, receiving and saving drinking party request information, evaluating emotions in real time using the emotion recognition system, adjusting work schedules, suggesting breaks, and changing the work environment.

[2069] 1. Receiving and storing user registration information

[2070] The user accesses the system using a terminal and enters personal information such as name and email address. The server receives this information and stores it in a database. The user is then notified of the completion of registration.

[2071] 2. Receiving and storing information about drinking party requests

[2072] The user accesses a form to request a drinking party through their device and inputs the request details (date, time, location, number of people, budget, special requests). The server receives the request details and stores them in a database. Based on the request information, the emotion engine evaluates the user's emotional state and reflects the results in the request information.

[2073] 3. Real-time evaluation using emotion recognition system

[2074] The emotion recognition system analyzes the facial expressions and voice of the user or participant to assess their emotional state in real time. Specifically, it uses a camera and microphone and leverages software libraries such as OpenCV and TensorFlow / Keras. Using a Haar cascade for face detection, the collected data is fed into an emotion recognition model, and the resulting emotion assessment is sent to a server.

[2075] 4. Adjusting work schedules and suggesting breaks

[2076] The server then adjusts the work schedule and suggests breaks based on the emotion evaluation results obtained from the emotion recognition system. For example, if the server detects that the user is "feeling stressed," it can make suggestions to reduce the workload.

[2077] 5. Changes in work environment

[2078] The server then makes suggestions to adjust the working environment, such as lighting, temperature, and acoustics, based on the emotion evaluation results, thereby improving the comfort level of users and workers.

[2079] Specific use cases

[2080] A user is working in a factory. The robot uses a camera and microphone to collect the worker's facial expressions and voice, which are then input into an emotion recognition model. For example, if the robot detects that the worker is feeling stressed, it can suggest a break and adjust the work schedule to reduce the workload. It can also make suggestions to adjust the lighting and temperature of the work environment.

[2081] Example prompts for generative AI models

[2082] Show us how to input facial and voice data from workers, recognize their emotions, and suggest work environment optimization solutions. Please provide the following information:

[2083] 1. Detailed instructions and code examples

[2084] 2. Hardware and Software Used

[2085] 3. Practical Applications

[2086] This enables efficient task substitution and optimization of the work environment while taking emotions into consideration, thereby improving user satisfaction and productivity.

[2087] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[2088] Step 1:

[2089] A user accesses the system using a terminal and enters personal information such as their name and email address. The server receives this information and stores it in a database. The input data is the user's name and email address, and the output is a message confirming registration.

[2090] Step 2:

[2091] A user inputs a request for a drinking party into a form on their device. The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database. At this time, the input data is detailed information about the drinking party, and the output is a notification that the request has been accepted.

[2092] Step 3:

[2093] The server uses an emotion recognition system to evaluate emotions based on the user's input included in the request information. Data collected from the camera and microphone is processed using OpenCV and TensorFlow / Keras to perform face detection and emotion classification. The input data is the user's facial expressions and voice, and the output is the user's emotional evaluation.

[2094] Step 4:

[2095] The server adjusts the work schedule and suggests breaks based on the emotion evaluation results. For example, if the user is evaluated as "feeling stressed," it will suggest appropriate break times and reducing the workload. The input data is the emotion evaluation results, and the output is a suggestion to adjust the work schedule.

[2096] Step 5:

[2097] The server then proposes changes to the work environment based on the emotion evaluation results. For example, if the user is rated as "I want to relax," the server will propose softening the lighting and adjusting the temperature to a comfortable range. The input data is the emotion evaluation results, and the output is specific suggestions for environmental changes.

[2098] Step 6:

[2099] The server searches for suitable candidate locations based on the stored request information and generates a list of them. The emotional evaluation results are also taken into consideration to select locations that are appropriate for the user's emotional state. The input data are the request information and the emotional evaluation results, and the output is a list of candidate locations.

[2100] Step 7:

[2101] The user uses a terminal to select a desired location from a list of candidate locations and notify the server. The server then makes a reservation for the selected location and obtains reservation confirmation information. The input data is the user-selected location information, and the output is reservation confirmation information.

[2102] Step 8:

[2103] The server receives the participant list and notifies the participants of the details of the drinking party. It also sends a reminder message the day before the drinking party. The input data is the participant list, and the output is the detailed information notification and the reminder message.

[2104] Step 9:

[2105] Participants use their devices to access the attendance confirmation page and enter whether they will attend. The server receives the attendance information, stores it in a database, and aggregates it. The input data is attendance information, and the output is the aggregated results.

[2106] Step 10:

[2107] The server generates the necessary information for the day of the drinking party (participant list, restaurant information, contact information) and provides it to the user. The emotion engine also evaluates the real-time reactions of participants and suggests appropriate additional support. The input data are the real-time reactions of participants, and the output is suggestions for additional support.

[2108] The specific processing unit 290 transmits the result of the specific processing to the headset type terminal 314. In the headset type terminal 314, the control unit 46A causes the speaker 240 and the display 343 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[2109] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[2110] In the above embodiment, an example was given in which the specific processing is performed by the data processing device 12, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the headset type terminal 314.

[2111] [Fourth embodiment]

[2112] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

[2113] 7, a data processing system 410 includes a data processing device 12 and a robot 414. An example of the data processing device 12 is a server.

[2114] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[2115] The robot 414 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a control target 443. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the control target 443 are also connected to the bus 52.

[2116] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[2117] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[2118] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[2119] The control object 443 includes a display device, LEDs in the eyes, and motors for driving the arms, hands, and feet. The posture and gestures of the robot 414 are controlled by controlling the motors of the arms, hands, and feet. Some of the emotions of the robot 414 can be expressed by controlling these motors. In addition, the facial expressions of the robot 414 can also be expressed by controlling the light emission state of the LEDs in the eyes of the robot 414.

[2120] Fig. 8 shows an example of the main functions of the data processing device 12 and the robot 414. As shown in Fig. 8, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[2121] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[2122] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[2123] In the robot 414, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[2124] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[2125] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[2126] Explanation of program processing

[2127] 1. User registration function

[2128] Users access the system using a terminal and enter personal information such as their name and email address.

[2129] The server receives this information and stores it in a database.

[2130] The user will receive a message confirming registration.

[2131] 2. Accepting drinking party requests

[2132] The user accesses a form for requesting a drinking party through the terminal.

[2133] The server receives the request details (date, time, location, number of people, budget, special requests) and stores them in a database.

[2134] The user is notified that the request has been accepted.

[2135] 3. Proposal of candidate stores

[2136] The server searches the database for store information based on the received request information.

[2137] The server generates a list of stores that match the criteria and provides it to the user via email or notification.

[2138] The user checks the list and selects the desired store.

[2139] 4. Store reservation agent

[2140] The store information selected by the user is sent to the server.

[2141] The server performs the reservation procedure with the store and obtains confirmation information that the reservation has been completed.

[2142] The user is notified that the reservation is complete.

[2143] 5. Notification and reminders to participants

[2144] The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[2145] It also sends a reminder message the day before the drinking party.

[2146] 6. Participation confirmation function

[2147] Participants access the attendance confirmation page via their terminal and enter whether or not they will attend.

[2148] The server receives the attendance information and stores and aggregates it in a database.

[2149] 7. Support on the day of the drinking party

[2150] The server provides users with the information they need on the day of the party (e.g., participant list, store information, contact information).

[2151] Users can use the system to receive the support they need based on their situation.

[2152] Specific examples

[2153] Example of a user registering in the system

[2154] The user accesses the "User Registration" page using a terminal and enters the name "Yamada Taro" and email address "taro_yamada@example.com."

[2155] The server receives this information and stores it in a database.

[2156] The user will receive a message saying "Registration complete."

[2157] Example of requesting a drinking party

[2158] Users access the "Drinking Party Request" form and enter their request details, such as "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food."

[2159] The server receives the request and stores it in a database.

[2160] The user will receive a notification that their request has been accepted.

[2161] Examples of proposed stores

[2162] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "budget of 5,000 yen" to generate a list of candidate restaurants, such as "Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN."

[2163] The user is notified of the list.

[2164] Store selection and reservation example

[2165] The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[2166] The server will make a reservation at Charcoal Grilled Meat ZEN.

[2167] The server receives the reservation confirmation and notifies the user.

[2168] Examples of notifications and reminders for participants

[2169] The server receives the participant list and notifies all participants of the details of the drinking party.

[2170] Send a reminder message the day before the drinking party.

[2171] Examples of support on the day of a drinking party

[2172] The server provides the user with a list of participants, store information, contact information, etc., and provides additional information as needed.

[2173] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[2174] The processing flow will be explained below.

[2175] User registration function

[2176] Step 1:

[2177] The user uses the terminal to access the URL of the user registration form.

[2178] Step 2:

[2179] The user enters personal information such as name, email address, and phone number.

[2180] Step 3:

[2181] The user presses the registration button.

[2182] Step 4:

[2183] The terminal transmits the input data to the server.

[2184] Step 5:

[2185] The server receives the data and stores it in a database.

[2186] Step 6:

[2187] The server generates a registration completion message and sends it to the terminal.

[2188] Step 7:

[2189] The user will see a message on their device confirming successful registration.

[2190] Accepting drinking party requests

[2191] Step 1:

[2192] The user uses the terminal to access the URL of the drinking party request form.

[2193] Step 2:

[2194] Users enter information such as date, time, location, number of participants, budget, and any special requests.

[2195] Step 3:

[2196] The user presses the request button.

[2197] Step 4:

[2198] The terminal transmits the input data to the server.

[2199] Step 5:

[2200] The server receives the data and stores it in a database.

[2201] Step 6:

[2202] The server generates a message accepting the request and sends it to the terminal.

[2203] Step 7:

[2204] The user checks the message on the terminal that the request has been accepted.

[2205] Proposal of candidate stores

[2206] Step 1:

[2207] The server searches for store information in the database.

[2208] Step 2:

[2209] The server will list appropriate stores based on the request information (date, time, location, budget, special requests).

[2210] Step 3:

[2211] The server generates a list of candidate stores.

[2212] Step 4:

[2213] The server sends the list to the user's email address.

[2214] Store selection and reservation

[2215] Step 1:

[2216] The user receives a list of candidate stores and selects the store of their choice.

[2217] Step 2:

[2218] The user notifies the server of the selected store information.

[2219] Step 3:

[2220] The server then performs the reservation procedure for the selected store.

[2221] Step 4:

[2222] The server acquires reservation confirmation information from the store.

[2223] Step 5:

[2224] The server will send a notification of reservation completion to the user's email address.

[2225] Notifications and reminders to participants

[2226] Step 1:

[2227] The user inputs the participant's email address and contact information into the server and sends it.

[2228] Step 2:

[2229] The server will notify participants of details about the drinking party via email or SNS message.

[2230] Step 3:

[2231] The server sends a reminder message the day before the party.

[2232] Participation confirmation function

[2233] Step 1:

[2234] Participants will access the participation confirmation page via a link in the email.

[2235] Step 2:

[2236] Participants enter whether they will attend and press the send button.

[2237] Step 3:

[2238] The terminal transmits the attendance information to the server.

[2239] Step 4:

[2240] The server receives the attendance information and stores it in a database.

[2241] Step 5:

[2242] The server tally the stored attendance information.

[2243] Support on the day of the drinking party

[2244] Step 1:

[2245] The server generates the information needed on the day of the drinking party (participant list, store information, contact information).

[2246] Step 2:

[2247] The server provides the necessary information to the user.

[2248] Step 3:

[2249] The user uses the system to check the necessary information.

[2250] Example 1

[2251] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[2252] Traditionally, organizing a drinking party was a time-consuming and labor-intensive process, placing a heavy burden on users. In particular, it was difficult to efficiently organize a drinking party due to the complex and wide-ranging tasks involved, such as selecting an appropriate restaurant based on the number of people and budget, making reservations, notifying and reminding participants, and confirming attendance.

[2253] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[2254] In this invention, the server includes: means for a user to access the system's "user registration" page using a terminal and input personal information such as name, email address, and password; means for the server to receive the input information and store it in a database; means for a user to input detailed information about a drinking party (date, time, location, number of people, budget, special requests); means for the server to receive the input information and store it in a database; means for the server to search the database for restaurant information matching the conditions based on the stored request information; means for the server to provide the user with the generated restaurant list; means for the user to make a reservation at a restaurant selected by the user and obtain reservation confirmation information; means for the server to notify the user of the reservation confirmation information; means for the server to notify participants of detailed information about the drinking party based on the attendee list provided by the user; means for the server to send a reminder message to participants the day before the drinking party; means for participants to access the attendance confirmation page through their terminal and input whether or not they will attend; means for the server to receive the attendance information and store and tally it in a database; and means for the server to provide users with information necessary on the day of the drinking party. This enables efficient management of drinking party events.

[2255] "User registration information" is a general term for personal information such as a user's name, email address, and password.

[2256] "Terminal" refers to an electronic device such as a computer or smartphone that a user uses to access a server via the Internet.

[2257] A "server" is a computer system that receives and processes requests from users, and provides functions such as database management and email transmission.

[2258] "Database" refers to a system for efficiently storing, managing, and retrieving information, and specifically includes relational databases such as MySQL.

[2259] "Drinking party request information" is a general term for detailed information necessary for hosting a drinking party, such as the date and time of the drinking party, the location, the number of people, the budget, and any special requests.

[2260] "Candidate store information" refers to a list of restaurants that meet the conditions based on the drinking party request information.

[2261] "Reservation confirmation information" refers to information indicating that the server has made a reservation with the restaurant and that the reservation has been confirmed.

[2262] "Participant list" is a general term for information provided by a user, such as names and contact information of people who plan to attend a drinking party.

[2263] A "reminder message" is a notification message sent to participants the day before a drinking party to help them remember to attend.

[2264] "Attendance confirmation information" refers to information indicating whether or not participants will be able to attend a drinking party, which is entered by participants through the attendance confirmation page.

[2265] The present invention provides a specific embodiment of a system that handles the organizing tasks of a drinking party, etc. This system streamlines the organizing tasks and reduces the burden on the user by smoothly performing user registration, accepting requests for drinking parties, proposing candidate restaurants, reserving restaurants, notifying participants, confirming attendance, and providing support on the day of the party.

[2266] Specifically, the following hardware and software are used:

[2267] Hardware:

[2268] Device (PC, smartphone, etc.)

[2269] Servers (web servers, database servers, etc.)

[2270] software:

[2271] Web browser

[2272] Web Applications

[2273] Database management system (e.g. MySQL)

[2274] Mail server (e.g. SMTP server)

[2275] API connection (e.g. Google Calendar API)

[2276] User Registration

[2277] The user accesses the system's "User Registration" page using a terminal and enters personal information such as name, email address, and password. The server receives this information and stores it in a database such as MySQL. The user receives a confirmation email stating "Registration completed."

[2278] Specific examples

[2279] The user accesses "https: / / nomikai-system.com / register" on a smartphone or PC and enters information such as "Yamada Taro," "taro_yamada@example.com," and "password123." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user a confirmation email stating "Registration completed."

[2280] Accepting drinking party requests

[2281] The user accesses the "Drinking Party Request" form through their device and enters the details of the drinking party (date, time, location, number of people, budget, special requests). The server receives the entered information and stores it in a database. The user receives an email notification that the "request has been accepted."

[2282] Specific examples

[2283] The user accesses "https: / / nomikai-system.com / request" and enters the information "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food." The server receives this information and saves it in the database using an INSERT statement. The server then sends the user an email notification that "the request has been accepted."

[2284] Proposal of candidate stores

[2285] The server searches for restaurant information in the database based on the drinking party request information. It generates a list of restaurants that match the criteria and provides it to the user via email or notification. The user can then review the list and select the restaurant they want.

[2286] Specific examples

[2287] The server searches the database using the criteria "Shinjuku," "Japanese cuisine," and "5,000 yen," and generates a list of restaurants that meet the criteria ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," and "Charcoal Grilled Meat ZEN"). The server then sends the list of candidate restaurants to the user via email. The user looks at the email they receive, selects the restaurant they want (for example, "Charcoal Grilled Meat ZEN"), and notifies the server.

[2288] Store reservation service

[2289] The user sends the store information they selected to the server. The server then completes the reservation procedure with the store and receives confirmation that the reservation is complete. The user receives a notification that the reservation is complete.

[2290] Specific examples

[2291] The user selects "Charcoal Grilled Meat ZEN" and notifies the server. The server processes the reservation with "Charcoal Grilled Meat ZEN" using an API call or a telephone automation system. The server obtains the reservation confirmation and stores it in a database. The user receives an email stating "Reservation completed."

[2292] Notifications and reminders to participants

[2293] The server notifies participants of the details of the drinking party based on the participant list provided by the user, and also sends a reminder message the day before the drinking party.

[2294] Specific examples

[2295] The server notifies all participants of the "Drinking Party Details" by email based on the participant list. The day before the drinking party, the server automatically sends a reminder message using the Google Calendar API.

[2296] Participation confirmation function

[2297] Participants access the attendance confirmation page via their terminal and enter whether they will attend. The server receives the attendance information and stores and compiles it in a database.

[2298] Specific examples

[2299] Participants access "https: / / nomikai-system.com / confirm" to confirm their attendance. The server receives the attendance information and stores it in a MySQL database. The server then sends the tally results to the user.

[2300] Support on the day of the drinking party

[2301] The server provides users with the necessary information on the day of the drinking party, and users use the system to receive the necessary support according to the situation.

[2302] Specific examples

[2303] On the morning of the party, the server will email the user details such as the participant list, store information, and emergency contact information. Any additional information or support the user needs will be received in real time through the system.

[2304] Prompt Sentence Examples

[2305] I want to register user information in the system. The username is "Yamada Taro" and the email address is "taro_yamada@example.com". Please explain the process for saving this information to the database.

[2306] A user fills out a form to request a drinking party with the following information: "Date and time: October 15, 2023, 7:00 PM," "Location: Shinjuku," "Number of participants: 10," "Budget: 5,000 yen," and "Request: Japanese food." Explain the process for saving this information to a database.

[2307] In this way, the system of the present invention can efficiently act as a party organizer and significantly reduce the burden on the user.

[2308] The flow of the identification process in the first embodiment will be described with reference to FIG.

[2309] Program processing flow

[2310] Step 1: User Registration

[2311] 1. The user accesses the "User Registration" page using a terminal.

[2312] Input: The URL where users will access the registration page.

[2313] Output: Display of user registration form.

[2314] Specific operation: The user accesses "https: / / nomikai-system.com / register".

[2315] 2. The user enters personal information such as name, email address, and password.

[2316] Input: Name, Email Address, Password.

[2317] Output: The information entered.

[2318] Specific operation: The user enters "Yamada Taro", "taro_yamada@example.com", and "password123".

[2319] 3. The server receives the entered information and stores it in a database.

[2320] Input: Personal information entered by the user.

[2321] Output: User information stored in the database.

[2322] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[2323] 4. The server sends the user a message confirming registration.

[2324] Input: User information stored in the database.

[2325] Output: A confirmation email confirming successful registration.

[2326] Specific behavior: The server sends a confirmation email saying "Registration completed."

[2327] Step 2: Accepting a drinking party request

[2328] 1. The user accesses the "Drinking Party Request" form via their device.

[2329] Input: The URL where users can access the request form.

[2330] Output: Display of drinking party request form.

[2331] Specific operation: The user accesses "https: / / nomikai-system.com / request".

[2332] 2. The user enters the details of the drinking party (date, time, location, number of people, budget, special requests).

[2333] Input: date, time, location, number of people, budget, special requests.

[2334] Output: The request information entered.

[2335] Specific operation: The user enters "October 15, 2023," "Shinjuku," "10 people," "5,000 yen," and "Japanese food."

[2336] 3. The server receives the entered information and stores it in a database.

[2337] Input: Request information entered by the user.

[2338] Output: Request information stored in a database.

[2339] What happens next: The server receives this information and stores it in a MySQL database using an SQL INSERT statement.

[2340] 4. The server sends a message to the user acknowledging the request.

[2341] Input: Request information stored in the database.

[2342] Output: Email confirming acceptance of request.

[2343] Specific behavior: The server sends a confirmation email saying "your request has been accepted."

[2344] Step 3: Proposing potential stores

[2345] 1. The server searches for store information in the database based on the drinking party request information.

[2346] Input: Request details (location, budget, special requests).

[2347] Output: A list of stores that match the criteria.

[2348] Specific operation: The server searches the database for the conditions "Shinjuku," "Japanese food," and "5,000 yen."

[2349] 2. The server generates a list of stores that match the conditions.

[2350] Input: Store information as search results.

[2351] Output: The generated store list.

[2352] Specific operation: Generate a list of stores that meet the conditions ("Japanese-style Izakaya Kacho Fuugetsu," "Shinjuku Japanese Restaurant Sakura," "Charcoal Grill Niku ZEN").

[2353] 3. The server notifies the user of the store list.

[2354] Input: Generated store list.

[2355] Output: Store list notification email.

[2356] Specific operation: The server sends the user a list of candidate stores by email.

[2357] 4. The user selects the store of their choice.

[2358] Input: Store list.

[2359] Output: Selected store information.

[2360] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[2361] Step 4: Store reservation

[2362] 1. The store information selected by the user is sent to the server.

[2363] Input: Selected store information.

[2364] Output: Store information sent to the server.

[2365] Specific operation: The user selects "Charcoal Grilled Meat ZEN" and notifies the server.

[2366] 2. The server makes a reservation with the store.

[2367] Input: Selected store information.

[2368] Output: A reservation request to the store.

[2369] Specific operation: The server makes a reservation to "Charcoal Grilled Meat ZEN" using an API call or an automated telephone system.

[2370] 3. The server receives confirmation of the reservation.

[2371] Input: Reservation confirmation information from the store.

[2372] Output: The retrieved reservation confirmation information.

[2373] What happens: The server gets the booking confirmation and stores it in the database.

[2374] 4. The server sends a notification to the user that the reservation is complete.

[2375] Input: Retrieved reservation confirmation information.

[2376] Output: Notification email of reservation completion.

[2377] Specific behavior: Sends the user an email saying "Reservation completed."

[2378] Step 5: Notify and remind participants

[2379] 1. The server notifies participants of the details of the drinking party based on the participant list provided by the user.

[2380] Input: Participant list, details of the drinking party.

[2381] Output: Notification email to participants.

[2382] Specific operation: Based on the participant list, the server notifies all participants of the "details of the drinking party" by email.

[2383] 2. The server sends a reminder message the day before the drinking party.

[2384] Input: Participant list.

[2385] Output: Reminder message email.

[2386] Specific operation: The server uses the Google Calendar API to automatically send a reminder message the day before the drinking party.

[2387] Step 6: Participation confirmation function

[2388] 1. Participants access the attendance confirmation page via their device.

[2389] Input: The URL of the attendance confirmation page.

[2390] Output: Display of attendance confirmation form.

[2391] Specific action: Participant accesses "https: / / nomikai-system.com / confirm".

[2392] 2. Participants enter whether they will attend.

[2393] Input: Attendance confirmation information.

[2394] Output: The attendance confirmation information entered.

[2395] Specific operation: Participants input whether they will attend or not.

[2396] 3. The server receives the attendance information and stores and aggregates it in a database.

[2397] Input: Attendance confirmation information entered by the participant.

[2398] Output: Attendance confirmation information and summary results stored in the database.

[2399] Specific operation: The server receives the attendance information, stores it in the database using SQL INSERT statements, and aggregates it.

[2400] Step 7: Support on the day of the drinking party

[2401] 1. The server provides the user with the information they need on the day of the drinking party.

[2402] Input: Party details, participant list, contact information.

[2403] Output: An email containing the required information.

[2404] Specific operation: On the morning of the drinking party, the server sends the user an email with details such as the list of participants, store information, and emergency contact information.

[2405] 2. Users use the system to receive the support they need in their context.

[2406] Input: The user's request.

[2407] Output: Supporting information provided.

[2408] Specific Action: The user receives any additional information or support they need in real time through the system.

[2409] (Application example 1)

[2410] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[2411] Conventional party organizer tasks involve multiple, complicated procedures that require a great deal of time and effort when planning and running a drinking party. Tasks such as selecting potential restaurants, making reservations, and notifying participants of information are particularly complex, placing a heavy burden on organizers. Furthermore, providing necessary information in real time on the day of the party is difficult, making it difficult to respond to unforeseen circumstances. Another problem is that efficient methods for operating and managing smart devices have not yet been fully established.

[2412] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[2413] In this invention, the server includes means for receiving and saving user registration information, means for receiving and saving drinking party request information, means for searching for and providing appropriate candidate restaurants based on the saved request information, means for making a reservation at a restaurant selected by the user and notifying the reservation confirmation information, means for notifying participants of drinking party information and sending reminder messages, means for receiving and compiling participant attendance information, means for providing information needed on the day of the drinking party, means for reading user registration information using a smart device when entering the restaurant and registering the user, means for displaying a list of candidate restaurants via the smart device and allowing selection, and means for visually providing information needed on the day of the drinking party using the smart device. This significantly reduces the workload involved in conventional organizing tasks and makes it possible to provide necessary information in real time.

[2414] "User registration information" refers to information including personal information such as the user's name and email address.

[2415] "Drinking party request information" refers to information such as the date and time of the drinking party, the location, the number of participants, the budget, and any special requests.

[2416] "Candidate store" refers to a store that is capable of hosting a drinking party and has been selected based on the drinking party request information.

[2417] "Reservation confirmation information" refers to the reservation confirmation information provided by the store after the reservation procedure has been completed.

[2418] "Participants" refers to people who plan to attend a drinking party.

[2419] "Information notification" refers to notifying participants of detailed information about the drinking party.

[2420] A "reminder message" refers to a confirmation message sent to participants the day before the drinking party.

[2421] "Attendance Information" refers to information regarding a participant's attendance confirmation.

[2422] "Smart device" refers to devices such as smartphones, smart glasses, or head-mounted displays.

[2423] "Visual presentation" refers to the method of displaying information directly in the user's field of vision through a smart device.

[2424] The present invention relates to a system that enables a user to efficiently perform administrative tasks using a smart device. The present invention is primarily implemented using a smart device such as a smartphone, smart glasses, or a head-mounted display.

[2425] First, the user accesses the system using a smart device. When the user enters a store, they scan a QR code installed at the entrance or elsewhere. After scanning the QR code, the necessary information for user registration is displayed on the screen of the smart device. The user enters personal information such as their name and email address and presses the send button. This information is sent to the server and stored in a database.

[2426] Next, the user uses a smart device to input information about the drinking party request, such as the date, time, location, number of participants, budget, and any special requests. This information is sent to the server, and the request is saved in a database. Based on this request, the server searches the database for candidate restaurants and generates a list of restaurants that meet the user's requirements.

[2427] The generated list of stores is displayed on the screen of the smart device, and the user selects the store they want from the list. The store information selected by the user is sent to the server, which then processes the reservation. Once the reservation is complete, the server generates confirmation information and notifies the user via the smart device.

[2428] The server then notifies participants of the details of the drinking party based on the participant list provided by the user. Furthermore, a reminder message is automatically sent the day before the drinking party to prompt participants to confirm their attendance. The participants' attendance information is sent to the server and stored in a database.

[2429] On the day of the party, the server will display the necessary information (participant list, store information, contact information, etc.) on the screen of the smart device, allowing users to check the necessary information in real time and smoothly carry out their organizing duties.

[2430] Furthermore, the system significantly improves the overall efficiency of administrative work by transmitting information obtained from smart devices to a server in real time for analysis and processing. For example, by using smart glasses, users can visually obtain necessary information without using their hands, improving operability.

[2431] Hardware and software used

[2432] Hardware:

[2433] Smart glasses (e.g. Google Glass)

[2434] Smartphone

[2435] head-mounted display

[2436] Software and Libraries:

[2437] QRScanner: A library for reading QR codes

[2438] UserRegistryAPI: API to send user registration information to the server

[2439] PartyRequestAPI: API for managing drinking party request information

[2440] StoreDatabase: Database for searching information on potential stores

[2441] ReservationAPI: API for making store reservations

[2442] NotificationService: Service for notifying and reminding participants

[2443] AttendanceCheckAPI: API for receiving attendance confirmation information

[2444] InformationDisplayService: A service that displays information about the day of the drinking party

[2445] Examples and prompts

[2446] Examples:

[2447] A user enters a store and scans the QR code with the smart glasses. The user then enters their name and email address into the form displayed on the smart glasses screen to complete registration.

[2448] The user uses smart glasses to access a drinking party request form and enters the following: "Date and time: October 15, 2023, 7:00 PM," "Location: Commercial location," "Number of participants: 10," "Budget: 5,000 yen," and "Special request: Japanese cuisine."

[2449] The server uses this information to search for candidate stores and displays the results on the smart glasses screen. The user selects an appropriate store from the list and notifies the server.

[2450] The server makes a reservation at the selected store and notifies the user of reservation confirmation information.

[2451] The day before the drinking party, the server sends a reminder message to all participants and collects attendance confirmation information.

[2452] Prompt for the generative AI model:

[2453] - "Please explain the process of an application for smart glasses that will completely take over as organizer of a drinking party at a specific location on a specific date."

[2454] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[2455] Step 1:

[2456] A user reads the QR code using a smart device. This allows the user to enter a store and scan the QR code displayed on the terminal using smart glasses or a smartphone. The input data is the content of the QR code (the URL of the user registration page), and the output is the user registration page being displayed on the smart device.

[2457] Step 2:

[2458] The user enters personal information such as name and email address into the user registration form displayed on the screen of the smart device and submits it. The input data is personal information such as name and email address, and is sent to the server. The server stores the submitted information in a database and returns a confirmation message to the user confirming completion of registration.

[2459] Step 3:

[2460] A user accesses a drinking party request form using a smart device and inputs the date, time, location, number of participants, budget, and any special requests for the drinking party. The input data is detailed information about the drinking party and is sent to the server. The server stores the received information in a database and notifies the user that the request has been accepted.

[2461] Step 4:

[2462] The server searches for candidate restaurants based on the drinking party request information it receives. The server searches the database and generates a list of suitable candidate restaurants based on the input data. The output data is the list of candidate restaurants, which is sent to the user's smart device.

[2463] Step 5:

[2464] The user selects the desired store from a list of candidate stores displayed on the screen of their smart device and sends that information to the server. The input data is the store information selected by the user, and the server processes the reservation based on this information. The server then generates reservation confirmation information and returns it to the user's smart device.

[2465] Step 6:

[2466] The server notifies participants of the details of the drinking party based on the participant list provided by the user. The input data is the participant list and drinking party details, and the output is a notification message to the participants. In addition, a reminder message is automatically sent the day before the drinking party.

[2467] Step 7:

[2468] Participants use smart devices to confirm their attendance. The input data, which indicates whether they are attending or not, is sent to the server and stored in a database. The server then compiles the attendance information and notifies the user.

[2469] Step 8:

[2470] On the day of the drinking party, users use smart devices to view the necessary information (e.g., participant list, store information, contact information). The server provides this information in real time, and users check the information displayed on the screen of their smart glasses or smartphone. The input data is the user's request, and the output data is the detailed information provided in real time.

[2471] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[2472] The present invention shows a specific embodiment of a system that handles the organizing tasks of drinking parties, etc., by combining an emotion engine that recognizes the user's emotions and reflects them in the processing. This system not only smoothly performs user registration, reception of drinking party requests, proposal of candidate restaurants, restaurant reservations, notification to participants, attendance confirmation, and support on the day of the drinking party, but also provides a more appropriate and satisfying service by taking into account the emotions of the user and participants.

[2473] Explanation of program processing

[2474] 1. User registration function

[2475] Users access the system using a terminal and enter personal information such as their name and email address.

[2476] The server receives this information and stores it in a database.

[2477] A message is sent to the user indicating that registration is complete. 【247...

Claims

1. means for receiving and storing user registration information; A means for receiving and storing drinking party request information; A means for searching for and providing suitable candidate stores based on the stored request information; A means for making a reservation at a store selected by the user and notifying the user of reservation confirmation information; A means for notifying participants of the drinking party information and sending reminder messages; means for receiving and aggregating participant attendance information; A means of providing necessary information on the day of the drinking party Including system.

2. 10. The system of claim 1, further comprising means for identifying the user based on user registration information.

3. 2. The system according to claim 1, further comprising means for listing only stores that satisfy specific conditions based on the request information in the search for candidate stores.

Images