system

Abstract

Provide a system. [Solution] A means of receiving the meeting target list and the project details; means for acquiring schedule data from the calendar system of each target person based on the target person list; A means for analyzing the acquired schedule data and identifying free time for each target person; A means to calculate the shortest time slot available to everyone, A means of registering the determined meeting time in each person's calendar; a means for sending a notification of completion of the conference setup to each of the participants; A means of collecting and analyzing actual meeting attendance data; A system including:

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] Scheduling a meeting for a large number of people is extremely difficult, especially when there are many upper-level members. Even if you want to schedule a meeting quickly, checking and adjusting the schedules of each member takes time and requires a lot of effort. Also, even when not everyone needs to attend a particular matter, it is not easy to determine this, making it difficult to schedule an efficient meeting. For this reason, there is a need for a method to efficiently and quickly set the optimal meeting time and hold a meeting with only the necessary members. [Means for solving the problem]

[0005] To solve the above problems, the present invention provides the following means: Efficient and prompt conference setting is achieved by combining a means for receiving a list of conference participants and the details of the matter, a means for acquiring schedule data from each participant's calendar system based on the list of participants, a means for analyzing the acquired schedule data and identifying each participant's free time, a means for calculating the shortest time slot in which all participants are free, a means for registering the determined conference time on each participant's calendar, a means for sending a notification that the conference has been set up to each participant, and a means for collecting and analyzing actual conference attendance data. The system also provides optimal conference setting by further including a means for determining whether a conference can be established with only members of a specific level based on the details of the conference's matter, and a means for analyzing information useful for setting up the next conference based on actual attendance data after the conference has been set up and providing feedback.

[0006] The "meeting participant list" is a list of each member who is scheduled to participate in the meeting.

[0007] "Item content" refers to the specific topics or agenda items to be discussed at the meeting.

[0008] The "calendar system" is a schedule management system used by each subject.

[0009] "Schedule data" is schedule information for each subject obtained from a calendar system.

[0010] "Available time" refers to the time period during which the target person is available to participate in the meeting.

[0011] The "shortest time slot" refers to the earliest time that everyone is free.

[0012] "Meeting time" refers to the determined start and end times of a meeting.

[0013] "Notification" is a means of informing the target person of the completion of conference setup.

[0014] "Conference participation data" refers to information such as the attendance status and speech records of participants at an actual conference.

[0015] "Members of a specific layer" refers to members who hold specific positions or roles. [Brief explanation of the drawings]

[0016] [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

[0017] 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.

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

[0019] 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).

[0020] 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.

[0021] 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.

[0022] 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.

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

[0024] [First embodiment]

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

[0026] 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.

[0027] 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).

[0028] 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.

[0029] 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.

[0030] 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.

[0031] 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.

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

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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."

[0037] ---

[0038] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[0039] System configuration

[0040] 1. User Interface

[0041] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[0042] For example, a form in a web browser or a dedicated application.

[0043] 2. Server

[0044] It is the central element for receiving input from the user and performing processing.

[0045] Processing flow

[0046] 1. Receiving the list of meeting participants and the details of the meeting

[0047] User

[0048] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0049] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0050] Terminal

[0051] The user's input is sent to the server.

[0052] 2. Obtain schedule data for each subject

[0053] server

[0054] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[0055] For example, use the Google (registered trademark) Calendar API or the Microsoft (registered trademark) Outlook API.

[0056] Calendar System

[0057] Each calendar system returns schedule data for the subject.

[0058] 3. Identifying participants' available times

[0059] server

[0060] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0061] Example: Count the number of people available for each time slot.

[0062] 4. Calculating optimal meeting times

[0063] server

[0064] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0065] Example: Find the next Monday at 3pm when everyone is free.

[0066] server

[0067] Depending on the content of the project, we also take into consideration the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0068] Example: Identify a time when at least the team lead is available to participate instead of the entire development team.

[0069] 5. Set up a meeting

[0070] server

[0071] Send an API request to register the determined meeting time in each person's calendar.

[0072] Example: Create an event called "Project Status Meeting" in Google Calendar.

[0073] 6. Sending Notifications

[0074] server

[0075] Send emails and push notifications to notify each participant that the meeting has been set up.

[0076] User

[0077] Each participant will see the new meeting setting in their calendar and notifications.

[0078] 7. Collecting and analyzing conference attendance data

[0079] server

[0080] After the conference ends, the server collects and analyzes actual conference attendance data.

[0081] Example: Use a conference tool's API to obtain participants' attendance status and speech records.

[0082] server

[0083] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0084] In this way, the system helps users easily and efficiently set up large-scale conferences, reducing wasted time and ensuring optimal conference management.

[0085] ---

[0086] The processing flow will be explained below.

[0087] Step 1:

[0088] User

[0089] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0090] Example: User enters "All development team members" and "Project status meeting."

[0091] Step 2:

[0092] Terminal

[0093] The user's input is sent to the server.

[0094] Example: An input form is submitted and the user's input is passed to the server.

[0095] Step 3:

[0096] server

[0097] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[0098] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[0099] Step 4:

[0100] Calendar System

[0101] Each calendar system returns the schedule data of the target person to the server.

[0102] Example: Schedule data for each participant is returned in JSON format.

[0103] Step 5:

[0104] server

[0105] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0106] Example: For each time slot, list the availability of each person.

[0107] Step 6:

[0108] server

[0109] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0110] Example: Find the next Monday at 3pm when everyone is free.

[0111] Step 7:

[0112] server

[0113] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0114] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[0115] Step 8:

[0116] server

[0117] Send an API request to register the determined meeting time in each person's calendar.

[0118] Example: Create an event called "Project Status Meeting" in Google Calendar.

[0119] Step 9:

[0120] server

[0121] Send emails and push notifications to notify each participant that the meeting has been set up.

[0122] Example: Send a notification with meeting details and date and time.

[0123] Step 10:

[0124] User

[0125] Each participant will see the new meeting setting in their calendar and notifications.

[0126] Example: Participants see the meeting entry in their calendar.

[0127] Step 11:

[0128] server

[0129] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[0130] Example: Obtaining attendance status and speech records.

[0131] Step 12:

[0132] server

[0133] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0134] For example: suggesting frequently required participants and suitable meeting times.

[0135] ---

[0136] Example 1

[0137] 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."

[0138] Conventional methods for setting up multi-person meetings have the drawback of being time-consuming and inefficient. In particular, it is difficult to find the optimal meeting time by adjusting the schedules of many participants, and it is difficult to effectively utilize the attendance rate and feedback of participants after the meeting is set up.

[0139] 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.

[0140] In this invention, the server includes means for receiving a list of meeting participants and the details of the meeting, means for acquiring schedule data from the calendar systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's free time, means for calculating the shortest time slot in which all participants are free, means for registering the determined meeting time in each participant's calendar, means for sending a notification that the meeting has been scheduled to each participant, and means for collecting and analyzing actual meeting attendance data. This allows users to easily and efficiently adjust meeting times, and also allows for notification of the completion of the schedule scheduling and collection and analysis of attendance data.

[0141] A "meeting target list" refers to a list that identifies the people or groups who are expected to attend a meeting.

[0142] "Items" refers to a detailed description of the agenda or topics to be addressed at the meeting.

[0143] A "calendar system" refers to an electronic system for managing a user's schedule and appointments.

[0144] "Schedule data" refers to time management information such as each person's schedule and free time.

[0145] "Analysis" refers to the data processing activity of processing the acquired schedule data and extracting the free time of each subject.

[0146] "Available time" refers to the time period when the subject is free from other schedules and obligations and available to attend the meeting.

[0147] The "shortest time slot" refers to the earliest time slot that is available to all meeting participants.

[0148] "Meeting Time" means the date and time confirmed for the meeting to take place.

[0149] "Calendar registration" refers to the act of adding the determined meeting time as an event to the target person's calendar system.

[0150] "Notification" refers to an electronic message sent to inform a target person of information such as the completion or change of a meeting setting.

[0151] "Participation data" refers to information such as the number of participants who actually attended a meeting and a record of what was said.

[0152] "Feedback" refers to the act of analyzing and providing information that will help improve the next meeting's setup and progress.

[0153] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[0154] System configuration

[0155] 1. User Interface

[0156] The user uses a terminal to access an interface for entering the list of participants and the contents of the meeting, using a form on a web browser or a dedicated application.

[0157] 2. Server

[0158] It is the central element for receiving input from the user and performing processing.

[0159] Processing flow and specific examples

[0160] 1. Receiving the list of meeting participants and the details of the meeting

[0161] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0162] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0163] The terminal sends the user's input to the server.

[0164] 2. Obtain schedule data for each subject

[0165] Based on the list of users, the server sends an API request to retrieve schedule data from each user's calendar system, using the Google Calendar API or Microsoft Outlook API.

[0166] The calendar system returns schedule data for each subject.

[0167] 3. Identifying participants' available times

[0168] The server analyzes the acquired schedule data and extracts the free time of each target person.

[0169] Example: Count the number of people available for each time slot.

[0170] 4. Calculating optimal meeting times

[0171] The server compares the free time slots of all participants and identifies the shortest common free time slot for all participants.

[0172] Example: Identify next Monday at 3pm when everyone is free.

[0173] Depending on the content of the project, the server will also take into account the layer of required participants and determine whether the meeting can be held with only the minimum number of participants.

[0174] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[0175] 5. Set up a meeting

[0176] The server sends an API request to register the determined meeting time in each person's calendar.

[0177] Example: Create an event in Google Calendar called "Project Status Meeting."

[0178] 6. Sending Notifications

[0179] The server sends emails or push notifications to notify each participant that the conference setup is complete.

[0180] Each user will see the new meeting setup in their calendar and notifications.

[0181] For example: Each target person receives an email confirming the new meeting settings.

[0182] 7. Collecting and analyzing conference attendance data

[0183] After the meeting ends, the server collects and analyzes the actual meeting participation data, using the meeting tool's API to obtain the participants' attendance status and speech records.

[0184] Example: Using data from a conferencing tool, inform users of improvements they can make to their next meeting.

[0185] Example prompts for generative AI models

[0186] Design a system to set the optimal time for multi-person meetings under the following conditions:

[0187] Target audience: All members of the development team

[0188] Project details: Project progress meeting

[0189] Calendar system used: Google Calendar

[0190] Notification method: Email notification

[0191] How to collect meeting participation data: Obtain attendance status and speech records from the meeting tool's API (e.g., Zoom API)

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

[0193] Step 1:

[0194] The user accesses the system interface and enters the list of participants for the meeting and the details of the matter. The user uses a terminal to open a form in a web browser or dedicated application and enters "All members of the development team" and "Project progress meeting." The terminal then sends this information to the server. The inputs are the list of participants and the details of the matter, and the output is the sending of data to the server.

[0195] Step 2:

[0196] The server sends an API request to retrieve schedule data from each person's calendar system based on the target person list. The server sends a request to the Google Calendar API or Microsoft Outlook API to retrieve schedule data for each person. In this step, the target person list is the input, and schedule data is retrieved by sending an API request. The output is the schedule data for each person.

[0197] Step 3:

[0198] The server analyzes the acquired schedule data and extracts the free time of each person. The server uses a Python library to analyze each person's schedule in chronological order. In this step, the acquired schedule data is input and analyzed to list the free time. The output is a free time list for each person.

[0199] Step 4:

[0200] The server compares the free time slots of all participants and identifies the shortest common free time slot. The server then executes logic to compare each person's free time list and identify the best time slot. In this step, the input is each person's free time list, and the common free time is identified through comparison and optimization. The output is the best meeting time.

[0201] Step 5:

[0202] The server considers the layer of required participants and determines whether the meeting can be held with the minimum number of participants. Based on the project content, it reevaluates the time slots that specific members can attend. In this step, the project content and participant list are input, and the layer is determined based on the conditions. The output is the time slots that can be held for the meeting.

[0203] Step 6:

[0204] The server sends an API request to register the determined meeting time in each person's calendar. Using an API such as Google Calendar, the meeting schedule is added to each person's calendar. In this step, the optimal meeting time and the list of people are input, and the schedule is added to the calendar by the API request. The output is the meeting registered in each person's calendar.

[0205] Step 7:

[0206] The server sends email or push notification to each participant to notify them that the conference has been set up. An SMTP server or notification service is used to send a conference setup completion message to each participant. In this step, the input is information about the completion of calendar registration, and the notification service sends notifications to participants. The output is the receipt of notifications.

[0207] Step 8:

[0208] After the meeting ends, the server collects and analyzes the actual meeting participation data. It uses the meeting tool's API to obtain participants' attendance data and speech records. In this step, the meeting end information is input, and the participation data is obtained using the API. The participation data is collected as the output.

[0209] Step 9:

[0210] The server analyzes the participation data to provide information useful for setting up the next meeting and provides feedback to the user. The collected data is analyzed to provide information useful for the next meeting. In this step, the participation data is input and feedback is generated through analysis. The feedback information is provided to the user as the output.

[0211] (Application example 1)

[0212] 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."

[0213] Setting up a multi-person meeting requires time and effort, as it requires coordinating the schedules of each participant and finding the optimal time. Furthermore, there is a need for a faster method for setting up meetings within a company. In particular, there is no existing technology that allows for efficient meeting setup using smart devices, so there is a need for a method to improve the efficiency of meeting setup and quickly notify participants.

[0214] 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.

[0215] In this invention, the server includes a means for receiving a list of participants and the contents of the meeting, a means for acquiring schedule data from each participant's schedule management system based on the list of participants, and a means for analyzing the acquired schedule data and identifying each participant's free time. This enables efficient meeting setup and prompt notification to participants. The server also includes a means for setting up a meeting by voice input or touch operation using smart glasses, and a means for each participant to receive notification using the smart glasses. This allows users to quickly and easily set up and participate in meetings through their smart devices.

[0216] A "meeting target list" is a list of people who should attend a meeting.

[0217] "Item content" refers to the matters or themes to be discussed at the meeting.

[0218] A "schedule management system" is a digital platform for managing each individual's schedule and free time.

[0219] "Schedule data" refers to information about plans and events registered in each subject's calendar.

[0220] "Available time" refers to a time period during which each person can participate in the conference without overlapping with other appointments.

[0221] The "shortest time slot" is the shortest time frame among the periods when all subjects are free.

[0222] "Meeting time" is the specific date and time when the meeting will be held.

[0223] "Notifications" are messages that inform target audiences about meeting setups or changes.

[0224] "Smart glasses" are eyeglass-type electronic devices that can display and input information and are used as wearable devices.

[0225] "Voice input" is a method of entering commands and data into a system using voice.

[0226] "Touch operation" refers to the method of operating a device's display screen or interface by touching it with your fingers.

[0227] MODE FOR CARRYING OUT THE INVENTION

[0228] System Overview

[0229] This invention is a system for quickly and efficiently setting up meetings. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting in each participant's schedule management system, and sends notifications. It also collects and analyzes actual meeting attendance data, which can be used to schedule future meetings.

[0230] Hardware and software used

[0231] Smart Glasses: Use smart glasses to schedule meetings and receive notifications using voice or touch input.

[0232] Server: The central hardware that processes and analyzes data.

[0233] Schedule management system: Software for managing each person's schedule data, such as Google Calendar API or Microsoft Outlook API.

[0234] Data analysis software: Uses programming languages ​​such as Python to analyze schedule data and identify available time.

[0235] Processing flow

[0236] 1. Enter the list of meeting participants and the details of the meeting

[0237] The user uses smart glasses to input the list of meeting participants and the details of the meeting into the terminal using voice input or touch operation.

[0238] 2. Retrieving schedule data

[0239] The terminal requests the server to acquire schedule data based on the input target person list.

[0240] The server obtains the schedule data of each target person through the schedule management system's API.

[0241] 3. Identifying available time slots

[0242] The server analyzes the acquired schedule data and identifies the free time of each subject.

[0243] For each time slot, the number of people who can attend is counted and the optimal meeting time is calculated.

[0244] 4. Set up a meeting

[0245] The server registers the calculated optimal meeting time in the schedule management system for each participant.

[0246] After registration, the server sends a notification to each participant that the conference has been set up.

[0247] 5. Sending notifications

[0248] Each participant uses the smart glasses to check the notification and become aware of the meeting time.

[0249] 6. Collecting and analyzing conference attendance data

[0250] The server collects actual conference attendance data and analyzes it for information useful in setting up the next conference.

[0251] This will make future meeting setup even more efficient.

[0252] Specific examples

[0253] For example, if a user puts on the smart glasses and says, "Schedule a project status meeting for the entire development team," the system retrieves the schedules of all participants, identifies the optimal time when everyone is free, and automatically schedules the meeting. A notification of the meeting schedule is then sent to the smart glasses, allowing for quick and efficient preparation for the meeting.

[0254] Prompt Sentence Examples

[0255] "I'd like to schedule a project status meeting for the entire development team. Please find the best time to meet by checking each person's availability."

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

[0257] Processing flow

[0258] Step 1:

[0259] Enter the meeting target list and the details of the matter

[0260] How it works:

[0261] The user puts on the smart glasses and inputs the list of meeting participants and the details of the meeting into the terminal using voice input or touch operations.

[0262] input:

[0263] List of target persons, project details

[0264] output:

[0265] The terminal receives the input and sends it to the server as data required for subsequent processing.

[0266] Step 2:

[0267] Request to retrieve schedule data

[0268] How it works:

[0269] Based on the received list of subjects, the terminal sends a request to the server to acquire schedule data for each subject.

[0270] input:

[0271] List of eligible individuals

[0272] output:

[0273] A get request is sent to the server.

[0274] Step 3:

[0275] Retrieving schedule data

[0276] How it works:

[0277] The server uses the schedule management system's API to obtain schedule data for each target person.

[0278] input:

[0279] List of eligible individuals

[0280] output:

[0281] Schedule data for each target person

[0282] Step 4:

[0283] Identifying free time

[0284] How it works:

[0285] The server analyzes the acquired schedule data and identifies the available time slots for each person, counting the number of people who can attend for each time slot.

[0286] input:

[0287] Schedule Data

[0288] output:

[0289] Free / busy information for each target person

[0290] Step 5:

[0291] Calculating optimal meeting times

[0292] How it works:

[0293] The server calculates the optimal meeting time when everyone is free.

[0294] input:

[0295] Free / busy information

[0296] output:

[0297] Best time to meet

[0298] Step 6:

[0299] Meeting Setup

[0300] How it works:

[0301] The server sends the calculated optimal meeting time via API to register it in each person's schedule management system, and sets up the meeting.

[0302] input:

[0303] Best time to meet

[0304] output:

[0305] The meeting will be registered in each person's schedule.

[0306] Step 7:

[0307] Sending notifications

[0308] How it works:

[0309] The server generates a notification that the conference has been set up and sends it to each participant via smart glasses or email.

[0310] input:

[0311] Meeting setting information

[0312] output:

[0313] A notification will be sent to each person.

[0314] Step 8:

[0315] Collection and analysis of conference attendance data

[0316] How it works:

[0317] After the conference ends, the server collects actual conference participation data and analyzes it for information useful in setting up the next conference.

[0318] input:

[0319] Meeting participation data

[0320] output:

[0321] Analysis results for setting up your next meeting

[0322] The above processing steps enable quick and efficient conference setup using smart glasses.

[0323] 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.

[0324] ---

[0325] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the agenda, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings. The system also incorporates an emotion engine that recognizes user emotions.

[0326] System configuration

[0327] 1. User Interface

[0328] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[0329] For example, a form in a web browser or a dedicated application.

[0330] 2. Server

[0331] It is the central element for receiving input from the user and performing processing.

[0332] It also has an emotion engine that recognizes and analyzes the user's emotions.

[0333] Processing flow

[0334] 1. Receiving the list of meeting participants and the details of the meeting

[0335] User

[0336] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0337] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0338] Terminal

[0339] The user's input is sent to the server.

[0340] 2. Obtain schedule data for each subject

[0341] server

[0342] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[0343] For example, using the Google Calendar API or Microsoft Outlook API.

[0344] Calendar System

[0345] Each calendar system returns the schedule data of the target person to the server.

[0346] 3. Identifying participants' available times

[0347] server

[0348] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0349] Example: For each time slot, list the availability of each person.

[0350] 4. Calculating optimal meeting times

[0351] server

[0352] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0353] Example: Find next Monday at 3pm when everyone is free.

[0354] server

[0355] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0356] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[0357] 5. Recognition of user emotions using an emotion engine

[0358] Server (emotion engine)

[0359] During the meeting setup process, the system analyzes the user's emotions and determines the urgency and importance of the meeting based on this emotional data.

[0360] Example: If a user is feeling stressed, set the meeting urgency high.

[0361] 6. Set up a meeting

[0362] server

[0363] Send an API request to register the determined meeting time in each person's calendar.

[0364] Example: Create an event in Google Calendar called "Project Status Meeting."

[0365] 7. Sending Notifications

[0366] server

[0367] Send emails and push notifications to notify each participant that the meeting has been set up.

[0368] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[0369] Example: If the user is relaxed, send the notification in a soft tone.

[0370] User

[0371] Each participant will see the new meeting setting in their calendar and notifications.

[0372] Example: Participants see the meeting entry in their calendar.

[0373] 8. Collecting and Analyzing Conference Participation Data

[0374] server

[0375] After the conference ends, the server uses the conference tool's API to collect actual conference participation data.

[0376] Example: Obtaining attendance and speech records.

[0377] server

[0378] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0379] It analyzes emotional data and proposes optimal meeting settings.

[0380] In this way, the system helps users easily and efficiently set up large-scale meetings, reducing wasted time and ensuring optimal meeting management. Furthermore, by using an emotion engine, flexible meeting setup is possible according to the user's emotional state.

[0381] ---

[0382] The processing flow will be explained below.

[0383] ---

[0384] Step 1:

[0385] User

[0386] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0387] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0388] Step 2:

[0389] Terminal

[0390] The user's input is sent to the server.

[0391] Example: An input form is submitted and the user's input is passed to the server.

[0392] Step 3:

[0393] server

[0394] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[0395] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[0396] Step 4:

[0397] Calendar System

[0398] Each calendar system returns the schedule data of the target person to the server.

[0399] Example: Schedule data for each participant is returned in JSON format.

[0400] Step 5:

[0401] server

[0402] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0403] Example: For each time slot, list the availability of each person.

[0404] Step 6:

[0405] server

[0406] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0407] Example: Find the next Monday at 3pm when everyone is free.

[0408] Step 7:

[0409] server

[0410] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0411] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[0412] Step 8:

[0413] Server (emotion engine)

[0414] During the meeting setup process, the device's camera and microphone are used to collect the user's facial expressions and tone of voice, which are then analyzed by the emotion engine.

[0415] Example: If a user is feeling stressed, record their emotional data.

[0416] Step 9:

[0417] server

[0418] The urgency and importance of the meeting are determined based on the user's emotional state recognized by the emotion engine.

[0419] Example: If a user is under high stress, schedule meetings earlier with increased urgency.

[0420] Step 10:

[0421] server

[0422] Send an API request to register the determined meeting time in each person's calendar.

[0423] Example: Create an event called "Project Status Meeting" in Google Calendar.

[0424] Step 11:

[0425] server

[0426] Send emails and push notifications to notify each participant that the meeting has been set up.

[0427] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[0428] Example: If the user is relaxed, send the notification in a soft tone.

[0429] Step 12:

[0430] User

[0431] Each participant will see the new meeting setting in their calendar and notifications.

[0432] Example: Participants see the meeting entry in their calendar.

[0433] Step 13:

[0434] server

[0435] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[0436] Example: Obtaining attendance status and speech records.

[0437] Step 14:

[0438] server

[0439] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0440] Emotional data from the emotion engine is also taken into consideration and reflected in the next meeting settings.

[0441] For example: suggesting frequently required participants and suitable meeting times.

[0442] Step 15:

[0443] server

[0444] Based on the feedback results, the emotion engine is trained to further improve accuracy in future meeting settings.

[0445] Example: The emotion engine uses historical emotion and participation data to derive better settings and notification methods.

[0446] ---

[0447] Example 2

[0448] 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."

[0449] Scheduled meetings with many participants are difficult to do efficiently because it takes time and effort to coordinate the schedules of each participant and select the optimal meeting time. Furthermore, meetings are sometimes scheduled without proper consideration of the urgency or importance of the meeting, which can lead to lower participant satisfaction. Furthermore, after the meeting, feedback that can be used to schedule the next meeting is often unavailable.

[0450] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and the event details, means for acquiring schedule data for each participant, means for analyzing the acquired schedule data and identifying the free time of each participant, means for calculating the shortest time slot available to all participants, means for determining the time when the minimum number of participants can attend based on the event details, means for registering the determined conference time in the calendars of each participant, means for sending a notification of conference setup completion to each participant, means for recognizing user emotions and adjusting the urgency and importance of the conference, and means for collecting and analyzing actual conference participation data. This enables conference setup for a large number of participants to be performed quickly and efficiently, and enables appropriate conference setup and feedback taking user emotions into consideration.

[0451] A "meeting target list" is a list containing names and information about people or groups who will be attending the meeting.

[0452] "Item content" refers to detailed information about the agenda items and proposals to be dealt with at the meeting.

[0453] "Schedule data" is a collection of information including each subject's planned activities and timetable.

[0454] "Free time" is a time period when the subject has no other activities or plans and can participate in a meeting, based on the schedule data.

[0455] The "shortest time slot" refers to the earliest time slot among the time slots in which all subjects have no scheduled appointments.

[0456] "Minimum necessary participants" refers to the minimum number of people or groups essential for a meeting to take place.

[0457] "Registering on the calendar" refers to the operation of reflecting the date, time, and content of the meeting in each person's schedule system.

[0458] "Notification of completion of meeting setup" refers to the transmission of information to inform the relevant person that the date, time, and content of the meeting have been decided and the setup has been completed.

[0459] "Emotion recognition" refers to analyzing and identifying a user's psychological state and emotions from their input data and behavior.

[0460] "Actual meeting participation data" is a collection of information that records attendees, remarks, progress, and so on at a meeting.

[0461] "Analyzing" refers to the process of examining collected data to find useful information and patterns.

[0462] This invention relates to a system for quickly and efficiently setting up meetings with many participants. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also has the ability to collect and analyze meeting attendance data to help schedule future meetings. It also incorporates an emotion engine that recognizes the user's emotions.

[0463] User Interface

[0464] Hardware and Software

[0465] Users access the system using a web browser or dedicated application on a device such as a personal computer or smartphone, and use this interface to input the list of participants and the details of the meeting.

[0466] Specific examples

[0467] The user enters "All members of the development team" and "Project progress meeting" in the form on the web browser and clicks the submit button.

[0468] Server Processing

[0469] Hardware and Software

[0470] The server is the central processing element, receiving input data from users and executing various processes. The server includes functions such as sending API requests to obtain schedule data, data analysis functions, and an emotion engine.

[0471] Obtaining schedule data for each target person

[0472] The server sends an API request to acquire schedule data from the calendar system (such as Google Calendar API or Microsoft Outlook API) of each target person based on the target person list.

[0473] Identifying participant availability

[0474] The server analyzes the acquired schedule data and extracts the free time of each subject for each time slot.

[0475] Calculating optimal meeting times

[0476] The system compares the free time of all participants and finds the shortest common available time slot. It also considers the time when the minimum number of participants can participate, depending on the content of the project.

[0477] Recognizing user emotions with an emotion engine

[0478] The server's emotion engine analyzes the user's emotions during the meeting setup process and adjusts the urgency and importance of the meeting based on the emotion data.

[0479] Meeting scheduling and calendar registration

[0480] The server registers the determined meeting time in each person's calendar by sending an API request to a calendar system such as Google Calendar to create an event.

[0481] Sending notifications

[0482] The server sends emails and push notifications to notify each participant that the meeting has been set up, customizing the content and method of the notifications based on the results of the emotion engine.

[0483] Collection and analysis of conference attendance data

[0484] The server collects actual conference participation data when a conference ends, analyzes the data, and provides feedback to users to help set up the next conference.

[0485] Prompt Sentence Examples

[0486] "I'd like to schedule a new project status meeting. Please find a time that works best for the entire development team."

[0487] "Enter the attendee list and subject matter of your next meeting. Use the emotion engine to set it up while taking into account the user's emotions."

[0488] In this way, the system allows users to efficiently schedule large-scale meetings, reduce wasted time, and achieve optimal meeting management. Furthermore, by utilizing the emotion engine, it is possible to set up meetings more flexibly according to the user's emotional state.

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

[0490] Step 1:

[0491] User input of meeting target list and agenda

[0492] Input: The user uses the terminal to input the list of participants and the contents of the meeting into the interface.

[0493] Specific actions: The user enters "All development team members" and "Project progress meeting" into a form on a web browser and clicks the submit button.

[0494] Output: The entered data is sent from the terminal to the server.

[0495] Step 2:

[0496] Server acquires schedule data for each target person

[0497] Input: The target list is sent to the server.

[0498] Specific operation: The server sends an API request to each target person's calendar system (such as the Google Calendar API).

[0499] Data processing: The server uses the target person's email address and user ID to collect schedule data from each calendar system.

[0500] Output: The schedule data for each subject is returned to the server.

[0501] Step 3:

[0502] The server determines the free time of participants

[0503] Input: Schedule data for each subject is returned to the server.

[0504] Specific operation: The server analyzes the schedule data and lists each target person's free time by time slot.

[0505] Data processing: Exclude busy times from schedule data and identify less busy times.

[0506] Output: A free / busy list for each target is generated.

[0507] Step 4:

[0508] Server calculates and determines optimal meeting time

[0509] Input: A free time list is provided for each subject.

[0510] Specific operation: The server compares the free time of all participants and identifies the shortest time slot in which all participants are available. Depending on the content of the project, it also takes into account the time when the minimum number of participants can participate.

[0511] Data calculation: Runs algorithms to find overlaps in the free time list and calculate the best time, as well as determine the urgency and importance of the request.

[0512] Output: A list of optimal meeting times and time slots with the minimum required number of participants is generated.

[0513] Step 5:

[0514] Recognition of user emotions using an emotion engine on the server

[0515] Input: Input data from the user is provided.

[0516] Specific operation: The server's emotion engine analyzes the user's emotions and identifies emotions such as stress, optimism, and anxiety.

[0517] Data Computing: Detecting sentiment from input text data using natural language processing models.

[0518] Output: Data about the user's emotional state is generated.

[0519] Step 6:

[0520] Server-based meeting setup and calendaring

[0521] Input: You have a list of optimal meeting times and time slots that allow the minimum number of participants you need to meet.

[0522] Specific operation: The server sends an API request to each target person's calendar system and registers the determined meeting time in their calendar.

[0523] Data processing: Information such as the meeting title, time, location, and participant list is registered as an event.

[0524] Output: The meeting will be reflected in each target person's calendar.

[0525] Step 7:

[0526] Sending and customizing notifications via the server

[0527] Input: Information on the completion of the conference setup and the user's emotion data are provided.

[0528] What happens: The server sends emails and push notifications, customizing the content and tone of the notifications based on the results of the emotion engine.

[0529] Data operations: Generate notification wording and format and adjust it based on sentiment data.

[0530] Output: A notification is sent to each participant that the meeting has been set up.

[0531] Step 8:

[0532] Server-based collection and analysis of conference attendance data

[0533] Input: Conference participation data is available after the conference has ended.

[0534] Specific operation: The server uses the conference tool's API to collect actual conference participation data such as the attendee list and speech content.

[0535] Data processing: Analyze the collected data and generate feedback that will help you set up your next meeting.

[0536] Output: Analysis results and feedback information are generated and provided to the user.

[0537] (Application example 2)

[0538] 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."

[0539] Conventional meeting scheduling systems have the problem that it takes time to coordinate the schedules of many participants and it is difficult to quickly determine the optimal meeting time. In addition, the user's emotional state can affect the efficiency and urgency of the meeting, so there is a need for meeting scheduling that appropriately reflects that emotional state. Solving these issues is particularly important when a quick response is required in security operations.

[0540] The specification processing by the specification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and matter details, means for acquiring schedule data from various schedule systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's available time, means for calculating the optimal time when all participants are free, means for registering the determined conference time in each participant's schedule, means for sending a conference setup completion notification to each participant, means for analyzing the emotional states of participants and adjusting the urgency of the conference and the notification content, and means for collecting and analyzing actual conference participation data. This enables conferences with many participants to be set up quickly and efficiently, and also enables flexible conference setup that takes into account the emotional states of participants.

[0541] The "meeting participant list" is a list of all participants attending the meeting.

[0542] "Item content" refers to the specific topics or themes to be discussed at the meeting.

[0543] "Schedule data" refers to data including appointment information obtained from the calendar systems of the participants.

[0544] "Free time" refers to the time period when participants do not have other plans.

[0545] The "optimal time" is the earliest time that can be set among the time slots that are available to all participants.

[0546] A "datebook" is part of a calendar system that records each participant's appointments and schedules.

[0547] "Notifications" are messages or alerts that inform participants about meeting settings or changes.

[0548] "Emotional state" is data obtained by analyzing participants' psychological states and emotions.

[0549] "Meeting Urgency" is a rating that indicates how quickly the meeting should occur.

[0550] "Actual conference attendance data" refers to data about participants who actually attended a conference and the contents of the conference.

[0551] This invention relates to a system for quickly and efficiently setting up multi-person meetings, particularly for emergency response meetings in security operations. This system receives a list of meeting participants and the details of the meeting submitted by the user, analyzes the schedules of all participants, calculates and registers the optimal meeting time, and takes into account the emotional state of the participants using an emotion analysis engine.

[0552] System Configuration

[0553] Hardware

[0554] Smartphone: Used to enter meeting requests and receive notifications.

[0555] Server: The central element responsible for retrieving, parsing, and processing schedule data, and also contains the sentiment analysis engine.

[0556] software

[0557] Calendar system API: Use the Google Calendar API or Microsoft Outlook API to obtain participants' schedule data.

[0558] Emotion analysis engine: Analyzes the user's emotional state and reflects the results in feedback. Examples include Emotion Recognition.

[0559] Generative AI model: Collects and analyzes actual meeting attendance data and provides feedback on next meeting setup through generative AI prompts.

[0560] Overview of program processing

[0561] 1. Enter a meeting request

[0562] The user uses a terminal (e.g., a smartphone) to input the list of participants and the details of the meeting, which then sends the request data to the server.

[0563] 2. Retrieving schedule data

[0564] The server acquires schedule data of each participant based on the meeting participant list through a calendar system API.

[0565] 3. Free Time Analysis

[0566] The server analyzes the acquired schedule data, identifies the available time for each participant, and calculates the optimal time when everyone is free.

[0567] 4. Emotional state analysis

[0568] The server's emotion analysis engine adjusts the urgency of the meeting and the content of the notification based on the user's emotional data obtained during the meeting setup process.

[0569] 5. Meeting Registration and Notification

[0570] The server uses a calendar system API to register the determined meeting time in each participant's calendar. After the meeting is set up, the server sends a notification to each participant.

[0571] 6. Collecting and analyzing actual conference attendance data

[0572] After the meeting, the server collects actual meeting participation data and uses a generative AI model to provide useful feedback for setting up the next meeting.

[0573] Specific examples

[0574] Example prompt sentence:

[0575] User List: [{"name": "Participant 1", "face_image": "path_to_image1.jpg"}, {"name": "Participant 2", "face_image": "path_to_image2.jpg"}]

[0576] Meeting Agenda: "Security Emergency Meeting"

[0577] Expected output:

[0578] "The security emergency meeting has been scheduled. The time everyone is available is next Monday at 3 PM."

[0579] "Participant 1 seems stressed. I've increased the urgency of the meeting."

[0580] This system allows for quick and efficient setting up of large-scale meetings, and allows flexible setting up of meetings taking into account the emotional state of participants. This is particularly useful in security work, where it allows for the rapid setting up of emergency response meetings.

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

[0582] Step 1:

[0583] The user uses a terminal to input the list of participants and the details of the meeting. This sends the request data to the server. The input data includes the participants who should attend the meeting and the meeting agenda. Based on this data, the server proceeds to the next step.

[0584] Step 2:

[0585] The server obtains the schedule data of each participant based on the meeting participant list through a calendar system API (e.g., Google Calendar API or Microsoft Outlook API). It sends a request using the list of each participant to the schedule API and obtains the corresponding schedule data.

[0586] Step 3:

[0587] The server analyzes the schedule data it has acquired. To identify each participant's available time, it extracts time periods that are free of other appointments from the schedule data. This provides a list of available times for each participant.

[0588] Step 4:

[0589] The server compares the free time lists of each participant obtained in the previous step and calculates the optimal time when all participants are free. Specifically, it sorts the free time slots of all participants and identifies the common free time slot. The optimal time is the earliest common free time.

[0590] Step 5:

[0591] The server's emotion analysis engine analyzes the emotional state of participants. It takes as input facial image data and voice data from each participant and estimates their emotional state (e.g., stress level, urgency). This information is used to adjust the urgency of the meeting and the content of notifications.

[0592] Step 6:

[0593] The server registers the determined meeting time in each participant's calendar. Using the calendar system API, a new meeting entry is added to each participant's calendar. The input is the meeting start time, end time, agenda, and participant list, and the output is the meeting entry registered in the calendar.

[0594] Step 7:

[0595] The server sends a notification to each participant that the conference has been set up. Notification methods include email and push notifications. The tone and urgency of the notification are adjusted based on the results of the sentiment analysis engine. The input is the notification content and participant information, and the output is the notification message received by each participant.

[0596] Step 8:

[0597] After the meeting ends, the server collects actual meeting participation data, such as attendance status and speech records, using the meeting tool API. This data is used in subsequent analysis steps.

[0598] Step 9:

[0599] The server analyzes the collected meeting participation data and uses a generative AI model to provide feedback that will be useful for setting up the next meeting. The collected data includes attendee lists, speech volume, and emotional state data, and based on this, it provides suggestions for optimal meeting settings and areas for improvement. The output is a feedback report.

[0600] 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.

[0601] 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.

[0602] 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.

[0603] [Second embodiment]

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

[0605] 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.

[0606] 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).

[0607] 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.

[0608] 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.

[0609] 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).

[0610] 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.

[0611] 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.

[0612] 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.

[0613] 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.

[0614] 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.

[0615] 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."

[0616] ---

[0617] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[0618] System configuration

[0619] 1. User Interface

[0620] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[0621] For example, a form in a web browser or a dedicated application.

[0622] 2. Server

[0623] It is the central element for receiving input from the user and performing processing.

[0624] Processing flow

[0625] 1. Receiving the list of meeting participants and the details of the meeting

[0626] User

[0627] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0628] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0629] Terminal

[0630] The user's input is sent to the server.

[0631] 2. Obtain schedule data for each subject

[0632] server

[0633] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[0634] For example, using the Google Calendar API or Microsoft Outlook API.

[0635] Calendar System

[0636] Each calendar system returns schedule data for the subject.

[0637] 3. Identifying participants' available times

[0638] server

[0639] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0640] Example: Count the number of people available for each time slot.

[0641] 4. Calculating optimal meeting times

[0642] server

[0643] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0644] Example: Find the next Monday at 3pm when everyone is free.

[0645] server

[0646] Depending on the content of the project, we also take into consideration the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0647] Example: Identify a time when at least the team lead is available to participate instead of the entire development team.

[0648] 5. Set up a meeting

[0649] server

[0650] Send an API request to register the determined meeting time in each person's calendar.

[0651] Example: Create an event called "Project Status Meeting" in Google Calendar.

[0652] 6. Sending Notifications

[0653] server

[0654] Send emails and push notifications to notify each participant that the meeting has been set up.

[0655] User

[0656] Each participant will see the new meeting setting in their calendar and notifications.

[0657] 7. Collecting and analyzing conference attendance data

[0658] server

[0659] After the conference ends, the server collects and analyzes actual conference attendance data.

[0660] Example: Use a conference tool's API to obtain participants' attendance status and speech records.

[0661] server

[0662] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0663] In this way, the system helps users easily and efficiently set up large-scale conferences, reducing wasted time and ensuring optimal conference management.

[0664] ---

[0665] The processing flow will be explained below.

[0666] Step 1:

[0667] User

[0668] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0669] Example: User enters "All development team members" and "Project status meeting."

[0670] Step 2:

[0671] Terminal

[0672] The user's input is sent to the server.

[0673] Example: An input form is submitted and the user's input is passed to the server.

[0674] Step 3:

[0675] server

[0676] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[0677] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[0678] Step 4:

[0679] Calendar System

[0680] Each calendar system returns the schedule data of the target person to the server.

[0681] Example: Schedule data for each participant is returned in JSON format.

[0682] Step 5:

[0683] server

[0684] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0685] Example: For each time slot, list the availability of each person.

[0686] Step 6:

[0687] server

[0688] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0689] Example: Find the next Monday at 3pm when everyone is free.

[0690] Step 7:

[0691] server

[0692] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0693] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[0694] Step 8:

[0695] server

[0696] Send an API request to register the determined meeting time in each person's calendar.

[0697] Example: Create an event called "Project Status Meeting" in Google Calendar.

[0698] Step 9:

[0699] server

[0700] Send emails and push notifications to notify each participant that the meeting has been set up.

[0701] Example: Send a notification with meeting details and date and time.

[0702] Step 10:

[0703] User

[0704] Each participant will see the new meeting setting in their calendar and notifications.

[0705] Example: Participants see the meeting entry in their calendar.

[0706] Step 11:

[0707] server

[0708] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[0709] Example: Obtaining attendance status and speech records.

[0710] Step 12:

[0711] server

[0712] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0713] For example: suggesting frequently required participants and suitable meeting times.

[0714] ---

[0715] Example 1

[0716] 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."

[0717] Conventional methods for setting up multi-person meetings have the drawback of being time-consuming and inefficient. In particular, it is difficult to find the optimal meeting time by adjusting the schedules of many participants, and it is difficult to effectively utilize the attendance rate and feedback of participants after the meeting is set up.

[0718] 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.

[0719] In this invention, the server includes means for receiving a list of meeting participants and the details of the meeting, means for acquiring schedule data from the calendar systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's free time, means for calculating the shortest time slot in which all participants are free, means for registering the determined meeting time in each participant's calendar, means for sending a notification that the meeting has been scheduled to each participant, and means for collecting and analyzing actual meeting attendance data. This allows users to easily and efficiently adjust meeting times, and also allows for notification of the completion of the schedule scheduling and collection and analysis of attendance data.

[0720] A "meeting target list" refers to a list that identifies the people or groups who are expected to attend a meeting.

[0721] "Items" refers to a detailed description of the agenda or topics to be addressed at the meeting.

[0722] A "calendar system" refers to an electronic system for managing a user's schedule and appointments.

[0723] "Schedule data" refers to time management information such as each person's schedule and free time.

[0724] "Analysis" refers to the data processing activity of processing the acquired schedule data and extracting the free time of each subject.

[0725] "Available time" refers to the time period when the subject is free from other schedules and obligations and available to attend the meeting.

[0726] The "shortest time slot" refers to the earliest time slot that is available to all meeting participants.

[0727] "Meeting Time" means the date and time confirmed for the meeting to take place.

[0728] "Calendar registration" refers to the act of adding the determined meeting time as an event to the target person's calendar system.

[0729] "Notification" refers to an electronic message sent to inform a target person of information such as the completion or change of a meeting setting.

[0730] "Participation data" refers to information such as the number of participants who actually attended a meeting and a record of what was said.

[0731] "Feedback" refers to the act of analyzing and providing information that will help improve the next meeting's setup and progress.

[0732] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[0733] System configuration

[0734] 1. User Interface

[0735] The user uses a terminal to access an interface for entering the list of participants and the contents of the meeting, using a form on a web browser or a dedicated application.

[0736] 2. Server

[0737] It is the central element for receiving input from the user and performing processing.

[0738] Processing flow and specific examples

[0739] 1. Receiving the list of meeting participants and the details of the meeting

[0740] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0741] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0742] The terminal sends the user's input to the server.

[0743] 2. Obtain schedule data for each subject

[0744] Based on the list of users, the server sends an API request to retrieve schedule data from each user's calendar system, using the Google Calendar API or Microsoft Outlook API.

[0745] The calendar system returns schedule data for each subject.

[0746] 3. Identifying participants' available times

[0747] The server analyzes the acquired schedule data and extracts the free time of each target person.

[0748] Example: Count the number of people available for each time slot.

[0749] 4. Calculating optimal meeting times

[0750] The server compares the free time slots of all participants and identifies the shortest common free time slot for all participants.

[0751] Example: Identify next Monday at 3pm when everyone is free.

[0752] Depending on the content of the project, the server will also take into account the layer of required participants and determine whether the meeting can be held with only the minimum number of participants.

[0753] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[0754] 5. Set up a meeting

[0755] The server sends an API request to register the determined meeting time in each person's calendar.

[0756] Example: Create an event in Google Calendar called "Project Status Meeting."

[0757] 6. Sending Notifications

[0758] The server sends emails or push notifications to notify each participant that the conference setup is complete.

[0759] Each user will see the new meeting setup in their calendar and notifications.

[0760] For example: Each target person receives an email confirming the new meeting settings.

[0761] 7. Collecting and analyzing conference attendance data

[0762] After the meeting ends, the server collects and analyzes the actual meeting participation data, using the meeting tool's API to obtain the participants' attendance status and speech records.

[0763] Example: Using data from a conferencing tool, inform users of improvements they can make to their next meeting.

[0764] Example prompts for generative AI models

[0765] Design a system to set the optimal time for multi-person meetings under the following conditions:

[0766] Target audience: All members of the development team

[0767] Project details: Project progress meeting

[0768] Calendar system used: Google Calendar

[0769] Notification method: Email notification

[0770] How to collect meeting participation data: Obtain attendance status and speech records from the meeting tool's API (e.g., Zoom API)

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

[0772] Step 1:

[0773] The user accesses the system interface and enters the list of participants for the meeting and the details of the matter. The user uses a terminal to open a form in a web browser or dedicated application and enters "All members of the development team" and "Project progress meeting." The terminal then sends this information to the server. The inputs are the list of participants and the details of the matter, and the output is the sending of data to the server.

[0774] Step 2:

[0775] The server sends an API request to retrieve schedule data from each person's calendar system based on the target person list. The server sends a request to the Google Calendar API or Microsoft Outlook API to retrieve schedule data for each person. In this step, the target person list is the input, and schedule data is retrieved by sending an API request. The output is the schedule data for each person.

[0776] Step 3:

[0777] The server analyzes the acquired schedule data and extracts the free time of each person. The server uses a Python library to analyze each person's schedule in chronological order. In this step, the acquired schedule data is input and analyzed to list the free time. The output is a free time list for each person.

[0778] Step 4:

[0779] The server compares the free time slots of all participants and identifies the shortest common free time slot. The server then executes logic to compare each person's free time list and identify the best time slot. In this step, the input is each person's free time list, and the common free time is identified through comparison and optimization. The output is the best meeting time.

[0780] Step 5:

[0781] The server considers the layer of required participants and determines whether the meeting can be held with the minimum number of participants. Based on the project content, it reevaluates the time slots that specific members can attend. In this step, the project content and participant list are input, and the layer is determined based on the conditions. The output is the time slots that can be held for the meeting.

[0782] Step 6:

[0783] The server sends an API request to register the determined meeting time in each person's calendar. Using an API such as Google Calendar, the meeting schedule is added to each person's calendar. In this step, the optimal meeting time and the list of people are input, and the schedule is added to the calendar by the API request. The output is the meeting registered in each person's calendar.

[0784] Step 7:

[0785] The server sends email or push notification to each participant to notify them that the conference has been set up. An SMTP server or notification service is used to send a conference setup completion message to each participant. In this step, the input is information about the completion of calendar registration, and the notification service sends notifications to participants. The output is the receipt of notifications.

[0786] Step 8:

[0787] After the meeting ends, the server collects and analyzes the actual meeting participation data. It uses the meeting tool's API to obtain participants' attendance data and speech records. In this step, the meeting end information is input, and the participation data is obtained using the API. The participation data is collected as the output.

[0788] Step 9:

[0789] The server analyzes the participation data to provide information useful for setting up the next meeting and provides feedback to the user. The collected data is analyzed to provide information useful for the next meeting. In this step, the participation data is input and feedback is generated through analysis. The feedback information is provided to the user as the output.

[0790] (Application example 1)

[0791] 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."

[0792] Setting up a multi-person meeting requires time and effort, as it requires coordinating the schedules of each participant and finding the optimal time. Furthermore, there is a need for a faster method for setting up meetings within a company. In particular, there is no existing technology that allows for efficient meeting setup using smart devices, so there is a need for a method to improve the efficiency of meeting setup and quickly notify participants.

[0793] 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.

[0794] In this invention, the server includes a means for receiving a list of participants and the contents of the meeting, a means for acquiring schedule data from each participant's schedule management system based on the list of participants, and a means for analyzing the acquired schedule data and identifying each participant's free time. This enables efficient meeting setup and prompt notification to participants. The server also includes a means for setting up a meeting by voice input or touch operation using smart glasses, and a means for each participant to receive notification using the smart glasses. This allows users to quickly and easily set up and participate in meetings through their smart devices.

[0795] A "meeting target list" is a list of people who should attend a meeting.

[0796] "Item content" refers to the matters or themes to be discussed at the meeting.

[0797] A "schedule management system" is a digital platform for managing each individual's schedule and free time.

[0798] "Schedule data" refers to information about plans and events registered in each subject's calendar.

[0799] "Available time" refers to a time period during which each person can participate in the conference without overlapping with other appointments.

[0800] The "shortest time slot" is the shortest time frame among the periods when all subjects are free.

[0801] "Meeting time" is the specific date and time when the meeting will be held.

[0802] "Notifications" are messages that inform target audiences about meeting setups or changes.

[0803] "Smart glasses" are eyeglass-type electronic devices that can display and input information and are used as wearable devices.

[0804] "Voice input" is a method of entering commands and data into a system using voice.

[0805] "Touch operation" refers to the method of operating a device's display screen or interface by touching it with your fingers.

[0806] MODE FOR CARRYING OUT THE INVENTION

[0807] System Overview

[0808] This invention is a system for quickly and efficiently setting up meetings. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting in each participant's schedule management system, and sends notifications. It also collects and analyzes actual meeting attendance data, which can be used to schedule future meetings.

[0809] Hardware and software used

[0810] Smart Glasses: Use smart glasses to schedule meetings and receive notifications using voice or touch input.

[0811] Server: The central hardware that processes and analyzes data.

[0812] Schedule management system: Software for managing each person's schedule data, such as Google Calendar API or Microsoft Outlook API.

[0813] Data analysis software: Uses programming languages ​​such as Python to analyze schedule data and identify available time.

[0814] Processing flow

[0815] 1. Enter the list of meeting participants and the details of the meeting

[0816] The user uses smart glasses to input the list of meeting participants and the details of the meeting into the terminal using voice input or touch operation.

[0817] 2. Retrieving schedule data

[0818] The terminal requests the server to acquire schedule data based on the input target person list.

[0819] The server obtains the schedule data of each target person through the schedule management system's API.

[0820] 3. Identifying available time slots

[0821] The server analyzes the acquired schedule data and identifies the free time of each subject.

[0822] For each time slot, the number of people who can attend is counted and the optimal meeting time is calculated.

[0823] 4. Set up a meeting

[0824] The server registers the calculated optimal meeting time in the schedule management system for each participant.

[0825] After registration, the server sends a notification to each participant that the conference has been set up.

[0826] 5. Sending notifications

[0827] Each participant uses the smart glasses to check the notification and become aware of the meeting time.

[0828] 6. Collecting and analyzing conference attendance data

[0829] The server collects actual conference attendance data and analyzes it for information useful in setting up the next conference.

[0830] This will make future meeting setup even more efficient.

[0831] Specific examples

[0832] For example, if a user puts on the smart glasses and says, "Schedule a project status meeting for the entire development team," the system retrieves the schedules of all participants, identifies the optimal time when everyone is free, and automatically schedules the meeting. A notification of the meeting schedule is then sent to the smart glasses, allowing for quick and efficient preparation for the meeting.

[0833] Prompt Sentence Examples

[0834] "I'd like to schedule a project status meeting for the entire development team. Please find the best time to meet by checking each person's availability."

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

[0836] Processing flow

[0837] Step 1:

[0838] Enter the meeting target list and the details of the matter

[0839] How it works:

[0840] The user puts on the smart glasses and inputs the list of meeting participants and the details of the meeting into the terminal using voice input or touch operations.

[0841] input:

[0842] List of target persons, project details

[0843] output:

[0844] The terminal receives the input and sends it to the server as data required for subsequent processing.

[0845] Step 2:

[0846] Request to retrieve schedule data

[0847] How it works:

[0848] Based on the received list of subjects, the terminal sends a request to the server to acquire schedule data for each subject.

[0849] input:

[0850] List of eligible individuals

[0851] output:

[0852] A get request is sent to the server.

[0853] Step 3:

[0854] Retrieving schedule data

[0855] How it works:

[0856] The server uses the schedule management system's API to obtain schedule data for each target person.

[0857] input:

[0858] List of eligible individuals

[0859] output:

[0860] Schedule data for each target person

[0861] Step 4:

[0862] Identifying free time

[0863] How it works:

[0864] The server analyzes the acquired schedule data and identifies the available time slots for each person, counting the number of people who can attend for each time slot.

[0865] input:

[0866] Schedule Data

[0867] output:

[0868] Free / busy information for each target person

[0869] Step 5:

[0870] Calculating optimal meeting times

[0871] How it works:

[0872] The server calculates the optimal meeting time when everyone is free.

[0873] input:

[0874] Free / busy information

[0875] output:

[0876] Best time to meet

[0877] Step 6:

[0878] Meeting Setup

[0879] How it works:

[0880] The server sends the calculated optimal meeting time via API to register it in each person's schedule management system, and sets up the meeting.

[0881] input:

[0882] Best time to meet

[0883] output:

[0884] The meeting will be registered in each person's schedule.

[0885] Step 7:

[0886] Sending notifications

[0887] How it works:

[0888] The server generates a notification that the conference has been set up and sends it to each participant via smart glasses or email.

[0889] input:

[0890] Meeting setting information

[0891] output:

[0892] A notification will be sent to each person.

[0893] Step 8:

[0894] Collection and analysis of conference attendance data

[0895] How it works:

[0896] After the conference ends, the server collects actual conference participation data and analyzes it for information useful in setting up the next conference.

[0897] input:

[0898] Meeting participation data

[0899] output:

[0900] Analysis results for setting up your next meeting

[0901] The above processing steps enable quick and efficient conference setup using smart glasses.

[0902] 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.

[0903] ---

[0904] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the agenda, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings. The system also incorporates an emotion engine that recognizes user emotions.

[0905] System configuration

[0906] 1. User Interface

[0907] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[0908] For example, a form in a web browser or a dedicated application.

[0909] 2. Server

[0910] It is the central element for receiving input from the user and performing processing.

[0911] It also has an emotion engine that recognizes and analyzes the user's emotions.

[0912] Processing flow

[0913] 1. Receiving the list of meeting participants and the details of the meeting

[0914] User

[0915] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0916] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0917] Terminal

[0918] The user's input is sent to the server.

[0919] 2. Obtain schedule data for each subject

[0920] server

[0921] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[0922] For example, using the Google Calendar API or Microsoft Outlook API.

[0923] Calendar System

[0924] Each calendar system returns the schedule data of the target person to the server.

[0925] 3. Identifying participants' available times

[0926] server

[0927] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0928] Example: For each time slot, list the availability of each person.

[0929] 4. Calculating optimal meeting times

[0930] server

[0931] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0932] Example: Find next Monday at 3pm when everyone is free.

[0933] server

[0934] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0935] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[0936] 5. Recognition of user emotions using an emotion engine

[0937] Server (emotion engine)

[0938] During the meeting setup process, the system analyzes the user's emotions and determines the urgency and importance of the meeting based on this emotional data.

[0939] Example: If a user is feeling stressed, set the meeting urgency high.

[0940] 6. Set up a meeting

[0941] server

[0942] Send an API request to register the determined meeting time in each person's calendar.

[0943] Example: Create an event in Google Calendar called "Project Status Meeting."

[0944] 7. Sending Notifications

[0945] server

[0946] Send emails and push notifications to notify each participant that the meeting has been set up.

[0947] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[0948] Example: If the user is relaxed, send the notification in a soft tone.

[0949] User

[0950] Each participant will see the new meeting setting in their calendar and notifications.

[0951] Example: Participants see the meeting entry in their calendar.

[0952] 8. Collecting and Analyzing Conference Participation Data

[0953] server

[0954] After the conference ends, the server uses the conference tool's API to collect actual conference participation data.

[0955] Example: Obtaining attendance and speech records.

[0956] server

[0957] Analyze participation data to help schedule your next meeting and provide feedback to users.

[0958] It analyzes emotional data and proposes optimal meeting settings.

[0959] In this way, the system helps users easily and efficiently set up large-scale meetings, reducing wasted time and ensuring optimal meeting management. Furthermore, by using an emotion engine, flexible meeting setup is possible according to the user's emotional state.

[0960] ---

[0961] The processing flow will be explained below.

[0962] ---

[0963] Step 1:

[0964] User

[0965] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[0966] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[0967] Step 2:

[0968] Terminal

[0969] The user's input is sent to the server.

[0970] Example: An input form is submitted and the user's input is passed to the server.

[0971] Step 3:

[0972] server

[0973] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[0974] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[0975] Step 4:

[0976] Calendar System

[0977] Each calendar system returns the schedule data of the target person to the server.

[0978] Example: Schedule data for each participant is returned in JSON format.

[0979] Step 5:

[0980] server

[0981] The acquired schedule data is analyzed and the free time of each subject is extracted.

[0982] Example: For each time slot, list the availability of each person.

[0983] Step 6:

[0984] server

[0985] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[0986] Example: Find the next Monday at 3pm when everyone is free.

[0987] Step 7:

[0988] server

[0989] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[0990] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[0991] Step 8:

[0992] Server (emotion engine)

[0993] During the meeting setup process, the device's camera and microphone are used to collect the user's facial expressions and tone of voice, which are then analyzed by the emotion engine.

[0994] Example: If a user is feeling stressed, record their emotional data.

[0995] Step 9:

[0996] server

[0997] The urgency and importance of the meeting are determined based on the user's emotional state recognized by the emotion engine.

[0998] Example: If a user is under high stress, schedule meetings earlier with increased urgency.

[0999] Step 10:

[1000] server

[1001] Send an API request to register the determined meeting time in each person's calendar.

[1002] Example: Create an event called "Project Status Meeting" in Google Calendar.

[1003] Step 11:

[1004] server

[1005] Send emails and push notifications to notify each participant that the meeting has been set up.

[1006] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[1007] Example: If the user is relaxed, send the notification in a soft tone.

[1008] Step 12:

[1009] User

[1010] Each participant will see the new meeting setting in their calendar and notifications.

[1011] Example: Participants see the meeting entry in their calendar.

[1012] Step 13:

[1013] server

[1014] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[1015] Example: Obtaining attendance status and speech records.

[1016] Step 14:

[1017] server

[1018] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1019] Emotional data from the emotion engine is also taken into consideration and reflected in the next meeting settings.

[1020] For example: suggesting frequently required participants and suitable meeting times.

[1021] Step 15:

[1022] server

[1023] Based on the feedback results, the emotion engine is trained to further improve accuracy in future meeting settings.

[1024] Example: The emotion engine uses historical emotion and participation data to derive better settings and notification methods.

[1025] ---

[1026] Example 2

[1027] 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."

[1028] Scheduled meetings with many participants are difficult to do efficiently because it takes time and effort to coordinate the schedules of each participant and select the optimal meeting time. Furthermore, meetings are sometimes scheduled without proper consideration of the urgency or importance of the meeting, which can lead to lower participant satisfaction. Furthermore, after the meeting, feedback that can be used to schedule the next meeting is often unavailable.

[1029] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and the event details, means for acquiring schedule data for each participant, means for analyzing the acquired schedule data and identifying the free time of each participant, means for calculating the shortest time slot available to all participants, means for determining the time when the minimum number of participants can attend based on the event details, means for registering the determined conference time in the calendars of each participant, means for sending a notification of conference setup completion to each participant, means for recognizing user emotions and adjusting the urgency and importance of the conference, and means for collecting and analyzing actual conference participation data. This enables conference setup for a large number of participants to be performed quickly and efficiently, and enables appropriate conference setup and feedback taking user emotions into consideration.

[1030] A "meeting target list" is a list containing names and information about people or groups who will be attending the meeting.

[1031] "Item content" refers to detailed information about the agenda items and proposals to be dealt with at the meeting.

[1032] "Schedule data" is a collection of information including each subject's planned activities and timetable.

[1033] "Free time" is a time period when the subject has no other activities or plans and can participate in a meeting, based on the schedule data.

[1034] The "shortest time slot" refers to the earliest time slot among the time slots in which all subjects have no scheduled appointments.

[1035] "Minimum necessary participants" refers to the minimum number of people or groups essential for a meeting to take place.

[1036] "Registering on the calendar" refers to the operation of reflecting the date, time, and content of the meeting in each person's schedule system.

[1037] "Notification of completion of meeting setup" refers to the transmission of information to inform the relevant person that the date, time, and content of the meeting have been decided and the setup has been completed.

[1038] "Emotion recognition" refers to analyzing and identifying a user's psychological state and emotions from their input data and behavior.

[1039] "Actual meeting participation data" is a collection of information that records attendees, remarks, progress, and so on at a meeting.

[1040] "Analyzing" refers to the process of examining collected data to find useful information and patterns.

[1041] This invention relates to a system for quickly and efficiently setting up meetings with many participants. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also has the ability to collect and analyze meeting attendance data to help schedule future meetings. It also incorporates an emotion engine that recognizes the user's emotions.

[1042] User Interface

[1043] Hardware and Software

[1044] Users access the system using a web browser or dedicated application on a device such as a personal computer or smartphone, and use this interface to input the list of participants and the details of the meeting.

[1045] Specific examples

[1046] The user enters "All members of the development team" and "Project progress meeting" in the form on the web browser and clicks the submit button.

[1047] Server Processing

[1048] Hardware and Software

[1049] The server is the central processing element, receiving input data from users and executing various processes. The server includes functions such as sending API requests to obtain schedule data, data analysis functions, and an emotion engine.

[1050] Obtaining schedule data for each target person

[1051] The server sends an API request to acquire schedule data from the calendar system (such as Google Calendar API or Microsoft Outlook API) of each target person based on the target person list.

[1052] Identifying participant availability

[1053] The server analyzes the acquired schedule data and extracts the free time of each subject for each time slot.

[1054] Calculating optimal meeting times

[1055] The system compares the free time of all participants and finds the shortest common available time slot. It also considers the time when the minimum number of participants can participate, depending on the content of the project.

[1056] Recognizing user emotions with an emotion engine

[1057] The server's emotion engine analyzes the user's emotions during the meeting setup process and adjusts the urgency and importance of the meeting based on the emotion data.

[1058] Meeting scheduling and calendar registration

[1059] The server registers the determined meeting time in each person's calendar by sending an API request to a calendar system such as Google Calendar to create an event.

[1060] Sending notifications

[1061] The server sends emails and push notifications to notify each participant that the meeting has been set up, customizing the content and method of the notifications based on the results of the emotion engine.

[1062] Collection and analysis of conference attendance data

[1063] The server collects actual conference participation data when a conference ends, analyzes the data, and provides feedback to users to help set up the next conference.

[1064] Prompt Sentence Examples

[1065] "I'd like to schedule a new project status meeting. Please find a time that works best for the entire development team."

[1066] "Enter the attendee list and subject matter of your next meeting. Use the emotion engine to set it up while taking into account the user's emotions."

[1067] In this way, the system allows users to efficiently schedule large-scale meetings, reduce wasted time, and achieve optimal meeting management. Furthermore, by utilizing the emotion engine, it is possible to set up meetings more flexibly according to the user's emotional state.

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

[1069] Step 1:

[1070] User input of meeting target list and agenda

[1071] Input: The user uses the terminal to input the list of participants and the contents of the meeting into the interface.

[1072] Specific actions: The user enters "All development team members" and "Project progress meeting" into a form on a web browser and clicks the submit button.

[1073] Output: The entered data is sent from the terminal to the server.

[1074] Step 2:

[1075] Server acquires schedule data for each target person

[1076] Input: The target list is sent to the server.

[1077] Specific operation: The server sends an API request to each target person's calendar system (such as the Google Calendar API).

[1078] Data processing: The server uses the target person's email address and user ID to collect schedule data from each calendar system.

[1079] Output: The schedule data for each subject is returned to the server.

[1080] Step 3:

[1081] The server determines the free time of participants

[1082] Input: Schedule data for each subject is returned to the server.

[1083] Specific operation: The server analyzes the schedule data and lists each target person's free time by time slot.

[1084] Data processing: Exclude busy times from schedule data and identify less busy times.

[1085] Output: A free / busy list for each target is generated.

[1086] Step 4:

[1087] Server calculates and determines optimal meeting time

[1088] Input: A free time list is provided for each subject.

[1089] Specific operation: The server compares the free time of all participants and identifies the shortest time slot in which all participants are available. Depending on the content of the project, it also takes into account the time when the minimum number of participants can participate.

[1090] Data calculation: Runs algorithms to find overlaps in the free time list and calculate the best time, as well as determine the urgency and importance of the request.

[1091] Output: A list of optimal meeting times and time slots with the minimum required number of participants is generated.

[1092] Step 5:

[1093] Recognition of user emotions using an emotion engine on the server

[1094] Input: Input data from the user is provided.

[1095] Specific operation: The server's emotion engine analyzes the user's emotions and identifies emotions such as stress, optimism, and anxiety.

[1096] Data Computing: Detecting sentiment from input text data using natural language processing models.

[1097] Output: Data about the user's emotional state is generated.

[1098] Step 6:

[1099] Server-based meeting setup and calendaring

[1100] Input: You have a list of optimal meeting times and time slots that allow the minimum number of participants you need to meet.

[1101] Specific operation: The server sends an API request to each target person's calendar system and registers the determined meeting time in their calendar.

[1102] Data processing: Information such as the meeting title, time, location, and participant list is registered as an event.

[1103] Output: The meeting will be reflected in each target person's calendar.

[1104] Step 7:

[1105] Sending and customizing notifications via the server

[1106] Input: Information on the completion of the conference setup and the user's emotion data are provided.

[1107] What happens: The server sends emails and push notifications, customizing the content and tone of the notifications based on the results of the emotion engine.

[1108] Data operations: Generate notification wording and format and adjust it based on sentiment data.

[1109] Output: A notification is sent to each participant that the meeting has been set up.

[1110] Step 8:

[1111] Server-based collection and analysis of conference attendance data

[1112] Input: Conference participation data is available after the conference has ended.

[1113] Specific operation: The server uses the conference tool's API to collect actual conference participation data such as the attendee list and speech content.

[1114] Data processing: Analyze the collected data and generate feedback that will help you set up your next meeting.

[1115] Output: Analysis results and feedback information are generated and provided to the user.

[1116] (Application example 2)

[1117] 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."

[1118] Conventional meeting scheduling systems have the problem that it takes time to coordinate the schedules of many participants and it is difficult to quickly determine the optimal meeting time. In addition, the user's emotional state can affect the efficiency and urgency of the meeting, so there is a need for meeting scheduling that appropriately reflects that emotional state. Solving these issues is particularly important when a quick response is required in security operations.

[1119] The specification processing by the specification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and matter details, means for acquiring schedule data from various schedule systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's available time, means for calculating the optimal time when all participants are free, means for registering the determined conference time in each participant's schedule, means for sending a conference setup completion notification to each participant, means for analyzing the emotional states of participants and adjusting the urgency of the conference and the notification content, and means for collecting and analyzing actual conference participation data. This enables conferences with many participants to be set up quickly and efficiently, and also enables flexible conference setup that takes into account the emotional states of participants.

[1120] The "meeting participant list" is a list of all participants attending the meeting.

[1121] "Item content" refers to the specific topics or themes to be discussed at the meeting.

[1122] "Schedule data" refers to data including appointment information obtained from the calendar systems of the participants.

[1123] "Free time" refers to the time period when participants do not have other plans.

[1124] The "optimal time" is the earliest time that can be set among the time slots that are available to all participants.

[1125] A "datebook" is part of a calendar system that records each participant's appointments and schedules.

[1126] "Notifications" are messages or alerts that inform participants about meeting settings or changes.

[1127] "Emotional state" is data obtained by analyzing participants' psychological states and emotions.

[1128] "Meeting Urgency" is a rating that indicates how quickly the meeting should occur.

[1129] "Actual conference attendance data" refers to data about participants who actually attended a conference and the contents of the conference.

[1130] This invention relates to a system for quickly and efficiently setting up multi-person meetings, particularly for emergency response meetings in security operations. This system receives a list of meeting participants and the details of the meeting submitted by the user, analyzes the schedules of all participants, calculates and registers the optimal meeting time, and takes into account the emotional state of the participants using an emotion analysis engine.

[1131] System Configuration

[1132] Hardware

[1133] Smartphone: Used to enter meeting requests and receive notifications.

[1134] Server: The central element responsible for retrieving, parsing, and processing schedule data, and also contains the sentiment analysis engine.

[1135] software

[1136] Calendar system API: Use the Google Calendar API or Microsoft Outlook API to obtain participants' schedule data.

[1137] Emotion analysis engine: Analyzes the user's emotional state and reflects the results in feedback. Examples include Emotion Recognition.

[1138] Generative AI model: Collects and analyzes actual meeting attendance data and provides feedback on next meeting setup through generative AI prompts.

[1139] Overview of program processing

[1140] 1. Enter a meeting request

[1141] The user uses a terminal (e.g., a smartphone) to input the list of participants and the details of the meeting, which then sends the request data to the server.

[1142] 2. Retrieving schedule data

[1143] The server acquires schedule data of each participant based on the meeting participant list through a calendar system API.

[1144] 3. Free Time Analysis

[1145] The server analyzes the acquired schedule data, identifies the available time for each participant, and calculates the optimal time when everyone is free.

[1146] 4. Emotional state analysis

[1147] The server's emotion analysis engine adjusts the urgency of the meeting and the content of the notification based on the user's emotional data obtained during the meeting setup process.

[1148] 5. Meeting Registration and Notification

[1149] The server uses a calendar system API to register the determined meeting time in each participant's calendar. After the meeting is set up, the server sends a notification to each participant.

[1150] 6. Collecting and analyzing actual conference attendance data

[1151] After the meeting, the server collects actual meeting participation data and uses a generative AI model to provide useful feedback for setting up the next meeting.

[1152] Specific examples

[1153] Example prompt sentence:

[1154] User List: [{"name": "Participant 1", "face_image": "path_to_image1.jpg"}, {"name": "Participant 2", "face_image": "path_to_image2.jpg"}]

[1155] Meeting Agenda: "Security Emergency Meeting"

[1156] Expected output:

[1157] "The security emergency meeting has been scheduled. The time everyone is available is next Monday at 3 PM."

[1158] "Participant 1 seems stressed. I've increased the urgency of the meeting."

[1159] This system allows for quick and efficient setting up of large-scale meetings, and allows flexible setting up of meetings taking into account the emotional state of participants. This is particularly useful in security work, where it allows for the rapid setting up of emergency response meetings.

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

[1161] Step 1:

[1162] The user uses a terminal to input the list of participants and the details of the meeting. This sends the request data to the server. The input data includes the participants who should attend the meeting and the meeting agenda. Based on this data, the server proceeds to the next step.

[1163] Step 2:

[1164] The server obtains the schedule data of each participant based on the meeting participant list through a calendar system API (e.g., Google Calendar API or Microsoft Outlook API). It sends a request using the list of each participant to the schedule API and obtains the corresponding schedule data.

[1165] Step 3:

[1166] The server analyzes the schedule data it has acquired. To identify each participant's available time, it extracts time periods that are free of other appointments from the schedule data. This provides a list of available times for each participant.

[1167] Step 4:

[1168] The server compares the free time lists of each participant obtained in the previous step and calculates the optimal time when all participants are free. Specifically, it sorts the free time slots of all participants and identifies the common free time slot. The optimal time is the earliest common free time.

[1169] Step 5:

[1170] The server's emotion analysis engine analyzes the emotional state of participants. It takes as input facial image data and voice data from each participant and estimates their emotional state (e.g., stress level, urgency). This information is used to adjust the urgency of the meeting and the content of notifications.

[1171] Step 6:

[1172] The server registers the determined meeting time in each participant's calendar. Using the calendar system API, a new meeting entry is added to each participant's calendar. The input is the meeting start time, end time, agenda, and participant list, and the output is the meeting entry registered in the calendar.

[1173] Step 7:

[1174] The server sends a notification to each participant that the conference has been set up. Notification methods include email and push notifications. The tone and urgency of the notification are adjusted based on the results of the sentiment analysis engine. The input is the notification content and participant information, and the output is the notification message received by each participant.

[1175] Step 8:

[1176] After the meeting ends, the server collects actual meeting participation data, such as attendance status and speech records, using the meeting tool API. This data is used in subsequent analysis steps.

[1177] Step 9:

[1178] The server analyzes the collected meeting participation data and uses a generative AI model to provide feedback that will be useful for setting up the next meeting. The collected data includes attendee lists, speech volume, and emotional state data, and based on this, it provides suggestions for optimal meeting settings and areas for improvement. The output is a feedback report.

[1179] 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.

[1180] 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.

[1181] 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.

[1182] [Third embodiment]

[1183] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.

[1184] 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.

[1185] 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).

[1186] 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.

[1187] 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.

[1188] 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).

[1189] 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.

[1190] 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.

[1191] 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.

[1192] 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.

[1193] 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.

[1194] 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."

[1195] ---

[1196] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[1197] System configuration

[1198] 1. User Interface

[1199] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[1200] For example, a form in a web browser or a dedicated application.

[1201] 2. Server

[1202] It is the central element for receiving input from the user and performing processing.

[1203] Processing flow

[1204] 1. Receiving the list of meeting participants and the details of the meeting

[1205] User

[1206] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1207] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[1208] Terminal

[1209] The user's input is sent to the server.

[1210] 2. Obtain schedule data for each subject

[1211] server

[1212] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[1213] For example, using the Google Calendar API or Microsoft Outlook API.

[1214] Calendar System

[1215] Each calendar system returns schedule data for the subject.

[1216] 3. Identifying participants' available times

[1217] server

[1218] The acquired schedule data is analyzed and the free time of each subject is extracted.

[1219] Example: Count the number of people available for each time slot.

[1220] 4. Calculating optimal meeting times

[1221] server

[1222] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[1223] Example: Find the next Monday at 3pm when everyone is free.

[1224] server

[1225] Depending on the content of the project, we also take into consideration the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[1226] Example: Identify a time when at least the team lead is available to participate instead of the entire development team.

[1227] 5. Set up a meeting

[1228] server

[1229] Send an API request to register the determined meeting time in each person's calendar.

[1230] Example: Create an event called "Project Status Meeting" in Google Calendar.

[1231] 6. Sending Notifications

[1232] server

[1233] Send emails and push notifications to notify each participant that the meeting has been set up.

[1234] User

[1235] Each participant will see the new meeting setting in their calendar and notifications.

[1236] 7. Collecting and analyzing conference attendance data

[1237] server

[1238] After the conference ends, the server collects and analyzes actual conference attendance data.

[1239] Example: Use a conference tool's API to obtain participants' attendance status and speech records.

[1240] server

[1241] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1242] In this way, the system helps users easily and efficiently set up large-scale conferences, reducing wasted time and ensuring optimal conference management.

[1243] ---

[1244] The processing flow will be explained below.

[1245] Step 1:

[1246] User

[1247] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1248] Example: User enters "All development team members" and "Project status meeting."

[1249] Step 2:

[1250] Terminal

[1251] The user's input is sent to the server.

[1252] Example: An input form is submitted and the user's input is passed to the server.

[1253] Step 3:

[1254] server

[1255] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[1256] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[1257] Step 4:

[1258] Calendar System

[1259] Each calendar system returns the schedule data of the target person to the server.

[1260] Example: Schedule data for each participant is returned in JSON format.

[1261] Step 5:

[1262] server

[1263] The acquired schedule data is analyzed and the free time of each subject is extracted.

[1264] Example: For each time slot, list the availability of each person.

[1265] Step 6:

[1266] server

[1267] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[1268] Example: Find the next Monday at 3pm when everyone is free.

[1269] Step 7:

[1270] server

[1271] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[1272] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[1273] Step 8:

[1274] server

[1275] Send an API request to register the determined meeting time in each person's calendar.

[1276] Example: Create an event called "Project Status Meeting" in Google Calendar.

[1277] Step 9:

[1278] server

[1279] Send emails and push notifications to notify each participant that the meeting has been set up.

[1280] Example: Send a notification with meeting details and date and time.

[1281] Step 10:

[1282] User

[1283] Each participant will see the new meeting setting in their calendar and notifications.

[1284] Example: Participants see the meeting entry in their calendar.

[1285] Step 11:

[1286] server

[1287] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[1288] Example: Obtaining attendance status and speech records.

[1289] Step 12:

[1290] server

[1291] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1292] For example: suggesting frequently required participants and suitable meeting times.

[1293] ---

[1294] Example 1

[1295] 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."

[1296] Conventional methods for setting up multi-person meetings have the drawback of being time-consuming and inefficient. In particular, it is difficult to find the optimal meeting time by adjusting the schedules of many participants, and it is difficult to effectively utilize the attendance rate and feedback of participants after the meeting is set up.

[1297] 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.

[1298] In this invention, the server includes means for receiving a list of meeting participants and the details of the meeting, means for acquiring schedule data from the calendar systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's free time, means for calculating the shortest time slot in which all participants are free, means for registering the determined meeting time in each participant's calendar, means for sending a notification that the meeting has been scheduled to each participant, and means for collecting and analyzing actual meeting attendance data. This allows users to easily and efficiently adjust meeting times, and also allows for notification of the completion of the schedule scheduling and collection and analysis of attendance data.

[1299] A "meeting target list" refers to a list that identifies the people or groups who are expected to attend a meeting.

[1300] "Items" refers to a detailed description of the agenda or topics to be addressed at the meeting.

[1301] A "calendar system" refers to an electronic system for managing a user's schedule and appointments.

[1302] "Schedule data" refers to time management information such as each person's schedule and free time.

[1303] "Analysis" refers to the data processing activity of processing the acquired schedule data and extracting the free time of each subject.

[1304] "Available time" refers to the time period when the subject is free from other schedules and obligations and available to attend the meeting.

[1305] The "shortest time slot" refers to the earliest time slot that is available to all meeting participants.

[1306] "Meeting Time" means the date and time confirmed for the meeting to take place.

[1307] "Calendar registration" refers to the act of adding the determined meeting time as an event to the target person's calendar system.

[1308] "Notification" refers to an electronic message sent to inform a target person of information such as the completion or change of a meeting setting.

[1309] "Participation data" refers to information such as the number of participants who actually attended a meeting and a record of what was said.

[1310] "Feedback" refers to the act of analyzing and providing information that will help improve the next meeting's setup and progress.

[1311] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[1312] System configuration

[1313] 1. User Interface

[1314] The user uses a terminal to access an interface for entering the list of participants and the contents of the meeting, using a form on a web browser or a dedicated application.

[1315] 2. Server

[1316] It is the central element for receiving input from the user and performing processing.

[1317] Processing flow and specific examples

[1318] 1. Receiving the list of meeting participants and the details of the meeting

[1319] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1320] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[1321] The terminal sends the user's input to the server.

[1322] 2. Obtain schedule data for each subject

[1323] Based on the list of users, the server sends an API request to retrieve schedule data from each user's calendar system, using the Google Calendar API or Microsoft Outlook API.

[1324] The calendar system returns schedule data for each subject.

[1325] 3. Identifying participants' available times

[1326] The server analyzes the acquired schedule data and extracts the free time of each target person.

[1327] Example: Count the number of people available for each time slot.

[1328] 4. Calculating optimal meeting times

[1329] The server compares the free time slots of all participants and identifies the shortest common free time slot for all participants.

[1330] Example: Identify next Monday at 3pm when everyone is free.

[1331] Depending on the content of the project, the server will also take into account the layer of required participants and determine whether the meeting can be held with only the minimum number of participants.

[1332] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[1333] 5. Set up a meeting

[1334] The server sends an API request to register the determined meeting time in each person's calendar.

[1335] Example: Create an event in Google Calendar called "Project Status Meeting."

[1336] 6. Sending Notifications

[1337] The server sends emails or push notifications to notify each participant that the conference setup is complete.

[1338] Each user will see the new meeting setup in their calendar and notifications.

[1339] For example: Each target person receives an email confirming the new meeting settings.

[1340] 7. Collecting and analyzing conference attendance data

[1341] After the meeting ends, the server collects and analyzes the actual meeting participation data, using the meeting tool's API to obtain the participants' attendance status and speech records.

[1342] Example: Using data from a conferencing tool, inform users of improvements they can make to their next meeting.

[1343] Example prompts for generative AI models

[1344] Design a system to set the optimal time for multi-person meetings under the following conditions:

[1345] Target audience: All members of the development team

[1346] Project details: Project progress meeting

[1347] Calendar system used: Google Calendar

[1348] Notification method: Email notification

[1349] How to collect meeting participation data: Obtain attendance status and speech records from the meeting tool's API (e.g., Zoom API)

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

[1351] Step 1:

[1352] The user accesses the system interface and enters the list of participants for the meeting and the details of the matter. The user uses a terminal to open a form in a web browser or dedicated application and enters "All members of the development team" and "Project progress meeting." The terminal then sends this information to the server. The inputs are the list of participants and the details of the matter, and the output is the sending of data to the server.

[1353] Step 2:

[1354] The server sends an API request to retrieve schedule data from each person's calendar system based on the target person list. The server sends a request to the Google Calendar API or Microsoft Outlook API to retrieve schedule data for each person. In this step, the target person list is the input, and schedule data is retrieved by sending an API request. The output is the schedule data for each person.

[1355] Step 3:

[1356] The server analyzes the acquired schedule data and extracts the free time of each person. The server uses a Python library to analyze each person's schedule in chronological order. In this step, the acquired schedule data is input and analyzed to list the free time. The output is a free time list for each person.

[1357] Step 4:

[1358] The server compares the free time slots of all participants and identifies the shortest common free time slot. The server then executes logic to compare each person's free time list and identify the best time slot. In this step, the input is each person's free time list, and the common free time is identified through comparison and optimization. The output is the best meeting time.

[1359] Step 5:

[1360] The server considers the layer of required participants and determines whether the meeting can be held with the minimum number of participants. Based on the project content, it reevaluates the time slots that specific members can attend. In this step, the project content and participant list are input, and the layer is determined based on the conditions. The output is the time slots that can be held for the meeting.

[1361] Step 6:

[1362] The server sends an API request to register the determined meeting time in each person's calendar. Using an API such as Google Calendar, the meeting schedule is added to each person's calendar. In this step, the optimal meeting time and the list of people are input, and the schedule is added to the calendar by the API request. The output is the meeting registered in each person's calendar.

[1363] Step 7:

[1364] The server sends email or push notification to each participant to notify them that the conference has been set up. An SMTP server or notification service is used to send a conference setup completion message to each participant. In this step, the input is information about the completion of calendar registration, and the notification service sends notifications to participants. The output is the receipt of notifications.

[1365] Step 8:

[1366] After the meeting ends, the server collects and analyzes the actual meeting participation data. It uses the meeting tool's API to obtain participants' attendance data and speech records. In this step, the meeting end information is input, and the participation data is obtained using the API. The participation data is collected as the output.

[1367] Step 9:

[1368] The server analyzes the participation data to provide information useful for setting up the next meeting and provides feedback to the user. The collected data is analyzed to provide information useful for the next meeting. In this step, the participation data is input and feedback is generated through analysis. The feedback information is provided to the user as the output.

[1369] (Application example 1)

[1370] 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."

[1371] Setting up a multi-person meeting requires time and effort, as it requires coordinating the schedules of each participant and finding the optimal time. Furthermore, there is a need for a faster method for setting up meetings within a company. In particular, there is no existing technology that allows for efficient meeting setup using smart devices, so there is a need for a method to improve the efficiency of meeting setup and quickly notify participants.

[1372] 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.

[1373] In this invention, the server includes a means for receiving a list of participants and the contents of the meeting, a means for acquiring schedule data from each participant's schedule management system based on the list of participants, and a means for analyzing the acquired schedule data and identifying each participant's free time. This enables efficient meeting setup and prompt notification to participants. The server also includes a means for setting up a meeting by voice input or touch operation using smart glasses, and a means for each participant to receive notification using the smart glasses. This allows users to quickly and easily set up and participate in meetings through their smart devices.

[1374] A "meeting target list" is a list of people who should attend a meeting.

[1375] "Item content" refers to the matters or themes to be discussed at the meeting.

[1376] A "schedule management system" is a digital platform for managing each individual's schedule and free time.

[1377] "Schedule data" refers to information about plans and events registered in each subject's calendar.

[1378] "Available time" refers to a time period during which each person can participate in the conference without overlapping with other appointments.

[1379] The "shortest time slot" is the shortest time frame among the periods when all subjects are free.

[1380] "Meeting time" is the specific date and time when the meeting will be held.

[1381] "Notifications" are messages that inform target audiences about meeting setups or changes.

[1382] "Smart glasses" are eyeglass-type electronic devices that can display and input information and are used as wearable devices.

[1383] "Voice input" is a method of entering commands and data into a system using voice.

[1384] "Touch operation" refers to the method of operating a device's display screen or interface by touching it with your fingers.

[1385] MODE FOR CARRYING OUT THE INVENTION

[1386] System Overview

[1387] This invention is a system for quickly and efficiently setting up meetings. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting in each participant's schedule management system, and sends notifications. It also collects and analyzes actual meeting attendance data, which can be used to schedule future meetings.

[1388] Hardware and software used

[1389] Smart Glasses: Use smart glasses to schedule meetings and receive notifications using voice or touch input.

[1390] Server: The central hardware that processes and analyzes data.

[1391] Schedule management system: Software for managing each person's schedule data, such as Google Calendar API or Microsoft Outlook API.

[1392] Data analysis software: Uses programming languages ​​such as Python to analyze schedule data and identify available time.

[1393] Processing flow

[1394] 1. Enter the list of meeting participants and the details of the meeting

[1395] The user uses smart glasses to input the list of meeting participants and the details of the meeting into the terminal using voice input or touch operation.

[1396] 2. Retrieving schedule data

[1397] The terminal requests the server to acquire schedule data based on the input target person list.

[1398] The server obtains the schedule data of each target person through the schedule management system's API.

[1399] 3. Identifying available time slots

[1400] The server analyzes the acquired schedule data and identifies the free time of each subject.

[1401] For each time slot, the number of people who can attend is counted and the optimal meeting time is calculated.

[1402] 4. Set up a meeting

[1403] The server registers the calculated optimal meeting time in the schedule management system for each participant.

[1404] After registration, the server sends a notification to each participant that the conference has been set up.

[1405] 5. Sending notifications

[1406] Each participant uses the smart glasses to check the notification and become aware of the meeting time.

[1407] 6. Collecting and analyzing conference attendance data

[1408] The server collects actual conference attendance data and analyzes it for information useful in setting up the next conference.

[1409] This will make future meeting setup even more efficient.

[1410] Specific examples

[1411] For example, if a user puts on the smart glasses and says, "Schedule a project status meeting for the entire development team," the system retrieves the schedules of all participants, identifies the optimal time when everyone is free, and automatically schedules the meeting. A notification of the meeting schedule is then sent to the smart glasses, allowing for quick and efficient preparation for the meeting.

[1412] Prompt Sentence Examples

[1413] "I'd like to schedule a project status meeting for the entire development team. Please find the best time to meet by checking each person's availability."

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

[1415] Processing flow

[1416] Step 1:

[1417] Enter the meeting target list and the details of the matter

[1418] How it works:

[1419] The user puts on the smart glasses and inputs the list of meeting participants and the details of the meeting into the terminal using voice input or touch operations.

[1420] input:

[1421] List of target persons, project details

[1422] output:

[1423] The terminal receives the input and sends it to the server as data required for subsequent processing.

[1424] Step 2:

[1425] Request to retrieve schedule data

[1426] How it works:

[1427] Based on the received list of subjects, the terminal sends a request to the server to acquire schedule data for each subject.

[1428] input:

[1429] List of eligible individuals

[1430] output:

[1431] A get request is sent to the server.

[1432] Step 3:

[1433] Retrieving schedule data

[1434] How it works:

[1435] The server uses the schedule management system's API to obtain schedule data for each target person.

[1436] input:

[1437] List of eligible individuals

[1438] output:

[1439] Schedule data for each target person

[1440] Step 4:

[1441] Identifying free time

[1442] How it works:

[1443] The server analyzes the acquired schedule data and identifies the available time slots for each person, counting the number of people who can attend for each time slot.

[1444] input:

[1445] Schedule Data

[1446] output:

[1447] Free / busy information for each target person

[1448] Step 5:

[1449] Calculating optimal meeting times

[1450] How it works:

[1451] The server calculates the optimal meeting time when everyone is free.

[1452] input:

[1453] Free / busy information

[1454] output:

[1455] Best time to meet

[1456] Step 6:

[1457] Meeting Setup

[1458] How it works:

[1459] The server sends the calculated optimal meeting time via API to register it in each person's schedule management system, and sets up the meeting.

[1460] input:

[1461] Best time to meet

[1462] output:

[1463] The meeting will be registered in each person's schedule.

[1464] Step 7:

[1465] Sending notifications

[1466] How it works:

[1467] The server generates a notification that the conference has been set up and sends it to each participant via smart glasses or email.

[1468] input:

[1469] Meeting setting information

[1470] output:

[1471] A notification will be sent to each person.

[1472] Step 8:

[1473] Collection and analysis of conference attendance data

[1474] How it works:

[1475] After the conference ends, the server collects actual conference participation data and analyzes it for information useful in setting up the next conference.

[1476] input:

[1477] Meeting participation data

[1478] output:

[1479] Analysis results for setting up your next meeting

[1480] The above processing steps enable quick and efficient conference setup using smart glasses.

[1481] 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.

[1482] ---

[1483] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the agenda, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings. The system also incorporates an emotion engine that recognizes user emotions.

[1484] System configuration

[1485] 1. User Interface

[1486] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[1487] For example, a form in a web browser or a dedicated application.

[1488] 2. Server

[1489] It is the central element for receiving input from the user and performing processing.

[1490] It also has an emotion engine that recognizes and analyzes the user's emotions.

[1491] Processing flow

[1492] 1. Receiving the list of meeting participants and the details of the meeting

[1493] User

[1494] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1495] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[1496] Terminal

[1497] The user's input is sent to the server.

[1498] 2. Obtain schedule data for each subject

[1499] server

[1500] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[1501] For example, using the Google Calendar API or Microsoft Outlook API.

[1502] Calendar System

[1503] Each calendar system returns the schedule data of the target person to the server.

[1504] 3. Identifying participants' available times

[1505] server

[1506] The acquired schedule data is analyzed and the free time of each subject is extracted.

[1507] Example: For each time slot, list the availability of each person.

[1508] 4. Calculating optimal meeting times

[1509] server

[1510] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[1511] Example: Find next Monday at 3pm when everyone is free.

[1512] server

[1513] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[1514] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[1515] 5. Recognition of user emotions using an emotion engine

[1516] Server (emotion engine)

[1517] During the meeting setup process, the system analyzes the user's emotions and determines the urgency and importance of the meeting based on this emotional data.

[1518] Example: If a user is feeling stressed, set the meeting urgency high.

[1519] 6. Set up a meeting

[1520] server

[1521] Send an API request to register the determined meeting time in each person's calendar.

[1522] Example: Create an event in Google Calendar called "Project Status Meeting."

[1523] 7. Sending Notifications

[1524] server

[1525] Send emails and push notifications to notify each participant that the meeting has been set up.

[1526] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[1527] Example: If the user is relaxed, send the notification in a soft tone.

[1528] User

[1529] Each participant will see the new meeting setting in their calendar and notifications.

[1530] Example: Participants see the meeting entry in their calendar.

[1531] 8. Collecting and Analyzing Conference Participation Data

[1532] server

[1533] After the conference ends, the server uses the conference tool's API to collect actual conference participation data.

[1534] Example: Obtaining attendance and speech records.

[1535] server

[1536] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1537] It analyzes emotional data and proposes optimal meeting settings.

[1538] In this way, the system helps users easily and efficiently set up large-scale meetings, reducing wasted time and ensuring optimal meeting management. Furthermore, by using an emotion engine, flexible meeting setup is possible according to the user's emotional state.

[1539] ---

[1540] The processing flow will be explained below.

[1541] ---

[1542] Step 1:

[1543] User

[1544] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1545] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[1546] Step 2:

[1547] Terminal

[1548] The user's input is sent to the server.

[1549] Example: An input form is submitted and the user's input is passed to the server.

[1550] Step 3:

[1551] server

[1552] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[1553] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[1554] Step 4:

[1555] Calendar System

[1556] Each calendar system returns the schedule data of the target person to the server.

[1557] Example: Schedule data for each participant is returned in JSON format.

[1558] Step 5:

[1559] server

[1560] The acquired schedule data is analyzed and the free time of each subject is extracted.

[1561] Example: For each time slot, list the availability of each person.

[1562] Step 6:

[1563] server

[1564] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[1565] Example: Find the next Monday at 3pm when everyone is free.

[1566] Step 7:

[1567] server

[1568] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[1569] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[1570] Step 8:

[1571] Server (emotion engine)

[1572] During the meeting setup process, the device's camera and microphone are used to collect the user's facial expressions and tone of voice, which are then analyzed by the emotion engine.

[1573] Example: If a user is feeling stressed, record their emotional data.

[1574] Step 9:

[1575] server

[1576] The urgency and importance of the meeting are determined based on the user's emotional state recognized by the emotion engine.

[1577] Example: If a user is under high stress, schedule meetings earlier with increased urgency.

[1578] Step 10:

[1579] server

[1580] Send an API request to register the determined meeting time in each person's calendar.

[1581] Example: Create an event called "Project Status Meeting" in Google Calendar.

[1582] Step 11:

[1583] server

[1584] Send emails and push notifications to notify each participant that the meeting has been set up.

[1585] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[1586] Example: If the user is relaxed, send the notification in a soft tone.

[1587] Step 12:

[1588] User

[1589] Each participant will see the new meeting setting in their calendar and notifications.

[1590] Example: Participants see the meeting entry in their calendar.

[1591] Step 13:

[1592] server

[1593] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[1594] Example: Obtaining attendance status and speech records.

[1595] Step 14:

[1596] server

[1597] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1598] Emotional data from the emotion engine is also taken into consideration and reflected in the next meeting settings.

[1599] For example: suggesting frequently required participants and suitable meeting times.

[1600] Step 15:

[1601] server

[1602] Based on the feedback results, the emotion engine is trained to further improve accuracy in future meeting settings.

[1603] Example: The emotion engine uses historical emotion and participation data to derive better settings and notification methods.

[1604] ---

[1605] Example 2

[1606] 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."

[1607] Scheduled meetings with many participants are difficult to do efficiently because it takes time and effort to coordinate the schedules of each participant and select the optimal meeting time. Furthermore, meetings are sometimes scheduled without proper consideration of the urgency or importance of the meeting, which can lead to lower participant satisfaction. Furthermore, after the meeting, feedback that can be used to schedule the next meeting is often unavailable.

[1608] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and the event details, means for acquiring schedule data for each participant, means for analyzing the acquired schedule data and identifying the free time of each participant, means for calculating the shortest time slot available to all participants, means for determining the time when the minimum number of participants can attend based on the event details, means for registering the determined conference time in the calendars of each participant, means for sending a notification of conference setup completion to each participant, means for recognizing user emotions and adjusting the urgency and importance of the conference, and means for collecting and analyzing actual conference participation data. This enables conference setup for a large number of participants to be performed quickly and efficiently, and enables appropriate conference setup and feedback taking user emotions into consideration.

[1609] A "meeting target list" is a list containing names and information about people or groups who will be attending the meeting.

[1610] "Item content" refers to detailed information about the agenda items and proposals to be dealt with at the meeting.

[1611] "Schedule data" is a collection of information including each subject's planned activities and timetable.

[1612] "Free time" is a time period when the subject has no other activities or plans and can participate in a meeting, based on the schedule data.

[1613] The "shortest time slot" refers to the earliest time slot among the time slots in which all subjects have no scheduled appointments.

[1614] "Minimum necessary participants" refers to the minimum number of people or groups essential for a meeting to take place.

[1615] "Registering on the calendar" refers to the operation of reflecting the date, time, and content of the meeting in each person's schedule system.

[1616] "Notification of completion of meeting setup" refers to the transmission of information to inform the relevant person that the date, time, and content of the meeting have been decided and the setup has been completed.

[1617] "Emotion recognition" refers to analyzing and identifying a user's psychological state and emotions from their input data and behavior.

[1618] "Actual meeting participation data" is a collection of information that records attendees, remarks, progress, and so on at a meeting.

[1619] "Analyzing" refers to the process of examining collected data to find useful information and patterns.

[1620] This invention relates to a system for quickly and efficiently setting up meetings with many participants. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also has the ability to collect and analyze meeting attendance data to help schedule future meetings. It also incorporates an emotion engine that recognizes the user's emotions.

[1621] User Interface

[1622] Hardware and Software

[1623] Users access the system using a web browser or dedicated application on a device such as a personal computer or smartphone, and use this interface to input the list of participants and the details of the meeting.

[1624] Specific examples

[1625] The user enters "All members of the development team" and "Project progress meeting" in the form on the web browser and clicks the submit button.

[1626] Server Processing

[1627] Hardware and Software

[1628] The server is the central processing element, receiving input data from users and executing various processes. The server includes functions such as sending API requests to obtain schedule data, data analysis functions, and an emotion engine.

[1629] Obtaining schedule data for each target person

[1630] The server sends an API request to acquire schedule data from the calendar system (such as Google Calendar API or Microsoft Outlook API) of each target person based on the target person list.

[1631] Identifying participant availability

[1632] The server analyzes the acquired schedule data and extracts the free time of each subject for each time slot.

[1633] Calculating optimal meeting times

[1634] The system compares the free time of all participants and finds the shortest common available time slot. It also considers the time when the minimum number of participants can participate, depending on the content of the project.

[1635] Recognizing user emotions with an emotion engine

[1636] The server's emotion engine analyzes the user's emotions during the meeting setup process and adjusts the urgency and importance of the meeting based on the emotion data.

[1637] Meeting scheduling and calendar registration

[1638] The server registers the determined meeting time in each person's calendar by sending an API request to a calendar system such as Google Calendar to create an event.

[1639] Sending notifications

[1640] The server sends emails and push notifications to notify each participant that the meeting has been set up, customizing the content and method of the notifications based on the results of the emotion engine.

[1641] Collection and analysis of conference attendance data

[1642] The server collects actual conference participation data when a conference ends, analyzes the data, and provides feedback to users to help set up the next conference.

[1643] Prompt Sentence Examples

[1644] "I'd like to schedule a new project status meeting. Please find a time that works best for the entire development team."

[1645] "Enter the attendee list and subject matter of your next meeting. Use the emotion engine to set it up while taking into account the user's emotions."

[1646] In this way, the system allows users to efficiently schedule large-scale meetings, reduce wasted time, and achieve optimal meeting management. Furthermore, by utilizing the emotion engine, it is possible to set up meetings more flexibly according to the user's emotional state.

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

[1648] Step 1:

[1649] User input of meeting target list and agenda

[1650] Input: The user uses the terminal to input the list of participants and the contents of the meeting into the interface.

[1651] Specific actions: The user enters "All development team members" and "Project progress meeting" into a form on a web browser and clicks the submit button.

[1652] Output: The entered data is sent from the terminal to the server.

[1653] Step 2:

[1654] Server acquires schedule data for each target person

[1655] Input: The target list is sent to the server.

[1656] Specific operation: The server sends an API request to each target person's calendar system (such as the Google Calendar API).

[1657] Data processing: The server uses the target person's email address and user ID to collect schedule data from each calendar system.

[1658] Output: The schedule data for each subject is returned to the server.

[1659] Step 3:

[1660] The server determines the free time of participants

[1661] Input: Schedule data for each subject is returned to the server.

[1662] Specific operation: The server analyzes the schedule data and lists each target person's free time by time slot.

[1663] Data processing: Exclude busy times from schedule data and identify less busy times.

[1664] Output: A free / busy list for each target is generated.

[1665] Step 4:

[1666] Server calculates and determines optimal meeting time

[1667] Input: A free time list is provided for each subject.

[1668] Specific operation: The server compares the free time of all participants and identifies the shortest time slot in which all participants are available. Depending on the content of the project, it also takes into account the time when the minimum number of participants can participate.

[1669] Data calculation: Runs algorithms to find overlaps in the free time list and calculate the best time, as well as determine the urgency and importance of the request.

[1670] Output: A list of optimal meeting times and time slots with the minimum required number of participants is generated.

[1671] Step 5:

[1672] Recognition of user emotions using an emotion engine on the server

[1673] Input: Input data from the user is provided.

[1674] Specific operation: The server's emotion engine analyzes the user's emotions and identifies emotions such as stress, optimism, and anxiety.

[1675] Data Computing: Detecting sentiment from input text data using natural language processing models.

[1676] Output: Data about the user's emotional state is generated.

[1677] Step 6:

[1678] Server-based meeting setup and calendaring

[1679] Input: You have a list of optimal meeting times and time slots that allow the minimum number of participants you need to meet.

[1680] Specific operation: The server sends an API request to each target person's calendar system and registers the determined meeting time in their calendar.

[1681] Data processing: Information such as the meeting title, time, location, and participant list is registered as an event.

[1682] Output: The meeting will be reflected in each target person's calendar.

[1683] Step 7:

[1684] Sending and customizing notifications via the server

[1685] Input: Information on the completion of the conference setup and the user's emotion data are provided.

[1686] What happens: The server sends emails and push notifications, customizing the content and tone of the notifications based on the results of the emotion engine.

[1687] Data operations: Generate notification wording and format and adjust it based on sentiment data.

[1688] Output: A notification is sent to each participant that the meeting has been set up.

[1689] Step 8:

[1690] Server-based collection and analysis of conference attendance data

[1691] Input: Conference participation data is available after the conference has ended.

[1692] Specific operation: The server uses the conference tool's API to collect actual conference participation data such as the attendee list and speech content.

[1693] Data processing: Analyze the collected data and generate feedback that will help you set up your next meeting.

[1694] Output: Analysis results and feedback information are generated and provided to the user.

[1695] (Application example 2)

[1696] 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."

[1697] Conventional meeting scheduling systems have the problem that it takes time to coordinate the schedules of many participants and it is difficult to quickly determine the optimal meeting time. In addition, the user's emotional state can affect the efficiency and urgency of the meeting, so there is a need for meeting scheduling that appropriately reflects that emotional state. Solving these issues is particularly important when a quick response is required in security operations.

[1698] The specification processing by the specification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and matter details, means for acquiring schedule data from various schedule systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's available time, means for calculating the optimal time when all participants are free, means for registering the determined conference time in each participant's schedule, means for sending a conference setup completion notification to each participant, means for analyzing the emotional states of participants and adjusting the urgency of the conference and the notification content, and means for collecting and analyzing actual conference participation data. This enables conferences with many participants to be set up quickly and efficiently, and also enables flexible conference setup that takes into account the emotional states of participants.

[1699] The "meeting participant list" is a list of all participants attending the meeting.

[1700] "Item content" refers to the specific topics or themes to be discussed at the meeting.

[1701] "Schedule data" refers to data including appointment information obtained from the calendar systems of the participants.

[1702] "Free time" refers to the time period when participants do not have other plans.

[1703] The "optimal time" is the earliest time that can be set among the time slots that are available to all participants.

[1704] A "datebook" is part of a calendar system that records each participant's appointments and schedules.

[1705] "Notifications" are messages or alerts that inform participants about meeting settings or changes.

[1706] "Emotional state" is data obtained by analyzing participants' psychological states and emotions.

[1707] "Meeting Urgency" is a rating that indicates how quickly the meeting should occur.

[1708] "Actual conference attendance data" refers to data about participants who actually attended a conference and the contents of the conference.

[1709] This invention relates to a system for quickly and efficiently setting up multi-person meetings, particularly for emergency response meetings in security operations. This system receives a list of meeting participants and the details of the meeting submitted by the user, analyzes the schedules of all participants, calculates and registers the optimal meeting time, and takes into account the emotional state of the participants using an emotion analysis engine.

[1710] System Configuration

[1711] Hardware

[1712] Smartphone: Used to enter meeting requests and receive notifications.

[1713] Server: The central element responsible for retrieving, parsing, and processing schedule data, and also contains the sentiment analysis engine.

[1714] software

[1715] Calendar system API: Use the Google Calendar API or Microsoft Outlook API to obtain participants' schedule data.

[1716] Emotion analysis engine: Analyzes the user's emotional state and reflects the results in feedback. Examples include Emotion Recognition.

[1717] Generative AI model: Collects and analyzes actual meeting attendance data and provides feedback on next meeting setup through generative AI prompts.

[1718] Overview of program processing

[1719] 1. Enter a meeting request

[1720] The user uses a terminal (e.g., a smartphone) to input the list of participants and the details of the meeting, which then sends the request data to the server.

[1721] 2. Retrieving schedule data

[1722] The server acquires schedule data of each participant based on the meeting participant list through a calendar system API.

[1723] 3. Free Time Analysis

[1724] The server analyzes the acquired schedule data, identifies the available time for each participant, and calculates the optimal time when everyone is free.

[1725] 4. Emotional state analysis

[1726] The server's emotion analysis engine adjusts the urgency of the meeting and the content of the notification based on the user's emotional data obtained during the meeting setup process.

[1727] 5. Meeting Registration and Notification

[1728] The server uses a calendar system API to register the determined meeting time in each participant's calendar. After the meeting is set up, the server sends a notification to each participant.

[1729] 6. Collecting and analyzing actual conference attendance data

[1730] After the meeting, the server collects actual meeting participation data and uses a generative AI model to provide useful feedback for setting up the next meeting.

[1731] Specific examples

[1732] Example prompt sentence:

[1733] User List: [{"name": "Participant 1", "face_image": "path_to_image1.jpg"}, {"name": "Participant 2", "face_image": "path_to_image2.jpg"}]

[1734] Meeting Agenda: "Security Emergency Meeting"

[1735] Expected output:

[1736] "The security emergency meeting has been scheduled. The time everyone is available is next Monday at 3 PM."

[1737] "Participant 1 seems stressed. I've increased the urgency of the meeting."

[1738] This system allows for quick and efficient setting up of large-scale meetings, and allows flexible setting up of meetings taking into account the emotional state of participants. This is particularly useful in security work, where it allows for the rapid setting up of emergency response meetings.

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

[1740] Step 1:

[1741] The user uses a terminal to input the list of participants and the details of the meeting. This sends the request data to the server. The input data includes the participants who should attend the meeting and the meeting agenda. Based on this data, the server proceeds to the next step.

[1742] Step 2:

[1743] The server obtains the schedule data of each participant based on the meeting participant list through a calendar system API (e.g., Google Calendar API or Microsoft Outlook API). It sends a request using the list of each participant to the schedule API and obtains the corresponding schedule data.

[1744] Step 3:

[1745] The server analyzes the schedule data it has acquired. To identify each participant's available time, it extracts time periods that are free of other appointments from the schedule data. This provides a list of available times for each participant.

[1746] Step 4:

[1747] The server compares the free time lists of each participant obtained in the previous step and calculates the optimal time when all participants are free. Specifically, it sorts the free time slots of all participants and identifies the common free time slot. The optimal time is the earliest common free time.

[1748] Step 5:

[1749] The server's emotion analysis engine analyzes the emotional state of participants. It takes as input facial image data and voice data from each participant and estimates their emotional state (e.g., stress level, urgency). This information is used to adjust the urgency of the meeting and the content of notifications.

[1750] Step 6:

[1751] The server registers the determined meeting time in each participant's calendar. Using the calendar system API, a new meeting entry is added to each participant's calendar. The input is the meeting start time, end time, agenda, and participant list, and the output is the meeting entry registered in the calendar.

[1752] Step 7:

[1753] The server sends a notification to each participant that the conference has been set up. Notification methods include email and push notifications. The tone and urgency of the notification are adjusted based on the results of the sentiment analysis engine. The input is the notification content and participant information, and the output is the notification message received by each participant.

[1754] Step 8:

[1755] After the meeting ends, the server collects actual meeting participation data, such as attendance status and speech records, using the meeting tool API. This data is used in subsequent analysis steps.

[1756] Step 9:

[1757] The server analyzes the collected meeting participation data and uses a generative AI model to provide feedback that will be useful for setting up the next meeting. The collected data includes attendee lists, speech volume, and emotional state data, and based on this, it provides suggestions for optimal meeting settings and areas for improvement. The output is a feedback report.

[1758] 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.

[1759] 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.

[1760] 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.

[1761] [Fourth embodiment]

[1762] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

[1763] 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.

[1764] 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).

[1765] 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.

[1766] 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.

[1767] 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).

[1768] 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.

[1769] 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.

[1770] 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.

[1771] 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.

[1772] 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.

[1773] 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.

[1774] 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."

[1775] ---

[1776] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[1777] System configuration

[1778] 1. User Interface

[1779] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[1780] For example, a form in a web browser or a dedicated application.

[1781] 2. Server

[1782] It is the central element for receiving input from the user and performing processing.

[1783] Processing flow

[1784] 1. Receiving the list of meeting participants and the details of the meeting

[1785] User

[1786] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1787] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[1788] Terminal

[1789] The user's input is sent to the server.

[1790] 2. Obtain schedule data for each subject

[1791] server

[1792] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[1793] For example, using the Google Calendar API or Microsoft Outlook API.

[1794] Calendar System

[1795] Each calendar system returns schedule data for the subject.

[1796] 3. Identifying participants' available times

[1797] server

[1798] The acquired schedule data is analyzed and the free time of each subject is extracted.

[1799] Example: Count the number of people available for each time slot.

[1800] 4. Calculating optimal meeting times

[1801] server

[1802] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[1803] Example: Find the next Monday at 3pm when everyone is free.

[1804] server

[1805] Depending on the content of the project, we also take into consideration the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[1806] Example: Identify a time when at least the team lead is available to participate instead of the entire development team.

[1807] 5. Set up a meeting

[1808] server

[1809] Send an API request to register the determined meeting time in each person's calendar.

[1810] Example: Create an event called "Project Status Meeting" in Google Calendar.

[1811] 6. Sending Notifications

[1812] server

[1813] Send emails and push notifications to notify each participant that the meeting has been set up.

[1814] User

[1815] Each participant will see the new meeting setting in their calendar and notifications.

[1816] 7. Collecting and analyzing conference attendance data

[1817] server

[1818] After the conference ends, the server collects and analyzes actual conference attendance data.

[1819] Example: Use a conference tool's API to obtain participants' attendance status and speech records.

[1820] server

[1821] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1822] In this way, the system helps users easily and efficiently set up large-scale conferences, reducing wasted time and ensuring optimal conference management.

[1823] ---

[1824] The processing flow will be explained below.

[1825] Step 1:

[1826] User

[1827] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1828] Example: User enters "All development team members" and "Project status meeting."

[1829] Step 2:

[1830] Terminal

[1831] The user's input is sent to the server.

[1832] Example: An input form is submitted and the user's input is passed to the server.

[1833] Step 3:

[1834] server

[1835] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[1836] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[1837] Step 4:

[1838] Calendar System

[1839] Each calendar system returns the schedule data of the target person to the server.

[1840] Example: Schedule data for each participant is returned in JSON format.

[1841] Step 5:

[1842] server

[1843] The acquired schedule data is analyzed and the free time of each subject is extracted.

[1844] Example: For each time slot, list the availability of each person.

[1845] Step 6:

[1846] server

[1847] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[1848] Example: Find the next Monday at 3pm when everyone is free.

[1849] Step 7:

[1850] server

[1851] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[1852] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[1853] Step 8:

[1854] server

[1855] Send an API request to register the determined meeting time in each person's calendar.

[1856] Example: Create an event called "Project Status Meeting" in Google Calendar.

[1857] Step 9:

[1858] server

[1859] Send emails and push notifications to notify each participant that the meeting has been set up.

[1860] Example: Send a notification with meeting details and date and time.

[1861] Step 10:

[1862] User

[1863] Each participant will see the new meeting setting in their calendar and notifications.

[1864] Example: Participants see the meeting entry in their calendar.

[1865] Step 11:

[1866] server

[1867] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[1868] Example: Obtaining attendance status and speech records.

[1869] Step 12:

[1870] server

[1871] Analyze participation data to help schedule your next meeting and provide feedback to users.

[1872] For example: suggesting frequently required participants and suitable meeting times.

[1873] ---

[1874] Example 1

[1875] 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."

[1876] Conventional methods for setting up multi-person meetings have the drawback of being time-consuming and inefficient. In particular, it is difficult to find the optimal meeting time by adjusting the schedules of many participants, and it is difficult to effectively utilize the attendance rate and feedback of participants after the meeting is set up.

[1877] 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.

[1878] In this invention, the server includes means for receiving a list of meeting participants and the details of the meeting, means for acquiring schedule data from the calendar systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's free time, means for calculating the shortest time slot in which all participants are free, means for registering the determined meeting time in each participant's calendar, means for sending a notification that the meeting has been scheduled to each participant, and means for collecting and analyzing actual meeting attendance data. This allows users to easily and efficiently adjust meeting times, and also allows for notification of the completion of the schedule scheduling and collection and analysis of attendance data.

[1879] A "meeting target list" refers to a list that identifies the people or groups who are expected to attend a meeting.

[1880] "Items" refers to a detailed description of the agenda or topics to be addressed at the meeting.

[1881] A "calendar system" refers to an electronic system for managing a user's schedule and appointments.

[1882] "Schedule data" refers to time management information such as each person's schedule and free time.

[1883] "Analysis" refers to the data processing activity of processing the acquired schedule data and extracting the free time of each subject.

[1884] "Available time" refers to the time period when the subject is free from other schedules and obligations and available to attend the meeting.

[1885] The "shortest time slot" refers to the earliest time slot that is available to all meeting participants.

[1886] "Meeting Time" means the date and time confirmed for the meeting to take place.

[1887] "Calendar registration" refers to the act of adding the determined meeting time as an event to the target person's calendar system.

[1888] "Notification" refers to an electronic message sent to inform a target person of information such as the completion or change of a meeting setting.

[1889] "Participation data" refers to information such as the number of participants who actually attended a meeting and a record of what was said.

[1890] "Feedback" refers to the act of analyzing and providing information that will help improve the next meeting's setup and progress.

[1891] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings.

[1892] System configuration

[1893] 1. User Interface

[1894] The user uses a terminal to access an interface for entering the list of participants and the contents of the meeting, using a form on a web browser or a dedicated application.

[1895] 2. Server

[1896] It is the central element for receiving input from the user and performing processing.

[1897] Processing flow and specific examples

[1898] 1. Receiving the list of meeting participants and the details of the meeting

[1899] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[1900] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[1901] The terminal sends the user's input to the server.

[1902] 2. Obtain schedule data for each subject

[1903] Based on the list of users, the server sends an API request to retrieve schedule data from each user's calendar system, using the Google Calendar API or Microsoft Outlook API.

[1904] The calendar system returns schedule data for each subject.

[1905] 3. Identifying participants' available times

[1906] The server analyzes the acquired schedule data and extracts the free time of each target person.

[1907] Example: Count the number of people available for each time slot.

[1908] 4. Calculating optimal meeting times

[1909] The server compares the free time slots of all participants and identifies the shortest common free time slot for all participants.

[1910] Example: Identify next Monday at 3pm when everyone is free.

[1911] Depending on the content of the project, the server will also take into account the layer of required participants and determine whether the meeting can be held with only the minimum number of participants.

[1912] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[1913] 5. Set up a meeting

[1914] The server sends an API request to register the determined meeting time in each person's calendar.

[1915] Example: Create an event in Google Calendar called "Project Status Meeting."

[1916] 6. Sending Notifications

[1917] The server sends emails or push notifications to notify each participant that the conference setup is complete.

[1918] Each user will see the new meeting setup in their calendar and notifications.

[1919] For example: Each target person receives an email confirming the new meeting settings.

[1920] 7. Collecting and analyzing conference attendance data

[1921] After the meeting ends, the server collects and analyzes the actual meeting participation data, using the meeting tool's API to obtain the participants' attendance status and speech records.

[1922] Example: Using data from a conferencing tool, inform users of improvements they can make to their next meeting.

[1923] Example prompts for generative AI models

[1924] Design a system to set the optimal time for multi-person meetings under the following conditions:

[1925] Target audience: All members of the development team

[1926] Project details: Project progress meeting

[1927] Calendar system used: Google Calendar

[1928] Notification method: Email notification

[1929] How to collect meeting participation data: Obtain attendance status and speech records from the meeting tool's API (e.g., Zoom API)

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

[1931] Step 1:

[1932] The user accesses the system interface and enters the list of participants for the meeting and the details of the matter. The user uses a terminal to open a form in a web browser or dedicated application and enters "All members of the development team" and "Project progress meeting." The terminal then sends this information to the server. The inputs are the list of participants and the details of the matter, and the output is the sending of data to the server.

[1933] Step 2:

[1934] The server sends an API request to retrieve schedule data from each person's calendar system based on the target person list. The server sends a request to the Google Calendar API or Microsoft Outlook API to retrieve schedule data for each person. In this step, the target person list is the input, and schedule data is retrieved by sending an API request. The output is the schedule data for each person.

[1935] Step 3:

[1936] The server analyzes the acquired schedule data and extracts the free time of each person. The server uses a Python library to analyze each person's schedule in chronological order. In this step, the acquired schedule data is input and analyzed to list the free time. The output is a free time list for each person.

[1937] Step 4:

[1938] The server compares the free time slots of all participants and identifies the shortest common free time slot. The server then executes logic to compare each person's free time list and identify the best time slot. In this step, the input is each person's free time list, and the common free time is identified through comparison and optimization. The output is the best meeting time.

[1939] Step 5:

[1940] The server considers the layer of required participants and determines whether the meeting can be held with the minimum number of participants. Based on the project content, it reevaluates the time slots that specific members can attend. In this step, the project content and participant list are input, and the layer is determined based on the conditions. The output is the time slots that can be held for the meeting.

[1941] Step 6:

[1942] The server sends an API request to register the determined meeting time in each person's calendar. Using an API such as Google Calendar, the meeting schedule is added to each person's calendar. In this step, the optimal meeting time and the list of people are input, and the schedule is added to the calendar by the API request. The output is the meeting registered in each person's calendar.

[1943] Step 7:

[1944] The server sends email or push notification to each participant to notify them that the conference has been set up. An SMTP server or notification service is used to send a conference setup completion message to each participant. In this step, the input is information about the completion of calendar registration, and the notification service sends notifications to participants. The output is the receipt of notifications.

[1945] Step 8:

[1946] After the meeting ends, the server collects and analyzes the actual meeting participation data. It uses the meeting tool's API to obtain participants' attendance data and speech records. In this step, the meeting end information is input, and the participation data is obtained using the API. The participation data is collected as the output.

[1947] Step 9:

[1948] The server analyzes the participation data to provide information useful for setting up the next meeting and provides feedback to the user. The collected data is analyzed to provide information useful for the next meeting. In this step, the participation data is input and feedback is generated through analysis. The feedback information is provided to the user as the output.

[1949] (Application example 1)

[1950] 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."

[1951] Setting up a multi-person meeting requires time and effort, as it requires coordinating the schedules of each participant and finding the optimal time. Furthermore, there is a need for a faster method for setting up meetings within a company. In particular, there is no existing technology that allows for efficient meeting setup using smart devices, so there is a need for a method to improve the efficiency of meeting setup and quickly notify participants.

[1952] 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.

[1953] In this invention, the server includes a means for receiving a list of participants and the contents of the meeting, a means for acquiring schedule data from each participant's schedule management system based on the list of participants, and a means for analyzing the acquired schedule data and identifying each participant's free time. This enables efficient meeting setup and prompt notification to participants. The server also includes a means for setting up a meeting by voice input or touch operation using smart glasses, and a means for each participant to receive notification using the smart glasses. This allows users to quickly and easily set up and participate in meetings through their smart devices.

[1954] A "meeting target list" is a list of people who should attend a meeting.

[1955] "Item content" refers to the matters or themes to be discussed at the meeting.

[1956] A "schedule management system" is a digital platform for managing each individual's schedule and free time.

[1957] "Schedule data" refers to information about plans and events registered in each subject's calendar.

[1958] "Available time" refers to a time period during which each person can participate in the conference without overlapping with other appointments.

[1959] The "shortest time slot" is the shortest time frame among the periods when all subjects are free.

[1960] "Meeting time" is the specific date and time when the meeting will be held.

[1961] "Notifications" are messages that inform target audiences about meeting setups or changes.

[1962] "Smart glasses" are eyeglass-type electronic devices that can display and input information and are used as wearable devices.

[1963] "Voice input" is a method of entering commands and data into a system using voice.

[1964] "Touch operation" refers to the method of operating a device's display screen or interface by touching it with your fingers.

[1965] MODE FOR CARRYING OUT THE INVENTION

[1966] System Overview

[1967] This invention is a system for quickly and efficiently setting up meetings. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting in each participant's schedule management system, and sends notifications. It also collects and analyzes actual meeting attendance data, which can be used to schedule future meetings.

[1968] Hardware and software used

[1969] Smart Glasses: Use smart glasses to schedule meetings and receive notifications using voice or touch input.

[1970] Server: The central hardware that processes and analyzes data.

[1971] Schedule management system: Software for managing each person's schedule data, such as Google Calendar API or Microsoft Outlook API.

[1972] Data analysis software: Uses programming languages ​​such as Python to analyze schedule data and identify available time.

[1973] Processing flow

[1974] 1. Enter the list of meeting participants and the details of the meeting

[1975] The user uses smart glasses to input the list of meeting participants and the details of the meeting into the terminal using voice input or touch operation.

[1976] 2. Retrieving schedule data

[1977] The terminal requests the server to acquire schedule data based on the input target person list.

[1978] The server obtains the schedule data of each target person through the schedule management system's API.

[1979] 3. Identifying available time slots

[1980] The server analyzes the acquired schedule data and identifies the free time of each subject.

[1981] For each time slot, the number of people who can attend is counted and the optimal meeting time is calculated.

[1982] 4. Set up a meeting

[1983] The server registers the calculated optimal meeting time in the schedule management system for each participant.

[1984] After registration, the server sends a notification to each participant that the conference has been set up.

[1985] 5. Sending notifications

[1986] Each participant uses the smart glasses to check the notification and become aware of the meeting time.

[1987] 6. Collecting and analyzing conference attendance data

[1988] The server collects actual conference attendance data and analyzes it for information useful in setting up the next conference.

[1989] This will make future meeting setup even more efficient.

[1990] Specific examples

[1991] For example, if a user puts on the smart glasses and says, "Schedule a project status meeting for the entire development team," the system retrieves the schedules of all participants, identifies the optimal time when everyone is free, and automatically schedules the meeting. A notification of the meeting schedule is then sent to the smart glasses, allowing for quick and efficient preparation for the meeting.

[1992] Prompt Sentence Examples

[1993] "I'd like to schedule a project status meeting for the entire development team. Please find the best time to meet by checking each person's availability."

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

[1995] Processing flow

[1996] Step 1:

[1997] Enter the meeting target list and the details of the matter

[1998] How it works:

[1999] The user puts on the smart glasses and inputs the list of meeting participants and the details of the meeting into the terminal using voice input or touch operations.

[2000] input:

[2001] List of target persons, project details

[2002] output:

[2003] The terminal receives the input and sends it to the server as data required for subsequent processing.

[2004] Step 2:

[2005] Request to retrieve schedule data

[2006] How it works:

[2007] Based on the received list of subjects, the terminal sends a request to the server to acquire schedule data for each subject.

[2008] input:

[2009] List of eligible individuals

[2010] output:

[2011] A get request is sent to the server.

[2012] Step 3:

[2013] Retrieving schedule data

[2014] How it works:

[2015] The server uses the schedule management system's API to obtain schedule data for each target person.

[2016] input:

[2017] List of eligible individuals

[2018] output:

[2019] Schedule data for each target person

[2020] Step 4:

[2021] Identifying free time

[2022] How it works:

[2023] The server analyzes the acquired schedule data and identifies the available time slots for each person, counting the number of people who can attend for each time slot.

[2024] input:

[2025] Schedule Data

[2026] output:

[2027] Free / busy information for each target person

[2028] Step 5:

[2029] Calculating optimal meeting times

[2030] How it works:

[2031] The server calculates the optimal meeting time when everyone is free.

[2032] input:

[2033] Free / busy information

[2034] output:

[2035] Best time to meet

[2036] Step 6:

[2037] Meeting Setup

[2038] How it works:

[2039] The server sends the calculated optimal meeting time via API to register it in each person's schedule management system, and sets up the meeting.

[2040] input:

[2041] Best time to meet

[2042] output:

[2043] The meeting will be registered in each person's schedule.

[2044] Step 7:

[2045] Sending notifications

[2046] How it works:

[2047] The server generates a notification that the conference has been set up and sends it to each participant via smart glasses or email.

[2048] input:

[2049] Meeting setting information

[2050] output:

[2051] A notification will be sent to each person.

[2052] Step 8:

[2053] Collection and analysis of conference attendance data

[2054] How it works:

[2055] After the conference ends, the server collects actual conference participation data and analyzes it for information useful in setting up the next conference.

[2056] input:

[2057] Meeting participation data

[2058] output:

[2059] Analysis results for setting up your next meeting

[2060] The above processing steps enable quick and efficient conference setup using smart glasses.

[2061] 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.

[2062] ---

[2063] This invention relates to a system for quickly and efficiently setting up multi-person meetings. The system receives a list of meeting participants and the agenda, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also collects and analyzes meeting attendance data to help schedule future meetings. The system also incorporates an emotion engine that recognizes user emotions.

[2064] System configuration

[2065] 1. User Interface

[2066] The user uses a terminal to access an interface for inputting a list of participants and the contents of the meeting.

[2067] For example, a form in a web browser or a dedicated application.

[2068] 2. Server

[2069] It is the central element for receiving input from the user and performing processing.

[2070] It also has an emotion engine that recognizes and analyzes the user's emotions.

[2071] Processing flow

[2072] 1. Receiving the list of meeting participants and the details of the meeting

[2073] User

[2074] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[2075] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[2076] Terminal

[2077] The user's input is sent to the server.

[2078] 2. Obtain schedule data for each subject

[2079] server

[2080] Based on the target list, an API request is sent to retrieve schedule data from each target's calendar system.

[2081] For example, using the Google Calendar API or Microsoft Outlook API.

[2082] Calendar System

[2083] Each calendar system returns the schedule data of the target person to the server.

[2084] 3. Identifying participants' available times

[2085] server

[2086] The acquired schedule data is analyzed and the free time of each subject is extracted.

[2087] Example: For each time slot, list the availability of each person.

[2088] 4. Calculating optimal meeting times

[2089] server

[2090] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[2091] Example: Find next Monday at 3pm when everyone is free.

[2092] server

[2093] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[2094] Example: Identify a time when at least the team lead is available to participate on behalf of the entire development team.

[2095] 5. Recognition of user emotions using an emotion engine

[2096] Server (emotion engine)

[2097] During the meeting setup process, the system analyzes the user's emotions and determines the urgency and importance of the meeting based on this emotional data.

[2098] Example: If a user is feeling stressed, set the meeting urgency high.

[2099] 6. Set up a meeting

[2100] server

[2101] Send an API request to register the determined meeting time in each person's calendar.

[2102] Example: Create an event in Google Calendar called "Project Status Meeting."

[2103] 7. Sending Notifications

[2104] server

[2105] Send emails and push notifications to notify each participant that the meeting has been set up.

[2106] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[2107] Example: If the user is relaxed, send the notification in a soft tone.

[2108] User

[2109] Each participant will see the new meeting setting in their calendar and notifications.

[2110] Example: Participants see the meeting entry in their calendar.

[2111] 8. Collecting and Analyzing Conference Participation Data

[2112] server

[2113] After the conference ends, the server uses the conference tool's API to collect actual conference participation data.

[2114] Example: Obtaining attendance and speech records.

[2115] server

[2116] Analyze participation data to help schedule your next meeting and provide feedback to users.

[2117] It analyzes emotional data and proposes optimal meeting settings.

[2118] In this way, the system helps users easily and efficiently set up large-scale meetings, reducing wasted time and ensuring optimal meeting management. Furthermore, by using an emotion engine, flexible meeting setup is possible according to the user's emotional state.

[2119] ---

[2120] The processing flow will be explained below.

[2121] ---

[2122] Step 1:

[2123] User

[2124] The user accesses the system interface and inputs the list of participants and the contents of the meeting.

[2125] Example: A user fills out a form with "All Development Team Members" and "Project Status Meeting."

[2126] Step 2:

[2127] Terminal

[2128] The user's input is sent to the server.

[2129] Example: An input form is submitted and the user's input is passed to the server.

[2130] Step 3:

[2131] server

[2132] Based on the received list of recipients, an API request is sent to retrieve schedule data from each recipient's calendar system.

[2133] Example: Using the Google Calendar API or Microsoft Outlook API to retrieve schedule data.

[2134] Step 4:

[2135] Calendar System

[2136] Each calendar system returns the schedule data of the target person to the server.

[2137] Example: Schedule data for each participant is returned in JSON format.

[2138] Step 5:

[2139] server

[2140] The acquired schedule data is analyzed and the free time of each subject is extracted.

[2141] Example: For each time slot, list the availability of each person.

[2142] Step 6:

[2143] server

[2144] The available time slots of all participants are compared to identify the shortest available time slot that is available to all participants.

[2145] Example: Find the next Monday at 3pm when everyone is free.

[2146] Step 7:

[2147] server

[2148] Depending on the content of the project, consider the level of essential participants and determine whether the meeting can be held with only the minimum number of participants.

[2149] Example: Identify times when at least the team lead is available to participate on behalf of the entire development team.

[2150] Step 8:

[2151] Server (emotion engine)

[2152] During the meeting setup process, the device's camera and microphone are used to collect the user's facial expressions and tone of voice, which are then analyzed by the emotion engine.

[2153] Example: If a user is feeling stressed, record their emotional data.

[2154] Step 9:

[2155] server

[2156] The urgency and importance of the meeting are determined based on the user's emotional state recognized by the emotion engine.

[2157] Example: If a user is under high stress, schedule meetings earlier with increased urgency.

[2158] Step 10:

[2159] server

[2160] Send an API request to register the determined meeting time in each person's calendar.

[2161] Example: Create an event called "Project Status Meeting" in Google Calendar.

[2162] Step 11:

[2163] server

[2164] Send emails and push notifications to notify each participant that the meeting has been set up.

[2165] The content and method of notifications to participants are adjusted based on the emotional data obtained by the emotion engine.

[2166] Example: If the user is relaxed, send the notification in a soft tone.

[2167] Step 12:

[2168] User

[2169] Each participant will see the new meeting setting in their calendar and notifications.

[2170] Example: Participants see the meeting entry in their calendar.

[2171] Step 13:

[2172] server

[2173] After the meeting ends, the API of the meeting tool is used to collect actual meeting participation data.

[2174] Example: Obtaining attendance status and speech records.

[2175] Step 14:

[2176] server

[2177] Analyze participation data to help schedule your next meeting and provide feedback to users.

[2178] Emotional data from the emotion engine is also taken into consideration and reflected in the next meeting settings.

[2179] For example: suggesting frequently required participants and suitable meeting times.

[2180] Step 15:

[2181] server

[2182] Based on the feedback results, the emotion engine is trained to further improve accuracy in future meeting settings.

[2183] Example: The emotion engine uses historical emotion and participation data to derive better settings and notification methods.

[2184] ---

[2185] Example 2

[2186] 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 robot 414 will be referred to as a "terminal."

[2187] Scheduled meetings with many participants are difficult to do efficiently because it takes time and effort to coordinate the schedules of each participant and select the optimal meeting time. Furthermore, meetings are sometimes scheduled without proper consideration of the urgency or importance of the meeting, which can lead to lower participant satisfaction. Furthermore, after the meeting, feedback that can be used to schedule the next meeting is often unavailable.

[2188] The identification process by the identification processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and the event details, means for acquiring schedule data for each participant, means for analyzing the acquired schedule data and identifying the free time of each participant, means for calculating the shortest time slot available to all participants, means for determining the time when the minimum number of participants can attend based on the event details, means for registering the determined conference time in the calendars of each participant, means for sending a notification of conference setup completion to each participant, means for recognizing user emotions and adjusting the urgency and importance of the conference, and means for collecting and analyzing actual conference participation data. This enables conference setup for a large number of participants to be performed quickly and efficiently, and enables appropriate conference setup and feedback taking user emotions into consideration.

[2189] A "meeting target list" is a list containing names and information about people or groups who will be attending the meeting.

[2190] "Item content" refers to detailed information about the agenda items and proposals to be dealt with at the meeting.

[2191] "Schedule data" is a collection of information including each subject's planned activities and timetable.

[2192] "Free time" is a time period when the subject has no other activities or plans and can participate in a meeting, based on the schedule data.

[2193] The "shortest time slot" refers to the earliest time slot among the time slots in which all subjects have no scheduled appointments.

[2194] "Minimum necessary participants" refers to the minimum number of people or groups essential for a meeting to take place.

[2195] "Registering on the calendar" refers to the operation of reflecting the date, time, and content of the meeting in each person's schedule system.

[2196] "Notification of completion of meeting setup" refers to the transmission of information to inform the relevant person that the date, time, and content of the meeting have been decided and the setup has been completed.

[2197] "Emotion recognition" refers to analyzing and identifying a user's psychological state and emotions from their input data and behavior.

[2198] "Actual meeting participation data" is a collection of information that records attendees, remarks, progress, and so on at a meeting.

[2199] "Analyzing" refers to the process of examining collected data to find useful information and patterns.

[2200] This invention relates to a system for quickly and efficiently setting up meetings with many participants. This system receives a list of meeting participants and the details of the meeting, calculates the optimal meeting time, registers the meeting on each participant's calendar, and sends notifications. It also has the ability to collect and analyze meeting attendance data to help schedule future meetings. It also incorporates an emotion engine that recognizes the user's emotions.

[2201] User Interface

[2202] Hardware and Software

[2203] Users access the system using a web browser or dedicated application on a device such as a personal computer or smartphone, and use this interface to input the list of participants and the details of the meeting.

[2204] Specific examples

[2205] The user enters "All members of the development team" and "Project progress meeting" in the form on the web browser and clicks the submit button.

[2206] Server Processing

[2207] Hardware and Software

[2208] The server is the central processing element, receiving input data from users and executing various processes. The server includes functions such as sending API requests to obtain schedule data, data analysis functions, and an emotion engine.

[2209] Obtaining schedule data for each target person

[2210] The server sends an API request to acquire schedule data from the calendar system (such as Google Calendar API or Microsoft Outlook API) of each target person based on the target person list.

[2211] Identifying participant availability

[2212] The server analyzes the acquired schedule data and extracts the free time of each subject for each time slot.

[2213] Calculating optimal meeting times

[2214] The system compares the free time of all participants and finds the shortest common available time slot. It also considers the time when the minimum number of participants can participate, depending on the content of the project.

[2215] Recognizing user emotions with an emotion engine

[2216] The server's emotion engine analyzes the user's emotions during the meeting setup process and adjusts the urgency and importance of the meeting based on the emotion data.

[2217] Meeting scheduling and calendar registration

[2218] The server registers the determined meeting time in each person's calendar by sending an API request to a calendar system such as Google Calendar to create an event.

[2219] Sending notifications

[2220] The server sends emails and push notifications to notify each participant that the meeting has been set up, customizing the content and method of the notifications based on the results of the emotion engine.

[2221] Collection and analysis of conference attendance data

[2222] The server collects actual conference participation data when a conference ends, analyzes the data, and provides feedback to users to help set up the next conference.

[2223] Prompt Sentence Examples

[2224] "I'd like to schedule a new project status meeting. Please find a time that works best for the entire development team."

[2225] "Enter the attendee list and subject matter of your next meeting. Use the emotion engine to set it up while taking into account the user's emotions."

[2226] In this way, the system allows users to efficiently schedule large-scale meetings, reduce wasted time, and achieve optimal meeting management. Furthermore, by utilizing the emotion engine, it is possible to set up meetings more flexibly according to the user's emotional state.

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

[2228] Step 1:

[2229] User input of meeting target list and agenda

[2230] Input: The user uses the terminal to input the list of participants and the contents of the meeting into the interface.

[2231] Specific actions: The user enters "All development team members" and "Project progress meeting" into a form on a web browser and clicks the submit button.

[2232] Output: The entered data is sent from the terminal to the server.

[2233] Step 2:

[2234] Server acquires schedule data for each target person

[2235] Input: The target list is sent to the server.

[2236] Specific operation: The server sends an API request to each target person's calendar system (such as the Google Calendar API).

[2237] Data processing: The server uses the target person's email address and user ID to collect schedule data from each calendar system.

[2238] Output: The schedule data for each subject is returned to the server.

[2239] Step 3:

[2240] The server determines the free time of participants

[2241] Input: Schedule data for each subject is returned to the server.

[2242] Specific operation: The server analyzes the schedule data and lists each target person's free time by time slot.

[2243] Data processing: Exclude busy times from schedule data and identify less busy times.

[2244] Output: A free / busy list for each target is generated.

[2245] Step 4:

[2246] Server calculates and determines optimal meeting time

[2247] Input: A free time list is provided for each subject.

[2248] Specific operation: The server compares the free time of all participants and identifies the shortest time slot in which all participants are available. Depending on the content of the project, it also takes into account the time when the minimum number of participants can participate.

[2249] Data calculation: Runs algorithms to find overlaps in the free time list and calculate the best time, as well as determine the urgency and importance of the request.

[2250] Output: A list of optimal meeting times and time slots with the minimum required number of participants is generated.

[2251] Step 5:

[2252] Recognition of user emotions using an emotion engine on the server

[2253] Input: Input data from the user is provided.

[2254] Specific operation: The server's emotion engine analyzes the user's emotions and identifies emotions such as stress, optimism, and anxiety.

[2255] Data Computing: Detecting sentiment from input text data using natural language processing models.

[2256] Output: Data about the user's emotional state is generated.

[2257] Step 6:

[2258] Server-based meeting setup and calendaring

[2259] Input: You have a list of optimal meeting times and time slots that allow the minimum number of participants you need to meet.

[2260] Specific operation: The server sends an API request to each target person's calendar system and registers the determined meeting time in their calendar.

[2261] Data processing: Information such as the meeting title, time, location, and participant list is registered as an event.

[2262] Output: The meeting will be reflected in each target person's calendar.

[2263] Step 7:

[2264] Sending and customizing notifications via the server

[2265] Input: Information on the completion of the conference setup and the user's emotion data are provided.

[2266] What happens: The server sends emails and push notifications, customizing the content and tone of the notifications based on the results of the emotion engine.

[2267] Data operations: Generate notification wording and format and adjust it based on sentiment data.

[2268] Output: A notification is sent to each participant that the meeting has been set up.

[2269] Step 8:

[2270] Server-based collection and analysis of conference attendance data

[2271] Input: Conference participation data is available after the conference has ended.

[2272] Specific operation: The server uses the conference tool's API to collect actual conference participation data such as the attendee list and speech content.

[2273] Data processing: Analyze the collected data and generate feedback that will help you set up your next meeting.

[2274] Output: Analysis results and feedback information are generated and provided to the user.

[2275] (Application example 2)

[2276] 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 robot 414 will be referred to as a "terminal."

[2277] Conventional meeting scheduling systems have the problem that it takes time to coordinate the schedules of many participants and it is difficult to quickly determine the optimal meeting time. In addition, the user's emotional state can affect the efficiency and urgency of the meeting, so there is a need for meeting scheduling that appropriately reflects that emotional state. Solving these issues is particularly important when a quick response is required in security operations.

[2278] The specification processing by the specification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for receiving a list of conference participants and matter details, means for acquiring schedule data from various schedule systems of each participant based on the list of participants, means for analyzing the acquired schedule data and identifying each participant's available time, means for calculating the optimal time when all participants are free, means for registering the determined conference time in each participant's schedule, means for sending a conference setup completion notification to each participant, means for analyzing the emotional states of participants and adjusting the urgency of the conference and the notification content, and means for collecting and analyzing actual conference participation data. This enables conferences with many participants to be set up quickly and efficiently, and also enables flexible conference setup that takes into account the emotional states of participants.

[2279] The "meeting participant list" is a list of all participants attending the meeting.

[2280] "Item content" refers to the specific topics or themes to be discussed at the meeting.

[2281] "Schedule data" refers to data including appointment information obtained from the calendar systems of the participants.

[2282] "Free time" refers to the time period when participants do not have other plans.

[2283] The "optimal time" is the earliest time that can be set among the time slots that are available to all participants.

[2284] A "datebook" is part of a calendar system that records each participant's appointments and schedules.

[2285] "Notifications" are messages or alerts that inform participants about meeting settings or changes.

[2286] "Emotional state" is data obtained by analyzing participants' psychological states and emotions.

[2287] "Meeting Urgency" is a rating that indicates how quickly the meeting should occur.

[2288] "Actual conference attendance data" refers to data about participants who actually attended a conference and the contents of the conference.

[2289] This invention relates to a system for quickly and efficiently setting up multi-person meetings, particularly for emergency response meetings in security operations. This system receives a list of meeting participants and the details of the meeting submitted by the user, analyzes the schedules of all participants, calculates and registers the optimal meeting time, and takes into account the emotional state of the participants using an emotion analysis engine.

[2290] System Configuration

[2291] Hardware

[2292] Smartphone: Used to enter meeting requests and receive notifications.

[2293] Server: The central element responsible for retrieving, parsing, and processing schedule data, and also contains the sentiment analysis engine.

[2294] software

[2295] Calendar system API: Use the Google Calendar API or Microsoft Outlook API to obtain participants' schedule data.

[2296] Emotion analysis engine: Analyzes the user's emotional state and reflects the results in feedback. Examples include Emotion Recognition.

[2297] Generative AI model: Collects and analyzes actual meeting attendance data and provides feedback on next meeting setup through generative AI prompts.

[2298] Overview of program processing

[2299] 1. Enter a meeting request

[2300] The user uses a terminal (e.g., a smartphone) to input the list of participants and the details of the meeting, which then sends the request data to the server.

[2301] 2. Retrieving schedule data

[2302] The server acquires schedule data of each participant based on the meeting participant list through a calendar system API.

[2303] 3. Free Time Analysis

[2304] The server analyzes the acquired schedule data, identifies the available time for each participant, and calculates the optimal time when everyone is free.

[2305] 4. Emotional state analysis

[2306] The server's emotion analysis engine adjusts the urgency of the meeting and the content of the notification based on the user's emotional data obtained during the meeting setup process.

[2307] 5. Meeting Registration and Notification

[2308] The server uses a calendar system API to register the determined meeting time in each participant's calendar. After the meeting is set up, the server sends a notification to each participant.

[2309] 6. Collecting and analyzing actual conference attendance data

[2310] After the meeting, the server collects actual meeting participation data and uses a generative AI model to provide useful feedback for setting up the next meeting.

[2311] Specific examples

[2312] Example prompt sentence:

[2313] User List: [{"name": "Participant 1", "face_image": "path_to_image1.jpg"}, {"name": "Participant 2", "face_image": "path_to_image2.jpg"}]

[2314] Meeting Agenda: "Security Emergency Meeting"

[2315] Expected output:

[2316] "The security emergency meeting has been scheduled. The time everyone is available is next Monday at 3 PM."

[2317] "Participant 1 seems stressed. I've increased the urgency of the meeting."

[2318] This system allows for quick and efficient setting up of large-scale meetings, and allows flexible setting up of meetings taking into account the emotional state of participants. This is particularly useful in security work, where it allows for the rapid setting up of emergency response meetings.

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

[2320] Step 1:

[2321] The user uses a terminal to input the list of participants and the details of the meeting. This sends the request data to the server. The input data includes the participants who should attend the meeting and the meeting agenda. Based on this data, the server proceeds to the next step.

[2322] Step 2:

[2323] The server obtains the schedule data of each participant based on the meeting participant list through a calendar system API (e.g., Google Calendar API or Microsoft Outlook API). It sends a request using the list of each participant to the schedule API and obtains the corresponding schedule data.

[2324] Step 3:

[2325] The server analyzes the schedule data it has acquired. To identify each participant's available time, it extracts time periods that are free of other appointments from the schedule data. This provides a list of available times for each participant.

[2326] Step 4:

[2327] The server compares the free time lists of each participant obtained in the previous step and calculates the optimal time when all participants are free. Specifically, it sorts the free time slots of all participants and identifies the common free time slot. The optimal time is the earliest common free time.

[2328] Step 5:

[2329] The server's emotion analysis engine analyzes the emotional state of participants. It takes as input facial image data and voice data from each participant and estimates their emotional state (e.g., stress level, urgency). This information is used to adjust the urgency of the meeting and the content of notifications.

[2330] Step 6:

[2331] The server registers the determined meeting time in each participant's calendar. Using the calendar system API, a new meeting entry is added to each participant's calendar. The input is the meeting start time, end time, agenda, and participant list, and the output is the meeting entry registered in the calendar.

[2332] Step 7:

[2333] The server sends a notification to each participant that the conference has been set up. Notification methods include email and push notifications. The tone and urgency of the notification are adjusted based on the results of the sentiment analysis engine. The input is the notification content and participant information, and the output is the notification message received by each participant.

[2334] Step 8:

[2335] After the meeting ends, the server collects actual meeting participation data, such as attendance status and speech records, using the meeting tool API. This data is used in subsequent analysis steps.

[2336] Step 9:

[2337] The server analyzes the collected meeting participation data and uses a generative AI model to provide feedback that will be useful for setting up the next meeting. The collected data includes attendee lists, speech volume, and emotional state data, and based on this, it provides suggestions for optimal meeting settings and areas for improvement. The output is a feedback report.

[2338] The specific processing unit 290 transmits the result of the specific processing to the robot 414. In the robot 414, the control unit 46A causes the speaker 240 and the control target 443 to output the result of the specific processing. The microphone 238 acquires voice indicating a user input regarding the result of the specific processing. The control unit 46A transmits voice 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 voice data.

[2339] 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.

[2340] 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 robot 414.

[2341] The emotion identification model 59 as an emotion engine may determine the user's emotion according to a specific mapping. Specifically, the emotion identification model 59 may determine the user's emotion according to an emotion map (see FIG. 9), which is a specific mapping. Similarly, the emotion identification model 59 may determine the robot's emotion, and the identification processing unit 290 may perform identification processing using the robot's emotion.

[2342] FIG. 9 illustrates an emotion map 400 on which multiple emotions are mapped. In the emotion map 400, emotions are arranged in concentric circles radiating from the center. Emotions closer to the center of the concentric circles are more primitive. Emotions representing states and behaviors arising from a state of mind are arranged on the outer edges of the concentric circles. The concept of emotion includes both affect and mental states. Emotions generally generated from reactions occurring in the brain are arranged on the left side of the concentric circles. Emotions generally induced by situational judgment are arranged on the right side of the concentric circles. Emotions generally generated from reactions occurring in the brain and induced by situational judgment are arranged on the upper and lower sides of the concentric circles. Furthermore, the emotion of "pleasure" is arranged on the upper side of the concentric circles, and the emotion of "discomfort" is arranged on the lower side. In this way, in the emotion map 400, multiple emotions are mapped based on the structure by which emotions are generated, and emotions that tend to occur simultaneously are mapped close to each other.

[2343] These emotions are distributed in the 3 o'clock direction on emotion map 400, and typically fluctuate between relief and anxiety. In the right half of emotion map 400, situational awareness dominates over internal sensations, resulting in a sense of calm.

[2344] The inside of emotion map 400 represents what is going on in the mind, and the outside of emotion map 400 represents behavior, so the further you go outside emotion map 400, the more visible the emotions become (the more they are expressed in behavior).

[2345] Human emotions are based on various balances, such as posture and blood sugar levels. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. Emotions can also be created for robots, automobiles, and motorcycles, based on various balances, such as posture and remaining battery life. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. An emotion map can be generated, for example, based on Dr. Mitsuyoshi's emotion map (Research on Voice Emotion Recognition and Emotional Brain Physiological Signal Analysis Systems, Tokushima University, Doctoral Dissertation: https: / / ci.nii.ac.jp / naid / 500000375379). The left half of the emotion map lists emotions belonging to the "reaction" domain, where sensation is dominant. The right half of the emotion map lists emotions belonging to the "situation" domain, where situational awareness is dominant.

[2346] The emotion map defines two emotions that promote learning. One is a negative emotion on the situation side, around the middle of "repentance" or "reflection." In other words, this occurs when the robot experiences negative emotions such as "I never want to feel this way again" or "I don't want to be scolded again." The other is a positive emotion on the response side, around "desire." In other words, this occurs when the robot experiences positive feelings such as "I want more" or "I want to know more."

[2347] The emotion identification model 59 inputs user input into a pre-trained neural network, obtains emotion values ​​indicating each emotion shown in the emotion map 400, and determines the user's emotion. This neural network is pre-trained based on multiple pieces of training data that are combinations of user input and emotion values ​​indicating each emotion shown in the emotion map 400. Furthermore, this neural network is trained so that emotions that are located close to each other have similar values, as in the emotion map 900 shown in FIG. 10. FIG. 10 shows an example in which multiple emotions, "relieved," "calm," and "reassuring," have similar emotion values.

[2348] The system according to the present disclosure has been described above mainly with respect to the functions of the data processing device 12, but the system according to the present disclosure is not necessarily implemented on a server. The system according to the present disclosure may be implemented as a general information processing system. The present disclosure may be implemented, for example, as a software program running on a personal computer or an application running on a smartphone, etc. The method according to the present disclosure may be provided to users in the form of SaaS (Software as a Service).

[2349] In the above embodiment, an example was given in which the specific processing is performed by one computer 22, but the technology of the present disclosure is not limited to this, and the specific processing may be distributed and performed by a plurality of computers including the computer 22. For example, the data generation model 58 may be provided in an external device of the data processing device 12, and data may be generated in the external device in accordance with input data.

[2350] In the above embodiment, an example in which the specific processing program 56 is stored in the storage 32 has been described, but the technology of the present disclosure is not limited to this. For example, the specific processing program 56 may be stored in a portable, computer-readable, non-transitory storage medium such as a USB (Universal Serial Bus) memory. The specific processing program 56 stored in the non-transitory storage medium is installed in the computer 22 of the data processing device 12. The processor 28 executes the specific processing in accordance with the specific processing program 56.

[2351] Alternatively, the specific processing program 56 may be stored in a storage device such as a server connected to the data processing device 12 via the network 54, and the specific processing program 56 may be downloaded and installed on the computer 22 in response to a request from the data processing device 12.

[2352] It is not necessary to store all of the specific processing program 56 in a storage device such as a server connected to the data processing device 12 via the network 54, or to store all of the specific processing program 56 in the storage 32; only a portion of the specific processing program 56 may be stored.

[2353] The hardware resource for executing a specific process can be any of the following processors: An example of a processor is a CPU, which is a general-purpose processor that functions as a hardware resource for executing a specific process by executing software, i.e., a program. Another example of a processor is a dedicated electrical circuit, such as an FPGA (Field-Programmable Gate Array), a PLD (Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit), which is a processor with a circuit configuration designed specifically for executing a specific process. Each processor has built-in or connected memory, and each processor uses the memory to execute the specific process.

[2354] The hardware resource that executes the specific processing may be configured with one of these various processors, or may be configured with a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Also, the hardware resource that executes the specific processing may be a single processor.

[2355] As an example of a system configured with a single processor, first, one processor is configured by combining one or more CPUs and software, and this processor functions as a hardware resource that executes a specific process. Second, there is a system that uses a processor that realizes the functions of an entire system including multiple hardware resources that execute a specific process on a single IC chip, as typified by SoC (System-on-a-chip). In this way, a specific process is realized using one or more of the above-mentioned various processors as hardware resources.

[2356] Furthermore, the hardware structure of these various processors can be, more specifically, an electric circuit that combines circuit elements such as semiconductor devices. The specific processing described above is merely an example. Therefore, it goes without saying that unnecessary steps may be deleted, new steps may be added, or the processing order may be rearranged, without departing from the spirit of the invention.

[2357] The above-described description and illustrations are a detailed explanation of the parts related to the technology of the present disclosure and are merely an example of the technology of the present disclosure. For example, the above description of the configuration, functions, actions, and effects is an explanation of an example of the configuration, functions, actions, and effects of the parts related to the technology of the present disclosure. Therefore, it goes without saying that unnecessary parts may be deleted, new elements may be added, or replacements may be made to the above-described description and illustrations within the scope of the gist of the technology of the present disclosure. Furthermore, to avoid confusion and facilitate understanding of the parts related to the technology of the present disclosure, the above-described description and illustrations omit explanations of common technical knowledge that do not require particular explanation to enable the implementation of the technology of the present disclosure.

[2358] All publications, patent applications, and technical standards mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication, patent application, or technical standard was specifically and individually indicated to be incorporated by reference.

[2359] The following is further disclosed regarding the above embodiment.

[2360] (Claim 1)

[2361] A means of receiving the meeting target list and the project details;

[2362] means for acquiring schedule data from the calendar system of each target person based on the target person list;

[2363] A means for analyzing the acquired schedule data and identifying free time for each target person;

[2364] A means to calculate the shortest time slot available to everyone,

[2365] A means of registering the determined meeting time in each person's calendar;

[2366] a means for sending a notification of completion of the conference setup to each of the participants;

[2367] A means of collecting and analyzing actual meeting attendance data;

[2368] A system including:

[2369] (Claim 2)

[2370] 2. The system according to claim 1, further comprising means for determining whether a conference can be held with only members of a specific layer based on the contents of the conference.

[2371] (Claim 3)

[2372] 10. The system of claim 1, further comprising means for analyzing, after the conference is set up, information useful for setting up a next conference based on actual participation data, and providing feedback.

[2373] "Example 1"

[2374] (Claim 1)

[2375] A means of receiving the meeting target list and the project details;

[2376] means for acquiring schedule data from the calendar system of each target person based on the target person list;

[2377] A means for analyzing the acquired schedule data and identifying free time for each target person;

[2378] A means to calculate the shortest time slot available to everyone,

[2379] A means of registering the determined meeting time in each person's calendar;

[2380] a means for sending a notification of completion of the conference setup to each of the participants;

[2381] A means of collecting and analyzing actual meeting attendance data;

[2382] A system including:

[2383] (Claim 2)

[2384] 2. The system according to claim 1, further comprising means for determining whether a meeting can be held with only members of a specific layer based on the contents of the meeting.

[2385] (Claim 3)

[2386] 10. The system of claim 1, further comprising means for analyzing, after the conference is set up, information useful for setting up a next conference based on actual participation data, and providing feedback.

[2387] "Application Example 1"

[2388] (Claim 1)

[2389] A means of receiving the meeting target list and the project details;

[2390] means for acquiring schedule data from a schedule management system for each subject based on the subject list;

[2391] A means for analyzing the acquired schedule data and identifying free time for each target person;

[2392] A means to calculate the shortest time slot available to everyone,

[2393] A means for registering the determined meeting time in the schedule management system of each person;

[2394] a means for sending a notification of completion of the conference setup to each of the participants;

[2395] A means of collecting and analyzing actual meeting attendance data;

[2396] A means for setting up a meeting by voice input or touch operation using smart glasses;

[2397] a means for each subject to receive notifications using smart glasses;

[2398] A system including:

[2399] (Claim 2)

[2400] 2. The system according to claim 1, further comprising means for determining whether a conference can be established with only participants of a specific layer based on the contents of the conference.

[2401] (Claim 3)

[2402] 10. The system of claim 1, further comprising means for analyzing, after the conference is set up, information useful for setting up a next conference based on actual participation data, and providing feedback.

[2403] "Example 2: Combining Emotion Engines"

[2404] (Claim 1)

[2405] A means of receiving the meeting target list and the project details;

[2406] means for acquiring schedule data for each subject based on the subject list;

[2407] A means for analyzing the acquired schedule data and identifying free time for each target person;

[2408] A means to calculate the shortest time slot available to everyone,

[2409] A method to determine the time when the minimum number of participants necessary can attend depending on the content of the project, and

[2410] A means of registering the determined meeting time in each person's calendar;

[2411] a means for sending a notification of completion of the conference setup to each of the participants;

[2412] A means for recognizing the user's emotions and adjusting the urgency and importance of the meeting;

[2413] A means of collecting and analyzing actual meeting attendance data;

[2414] A system including:

[2415] (Claim 2)

[2416] 2. The system according to claim 1, further comprising means for determining whether a conference can be held with only members of a specific layer based on the contents of the conference.

[2417] (Claim 3)

[2418] 10. The system of claim 1, further comprising means for analyzing, after the conference is set up, information useful for setting up a next conference based on actual participation data, and providing feedback.

[2419] "Application example 2 when combining emotion engines"

[2420] (Claim 1)

[2421] A means of receiving the meeting target list and the project details;

[2422] A means for acquiring schedule data from various schedule systems of each participant based on the target person list;

[2423] A means for analyzing the acquired schedule data and identifying the slack time of each participant;

[2424] A means to calculate the optimal time when everyone is free, and

[2425] A means for registering the determined meeting time in each participant's calendar;

[2426] a means for sending a notification to each participant that the conference has been set up;

[2427] A means to analyze the emotional state of participants and adjust the urgency of the meeting and the content of notifications;

[2428] A means of collecting and analyzing actual meeting attendance data;

[2429] A system including:

[2430] (Claim 2)

[2431] 2. The system according to claim 1, further comprising means for determining whether a conference can be held with only members of a specific layer based on the contents of the conference.

[2432] (Claim 3)

[2433] 10. The system of claim 1, further comprising means for analyzing, after the meeting is set up, information useful for setting up a next meeting based on actual attendance data and providing feedback using a generative AI model. [Explanation of symbols]

[2434] 10, 210, 310, 410 Data Processing Systems 12 Data Processing Device 14 Smart Devices 214 Smart Glasses 314 Headset-type terminal 414 Robot< / url:> < / url:> < / url:> < / url:>

Claims

1. A means of receiving the meeting target list and the project details; means for acquiring schedule data from the calendar system of each target person based on the target person list; A means for analyzing the acquired schedule data and identifying free time for each target person; A means to calculate the shortest time slot available to everyone, A means of registering the determined meeting time in each person's calendar; a means for sending a notification of completion of the conference setup to each of the participants; A means of collecting and analyzing actual meeting attendance data; A system including:

2. 2. The system according to claim 1, further comprising means for determining whether a conference can be held with only members of a specific layer based on the contents of the conference agenda.

3. The system according to claim 1 , further comprising means for analyzing, after the conference is set up, information useful for setting up a next conference based on actual participation data, and providing feedback.

Images