system

Abstract

Provide a system. [Solution] a means of setting meeting agendas and scheduled times; a means for signaling the start and end of a conference; A means of managing the progress of meetings based on a plan; A means for recording and storing the audio of the meeting; A means for searching the stored recording data; A means to extract and store ideas from recordings and minutes, a means for displaying the extracted ideas; 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] Effectively managing meeting progress and properly allocating time to agenda items are important challenges for many organizations. However, progress management in many meetings is often done manually, which can lead to imbalances in time allocation and important agenda items being overlooked. Furthermore, ideas and proposals raised during meetings tend to be one-off and are rarely reused in subsequent meetings. As a result, useful ideas from past meetings can be lost, and new developments and innovations can be overlooked. Furthermore, the current lack of a way to record important discussions and ideas and easily search and reference them later is also an obstacle to efficient organizational management. [Means for solving the problem]

[0005] To solve the above problems, the present invention provides a means for setting the agenda and scheduled time for a meeting, and a means for notifying the start and end of the meeting. It also includes a means for systematically managing the progress of the meeting and adhering to the time allocation set for each agenda. It also provides a system that includes a means for recording the audio of the meeting and storing the recorded data, making the meeting contents available for later reference. This system also includes a means for searching the stored recorded data and displaying past discussion contents in a reusable format based on specific keywords. It also provides a means for extracting useful ideas from the recorded data and minutes, storing them, and displaying them later. The use of timestamps enables more accurate and rapid searching of past discussion contents and ideas. These means provide a system that enables efficient progress management of meetings and the active utilization of useful ideas.

[0006] A "meeting agenda" indicates the topics or themes to be covered at the meeting.

[0007] "Scheduled time" refers to the time allocated to each agenda item in a meeting, and serves as a basis for progress management.

[0008] "Notification" refers to the act or process of informing participants about the start or end of a meeting or other important events.

[0009] "Progress management" means supervising and adjusting the flow of the meeting according to plan, and properly allocating time and progressing the content.

[0010] "Audio recording" means recording what is said or discussed during a meeting in digital or analog form.

[0011] "Storing data" means saving recorded audio data or extracted ideas so that they can be accessed later.

[0012] "Searching" refers to the act of finding relevant information from accumulated data based on specific keywords or conditions.

[0013] "Idea extraction" means identifying and consciously extracting useful suggestions and thoughts from recordings or minutes.

[0014] "Display" means visually presenting accumulated data and extracted ideas, allowing users to confirm and use the information.

[0015] A "timestamp" is information that indicates the date and time when data was recorded, and is used to facilitate data management and retrieval. [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] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. An example of this system is shown below.

[0038] Meeting progress management implementation example

[0039] 1. Setting the meeting agenda

[0040] Users set up a meeting agenda by entering the meeting topic and scheduled time into their terminal. This agenda includes the topic name and the scheduled time allocated to each topic. For example, a meeting topic could be "market analysis" and "new product proposal," with 30 minutes and 45 minutes allocated to each topic, respectively.

[0041] 2. Starting and managing meetings

[0042] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies that the "market analysis" agenda item has started, and notifies the user to move on to the next agenda item, "new product proposal," after 30 minutes have passed.

[0043] 3. End of meeting notification

[0044] When the conference ends, the terminal notifies the user that the conference is ending.

[0045] Embodiments of storing and searching audio data

[0046] 1. Starting recording and data accumulation

[0047] To start recording a meeting, a user enters the meeting ID into their device. The server obtains the current timestamp and combines it with the meeting ID to generate a recording filename. The recording data is saved on the server and stored in a database along with the file name and timestamp.

[0048] 2. Search for recording data

[0049] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into their device. The server searches for recording files that match the keyword and displays the results to the user. For example, if a user searches for the keyword "meeting001," a list of recording data related to this meeting ID will be displayed.

[0050] Idea extraction and display embodiment

[0051] 1. Extracting ideas from minutes and audio recordings

[0052] Users provide the minutes and audio recordings generated after the meeting to their devices. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, if the minutes contain "ideas for improving a new product concept," they will be automatically extracted.

[0053] 2. Displaying accumulated ideas

[0054] A user can use a terminal to request to view the accumulated ideas. The server searches the database for relevant ideas and displays the results in a list. This allows the user to review and reuse useful suggestions made in past meetings.

[0055] The above-described embodiments of the present invention provide a system that enables efficient management of the progress of meetings and the reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

[0056] The processing flow will be explained below.

[0057] Meeting progress management process steps

[0058] Step 1:

[0059] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[0060] Step 2:

[0061] The terminal notifies the user that the conference is about to begin. The terminal displays the message "Conference is about to begin" to notify the user that the conference is about to begin.

[0062] Step 3:

[0063] The terminal manages the progress of the meeting. Based on the agenda, the terminal displays the items in order and monitors and measures the scheduled time for each item. Users proceed with the discussion according to the displayed items.

[0064] Step 4:

[0065] When the time for each topic has elapsed, the device will notify the user to move on to the next topic. For example, when 30 minutes have elapsed for "Market Analysis," the device will display the next topic, such as "New Product Proposal."

[0066] Step 5:

[0067] When all the agenda items have been covered, the terminal notifies the user that the conference is over. The terminal displays the message "The conference is ending" to inform the user that the conference is over.

[0068] Recording data storage and retrieval processing steps

[0069] Step 1:

[0070] To start recording a conference, the user enters the conference ID into the terminal and presses the record button to start recording.

[0071] Step 2:

[0072] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording filename. The server saves the recording data in the specified directory based on the generated filename.

[0073] Step 3:

[0074] The user searches for recorded data. The user enters search keywords (such as the meeting ID or related topic) into the device and makes a search request.

[0075] Step 4:

[0076] The server searches for recorded data. The server searches for recorded files in the specified directory based on the keyword and displays a list of search results. If a recorded data matching the keyword is found, the file name and detailed information are provided to the user.

[0077] Idea extraction and display process steps

[0078] Step 1:

[0079] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[0080] Step 2:

[0081] The server extracts ideas. The server analyzes the provided text data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[0082] Step 3:

[0083] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[0084] Step 4:

[0085] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[0086] These are the specific processing steps of the system. Each step is realized through cooperation between users, terminals, and servers, and supports efficient management of the progress of meetings and the reuse of useful ideas.

[0087] Example 1

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

[0089] Conventional conference management systems can manage the progress of meetings and store recorded data, but they have difficulty efficiently extracting and reusing useful information discussed during meetings. This results in problems such as the content of meetings not being managed systematically, making it difficult to reuse information. Furthermore, meeting time management is sometimes inappropriate, which can reduce the efficiency of meetings.

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

[0091] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing useful information from the recorded data and minutes, and means for displaying the extracted useful information. This enables efficient progress management of the meeting and reuse of recorded meeting content and ideas.

[0092] A "meeting agenda" refers to the specific themes or topics that will be addressed at the meeting.

[0093] "Scheduled time" refers to the predetermined time frame for each agenda item.

[0094] The "means for notifying the start and end of a conference" refers to a function for notifying the user of the start and end times of a conference.

[0095] "Means for managing the progress of a meeting based on a plan" refers to the function of managing the progress of a meeting based on a pre-set agenda.

[0096] "Means for recording and storing conference audio" refers to the function for recording audio during a conference and saving that data.

[0097] "Means for searching stored recorded data" refers to the function of searching stored recorded data based on specific conditions.

[0098] "Means for extracting and storing useful information from audio recordings and minutes" refers to the ability to extract useful ideas and information from audio recordings and written minutes and store them in a database.

[0099] "Means for displaying extracted useful information" refers to a function for visually presenting useful information stored in the database to the user.

[0100] "Time information" refers to information that indicates the current time or the time when a specific event occurred.

[0101] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. A specific embodiment of this system is shown below.

[0102] Meeting progress management implementation example

[0103] The user first inputs the meeting topic and scheduled time into the terminal to set up the meeting agenda. The agenda includes the topic name and the allocated time for each topic. For example, the user may set the topics "Market Analysis" and "New Product Proposal" and allocate 30 and 45 minutes for each topic. The terminal receives the input information and generates the meeting agenda.

[0104] Next, the device notifies the user that the meeting is about to begin based on the set agenda. For example, it displays a pop-up message saying, "Please begin the meeting." Once the user starts the meeting, the device manages the progress of each agenda item according to the time allocation. Specifically, the device notifies the user that the "Market Analysis" agenda item has begun, and after 30 minutes has passed, it notifies the user, "Please move on to the next agenda item, 'New Product Proposal.'" This allows the user to proceed with the meeting under appropriate time management. When the meeting ends, the device notifies the user that "The meeting is ending," and once the user confirms the end, the recording of the meeting is officially completed.

[0105] Embodiments of storing and searching audio data

[0106] To efficiently record important discussions during a meeting, a user enters the meeting ID into their device to start recording the meeting. For example, they enter "meeting001" and click the "Start Recording" button. The server obtains the current timestamp and combines it with the meeting ID to generate a recording file name. Specifically, it generates a file name such as "meeting001_20231012_1500.wav." The recording data is saved on the server and accumulated in a database along with the file name and timestamp.

[0107] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into the terminal. For example, they enter "meeting001" into the search form and click the "Search" button. The server searches for recording files that match the keyword and displays the results to the user. Specifically, search results including "meeting001_20231012_1500.wav" are displayed in a list.

[0108] Idea extraction and display embodiment

[0109] After the meeting, the user provides the generated minutes and recording data to the device. Specifically, the user uploads the minutes text and drags and drops the meeting recording file to the device. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, the server analyzes the minutes text to extract "ideas for improving new product concepts" and stores them in the database.

[0110] A user uses a device to request to view the stored ideas. For example, the user enters "new product proposal" into the search form and clicks the "Search" button. The server searches for related ideas and displays results including "improvement ideas for new product concepts" on the user's device.

[0111] Examples of prompt statements

[0112] For example, when setting a meeting agenda, a user might enter:

[0113] "I'd like to set aside 30 minutes for market analysis and 45 minutes for new product proposals."

[0114] Also, if you want to search for recording data for a specific meeting ID, "meeting001," enter the following:

[0115] "meeting001"

[0116] Furthermore, if you want to review the accumulated ideas, you can make a request to the generative AI model with the following prompt:

[0117] "Show me new product proposal ideas extracted from past meetings."

[0118] Through these specific operations, the system of the present invention enables efficient management of meeting progress and reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

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

[0120] Step 1:

[0121] The user inputs the agenda and scheduled time of the meeting into the terminal.

[0122] As a specific example of operation, a user inputs "market analysis," "30 minutes," "new product proposal," and "45 minutes" into an input form on a terminal.

[0123] Input: Meeting agenda (market analysis, new product proposal), estimated time for each agenda item (30 minutes, 45 minutes)

[0124] Output: Meeting agenda (market analysis: 30 minutes, new product proposal: 45 minutes)

[0125] The terminal receives the input information and generates a meeting agenda.

[0126] Step 2:

[0127] The terminal notifies the user of the start of the conference based on the set agenda.

[0128] As a specific example of how this works, a pop-up message will appear saying "Please start the meeting."

[0129] Input: Meeting agenda

[0130] Output: Notification of meeting start

[0131] The user clicks the Start Conference button.

[0132] As a specific example of operation, the user clicks the "Start" button.

[0133] Input: User action (clicking the start button)

[0134] Output:Confirmation of meeting start

[0135] Step 3:

[0136] The terminal manages the progress of each agenda item according to the time allocation.

[0137] As a specific example of operation, the terminal notifies by voice or on the screen that the topic "Market Analysis" has started.

[0138] Input: Meeting agenda, meeting start confirmation

[0139] Output: Agenda start notification (market analysis, new product proposal in 30 minutes)

[0140] After 30 minutes, a notice will be given to move on to the next agenda item, "New product proposals."

[0141] As a specific example of how it works, the terminal will display, "The next topic is 'New product proposals.'"

[0142] Input: Time passed (30 minutes)

[0143] Output: Next Agenda Notification

[0144] Step 4:

[0145] When the conference ends, the terminal notifies the user of the end of the conference.

[0146] As a specific example of operation, the message "The meeting will end" is displayed and an audio notification is also given.

[0147] Input: Meeting agenda complete, all items closed

[0148] Output: Notification of end of meeting

[0149] The user confirms the end of the conference.

[0150] As a specific example of the operation, the user clicks the "Confirm termination" button.

[0151] Input: User operation (clicking the confirmation button to exit)

[0152] Output: Official record of meeting end

[0153] Step 5:

[0154] To start recording a conference, the user enters the conference ID into the terminal.

[0155] As a specific example of operation, the user enters "meeting001" and clicks the "Start Recording" button.

[0156] Input: Meeting ID (meeting001)

[0157] Output: Recording start command

[0158] The server takes the current timestamp and combines it with the conference ID to generate the recording filename.

[0159] As a specific example of operation, the server generates a file name such as "meeting001_20231012_1500.wav".

[0160] Input: Meeting ID, current timestamp

[0161] Output: Recording file name (meeting001_20231012_1500.wav)

[0162] The recorded data is stored on the server and accumulated in a database along with the file name and timestamp.

[0163] As a specific example of operation, a recording file is generated and an entry called "meeting001_20231012_1500.wav" is saved in the database.

[0164] Input: Recording data, recording file name, timestamp

[0165] Output: Database entries

[0166] Step 6:

[0167] To search for past conference recordings, a user inputs a specific keyword (e.g., a conference ID) into the terminal.

[0168] As a specific example of operation, a user enters "meeting001" into the search form on the device and clicks the "Search" button.

[0169] Input: Search keyword (meeting001)

[0170] Output: Search results request

[0171] The server searches for recording files that match the keywords and displays the results to the user.

[0172] As a specific example of operation, the server searches the database and displays a list of search results including "meeting001_20231012_1500.wav".

[0173] Input: Search keywords, database

[0174] Output: Search results (meeting001_20231012_1500.wav)

[0175] Step 7:

[0176] The user provides the minutes and recording data generated after the meeting to the terminal.

[0177] As a specific example of operation, the user uploads the minutes text and provides the meeting recording file to the terminal by dragging and dropping it.

[0178] Input: minutes text, recording data file

[0179] Output: Data Request

[0180] The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database.

[0181] As a specific example of operation, the server analyzes the text of the minutes, extracts "ideas for improving the new product concept," and stores them in a database.

[0182] Input: minutes text, audio recording data

[0183] Output: Extracted ideas, database entries

[0184] Step 8:

[0185] A user uses a terminal to make a request to view the stored ideas.

[0186] As a specific example of operation, a user enters "new product proposal" into the "idea search" form on the terminal and clicks the "search" button.

[0187] Input: Idea search keyword (new product proposal)

[0188] Output: Search results request

[0189] The server searches the database for relevant ideas and displays the results in a list.

[0190] As a specific example of operation, the server searches for related ideas and displays results including "ideas for improving new product concepts" on the user's terminal.

[0191] Input: idea search keywords, database

[0192] Output: Search results (improvement ideas for new product concepts)

[0193] (Application example 1)

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

[0195] Meetings and discussions in modern manufacturing sites require efficient progress and record management. However, many meetings have long agendas, time management is inadequate, and important proposals and ideas are often not properly recorded. Furthermore, content discussed in previous meetings is rarely reused, making efficient management difficult. In addition, the reliance on human labor to conduct meetings in manufacturing sites is an obstacle to improving efficiency.

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

[0197] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes of the meeting, means for displaying the extracted ideas, and means for cooperating with factory robots to efficiently manage the progress of meetings at the manufacturing site. This makes it possible to effectively manage meetings at the manufacturing site and easily search for and reuse past discussions and proposals.

[0198] A "meeting agenda" refers to the specific topics or themes to be discussed at a meeting.

[0199] "Scheduled Time" refers to the planned time allocated for discussion of each agenda item.

[0200] "Means of notification" refers to the method or device for announcing the start or end of a meeting or the transition of agenda items.

[0201] "Means for managing progress" refers to a system or device that supervises the progress of a meeting in an orderly manner based on a set plan or agenda.

[0202] "Means for recording and storing audio" refers to systems or devices that record meeting conversations and discussions and store them as digital data.

[0203] "Means for searching recorded data" refers to a system or device that searches for previously recorded conference audio data using specific keywords or conditions.

[0204] "Means for extracting and storing ideas" refers to systems or devices that automatically extract important suggestions and ideas from audio recordings and minutes and store them in a database.

[0205] "Factory robots" refer to autonomous robots used to assist with work and manage meeting progress in manufacturing sites.

[0206] "Manufacturing site" refers to a location where products or parts are manufactured, such as a factory or production line.

[0207] "Means for efficiently managing the progress of meetings" refers to systems and devices that ensure that meetings proceed smoothly and that time management and agenda transitions are carried out effectively.

[0208] "Past recording data" refers to audio data recorded and stored during meetings and conferences.

[0209] The present invention introduces a factory robot into a conference management system to improve the efficiency of conference progress management and recording at manufacturing sites.

[0210] System programs and hardware

[0211] The system primarily utilizes the following hardware and software:

[0212] 1. Factory robot: Supports meeting management, recording, and notifications.

[0213] 2. Server: Stores recording data and minutes, and extracts and displays ideas.

[0214] 3. Device (smartphone or PC): Used by users to set the meeting agenda and search for recording data.

[0215] DETAILED DESCRIPTION OF THE INVENTION

[0216] 1. Setting the meeting agenda

[0217] The user inputs the meeting topic and scheduled time using the terminal, and the meeting agenda is set in the system. For example, "Production line optimization: 45 minutes" and "Equipment maintenance planning: 30 minutes."

[0218] 2. Starting and managing meetings

[0219] When a meeting begins, the factory robot announces the first item on the agenda based on the set agenda and then proceeds with the meeting. At the end of each item, it automatically notifies the user to move on to the next item.

[0220] 3. Starting recording and data accumulation

[0221] A factory robot records the meeting, and the server stores the recorded data. The server manages the recording files using the meeting ID and timestamp. For example, the server combines the meeting ID "meeting001" with the timestamp "20230101123000" and saves the file with the file name "meeting001_20230101123000.wav."

[0222] 4. End of meeting notice

[0223] When the meeting ends, the factory robot announces, "The meeting is ending."

[0224] 5. Searching and reusing stored data

[0225] When a user enters a specific keyword (e.g., "production line optimization") into the terminal, the server searches for relevant audio recordings and displays the results.

[0226] 6. Idea extraction and display

[0227] The server automatically extracts useful ideas from the recordings and minutes and stores them in a database, which users can then view using their devices.

[0228] Specific examples of system processing

[0229] Program processing description

[0230] Setting the meeting agenda: The server registers the topic and scheduled time entered by the user as an agenda in the system.

[0231] Meeting progress and management: The factory robot manages the time and notifies the start and end of each agenda item, which is recorded by the server.

[0232] Recording initiation and storage: The factory robot records the meeting audio, and the server stores the data using a timestamp and the meeting ID.

[0233] Searching audio recordings: When a user enters a search keyword, the server searches the stored audio recordings and returns the results.

[0234] Idea extraction and display: The server extracts important ideas from the recording data, stores them in a database, and displays them to the user.

[0235] Hardware and software used:

[0236] Factory robot: Announces and records meeting progress.

[0237] Server: Stores data, searches, and processes idea extraction.

[0238] Device (smartphone or PC): The user sets the agenda and searches for data.

[0239] Prompt Sentence Examples

[0240] "Please extract important suggestions and ideas from the following meeting recording: Meeting ID: Production Line Optimization_20231030120000.wav"

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

[0242] Step 1:

[0243] A user uses a terminal to input the meeting agenda and scheduled time. The input agenda and scheduled time are sent to the server and registered in the system as an agenda. At this time, the agenda and time are saved in the database. Example input data: "Production line optimization: 45 minutes", "Equipment maintenance plan: 30 minutes". The output is the meeting agenda saved on the server.

[0244] Step 2:

[0245] Before the meeting starts, the server sends the agenda data to the factory robot. The factory robot performs initialization and notifies the user when the meeting starts. Specifically, the robot announces, "The meeting will start." The output is a notification that the meeting has started.

[0246] Step 3:

[0247] When the meeting begins, the factory robot announces the first topic based on the agenda and the meeting proceeds. It notifies the user by voice when each topic begins and ends, and automatically notifies the user when the next topic will be discussed after a set time has elapsed. The server records this information. At this time, the robot announces, "We will begin optimizing the production line," and after 45 minutes, announces, "We will move on to the next topic."

[0248] Step 4:

[0249] When a user inputs a command to start recording a meeting, the factory robot starts recording and sends the audio data to the server in real time. The server generates a recording file name using the meeting ID and timestamp and saves it in a database. The input is the command to start the meeting, and the output is a recording data file with a timestamp. For example, the file name might be "meeting001_20230101123000.wav."

[0250] Step 5:

[0251] When the meeting ends, the factory robot notifies the server that the meeting is ending. The server recognizes this and saves the recording file. The output is a notification that the meeting has ended and that the recording has stopped.

[0252] Step 6:

[0253] The user inputs a command into the terminal to search for audio recordings using specific keywords. The server searches the database for matching files and displays the results to the user. For example, if the user searches for "production line optimization," a list of related audio recordings is displayed. The input is the search keyword, and the output is a list of search results.

[0254] Step 7:

[0255] The server automatically extracts useful ideas from audio recordings and meeting minutes. It uses a generative AI model to do this and stores the extracted ideas in a database. Data processing involves converting the audio data into text and extracting useful information. The output is a list of ideas. As a specific example, "ideas for new products" are extracted.

[0256] Step 8:

[0257] Users can use their terminals to view the accumulated ideas. The user inputs a request into the terminal, and the server searches the database for relevant ideas and displays a list of the results. The input is a request to view ideas, and the output is a list of ideas. An example of a prompt is, "Please extract important suggestions and ideas from the following meeting recording data. Meeting ID: Production Line Optimization_20231030120000.wav."

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

[0259] The system of the present invention not only manages the progress of a meeting, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage the meeting more effectively. Specific embodiments are described below.

[0260] Meeting progress management implementation example

[0261] 1. Setting the meeting agenda

[0262] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[0263] 2. Starting and managing meetings

[0264] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies the start and end of "Agenda A," and then moves on to "Agenda B."

[0265] 3. End of meeting notification

[0266] When all the agenda items have been completed, the terminal will notify the user that the meeting will end. The user will then confirm that they wish to end the meeting.

[0267] Embodiments of storing and searching audio data

[0268] 1. Starting recording and data accumulation

[0269] To start recording a conference, the user enters the conference ID into the terminal. After recording starts, the server stores the recorded data along with a timestamp.

[0270] 2. Search for recording data

[0271] The user inputs search keywords into the terminal to search for past recorded data. The server searches for recorded data based on the specified keywords and displays the results to the user.

[0272] Idea extraction and display embodiment

[0273] 1. Extracting ideas from minutes and audio recordings

[0274] Users provide minutes and audio recordings to their devices, and the server analyzes, extracts, and stores ideas from the data.

[0275] 2. Displaying accumulated ideas

[0276] A user uses a terminal to make a request to view the stored ideas, and the server searches the database for relevant ideas and displays them to the user.

[0277] Embodiment of Emotion Engine

[0278] 1. Incorporating an emotional engine

[0279] An emotion engine is built into the system, and the device analyzes the user's voice and facial expressions in real time during the meeting to generate emotion data.

[0280] 2. Use of Emotional Data

[0281] The server adjusts the progress of the meeting based on the emotional data collected in real time. For example, if a participant is feeling stressed during the meeting, it will suggest slowing down the progress or changing the agenda.

[0282] 3. Accumulation and analysis of emotional data

[0283] The server accumulates emotional data and later analyzes it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past emotional data, it is possible to determine the impact of specific agenda items on participants and the optimal way to proceed with a meeting.

[0284] Specific examples of program processing

[0285] 1. Setting the meeting agenda

[0286] The user sets up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[0287] 2. Meeting progress management

[0288] The device will start with "market analysis" and then move on to "new product proposals" after 30 minutes.

[0289] 3. Recording and Data Storage

[0290] The server saves the recording data of the meeting with a timestamp, such as "meeting001_20230415103000.wav."

[0291] 4. Searching for Recording Data

[0292] The user searches for "meeting001" and the server displays the relevant recordings.

[0293] 5. Idea extraction

[0294] If the minutes contain "ideas for improving new product concepts," the server extracts and stores them.

[0295] 6. Emotional Recognition and Regulation

[0296] The device uses an emotion engine to recognize when the user is feeling stressed during a meeting and adjusts the progress to ease the stress.

[0297] 7. Accumulation and analysis of emotional data

[0298] After the meeting ends, the server analyzes the accumulated emotional data and uses it to help guide the next meeting.

[0299] The above is a specific embodiment of the present invention. This system has the function of efficiently managing the progress of meetings, extracting and reusing useful ideas, and optimizing meetings based on the emotions of participants.

[0300] The processing flow will be explained below.

[0301] Meeting progress management process steps

[0302] Step 1:

[0303] The user sets the meeting topic and scheduled time using the terminal. Specifically, the user inputs the topic name and scheduled time for each topic (e.g., "Market Analysis (30 minutes)") and creates a meeting agenda.

[0304] Step 2:

[0305] The terminal notifies the user that the conference is about to begin. When the conference begins, the terminal displays the message "Conference is about to begin" to prompt the user to start the conference.

[0306] Step 3:

[0307] The terminal manages the progress of the meeting. Based on the set agenda, the terminal displays the items in order and monitors the scheduled time for each item. Users can proceed with the discussion according to the displayed items.

[0308] Step 4:

[0309] The terminal will notify the user when it is time to move on to the next topic. For example, after 30 minutes of "Market Analysis," the terminal will display the message, "The next topic is 'New Product Proposal (45 minutes)'."

[0310] Step 5:

[0311] The terminal notifies the user that the conference is over. When all the agenda items have been completed, the terminal displays the message "The conference is over" to notify the user that the conference is over.

[0312] Recording data storage and retrieval processing steps

[0313] Step 1:

[0314] To start recording a meeting, the user enters the meeting ID into the terminal. Presses the Start Recording button and enters the meeting ID (e.g., "meeting001").

[0315] Step 2:

[0316] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording file name (e.g., "meeting001_20230415103000.wav"). The recording data is saved on the server with this file name.

[0317] Step 3:

[0318] The user searches for recorded data. The user enters a specific keyword (e.g., "meeting001") into the terminal and makes a search request.

[0319] Step 4:

[0320] The server searches for recorded data. The server searches for recorded files in the specified directory based on keywords and displays the search results to the user.

[0321] Idea extraction and display process steps

[0322] Step 1:

[0323] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[0324] Step 2:

[0325] The server extracts ideas. The server analyzes the provided text and audio data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[0326] Step 3:

[0327] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[0328] Step 4:

[0329] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[0330] Processing Steps of Emotion Engine Embodiments

[0331] Step 1:

[0332] The system incorporates an emotion engine that analyzes the user's voice and facial expressions to generate emotion data in real time.

[0333] Step 2:

[0334] During a meeting, users input their voice and facial expressions into the device, which then sends the voice data and camera footage to the emotion engine for analysis.

[0335] Step 3:

[0336] The server receives the emotional data and adjusts the progress of the meeting. For example, if a participant feels stressed during the meeting, the server will use that information to suggest slowing down the progress.

[0337] Step 4:

[0338] The server accumulates emotional data. After the meeting ends, the emotional data is stored on the server and can be analyzed later.

[0339] Step 5:

[0340] The server analyzes the emotional data and generates feedback based on past emotional data to improve meeting efficiency and participant satisfaction, which can be used for future meetings.

[0341] These are the specific processing steps of the system that combines the emotion engine. As a result, the system efficiently manages the progress of meetings and provides an optimal discussion environment that reflects the emotions of participants.

[0342] Example 2

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

[0344] While conventional conferencing systems provide basic functions such as meeting progress management, storing and searching recorded data, and extracting and displaying ideas, they are limited in their ability to optimize meeting progress while taking participants' emotions into account. Furthermore, they lack the ability to effectively utilize stored recorded data, reuse past discussions, or analyze participants' emotions in real time and adjust meetings accordingly. This creates challenges that make it difficult to improve meeting efficiency and participant satisfaction.

[0345] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for setting the agenda and scheduled time of the conference, means for notifying the start and end of the conference, means for managing the progress of the conference based on a plan, means for recording and storing the audio of the conference, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, means for analyzing the user's voice and facial expression to generate emotional data, means for adjusting the progress of the conference based on the generated emotional data, and means for accumulating and analyzing the emotional data. This makes it possible to optimize the management of the progress of the conference by taking into account the emotional state of each participant, thereby improving the efficiency of the conference and the satisfaction of the participants.

[0346] The "means for setting the agenda and scheduled time of the meeting" is a means for providing a function for the user to input and save the name of each agenda item and the scheduled time of each meeting.

[0347] The "means for notifying the start and end of a conference" is a means for providing a function for notifying a user of the start and end timing of a conference.

[0348] The "means for managing the progress of a meeting based on a plan" is a means for automatically managing the progress of a meeting according to a preset meeting agenda.

[0349] "Means for recording and storing conference audio" refers to means for providing a function for recording audio during a conference and storing it in a database or the like.

[0350] The "means for searching stored recorded data" refers to a means for providing a function for searching for a specific recording using a search keyword from stored recorded data.

[0351] "Means for extracting and storing ideas from audio recordings and minutes" refers to means for providing a function for analyzing, extracting, and storing useful ideas from audio recordings and minutes.

[0352] The "means for displaying extracted ideas" is a means for providing a function for displaying accumulated ideas to a user.

[0353] The "means for analyzing the user's voice and facial expression and generating emotion data" is a means for providing a function for analyzing the content of what the user says and the facial expression and generating emotion data.

[0354] The "means for adjusting the progress of a meeting based on the generated emotion data" is a means for providing a function for adjusting the progress speed and content of a meeting by using the generated emotion data in real time.

[0355] "Means for storing and analyzing emotional data" refers to a means for storing collected emotional data in a database and providing a function for later analysis.

[0356] The system of the present invention not only manages the progress of meetings, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage meetings more effectively. Specific embodiments of this system are described below.

[0357] Meeting progress management

[0358] To manage the progress of a meeting, the user first sets up the meeting agenda using their terminal. The user logs in and enters each topic and the scheduled time on the "Meeting Agenda Settings" screen. This information is sent from the terminal to the server, and the server stores the received agenda in a database. For example, a user can set up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[0359] When a meeting starts, the terminal notifies the user that the meeting has started based on the set agenda. The terminal manages the progress of each agenda item, for example, starting a timer for "Market Analysis (30 minutes)" and notifying the user to move on to "New Product Proposal (45 minutes)" after 30 minutes. When all agenda items have been completed, the terminal notifies the user that "The meeting will end," and the user confirms the end of the meeting.

[0360] Storage and retrieval of recorded data

[0361] To store recording data for a meeting, a user enters the meeting ID into their device and starts recording. The recorded data is sent to the server and saved as a file with a timestamp, such as "meeting001_20230415103000.wav."

[0362] Users can search for past recordings by entering search keywords into their devices. The server searches the database based on the keywords and provides relevant recording files to the user. For example, if a user enters "meeting001," the server will search for and display relevant recordings.

[0363] Idea extraction and display

[0364] It also has the ability to extract useful ideas from meeting minutes and audio recordings. When users provide minutes and audio recordings to their devices, the server analyzes the data, extracts ideas, and stores them. For example, if the minutes contain "ideas for improving new product concepts," the server extracts these and stores them in a database.

[0365] A user can use a terminal to make a request to view the stored ideas, and the server will search the database for relevant ideas and display them to the user.

[0366] Emotion Engine

[0367] The emotion engine is used to analyze the user's voice and facial expressions in real time during a meeting and generate emotion data. The device analyzes the user's voice and camera footage during the meeting, generates emotion data such as "stress" and "joy," and sends it to the server.

[0368] Based on the generated emotion data, the server can adjust the progress of the meeting. For example, if the emotion data indicates "increasing stress," the device will notify the user and suggest relaxing the progress of the meeting or changing the agenda.

[0369] The server stores the emotional data in a database and analyzes it after the meeting. This allows it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past data, it can identify the impact of specific agenda items on participants and the optimal way to proceed with the meeting.

[0370] Prompt Sentence Examples

[0371] Prompt: "Please give us an overview of a system that can manage meeting progress, store recording data, extract and display ideas, and recognize emotions."

[0372] Prompt: "Tell me how to adjust meeting flow based on emotional data."

[0373] This system enables efficient management of the progress of meetings, reuses accumulated data, and adjusts the progress based on the emotions of participants, thereby improving meeting efficiency and participant satisfaction.

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

[0375] Meeting progress management implementation example

[0376] Step 1:

[0377] The user logs in to the terminal and accesses the "Meeting Agenda Settings" screen. The user enters the topic name and scheduled time for each agenda item and clicks the "Save Agenda" button. The entered information, which is the topic name and scheduled time, is sent from the terminal to the server. The server receives the data and saves it in a database. As a specific example of operation, the user enters and saves "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[0378] Step 2:

[0379] The server sends instructions to the terminal notifying the start of the meeting based on pre-set agenda information. The terminal receives the instructions and displays a meeting start notification to the user. The user clicks the "Start Meeting" button to start the meeting. The terminal then proceeds with the agenda according to the set agenda. As a specific example of operation, a timer for "Market Analysis (30 minutes)" is started, and when the timer reaches 30 minutes, a notification is sent to move on to the next item, "New Product Proposal."

[0380] Step 3:

[0381] When all the agenda items have been completed, the server sends a notification to end the meeting to the terminal, and the terminal displays "Ending the meeting." The user clicks the "Confirm End" button, and the meeting officially ends. The server records the end information in the database.

[0382] Embodiments of storing and searching audio data

[0383] Step 1:

[0384] To start recording a meeting on a device, a user enters the meeting ID and presses the "Start Recording" button. The input data is the meeting ID. The device starts recording and transfers the data to the server. The server saves the received recording data with a file name that includes a timestamp, such as "meeting001_20230415103000.wav."

[0385] Step 2:

[0386] To search for recorded data, a user enters a search keyword into the device and clicks the "Search" button. The input data is the search keyword. The server searches the database based on the received keyword and extracts related recorded data. The server returns a list of extracted recorded files to the device, which then displays it to the user. As a specific example of operation, entering "meeting001" will display related recorded data.

[0387] Idea extraction and display embodiment

[0388] Step 1:

[0389] The user uploads meeting minutes or audio recordings to the device. The input data is the minutes or audio recording files. The device transfers the data to the server, which analyzes the data and extracts useful ideas. For example, it generates tags such as "ideas for improving a new product concept" and stores them in a database.

[0390] Step 2:

[0391] A user makes a request to view ideas stored on a terminal. The input data is the view request. The server receives the request and searches the database for related ideas. The server returns the search results to the terminal, which displays them to the user. As a specific example of operation, when a user requests an "idea list," related ideas are displayed.

[0392] Embodiment of Emotion Engine

[0393] Step 1:

[0394] The system is equipped with an emotion engine that analyzes the user's voice and facial expressions in real time to generate emotion data. The input data is the user's voice and camera footage. The device analyzes this data to generate emotion data such as "stress" or "joy" and sends it to the server. As a specific example, the emotion engine analyzes the content of the user's remarks and changes in facial expressions during a meeting.

[0395] Step 2:

[0396] Based on the generated emotion data, the server adjusts the progress of the meeting. The input data is emotion data. The server analyzes the received emotion data and sends instructions to the terminal suggesting changes to the progress speed or agenda as necessary. The terminal notifies the user of the instructions. A specific example of operation is a notification that "stress is increasing" and a suggestion to ease the progress.

[0397] Step 3:

[0398] After the meeting ends, the server stores the collected emotional data in a database for later analysis. The input data is the emotional data collected during the meeting. The server analyzes the data, determines the impact that specific agenda items had on participants, and the optimal way to proceed with the meeting, and provides feedback. A specific example of how it works is to generate analysis results such as "a specific agenda item caused the most stress."

[0399] (Application example 2)

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

[0401] Conventional meeting management systems have basic functions such as agenda and progress management, recording and search, and idea extraction and display. However, they lack the ability to analyze participants' emotions in real time to optimize the progress of the meeting. This can easily lead to situations where participants feel stressed or dissatisfied, reducing the efficiency and effectiveness of the meeting. Furthermore, particularly in dynamic environments such as factory floors, flexible meeting management that can respond to emotional fluctuations is required.

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

[0403] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, and means for analyzing the emotions of participants in real time and adjusting the progress. This allows the progress of the meeting to be optimized in accordance with the emotional state of the participants, enabling efficient and satisfying meeting management.

[0404] A "means for setting the meeting agenda and scheduled time" is a device or software for predetermining and recording the main topics of a meeting and the time allotted for each topic.

[0405] The "means for notifying the start and end of a conference" refers to a device or software for notifying participants of the start and end times of a conference.

[0406] A "means for managing the progress of a meeting based on a plan" is a device or software for supervising and coordinating the progress of a meeting according to a set agenda and scheduled time.

[0407] "Means for recording and storing conference audio" refers to a device or software that records the audio during a conference and stores the data in a form that can be accessed later.

[0408] "Means for searching stored recorded data" refers to a device or software that searches stored recorded data based on specified keywords or conditions and obtains the required information.

[0409] "Means for extracting and storing ideas from audio recordings and minutes" refers to devices or software that select useful ideas from the content discussed during meetings and audio recordings, and store them in a reusable form.

[0410] The "means for displaying extracted ideas" is a device or software for visually displaying extracted ideas.

[0411] "Means for analyzing participants' emotions in real time and adjusting the progress" refers to a device or software that analyzes the voices and facial expressions of participants during a meeting and dynamically adjusts the progress of the meeting based on their emotional state.

[0412] The system of this invention is an application for managing robot operation and maintenance meetings in factories, analyzing participants' emotions in real time, and optimizing the progress of the meetings. This application is installed on smart glasses and realizes the following functions.

[0413] Setting the Meeting Agenda

[0414] Users use the smart glasses to set the meeting agenda and scheduled time. Users create a meeting agenda by entering the topic name and scheduled time for each topic through the smart glasses interface. For example, equipment maintenance can be scheduled for 30 minutes, and the proposal to introduce a new robot can be scheduled for 45 minutes.

[0415] Meeting progress management

[0416] The smart glasses notify the start of a meeting based on the set agenda. The user starts the meeting, and the smart glasses manage the progress of each agenda item according to the time allocation. For example, if equipment maintenance begins, the glasses will automatically move on to the proposal to introduce a new robot 30 minutes later.

[0417] Storage and retrieval of recorded data

[0418] The smart glasses record and store the audio of meetings. The server saves the recordings with timestamps and stores them in a searchable format. Users can easily search and view past recordings by entering search keywords.

[0419] Idea extraction and display

[0420] Users provide recorded data, and the server analyzes, extracts, and stores ideas from the data. When a user makes a viewing request, relevant ideas are displayed on the smart glasses. For example, new maintenance methods and improvement ideas recorded during a meeting can be extracted.

[0421] Use of emotion engine

[0422] An emotion engine is built into the device, and emotion data is generated by analyzing the user's voice and facial expressions in real time. The server adjusts the progress of the meeting based on the emotion data collected in real time. For example, if a participant in a meeting is feeling stressed, it may suggest slowing down the progress. After the meeting, emotion data is accumulated and analyzed, and improvement measures that will lead to increased meeting efficiency and participant satisfaction are provided.

[0423] Hardware and software used

[0424] This system uses the following hardware and software:

[0425] 1. Smart glasses: Provides data collection and user interface.

[0426] 2. Emotion engine: An AI model that analyzes speech and facial expressions (e.g., Emotional Analysis API).

[0427] 3. Recording and retrieval server: A cloud server for storing, searching, and analyzing recording data (e.g., cloud storage and search engine).

[0428] 4. Data analysis engine: An AI model (e.g., a Natural Language Processing model) that analyzes and extracts useful ideas and maintenance techniques from recorded data.

[0429] Examples and prompts

[0430] For example, a factory manager schedules a meeting and inputs the following agenda items: "Equipment maintenance (30 minutes)" and "Proposal for introducing a new robot (45 minutes)." As the meeting progresses, the smart glasses analyze the user's emotions and adjust the progress at the appropriate time.

[0431] Example prompt sentence:

[0432] "Please set up today's meeting agenda. 'Facility Maintenance' takes 30 minutes, and 'New Robot Implementation Proposal' takes 45 minutes."

[0433] "Analyze participants' emotions in real time during the meeting and adjust the pace if they are feeling stressed."

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

[0435] Step 1:

[0436] A user uses smart glasses to set the meeting agenda and scheduled time. The user inputs the agenda name and the scheduled time for each agenda item. This input data is received by the device and set as the meeting agenda. The input data can be "equipment maintenance (30 minutes)" or "proposed introduction of a new robot (45 minutes)," and the output data is the set agenda.

[0437] Step 2:

[0438] The terminal notifies the start of the conference based on the set agenda. The user confirms the start. A start signal is sent to the server, and the conference begins. The input data is the conference start confirmation from the user, and the output data is the conference start notification.

[0439] Step 3:

[0440] The terminal manages the progress of the meeting based on the time allocation of each agenda item. It notifies the start and end of each agenda item and automatically moves on to the next agenda item. The input data is the agenda setting information and elapsed time, and the output data is the start and end notification of each agenda item.

[0441] Step 4:

[0442] The smart glasses record the audio during the meeting and send the data to the server, which stores the recorded data with a timestamp. The input data is real-time audio data, and the output data is a time-stamped audio file.

[0443] Step 5:

[0444] The user inputs keywords into the terminal to search for recorded data. The server searches for recorded data based on the keywords and displays the results to the user. The input data are the search keywords, and the output data are the recorded data as search results.

[0445] Step 6:

[0446] Users provide audio recordings and minutes, and the server analyzes and extracts ideas from the data. The extracted ideas are stored in a database. The input data is the audio recordings and minutes, and the output data is the extracted ideas.

[0447] Step 7:

[0448] A user makes a request to browse stored ideas using a terminal. The server searches the database for relevant ideas and displays them to the user. The input data is the browsing request, and the output data is the displayed ideas.

[0449] Step 8:

[0450] The device uses an emotion engine to analyze the user's voice and facial expressions during the meeting and generate emotion data in real time. The input data is the user's voice and facial expression data, and the output data is the analyzed emotion data.

[0451] Step 9:

[0452] The server adjusts the progress of the meeting based on the emotion data collected in real time, adjusting the progress speed according to the emotion data and proposing changes to the agenda as necessary. The input data is the real-time emotion data, and the output data is the adjusted progress instructions.

[0453] Step 10:

[0454] After the meeting, the server analyzes the accumulated emotional data and provides feedback to improve the efficiency of the meeting and the satisfaction of the participants. The input data is the accumulated emotional data, and the output data is the feedback information.

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

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

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

[0458] [Second embodiment]

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

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

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

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

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

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

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

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

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

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

[0469] In the smart glasses 214, the 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.

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

[0471] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. An example of this system is shown below.

[0472] Meeting progress management implementation example

[0473] 1. Setting the meeting agenda

[0474] Users set up a meeting agenda by entering the meeting topic and scheduled time into their terminal. This agenda includes the topic name and the scheduled time allocated to each topic. For example, a meeting topic could be "market analysis" and "new product proposal," with 30 minutes and 45 minutes allocated to each topic, respectively.

[0475] 2. Starting and managing meetings

[0476] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies that the "market analysis" agenda item has started, and notifies the user to move on to the next agenda item, "new product proposal," after 30 minutes have passed.

[0477] 3. End of meeting notification

[0478] When the conference ends, the terminal notifies the user that the conference is ending.

[0479] Embodiments of storing and searching audio data

[0480] 1. Starting recording and data accumulation

[0481] To start recording a meeting, a user enters the meeting ID into their device. The server obtains the current timestamp and combines it with the meeting ID to generate a recording filename. The recording data is saved on the server and stored in a database along with the file name and timestamp.

[0482] 2. Search for recording data

[0483] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into their device. The server searches for recording files that match the keyword and displays the results to the user. For example, if a user searches for the keyword "meeting001," a list of recording data related to this meeting ID will be displayed.

[0484] Idea extraction and display embodiment

[0485] 1. Extracting ideas from minutes and audio recordings

[0486] Users provide the minutes and audio recordings generated after the meeting to their devices. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, if the minutes contain "ideas for improving a new product concept," they will be automatically extracted.

[0487] 2. Displaying accumulated ideas

[0488] A user can use a terminal to request to view the accumulated ideas. The server searches the database for relevant ideas and displays the results in a list. This allows the user to review and reuse useful suggestions made in past meetings.

[0489] The above-described embodiments of the present invention provide a system that enables efficient management of the progress of meetings and the reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

[0490] The processing flow will be explained below.

[0491] Meeting progress management process steps

[0492] Step 1:

[0493] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[0494] Step 2:

[0495] The terminal notifies the user that the conference is about to begin. The terminal displays the message "Conference is about to begin" to notify the user that the conference is about to begin.

[0496] Step 3:

[0497] The terminal manages the progress of the meeting. Based on the agenda, the terminal displays the items in order and monitors and measures the scheduled time for each item. Users proceed with the discussion according to the displayed items.

[0498] Step 4:

[0499] When the time for each topic has elapsed, the device will notify the user to move on to the next topic. For example, when 30 minutes have elapsed for "Market Analysis," the device will display the next topic, such as "New Product Proposal."

[0500] Step 5:

[0501] When all the agenda items have been covered, the terminal notifies the user that the conference is over. The terminal displays the message "The conference is ending" to inform the user that the conference is over.

[0502] Recording data storage and retrieval processing steps

[0503] Step 1:

[0504] To start recording a conference, the user enters the conference ID into the terminal and presses the record button to start recording.

[0505] Step 2:

[0506] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording filename. The server saves the recording data in the specified directory based on the generated filename.

[0507] Step 3:

[0508] The user searches for recorded data. The user enters search keywords (such as the meeting ID or related topic) into the device and makes a search request.

[0509] Step 4:

[0510] The server searches for recorded data. The server searches for recorded files in the specified directory based on the keyword and displays a list of search results. If a recorded data matching the keyword is found, the file name and detailed information are provided to the user.

[0511] Idea extraction and display process steps

[0512] Step 1:

[0513] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[0514] Step 2:

[0515] The server extracts ideas. The server analyzes the provided text data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[0516] Step 3:

[0517] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[0518] Step 4:

[0519] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[0520] These are the specific processing steps of the system. Each step is realized through cooperation between users, terminals, and servers, and supports efficient management of the progress of meetings and the reuse of useful ideas.

[0521] Example 1

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

[0523] Conventional conference management systems can manage the progress of meetings and store recorded data, but they have difficulty efficiently extracting and reusing useful information discussed during meetings. This results in problems such as the content of meetings not being managed systematically, making it difficult to reuse information. Furthermore, meeting time management is sometimes inappropriate, which can reduce the efficiency of meetings.

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

[0525] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing useful information from the recorded data and minutes, and means for displaying the extracted useful information. This enables efficient progress management of the meeting and reuse of recorded meeting content and ideas.

[0526] A "meeting agenda" refers to the specific themes or topics that will be addressed at the meeting.

[0527] "Scheduled time" refers to the predetermined time frame for each agenda item.

[0528] The "means for notifying the start and end of a conference" refers to a function for notifying the user of the start and end times of a conference.

[0529] "Means for managing the progress of a meeting based on a plan" refers to the function of managing the progress of a meeting based on a pre-set agenda.

[0530] "Means for recording and storing conference audio" refers to the function for recording audio during a conference and saving that data.

[0531] "Means for searching stored recorded data" refers to the function of searching stored recorded data based on specific conditions.

[0532] "Means for extracting and storing useful information from audio recordings and minutes" refers to the ability to extract useful ideas and information from audio recordings and written minutes and store them in a database.

[0533] "Means for displaying extracted useful information" refers to a function for visually presenting useful information stored in the database to the user.

[0534] "Time information" refers to information that indicates the current time or the time when a specific event occurred.

[0535] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. A specific embodiment of this system is shown below.

[0536] Meeting progress management implementation example

[0537] The user first inputs the meeting topic and scheduled time into the terminal to set up the meeting agenda. The agenda includes the topic name and the allocated time for each topic. For example, the user may set the topics "Market Analysis" and "New Product Proposal" and allocate 30 and 45 minutes for each topic. The terminal receives the input information and generates the meeting agenda.

[0538] Next, the device notifies the user that the meeting is about to begin based on the set agenda. For example, it displays a pop-up message saying, "Please begin the meeting." Once the user starts the meeting, the device manages the progress of each agenda item according to the time allocation. Specifically, the device notifies the user that the "Market Analysis" agenda item has begun, and after 30 minutes has passed, it notifies the user, "Please move on to the next agenda item, 'New Product Proposal.'" This allows the user to proceed with the meeting under appropriate time management. When the meeting ends, the device notifies the user that "The meeting is ending," and once the user confirms the end, the recording of the meeting is officially completed.

[0539] Embodiments of storing and searching audio data

[0540] To efficiently record important discussions during a meeting, a user enters the meeting ID into their device to start recording the meeting. For example, they enter "meeting001" and click the "Start Recording" button. The server obtains the current timestamp and combines it with the meeting ID to generate a recording file name. Specifically, it generates a file name such as "meeting001_20231012_1500.wav." The recording data is saved on the server and accumulated in a database along with the file name and timestamp.

[0541] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into the terminal. For example, they enter "meeting001" into the search form and click the "Search" button. The server searches for recording files that match the keyword and displays the results to the user. Specifically, search results including "meeting001_20231012_1500.wav" are displayed in a list.

[0542] Idea extraction and display embodiment

[0543] After the meeting, the user provides the generated minutes and recording data to the device. Specifically, the user uploads the minutes text and drags and drops the meeting recording file to the device. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, the server analyzes the minutes text to extract "ideas for improving new product concepts" and stores them in the database.

[0544] A user uses a device to request to view the stored ideas. For example, the user enters "new product proposal" into the search form and clicks the "Search" button. The server searches for related ideas and displays results including "improvement ideas for new product concepts" on the user's device.

[0545] Examples of prompt statements

[0546] For example, when setting a meeting agenda, a user might enter:

[0547] "I'd like to set aside 30 minutes for market analysis and 45 minutes for new product proposals."

[0548] Also, if you want to search for recording data for a specific meeting ID, "meeting001," enter the following:

[0549] "meeting001"

[0550] Furthermore, if you want to review the accumulated ideas, you can make a request to the generative AI model with the following prompt:

[0551] "Show me new product proposal ideas extracted from past meetings."

[0552] Through these specific operations, the system of the present invention enables efficient management of meeting progress and reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

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

[0554] Step 1:

[0555] The user inputs the agenda and scheduled time of the meeting into the terminal.

[0556] As a specific example of operation, a user inputs "market analysis," "30 minutes," "new product proposal," and "45 minutes" into an input form on a terminal.

[0557] Input: Meeting agenda (market analysis, new product proposal), estimated time for each agenda item (30 minutes, 45 minutes)

[0558] Output: Meeting agenda (market analysis: 30 minutes, new product proposal: 45 minutes)

[0559] The terminal receives the input information and generates a meeting agenda.

[0560] Step 2:

[0561] The terminal notifies the user of the start of the conference based on the set agenda.

[0562] As a specific example of how this works, a pop-up message will appear saying "Please start the meeting."

[0563] Input: Meeting agenda

[0564] Output: Notification of meeting start

[0565] The user clicks the Start Conference button.

[0566] As a specific example of operation, the user clicks the "Start" button.

[0567] Input: User action (clicking the start button)

[0568] Output:Confirmation of meeting start

[0569] Step 3:

[0570] The terminal manages the progress of each agenda item according to the time allocation.

[0571] As a specific example of operation, the terminal notifies by voice or on the screen that the topic "Market Analysis" has started.

[0572] Input: Meeting agenda, meeting start confirmation

[0573] Output: Agenda start notification (market analysis, new product proposal in 30 minutes)

[0574] After 30 minutes, a notice will be given to move on to the next agenda item, "New product proposals."

[0575] As a specific example of how it works, the terminal will display, "The next topic is 'New product proposals.'"

[0576] Input: Time passed (30 minutes)

[0577] Output: Next Agenda Notification

[0578] Step 4:

[0579] When the conference ends, the terminal notifies the user of the end of the conference.

[0580] As a specific example of operation, the message "The meeting will end" is displayed and an audio notification is also given.

[0581] Input: Meeting agenda complete, all items closed

[0582] Output: Notification of end of meeting

[0583] The user confirms the end of the conference.

[0584] As a specific example of the operation, the user clicks the "Confirm termination" button.

[0585] Input: User operation (clicking the confirmation button to exit)

[0586] Output: Official record of meeting end

[0587] Step 5:

[0588] To start recording a conference, the user enters the conference ID into the terminal.

[0589] As a specific example of operation, the user enters "meeting001" and clicks the "Start Recording" button.

[0590] Input: Meeting ID (meeting001)

[0591] Output: Recording start command

[0592] The server takes the current timestamp and combines it with the conference ID to generate the recording filename.

[0593] As a specific example of operation, the server generates a file name such as "meeting001_20231012_1500.wav".

[0594] Input: Meeting ID, current timestamp

[0595] Output: Recording file name (meeting001_20231012_1500.wav)

[0596] The recorded data is stored on the server and accumulated in a database along with the file name and timestamp.

[0597] As a specific example of operation, a recording file is generated and an entry called "meeting001_20231012_1500.wav" is saved in the database.

[0598] Input: Recording data, recording file name, timestamp

[0599] Output: Database entries

[0600] Step 6:

[0601] To search for past conference recordings, a user inputs a specific keyword (e.g., a conference ID) into the terminal.

[0602] As a specific example of operation, a user enters "meeting001" into the search form on the device and clicks the "Search" button.

[0603] Input: Search keyword (meeting001)

[0604] Output: Search results request

[0605] The server searches for recording files that match the keywords and displays the results to the user.

[0606] As a specific example of operation, the server searches the database and displays a list of search results including "meeting001_20231012_1500.wav".

[0607] Input: Search keywords, database

[0608] Output: Search results (meeting001_20231012_1500.wav)

[0609] Step 7:

[0610] The user provides the minutes and recording data generated after the meeting to the terminal.

[0611] As a specific example of operation, the user uploads the minutes text and provides the meeting recording file to the terminal by dragging and dropping it.

[0612] Input: minutes text, recording data file

[0613] Output: Data Request

[0614] The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database.

[0615] As a specific example of operation, the server analyzes the text of the minutes, extracts "ideas for improving the new product concept," and stores them in a database.

[0616] Input: minutes text, audio recording data

[0617] Output: Extracted ideas, database entries

[0618] Step 8:

[0619] A user uses a terminal to make a request to view the stored ideas.

[0620] As a specific example of operation, a user enters "new product proposal" into the "idea search" form on the terminal and clicks the "search" button.

[0621] Input: Idea search keyword (new product proposal)

[0622] Output: Search results request

[0623] The server searches the database for relevant ideas and displays the results in a list.

[0624] As a specific example of operation, the server searches for related ideas and displays results including "ideas for improving new product concepts" on the user's terminal.

[0625] Input: idea search keywords, database

[0626] Output: Search results (improvement ideas for new product concepts)

[0627] (Application example 1)

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

[0629] Meetings and discussions in modern manufacturing sites require efficient progress and record management. However, many meetings have long agendas, time management is inadequate, and important proposals and ideas are often not properly recorded. Furthermore, content discussed in previous meetings is rarely reused, making efficient management difficult. In addition, the reliance on human labor to conduct meetings in manufacturing sites is an obstacle to improving efficiency.

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

[0631] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes of the meeting, means for displaying the extracted ideas, and means for cooperating with factory robots to efficiently manage the progress of meetings at the manufacturing site. This makes it possible to effectively manage meetings at the manufacturing site and easily search for and reuse past discussions and proposals.

[0632] A "meeting agenda" refers to the specific topics or themes to be discussed at a meeting.

[0633] "Scheduled Time" refers to the planned time allocated for discussion of each agenda item.

[0634] "Means of notification" refers to the method or device for announcing the start or end of a meeting or the transition of agenda items.

[0635] "Means for managing progress" refers to a system or device that supervises the progress of a meeting in an orderly manner based on a set plan or agenda.

[0636] "Means for recording and storing audio" refers to systems or devices that record meeting conversations and discussions and store them as digital data.

[0637] "Means for searching recorded data" refers to a system or device that searches for previously recorded conference audio data using specific keywords or conditions.

[0638] "Means for extracting and storing ideas" refers to systems or devices that automatically extract important suggestions and ideas from audio recordings and minutes and store them in a database.

[0639] "Factory robots" refer to autonomous robots used to assist with work and manage meeting progress in manufacturing sites.

[0640] "Manufacturing site" refers to a location where products or parts are manufactured, such as a factory or production line.

[0641] "Means for efficiently managing the progress of meetings" refers to systems and devices that ensure that meetings proceed smoothly and that time management and agenda transitions are carried out effectively.

[0642] "Past recording data" refers to audio data recorded and stored during meetings and conferences.

[0643] The present invention introduces a factory robot into a conference management system to improve the efficiency of conference progress management and recording at manufacturing sites.

[0644] System programs and hardware

[0645] The system primarily utilizes the following hardware and software:

[0646] 1. Factory robot: Supports meeting management, recording, and notifications.

[0647] 2. Server: Stores recording data and minutes, and extracts and displays ideas.

[0648] 3. Device (smartphone or PC): Used by users to set the meeting agenda and search for recording data.

[0649] DETAILED DESCRIPTION OF THE INVENTION

[0650] 1. Setting the meeting agenda

[0651] The user inputs the meeting topic and scheduled time using the terminal, and the meeting agenda is set in the system. For example, "Production line optimization: 45 minutes" and "Equipment maintenance planning: 30 minutes."

[0652] 2. Starting and managing meetings

[0653] When a meeting begins, the factory robot announces the first item on the agenda based on the set agenda and then proceeds with the meeting. At the end of each item, it automatically notifies the user to move on to the next item.

[0654] 3. Starting recording and data accumulation

[0655] A factory robot records the meeting, and the server stores the recorded data. The server manages the recording files using the meeting ID and timestamp. For example, the server combines the meeting ID "meeting001" with the timestamp "20230101123000" and saves the file with the file name "meeting001_20230101123000.wav."

[0656] 4. End of meeting notice

[0657] When the meeting ends, the factory robot announces, "The meeting is ending."

[0658] 5. Searching and reusing stored data

[0659] When a user enters a specific keyword (e.g., "production line optimization") into the terminal, the server searches for relevant audio recordings and displays the results.

[0660] 6. Idea extraction and display

[0661] The server automatically extracts useful ideas from the recordings and minutes and stores them in a database, which users can then view using their devices.

[0662] Specific examples of system processing

[0663] Program processing description

[0664] Setting the meeting agenda: The server registers the topic and scheduled time entered by the user as an agenda in the system.

[0665] Meeting progress and management: The factory robot manages the time and notifies the start and end of each agenda item, which is recorded by the server.

[0666] Recording initiation and storage: The factory robot records the meeting audio, and the server stores the data using a timestamp and the meeting ID.

[0667] Searching audio recordings: When a user enters a search keyword, the server searches the stored audio recordings and returns the results.

[0668] Idea extraction and display: The server extracts important ideas from the recording data, stores them in a database, and displays them to the user.

[0669] Hardware and software used:

[0670] Factory robot: Announces and records meeting progress.

[0671] Server: Stores data, searches, and processes idea extraction.

[0672] Device (smartphone or PC): The user sets the agenda and searches for data.

[0673] Prompt Sentence Examples

[0674] "Please extract important suggestions and ideas from the following meeting recording: Meeting ID: Production Line Optimization_20231030120000.wav"

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

[0676] Step 1:

[0677] A user uses a terminal to input the meeting agenda and scheduled time. The input agenda and scheduled time are sent to the server and registered in the system as an agenda. At this time, the agenda and time are saved in the database. Example input data: "Production line optimization: 45 minutes", "Equipment maintenance plan: 30 minutes". The output is the meeting agenda saved on the server.

[0678] Step 2:

[0679] Before the meeting starts, the server sends the agenda data to the factory robot. The factory robot performs initialization and notifies the user when the meeting starts. Specifically, the robot announces, "The meeting will start." The output is a notification that the meeting has started.

[0680] Step 3:

[0681] When the meeting begins, the factory robot announces the first topic based on the agenda and the meeting proceeds. It notifies the user by voice when each topic begins and ends, and automatically notifies the user when the next topic will be discussed after a set time has elapsed. The server records this information. At this time, the robot announces, "We will begin optimizing the production line," and after 45 minutes, announces, "We will move on to the next topic."

[0682] Step 4:

[0683] When a user inputs a command to start recording a meeting, the factory robot starts recording and sends the audio data to the server in real time. The server generates a recording file name using the meeting ID and timestamp and saves it in a database. The input is the command to start the meeting, and the output is a recording data file with a timestamp. For example, the file name might be "meeting001_20230101123000.wav."

[0684] Step 5:

[0685] When the meeting ends, the factory robot notifies the server that the meeting is ending. The server recognizes this and saves the recording file. The output is a notification that the meeting has ended and that the recording has stopped.

[0686] Step 6:

[0687] The user inputs a command into the terminal to search for audio recordings using specific keywords. The server searches the database for matching files and displays the results to the user. For example, if the user searches for "production line optimization," a list of related audio recordings is displayed. The input is the search keyword, and the output is a list of search results.

[0688] Step 7:

[0689] The server automatically extracts useful ideas from audio recordings and meeting minutes. It uses a generative AI model to do this and stores the extracted ideas in a database. Data processing involves converting the audio data into text and extracting useful information. The output is a list of ideas. As a specific example, "ideas for new products" are extracted.

[0690] Step 8:

[0691] Users can use their terminals to view the accumulated ideas. The user inputs a request into the terminal, and the server searches the database for relevant ideas and displays a list of the results. The input is a request to view ideas, and the output is a list of ideas. An example of a prompt is, "Please extract important suggestions and ideas from the following meeting recording data. Meeting ID: Production Line Optimization_20231030120000.wav."

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

[0693] The system of the present invention not only manages the progress of a meeting, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage the meeting more effectively. Specific embodiments are described below.

[0694] Meeting progress management implementation example

[0695] 1. Setting the meeting agenda

[0696] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[0697] 2. Starting and managing meetings

[0698] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies the start and end of "Agenda A," and then moves on to "Agenda B."

[0699] 3. End of meeting notification

[0700] When all the agenda items have been completed, the terminal will notify the user that the meeting will end. The user will then confirm that they wish to end the meeting.

[0701] Embodiments of storing and searching audio data

[0702] 1. Starting recording and data accumulation

[0703] To start recording a conference, the user enters the conference ID into the terminal. After recording starts, the server stores the recorded data along with a timestamp.

[0704] 2. Search for recording data

[0705] The user inputs search keywords into the terminal to search for past recorded data. The server searches for recorded data based on the specified keywords and displays the results to the user.

[0706] Idea extraction and display embodiment

[0707] 1. Extracting ideas from minutes and audio recordings

[0708] Users provide minutes and audio recordings to their devices, and the server analyzes, extracts, and stores ideas from the data.

[0709] 2. Displaying accumulated ideas

[0710] A user uses a terminal to make a request to view the stored ideas, and the server searches the database for relevant ideas and displays them to the user.

[0711] Embodiment of Emotion Engine

[0712] 1. Incorporating an emotional engine

[0713] An emotion engine is built into the system, and the device analyzes the user's voice and facial expressions in real time during the meeting to generate emotion data.

[0714] 2. Use of Emotional Data

[0715] The server adjusts the progress of the meeting based on the emotional data collected in real time. For example, if a participant is feeling stressed during the meeting, it will suggest slowing down the progress or changing the agenda.

[0716] 3. Accumulation and analysis of emotional data

[0717] The server accumulates emotional data and later analyzes it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past emotional data, it is possible to determine the impact of specific agenda items on participants and the optimal way to proceed with a meeting.

[0718] Specific examples of program processing

[0719] 1. Setting the meeting agenda

[0720] The user sets up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[0721] 2. Meeting progress management

[0722] The device will start with "market analysis" and then move on to "new product proposals" after 30 minutes.

[0723] 3. Recording and Data Storage

[0724] The server saves the recording data of the meeting with a timestamp, such as "meeting001_20230415103000.wav."

[0725] 4. Searching for Recording Data

[0726] The user searches for "meeting001" and the server displays the relevant recordings.

[0727] 5. Idea extraction

[0728] If the minutes contain "ideas for improving new product concepts," the server extracts and stores them.

[0729] 6. Emotional Recognition and Regulation

[0730] The device uses an emotion engine to recognize when the user is feeling stressed during a meeting and adjusts the progress to ease the stress.

[0731] 7. Accumulation and analysis of emotional data

[0732] After the meeting ends, the server analyzes the accumulated emotional data and uses it to help guide the next meeting.

[0733] The above is a specific embodiment of the present invention. This system has the function of efficiently managing the progress of meetings, extracting and reusing useful ideas, and optimizing meetings based on the emotions of participants.

[0734] The processing flow will be explained below.

[0735] Meeting progress management process steps

[0736] Step 1:

[0737] The user sets the meeting topic and scheduled time using the terminal. Specifically, the user inputs the topic name and scheduled time for each topic (e.g., "Market Analysis (30 minutes)") and creates a meeting agenda.

[0738] Step 2:

[0739] The terminal notifies the user that the conference is about to begin. When the conference begins, the terminal displays the message "Conference is about to begin" to prompt the user to start the conference.

[0740] Step 3:

[0741] The terminal manages the progress of the meeting. Based on the set agenda, the terminal displays the items in order and monitors the scheduled time for each item. Users can proceed with the discussion according to the displayed items.

[0742] Step 4:

[0743] The terminal will notify the user when it is time to move on to the next topic. For example, after 30 minutes of "Market Analysis," the terminal will display the message, "The next topic is 'New Product Proposal (45 minutes)'."

[0744] Step 5:

[0745] The terminal notifies the user that the conference is over. When all the agenda items have been completed, the terminal displays the message "The conference is over" to notify the user that the conference is over.

[0746] Recording data storage and retrieval processing steps

[0747] Step 1:

[0748] To start recording a meeting, the user enters the meeting ID into the terminal. Presses the Start Recording button and enters the meeting ID (e.g., "meeting001").

[0749] Step 2:

[0750] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording file name (e.g., "meeting001_20230415103000.wav"). The recording data is saved on the server with this file name.

[0751] Step 3:

[0752] The user searches for recorded data. The user enters a specific keyword (e.g., "meeting001") into the terminal and makes a search request.

[0753] Step 4:

[0754] The server searches for recorded data. The server searches for recorded files in the specified directory based on keywords and displays the search results to the user.

[0755] Idea extraction and display process steps

[0756] Step 1:

[0757] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[0758] Step 2:

[0759] The server extracts ideas. The server analyzes the provided text and audio data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[0760] Step 3:

[0761] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[0762] Step 4:

[0763] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[0764] Processing Steps of Emotion Engine Embodiments

[0765] Step 1:

[0766] The system incorporates an emotion engine that analyzes the user's voice and facial expressions to generate emotion data in real time.

[0767] Step 2:

[0768] During a meeting, users input their voice and facial expressions into the device, which then sends the voice data and camera footage to the emotion engine for analysis.

[0769] Step 3:

[0770] The server receives the emotional data and adjusts the progress of the meeting. For example, if a participant feels stressed during the meeting, the server will use that information to suggest slowing down the progress.

[0771] Step 4:

[0772] The server accumulates emotional data. After the meeting ends, the emotional data is stored on the server and can be analyzed later.

[0773] Step 5:

[0774] The server analyzes the emotional data and generates feedback based on past emotional data to improve meeting efficiency and participant satisfaction, which can be used for future meetings.

[0775] These are the specific processing steps of the system that combines the emotion engine. As a result, the system efficiently manages the progress of meetings and provides an optimal discussion environment that reflects the emotions of participants.

[0776] Example 2

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

[0778] While conventional conferencing systems provide basic functions such as meeting progress management, storing and searching recorded data, and extracting and displaying ideas, they are limited in their ability to optimize meeting progress while taking participants' emotions into account. Furthermore, they lack the ability to effectively utilize stored recorded data, reuse past discussions, or analyze participants' emotions in real time and adjust meetings accordingly. This creates challenges that make it difficult to improve meeting efficiency and participant satisfaction.

[0779] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for setting the agenda and scheduled time of the conference, means for notifying the start and end of the conference, means for managing the progress of the conference based on a plan, means for recording and storing the audio of the conference, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, means for analyzing the user's voice and facial expression to generate emotional data, means for adjusting the progress of the conference based on the generated emotional data, and means for accumulating and analyzing the emotional data. This makes it possible to optimize the management of the progress of the conference by taking into account the emotional state of each participant, thereby improving the efficiency of the conference and the satisfaction of the participants.

[0780] The "means for setting the agenda and scheduled time of the meeting" is a means for providing a function for the user to input and save the name of each agenda item and the scheduled time of each meeting.

[0781] The "means for notifying the start and end of a conference" is a means for providing a function for notifying a user of the start and end timing of a conference.

[0782] The "means for managing the progress of a meeting based on a plan" is a means for automatically managing the progress of a meeting according to a preset meeting agenda.

[0783] "Means for recording and storing conference audio" refers to means for providing a function for recording audio during a conference and storing it in a database or the like.

[0784] The "means for searching stored recorded data" refers to a means for providing a function for searching for a specific recording using a search keyword from stored recorded data.

[0785] "Means for extracting and storing ideas from audio recordings and minutes" refers to means for providing a function for analyzing, extracting, and storing useful ideas from audio recordings and minutes.

[0786] The "means for displaying extracted ideas" is a means for providing a function for displaying accumulated ideas to a user.

[0787] The "means for analyzing the user's voice and facial expression and generating emotion data" is a means for providing a function for analyzing the content of what the user says and the facial expression and generating emotion data.

[0788] The "means for adjusting the progress of a meeting based on the generated emotion data" is a means for providing a function for adjusting the progress speed and content of a meeting by using the generated emotion data in real time.

[0789] "Means for storing and analyzing emotional data" refers to a means for storing collected emotional data in a database and providing a function for later analysis.

[0790] The system of the present invention not only manages the progress of meetings, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage meetings more effectively. Specific embodiments of this system are described below.

[0791] Meeting progress management

[0792] To manage the progress of a meeting, the user first sets up the meeting agenda using their terminal. The user logs in and enters each topic and the scheduled time on the "Meeting Agenda Settings" screen. This information is sent from the terminal to the server, and the server stores the received agenda in a database. For example, a user can set up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[0793] When a meeting starts, the terminal notifies the user that the meeting has started based on the set agenda. The terminal manages the progress of each agenda item, for example, starting a timer for "Market Analysis (30 minutes)" and notifying the user to move on to "New Product Proposal (45 minutes)" after 30 minutes. When all agenda items have been completed, the terminal notifies the user that "The meeting will end," and the user confirms the end of the meeting.

[0794] Storage and retrieval of recorded data

[0795] To store recording data for a meeting, a user enters the meeting ID into their device and starts recording. The recorded data is sent to the server and saved as a file with a timestamp, such as "meeting001_20230415103000.wav."

[0796] Users can search for past recordings by entering search keywords into their devices. The server searches the database based on the keywords and provides relevant recording files to the user. For example, if a user enters "meeting001," the server will search for and display relevant recordings.

[0797] Idea extraction and display

[0798] It also has the ability to extract useful ideas from meeting minutes and audio recordings. When users provide minutes and audio recordings to their devices, the server analyzes the data, extracts ideas, and stores them. For example, if the minutes contain "ideas for improving new product concepts," the server extracts these and stores them in a database.

[0799] A user can use a terminal to make a request to view the stored ideas, and the server will search the database for relevant ideas and display them to the user.

[0800] Emotion Engine

[0801] The emotion engine is used to analyze the user's voice and facial expressions in real time during a meeting and generate emotion data. The device analyzes the user's voice and camera footage during the meeting, generates emotion data such as "stress" and "joy," and sends it to the server.

[0802] Based on the generated emotion data, the server can adjust the progress of the meeting. For example, if the emotion data indicates "increasing stress," the device will notify the user and suggest relaxing the progress of the meeting or changing the agenda.

[0803] The server stores the emotional data in a database and analyzes it after the meeting. This allows it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past data, it can identify the impact of specific agenda items on participants and the optimal way to proceed with the meeting.

[0804] Prompt Sentence Examples

[0805] Prompt: "Please give us an overview of a system that can manage meeting progress, store recording data, extract and display ideas, and recognize emotions."

[0806] Prompt: "Tell me how to adjust meeting flow based on emotional data."

[0807] This system enables efficient management of the progress of meetings, reuses accumulated data, and adjusts the progress based on the emotions of participants, thereby improving meeting efficiency and participant satisfaction.

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

[0809] Meeting progress management implementation example

[0810] Step 1:

[0811] The user logs in to the terminal and accesses the "Meeting Agenda Settings" screen. The user enters the topic name and scheduled time for each agenda item and clicks the "Save Agenda" button. The entered information, which is the topic name and scheduled time, is sent from the terminal to the server. The server receives the data and saves it in a database. As a specific example of operation, the user enters and saves "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[0812] Step 2:

[0813] The server sends instructions to the terminal notifying the start of the meeting based on pre-set agenda information. The terminal receives the instructions and displays a meeting start notification to the user. The user clicks the "Start Meeting" button to start the meeting. The terminal then proceeds with the agenda according to the set agenda. As a specific example of operation, a timer for "Market Analysis (30 minutes)" is started, and when the timer reaches 30 minutes, a notification is sent to move on to the next item, "New Product Proposal."

[0814] Step 3:

[0815] When all the agenda items have been completed, the server sends a notification to end the meeting to the terminal, and the terminal displays "Ending the meeting." The user clicks the "Confirm End" button, and the meeting officially ends. The server records the end information in the database.

[0816] Embodiments of storing and searching audio data

[0817] Step 1:

[0818] To start recording a meeting on a device, a user enters the meeting ID and presses the "Start Recording" button. The input data is the meeting ID. The device starts recording and transfers the data to the server. The server saves the received recording data with a file name that includes a timestamp, such as "meeting001_20230415103000.wav."

[0819] Step 2:

[0820] To search for recorded data, a user enters a search keyword into the device and clicks the "Search" button. The input data is the search keyword. The server searches the database based on the received keyword and extracts related recorded data. The server returns a list of extracted recorded files to the device, which then displays it to the user. As a specific example of operation, entering "meeting001" will display related recorded data.

[0821] Idea extraction and display embodiment

[0822] Step 1:

[0823] The user uploads meeting minutes or audio recordings to the device. The input data is the minutes or audio recording files. The device transfers the data to the server, which analyzes the data and extracts useful ideas. For example, it generates tags such as "ideas for improving a new product concept" and stores them in a database.

[0824] Step 2:

[0825] A user makes a request to view ideas stored on a terminal. The input data is the view request. The server receives the request and searches the database for related ideas. The server returns the search results to the terminal, which displays them to the user. As a specific example of operation, when a user requests an "idea list," related ideas are displayed.

[0826] Embodiment of Emotion Engine

[0827] Step 1:

[0828] The system is equipped with an emotion engine that analyzes the user's voice and facial expressions in real time to generate emotion data. The input data is the user's voice and camera footage. The device analyzes this data to generate emotion data such as "stress" or "joy" and sends it to the server. As a specific example, the emotion engine analyzes the content of the user's remarks and changes in facial expressions during a meeting.

[0829] Step 2:

[0830] Based on the generated emotion data, the server adjusts the progress of the meeting. The input data is emotion data. The server analyzes the received emotion data and sends instructions to the terminal suggesting changes to the progress speed or agenda as necessary. The terminal notifies the user of the instructions. A specific example of operation is a notification that "stress is increasing" and a suggestion to ease the progress.

[0831] Step 3:

[0832] After the meeting ends, the server stores the collected emotional data in a database for later analysis. The input data is the emotional data collected during the meeting. The server analyzes the data, determines the impact that specific agenda items had on participants, and the optimal way to proceed with the meeting, and provides feedback. A specific example of how it works is to generate analysis results such as "a specific agenda item caused the most stress."

[0833] (Application example 2)

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

[0835] Conventional meeting management systems have basic functions such as agenda and progress management, recording and search, and idea extraction and display. However, they lack the ability to analyze participants' emotions in real time to optimize the progress of the meeting. This can easily lead to situations where participants feel stressed or dissatisfied, reducing the efficiency and effectiveness of the meeting. Furthermore, particularly in dynamic environments such as factory floors, flexible meeting management that can respond to emotional fluctuations is required.

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

[0837] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, and means for analyzing the emotions of participants in real time and adjusting the progress. This allows the progress of the meeting to be optimized in accordance with the emotional state of the participants, enabling efficient and satisfying meeting management.

[0838] A "means for setting the meeting agenda and scheduled time" is a device or software for predetermining and recording the main topics of a meeting and the time allotted for each topic.

[0839] The "means for notifying the start and end of a conference" refers to a device or software for notifying participants of the start and end times of a conference.

[0840] A "means for managing the progress of a meeting based on a plan" is a device or software for supervising and coordinating the progress of a meeting according to a set agenda and scheduled time.

[0841] "Means for recording and storing conference audio" refers to a device or software that records the audio during a conference and stores the data in a form that can be accessed later.

[0842] "Means for searching stored recorded data" refers to a device or software that searches stored recorded data based on specified keywords or conditions and obtains the required information.

[0843] "Means for extracting and storing ideas from audio recordings and minutes" refers to devices or software that select useful ideas from the content discussed during meetings and audio recordings, and store them in a reusable form.

[0844] The "means for displaying extracted ideas" is a device or software for visually displaying extracted ideas.

[0845] "Means for analyzing participants' emotions in real time and adjusting the progress" refers to a device or software that analyzes the voices and facial expressions of participants during a meeting and dynamically adjusts the progress of the meeting based on their emotional state.

[0846] The system of this invention is an application for managing robot operation and maintenance meetings in factories, analyzing participants' emotions in real time, and optimizing the progress of the meetings. This application is installed on smart glasses and realizes the following functions.

[0847] Setting the Meeting Agenda

[0848] Users use the smart glasses to set the meeting agenda and scheduled time. Users create a meeting agenda by entering the topic name and scheduled time for each topic through the smart glasses interface. For example, equipment maintenance can be scheduled for 30 minutes, and the proposal to introduce a new robot can be scheduled for 45 minutes.

[0849] Meeting progress management

[0850] The smart glasses notify the start of a meeting based on the set agenda. The user starts the meeting, and the smart glasses manage the progress of each agenda item according to the time allocation. For example, if equipment maintenance begins, the glasses will automatically move on to the proposal to introduce a new robot 30 minutes later.

[0851] Storage and retrieval of recorded data

[0852] The smart glasses record and store the audio of meetings. The server saves the recordings with timestamps and stores them in a searchable format. Users can easily search and view past recordings by entering search keywords.

[0853] Idea extraction and display

[0854] Users provide recorded data, and the server analyzes, extracts, and stores ideas from the data. When a user makes a viewing request, relevant ideas are displayed on the smart glasses. For example, new maintenance methods and improvement ideas recorded during a meeting can be extracted.

[0855] Use of emotion engine

[0856] An emotion engine is built into the device, and emotion data is generated by analyzing the user's voice and facial expressions in real time. The server adjusts the progress of the meeting based on the emotion data collected in real time. For example, if a participant in a meeting is feeling stressed, it may suggest slowing down the progress. After the meeting, emotion data is accumulated and analyzed, and improvement measures that will lead to increased meeting efficiency and participant satisfaction are provided.

[0857] Hardware and software used

[0858] This system uses the following hardware and software:

[0859] 1. Smart glasses: Provides data collection and user interface.

[0860] 2. Emotion engine: An AI model that analyzes speech and facial expressions (e.g., Emotional Analysis API).

[0861] 3. Recording and retrieval server: A cloud server for storing, searching, and analyzing recording data (e.g., cloud storage and search engine).

[0862] 4. Data analysis engine: An AI model (e.g., a Natural Language Processing model) that analyzes and extracts useful ideas and maintenance techniques from recorded data.

[0863] Examples and prompts

[0864] For example, a factory manager schedules a meeting and inputs the following agenda items: "Equipment maintenance (30 minutes)" and "Proposal for introducing a new robot (45 minutes)." As the meeting progresses, the smart glasses analyze the user's emotions and adjust the progress at the appropriate time.

[0865] Example prompt sentence:

[0866] "Please set up today's meeting agenda. 'Facility Maintenance' takes 30 minutes, and 'New Robot Implementation Proposal' takes 45 minutes."

[0867] "Analyze participants' emotions in real time during the meeting and adjust the pace if they are feeling stressed."

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

[0869] Step 1:

[0870] A user uses smart glasses to set the meeting agenda and scheduled time. The user inputs the agenda name and the scheduled time for each agenda item. This input data is received by the device and set as the meeting agenda. The input data can be "equipment maintenance (30 minutes)" or "proposed introduction of a new robot (45 minutes)," and the output data is the set agenda.

[0871] Step 2:

[0872] The terminal notifies the start of the conference based on the set agenda. The user confirms the start. A start signal is sent to the server, and the conference begins. The input data is the conference start confirmation from the user, and the output data is the conference start notification.

[0873] Step 3:

[0874] The terminal manages the progress of the meeting based on the time allocation of each agenda item. It notifies the start and end of each agenda item and automatically moves on to the next agenda item. The input data is the agenda setting information and elapsed time, and the output data is the start and end notification of each agenda item.

[0875] Step 4:

[0876] The smart glasses record the audio during the meeting and send the data to the server, which stores the recorded data with a timestamp. The input data is real-time audio data, and the output data is a time-stamped audio file.

[0877] Step 5:

[0878] The user inputs keywords into the terminal to search for recorded data. The server searches for recorded data based on the keywords and displays the results to the user. The input data are the search keywords, and the output data are the recorded data as search results.

[0879] Step 6:

[0880] Users provide audio recordings and minutes, and the server analyzes and extracts ideas from the data. The extracted ideas are stored in a database. The input data is the audio recordings and minutes, and the output data is the extracted ideas.

[0881] Step 7:

[0882] A user makes a request to browse stored ideas using a terminal. The server searches the database for relevant ideas and displays them to the user. The input data is the browsing request, and the output data is the displayed ideas.

[0883] Step 8:

[0884] The device uses an emotion engine to analyze the user's voice and facial expressions during the meeting and generate emotion data in real time. The input data is the user's voice and facial expression data, and the output data is the analyzed emotion data.

[0885] Step 9:

[0886] The server adjusts the progress of the meeting based on the emotion data collected in real time, adjusting the progress speed according to the emotion data and proposing changes to the agenda as necessary. The input data is the real-time emotion data, and the output data is the adjusted progress instructions.

[0887] Step 10:

[0888] After the meeting, the server analyzes the accumulated emotional data and provides feedback to improve the efficiency of the meeting and the satisfaction of the participants. The input data is the accumulated emotional data, and the output data is the feedback information.

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

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

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

[0892] [Third embodiment]

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

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

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

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

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

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

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

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

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

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

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

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

[0905] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. An example of this system is shown below.

[0906] Meeting progress management implementation example

[0907] 1. Setting the meeting agenda

[0908] Users set up a meeting agenda by entering the meeting topic and scheduled time into their terminal. This agenda includes the topic name and the scheduled time allocated to each topic. For example, a meeting topic could be "market analysis" and "new product proposal," with 30 minutes and 45 minutes allocated to each topic, respectively.

[0909] 2. Starting and managing meetings

[0910] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies that the "market analysis" agenda item has started, and notifies the user to move on to the next agenda item, "new product proposal," after 30 minutes have passed.

[0911] 3. End of meeting notification

[0912] When the conference ends, the terminal notifies the user that the conference is ending.

[0913] Embodiments of storing and searching audio data

[0914] 1. Starting recording and data accumulation

[0915] To start recording a meeting, a user enters the meeting ID into their device. The server obtains the current timestamp and combines it with the meeting ID to generate a recording filename. The recording data is saved on the server and stored in a database along with the file name and timestamp.

[0916] 2. Search for recording data

[0917] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into their device. The server searches for recording files that match the keyword and displays the results to the user. For example, if a user searches for the keyword "meeting001," a list of recording data related to this meeting ID will be displayed.

[0918] Idea extraction and display embodiment

[0919] 1. Extracting ideas from minutes and audio recordings

[0920] Users provide the minutes and audio recordings generated after the meeting to their devices. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, if the minutes contain "ideas for improving a new product concept," they will be automatically extracted.

[0921] 2. Displaying accumulated ideas

[0922] A user can use a terminal to request to view the accumulated ideas. The server searches the database for relevant ideas and displays the results in a list. This allows the user to review and reuse useful suggestions made in past meetings.

[0923] The above-described embodiments of the present invention provide a system that enables efficient management of the progress of meetings and the reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

[0924] The processing flow will be explained below.

[0925] Meeting progress management process steps

[0926] Step 1:

[0927] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[0928] Step 2:

[0929] The terminal notifies the user that the conference is about to begin. The terminal displays the message "Conference is about to begin" to notify the user that the conference is about to begin.

[0930] Step 3:

[0931] The terminal manages the progress of the meeting. Based on the agenda, the terminal displays the items in order and monitors and measures the scheduled time for each item. Users proceed with the discussion according to the displayed items.

[0932] Step 4:

[0933] When the time for each topic has elapsed, the device will notify the user to move on to the next topic. For example, when 30 minutes have elapsed for "Market Analysis," the device will display the next topic, such as "New Product Proposal."

[0934] Step 5:

[0935] When all the agenda items have been covered, the terminal notifies the user that the conference is over. The terminal displays the message "The conference is ending" to inform the user that the conference is over.

[0936] Recording data storage and retrieval processing steps

[0937] Step 1:

[0938] To start recording a conference, the user enters the conference ID into the terminal and presses the record button to start recording.

[0939] Step 2:

[0940] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording filename. The server saves the recording data in the specified directory based on the generated filename.

[0941] Step 3:

[0942] The user searches for recorded data. The user enters search keywords (such as the meeting ID or related topic) into the device and makes a search request.

[0943] Step 4:

[0944] The server searches for recorded data. The server searches for recorded files in the specified directory based on the keyword and displays a list of search results. If a recorded data matching the keyword is found, the file name and detailed information are provided to the user.

[0945] Idea extraction and display process steps

[0946] Step 1:

[0947] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[0948] Step 2:

[0949] The server extracts ideas. The server analyzes the provided text data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[0950] Step 3:

[0951] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[0952] Step 4:

[0953] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[0954] These are the specific processing steps of the system. Each step is realized through cooperation between users, terminals, and servers, and supports efficient management of the progress of meetings and the reuse of useful ideas.

[0955] Example 1

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

[0957] Conventional conference management systems can manage the progress of meetings and store recorded data, but they have difficulty efficiently extracting and reusing useful information discussed during meetings. This results in problems such as the content of meetings not being managed systematically, making it difficult to reuse information. Furthermore, meeting time management is sometimes inappropriate, which can reduce the efficiency of meetings.

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

[0959] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing useful information from the recorded data and minutes, and means for displaying the extracted useful information. This enables efficient progress management of the meeting and reuse of recorded meeting content and ideas.

[0960] A "meeting agenda" refers to the specific themes or topics that will be addressed at the meeting.

[0961] "Scheduled time" refers to the predetermined time frame for each agenda item.

[0962] The "means for notifying the start and end of a conference" refers to a function for notifying the user of the start and end times of a conference.

[0963] "Means for managing the progress of a meeting based on a plan" refers to the function of managing the progress of a meeting based on a pre-set agenda.

[0964] "Means for recording and storing conference audio" refers to the function for recording audio during a conference and saving that data.

[0965] "Means for searching stored recorded data" refers to the function of searching stored recorded data based on specific conditions.

[0966] "Means for extracting and storing useful information from audio recordings and minutes" refers to the ability to extract useful ideas and information from audio recordings and written minutes and store them in a database.

[0967] "Means for displaying extracted useful information" refers to a function for visually presenting useful information stored in the database to the user.

[0968] "Time information" refers to information that indicates the current time or the time when a specific event occurred.

[0969] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. A specific embodiment of this system is shown below.

[0970] Meeting progress management implementation example

[0971] The user first inputs the meeting topic and scheduled time into the terminal to set up the meeting agenda. The agenda includes the topic name and the allocated time for each topic. For example, the user may set the topics "Market Analysis" and "New Product Proposal" and allocate 30 and 45 minutes for each topic. The terminal receives the input information and generates the meeting agenda.

[0972] Next, the device notifies the user that the meeting is about to begin based on the set agenda. For example, it displays a pop-up message saying, "Please begin the meeting." Once the user starts the meeting, the device manages the progress of each agenda item according to the time allocation. Specifically, the device notifies the user that the "Market Analysis" agenda item has begun, and after 30 minutes has passed, it notifies the user, "Please move on to the next agenda item, 'New Product Proposal.'" This allows the user to proceed with the meeting under appropriate time management. When the meeting ends, the device notifies the user that "The meeting is ending," and once the user confirms the end, the recording of the meeting is officially completed.

[0973] Embodiments of storing and searching audio data

[0974] To efficiently record important discussions during a meeting, a user enters the meeting ID into their device to start recording the meeting. For example, they enter "meeting001" and click the "Start Recording" button. The server obtains the current timestamp and combines it with the meeting ID to generate a recording file name. Specifically, it generates a file name such as "meeting001_20231012_1500.wav." The recording data is saved on the server and accumulated in a database along with the file name and timestamp.

[0975] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into the terminal. For example, they enter "meeting001" into the search form and click the "Search" button. The server searches for recording files that match the keyword and displays the results to the user. Specifically, search results including "meeting001_20231012_1500.wav" are displayed in a list.

[0976] Idea extraction and display embodiment

[0977] After the meeting, the user provides the generated minutes and recording data to the device. Specifically, the user uploads the minutes text and drags and drops the meeting recording file to the device. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, the server analyzes the minutes text to extract "ideas for improving new product concepts" and stores them in the database.

[0978] A user uses a device to request to view the stored ideas. For example, the user enters "new product proposal" into the search form and clicks the "Search" button. The server searches for related ideas and displays results including "improvement ideas for new product concepts" on the user's device.

[0979] Examples of prompt statements

[0980] For example, when setting a meeting agenda, a user might enter:

[0981] "I'd like to set aside 30 minutes for market analysis and 45 minutes for new product proposals."

[0982] Also, if you want to search for recording data for a specific meeting ID, "meeting001," enter the following:

[0983] "meeting001"

[0984] Furthermore, if you want to review the accumulated ideas, you can make a request to the generative AI model with the following prompt:

[0985] "Show me new product proposal ideas extracted from past meetings."

[0986] Through these specific operations, the system of the present invention enables efficient management of meeting progress and reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

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

[0988] Step 1:

[0989] The user inputs the agenda and scheduled time of the meeting into the terminal.

[0990] As a specific example of operation, a user inputs "market analysis," "30 minutes," "new product proposal," and "45 minutes" into an input form on a terminal.

[0991] Input: Meeting agenda (market analysis, new product proposal), estimated time for each agenda item (30 minutes, 45 minutes)

[0992] Output: Meeting agenda (market analysis: 30 minutes, new product proposal: 45 minutes)

[0993] The terminal receives the input information and generates a meeting agenda.

[0994] Step 2:

[0995] The terminal notifies the user of the start of the conference based on the set agenda.

[0996] As a specific example of how this works, a pop-up message will appear saying "Please start the meeting."

[0997] Input: Meeting agenda

[0998] Output: Notification of meeting start

[0999] The user clicks the Start Conference button.

[1000] As a specific example of operation, the user clicks the "Start" button.

[1001] Input: User action (clicking the start button)

[1002] Output:Confirmation of meeting start

[1003] Step 3:

[1004] The terminal manages the progress of each agenda item according to the time allocation.

[1005] As a specific example of operation, the terminal notifies by voice or on the screen that the topic "Market Analysis" has started.

[1006] Input: Meeting agenda, meeting start confirmation

[1007] Output: Agenda start notification (market analysis, new product proposal in 30 minutes)

[1008] After 30 minutes, a notice will be given to move on to the next agenda item, "New product proposals."

[1009] As a specific example of how it works, the terminal will display, "The next topic is 'New product proposals.'"

[1010] Input: Time passed (30 minutes)

[1011] Output: Next Agenda Notification

[1012] Step 4:

[1013] When the conference ends, the terminal notifies the user of the end of the conference.

[1014] As a specific example of operation, the message "The meeting will end" is displayed and an audio notification is also given.

[1015] Input: Meeting agenda complete, all items closed

[1016] Output: Notification of end of meeting

[1017] The user confirms the end of the conference.

[1018] As a specific example of the operation, the user clicks the "Confirm termination" button.

[1019] Input: User operation (clicking the confirmation button to exit)

[1020] Output: Official record of meeting end

[1021] Step 5:

[1022] To start recording a conference, the user enters the conference ID into the terminal.

[1023] As a specific example of operation, the user enters "meeting001" and clicks the "Start Recording" button.

[1024] Input: Meeting ID (meeting001)

[1025] Output: Recording start command

[1026] The server takes the current timestamp and combines it with the conference ID to generate the recording filename.

[1027] As a specific example of operation, the server generates a file name such as "meeting001_20231012_1500.wav".

[1028] Input: Meeting ID, current timestamp

[1029] Output: Recording file name (meeting001_20231012_1500.wav)

[1030] The recorded data is stored on the server and accumulated in a database along with the file name and timestamp.

[1031] As a specific example of operation, a recording file is generated and an entry called "meeting001_20231012_1500.wav" is saved in the database.

[1032] Input: Recording data, recording file name, timestamp

[1033] Output: Database entries

[1034] Step 6:

[1035] To search for past conference recordings, a user inputs a specific keyword (e.g., a conference ID) into the terminal.

[1036] As a specific example of operation, a user enters "meeting001" into the search form on the device and clicks the "Search" button.

[1037] Input: Search keyword (meeting001)

[1038] Output: Search results request

[1039] The server searches for recording files that match the keywords and displays the results to the user.

[1040] As a specific example of operation, the server searches the database and displays a list of search results including "meeting001_20231012_1500.wav".

[1041] Input: Search keywords, database

[1042] Output: Search results (meeting001_20231012_1500.wav)

[1043] Step 7:

[1044] The user provides the minutes and recording data generated after the meeting to the terminal.

[1045] As a specific example of operation, the user uploads the minutes text and provides the meeting recording file to the terminal by dragging and dropping it.

[1046] Input: minutes text, recording data file

[1047] Output: Data Request

[1048] The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database.

[1049] As a specific example of operation, the server analyzes the text of the minutes, extracts "ideas for improving the new product concept," and stores them in a database.

[1050] Input: minutes text, audio recording data

[1051] Output: Extracted ideas, database entries

[1052] Step 8:

[1053] A user uses a terminal to make a request to view the stored ideas.

[1054] As a specific example of operation, a user enters "new product proposal" into the "idea search" form on the terminal and clicks the "search" button.

[1055] Input: Idea search keyword (new product proposal)

[1056] Output: Search results request

[1057] The server searches the database for relevant ideas and displays the results in a list.

[1058] As a specific example of operation, the server searches for related ideas and displays results including "ideas for improving new product concepts" on the user's terminal.

[1059] Input: idea search keywords, database

[1060] Output: Search results (improvement ideas for new product concepts)

[1061] (Application example 1)

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

[1063] Meetings and discussions in modern manufacturing sites require efficient progress and record management. However, many meetings have long agendas, time management is inadequate, and important proposals and ideas are often not properly recorded. Furthermore, content discussed in previous meetings is rarely reused, making efficient management difficult. In addition, the reliance on human labor to conduct meetings in manufacturing sites is an obstacle to improving efficiency.

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

[1065] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes of the meeting, means for displaying the extracted ideas, and means for cooperating with factory robots to efficiently manage the progress of meetings at the manufacturing site. This makes it possible to effectively manage meetings at the manufacturing site and easily search for and reuse past discussions and proposals.

[1066] A "meeting agenda" refers to the specific topics or themes to be discussed at a meeting.

[1067] "Scheduled Time" refers to the planned time allocated for discussion of each agenda item.

[1068] "Means of notification" refers to the method or device for announcing the start or end of a meeting or the transition of agenda items.

[1069] "Means for managing progress" refers to a system or device that supervises the progress of a meeting in an orderly manner based on a set plan or agenda.

[1070] "Means for recording and storing audio" refers to systems or devices that record meeting conversations and discussions and store them as digital data.

[1071] "Means for searching recorded data" refers to a system or device that searches for previously recorded conference audio data using specific keywords or conditions.

[1072] "Means for extracting and storing ideas" refers to systems or devices that automatically extract important suggestions and ideas from audio recordings and minutes and store them in a database.

[1073] "Factory robots" refer to autonomous robots used to assist with work and manage meeting progress in manufacturing sites.

[1074] "Manufacturing site" refers to a location where products or parts are manufactured, such as a factory or production line.

[1075] "Means for efficiently managing the progress of meetings" refers to systems and devices that ensure that meetings proceed smoothly and that time management and agenda transitions are carried out effectively.

[1076] "Past recording data" refers to audio data recorded and stored during meetings and conferences.

[1077] The present invention introduces a factory robot into a conference management system to improve the efficiency of conference progress management and recording at manufacturing sites.

[1078] System programs and hardware

[1079] The system primarily utilizes the following hardware and software:

[1080] 1. Factory robot: Supports meeting management, recording, and notifications.

[1081] 2. Server: Stores recording data and minutes, and extracts and displays ideas.

[1082] 3. Device (smartphone or PC): Used by users to set the meeting agenda and search for recording data.

[1083] DETAILED DESCRIPTION OF THE INVENTION

[1084] 1. Setting the meeting agenda

[1085] The user inputs the meeting topic and scheduled time using the terminal, and the meeting agenda is set in the system. For example, "Production line optimization: 45 minutes" and "Equipment maintenance planning: 30 minutes."

[1086] 2. Starting and managing meetings

[1087] When a meeting begins, the factory robot announces the first item on the agenda based on the set agenda and then proceeds with the meeting. At the end of each item, it automatically notifies the user to move on to the next item.

[1088] 3. Starting recording and data accumulation

[1089] A factory robot records the meeting, and the server stores the recorded data. The server manages the recording files using the meeting ID and timestamp. For example, the server combines the meeting ID "meeting001" with the timestamp "20230101123000" and saves the file with the file name "meeting001_20230101123000.wav."

[1090] 4. End of meeting notice

[1091] When the meeting ends, the factory robot announces, "The meeting is ending."

[1092] 5. Searching and reusing stored data

[1093] When a user enters a specific keyword (e.g., "production line optimization") into the terminal, the server searches for relevant audio recordings and displays the results.

[1094] 6. Idea extraction and display

[1095] The server automatically extracts useful ideas from the recordings and minutes and stores them in a database, which users can then view using their devices.

[1096] Specific examples of system processing

[1097] Program processing description

[1098] Setting the meeting agenda: The server registers the topic and scheduled time entered by the user as an agenda in the system.

[1099] Meeting progress and management: The factory robot manages the time and notifies the start and end of each agenda item, which is recorded by the server.

[1100] Recording initiation and storage: The factory robot records the meeting audio, and the server stores the data using a timestamp and the meeting ID.

[1101] Searching audio recordings: When a user enters a search keyword, the server searches the stored audio recordings and returns the results.

[1102] Idea extraction and display: The server extracts important ideas from the recording data, stores them in a database, and displays them to the user.

[1103] Hardware and software used:

[1104] Factory robot: Announces and records meeting progress.

[1105] Server: Stores data, searches, and processes idea extraction.

[1106] Device (smartphone or PC): The user sets the agenda and searches for data.

[1107] Prompt Sentence Examples

[1108] "Please extract important suggestions and ideas from the following meeting recording: Meeting ID: Production Line Optimization_20231030120000.wav"

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

[1110] Step 1:

[1111] A user uses a terminal to input the meeting agenda and scheduled time. The input agenda and scheduled time are sent to the server and registered in the system as an agenda. At this time, the agenda and time are saved in the database. Example input data: "Production line optimization: 45 minutes", "Equipment maintenance plan: 30 minutes". The output is the meeting agenda saved on the server.

[1112] Step 2:

[1113] Before the meeting starts, the server sends the agenda data to the factory robot. The factory robot performs initialization and notifies the user when the meeting starts. Specifically, the robot announces, "The meeting will start." The output is a notification that the meeting has started.

[1114] Step 3:

[1115] When the meeting begins, the factory robot announces the first topic based on the agenda and the meeting proceeds. It notifies the user by voice when each topic begins and ends, and automatically notifies the user when the next topic will be discussed after a set time has elapsed. The server records this information. At this time, the robot announces, "We will begin optimizing the production line," and after 45 minutes, announces, "We will move on to the next topic."

[1116] Step 4:

[1117] When a user inputs a command to start recording a meeting, the factory robot starts recording and sends the audio data to the server in real time. The server generates a recording file name using the meeting ID and timestamp and saves it in a database. The input is the command to start the meeting, and the output is a recording data file with a timestamp. For example, the file name might be "meeting001_20230101123000.wav."

[1118] Step 5:

[1119] When the meeting ends, the factory robot notifies the server that the meeting is ending. The server recognizes this and saves the recording file. The output is a notification that the meeting has ended and that the recording has stopped.

[1120] Step 6:

[1121] The user inputs a command into the terminal to search for audio recordings using specific keywords. The server searches the database for matching files and displays the results to the user. For example, if the user searches for "production line optimization," a list of related audio recordings is displayed. The input is the search keyword, and the output is a list of search results.

[1122] Step 7:

[1123] The server automatically extracts useful ideas from audio recordings and meeting minutes. It uses a generative AI model to do this and stores the extracted ideas in a database. Data processing involves converting the audio data into text and extracting useful information. The output is a list of ideas. As a specific example, "ideas for new products" are extracted.

[1124] Step 8:

[1125] Users can use their terminals to view the accumulated ideas. The user inputs a request into the terminal, and the server searches the database for relevant ideas and displays a list of the results. The input is a request to view ideas, and the output is a list of ideas. An example of a prompt is, "Please extract important suggestions and ideas from the following meeting recording data. Meeting ID: Production Line Optimization_20231030120000.wav."

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

[1127] The system of the present invention not only manages the progress of a meeting, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage the meeting more effectively. Specific embodiments are described below.

[1128] Meeting progress management implementation example

[1129] 1. Setting the meeting agenda

[1130] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[1131] 2. Starting and managing meetings

[1132] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies the start and end of "Agenda A," and then moves on to "Agenda B."

[1133] 3. End of meeting notification

[1134] When all the agenda items have been completed, the terminal will notify the user that the meeting will end. The user will then confirm that they wish to end the meeting.

[1135] Embodiments of storing and searching audio data

[1136] 1. Starting recording and data accumulation

[1137] To start recording a conference, the user enters the conference ID into the terminal. After recording starts, the server stores the recorded data along with a timestamp.

[1138] 2. Search for recording data

[1139] The user inputs search keywords into the terminal to search for past recorded data. The server searches for recorded data based on the specified keywords and displays the results to the user.

[1140] Idea extraction and display embodiment

[1141] 1. Extracting ideas from minutes and audio recordings

[1142] Users provide minutes and audio recordings to their devices, and the server analyzes, extracts, and stores ideas from the data.

[1143] 2. Displaying accumulated ideas

[1144] A user uses a terminal to make a request to view the stored ideas, and the server searches the database for relevant ideas and displays them to the user.

[1145] Embodiment of Emotion Engine

[1146] 1. Incorporating an emotional engine

[1147] An emotion engine is built into the system, and the device analyzes the user's voice and facial expressions in real time during the meeting to generate emotion data.

[1148] 2. Use of Emotional Data

[1149] The server adjusts the progress of the meeting based on the emotional data collected in real time. For example, if a participant is feeling stressed during the meeting, it will suggest slowing down the progress or changing the agenda.

[1150] 3. Accumulation and analysis of emotional data

[1151] The server accumulates emotional data and later analyzes it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past emotional data, it is possible to determine the impact of specific agenda items on participants and the optimal way to proceed with a meeting.

[1152] Specific examples of program processing

[1153] 1. Setting the meeting agenda

[1154] The user sets up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[1155] 2. Meeting progress management

[1156] The device will start with "market analysis" and then move on to "new product proposals" after 30 minutes.

[1157] 3. Recording and Data Storage

[1158] The server saves the recording data of the meeting with a timestamp, such as "meeting001_20230415103000.wav."

[1159] 4. Searching for Recording Data

[1160] The user searches for "meeting001" and the server displays the relevant recordings.

[1161] 5. Idea extraction

[1162] If the minutes contain "ideas for improving new product concepts," the server extracts and stores them.

[1163] 6. Emotional Recognition and Regulation

[1164] The device uses an emotion engine to recognize when the user is feeling stressed during a meeting and adjusts the progress to ease the stress.

[1165] 7. Accumulation and analysis of emotional data

[1166] After the meeting ends, the server analyzes the accumulated emotional data and uses it to help guide the next meeting.

[1167] The above is a specific embodiment of the present invention. This system has the function of efficiently managing the progress of meetings, extracting and reusing useful ideas, and optimizing meetings based on the emotions of participants.

[1168] The processing flow will be explained below.

[1169] Meeting progress management process steps

[1170] Step 1:

[1171] The user sets the meeting topic and scheduled time using the terminal. Specifically, the user inputs the topic name and scheduled time for each topic (e.g., "Market Analysis (30 minutes)") and creates a meeting agenda.

[1172] Step 2:

[1173] The terminal notifies the user that the conference is about to begin. When the conference begins, the terminal displays the message "Conference is about to begin" to prompt the user to start the conference.

[1174] Step 3:

[1175] The terminal manages the progress of the meeting. Based on the set agenda, the terminal displays the items in order and monitors the scheduled time for each item. Users can proceed with the discussion according to the displayed items.

[1176] Step 4:

[1177] The terminal will notify the user when it is time to move on to the next topic. For example, after 30 minutes of "Market Analysis," the terminal will display the message, "The next topic is 'New Product Proposal (45 minutes)'."

[1178] Step 5:

[1179] The terminal notifies the user that the conference is over. When all the agenda items have been completed, the terminal displays the message "The conference is over" to notify the user that the conference is over.

[1180] Recording data storage and retrieval processing steps

[1181] Step 1:

[1182] To start recording a meeting, the user enters the meeting ID into the terminal. Presses the Start Recording button and enters the meeting ID (e.g., "meeting001").

[1183] Step 2:

[1184] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording file name (e.g., "meeting001_20230415103000.wav"). The recording data is saved on the server with this file name.

[1185] Step 3:

[1186] The user searches for recorded data. The user enters a specific keyword (e.g., "meeting001") into the terminal and makes a search request.

[1187] Step 4:

[1188] The server searches for recorded data. The server searches for recorded files in the specified directory based on keywords and displays the search results to the user.

[1189] Idea extraction and display process steps

[1190] Step 1:

[1191] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[1192] Step 2:

[1193] The server extracts ideas. The server analyzes the provided text and audio data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[1194] Step 3:

[1195] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[1196] Step 4:

[1197] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[1198] Processing Steps of Emotion Engine Embodiments

[1199] Step 1:

[1200] The system incorporates an emotion engine that analyzes the user's voice and facial expressions to generate emotion data in real time.

[1201] Step 2:

[1202] During a meeting, users input their voice and facial expressions into the device, which then sends the voice data and camera footage to the emotion engine for analysis.

[1203] Step 3:

[1204] The server receives the emotional data and adjusts the progress of the meeting. For example, if a participant feels stressed during the meeting, the server will use that information to suggest slowing down the progress.

[1205] Step 4:

[1206] The server accumulates emotional data. After the meeting ends, the emotional data is stored on the server and can be analyzed later.

[1207] Step 5:

[1208] The server analyzes the emotional data and generates feedback based on past emotional data to improve meeting efficiency and participant satisfaction, which can be used for future meetings.

[1209] These are the specific processing steps of the system that combines the emotion engine. As a result, the system efficiently manages the progress of meetings and provides an optimal discussion environment that reflects the emotions of participants.

[1210] Example 2

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

[1212] While conventional conferencing systems provide basic functions such as meeting progress management, storing and searching recorded data, and extracting and displaying ideas, they are limited in their ability to optimize meeting progress while taking participants' emotions into account. Furthermore, they lack the ability to effectively utilize stored recorded data, reuse past discussions, or analyze participants' emotions in real time and adjust meetings accordingly. This creates challenges that make it difficult to improve meeting efficiency and participant satisfaction.

[1213] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for setting the agenda and scheduled time of the conference, means for notifying the start and end of the conference, means for managing the progress of the conference based on a plan, means for recording and storing the audio of the conference, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, means for analyzing the user's voice and facial expression to generate emotional data, means for adjusting the progress of the conference based on the generated emotional data, and means for accumulating and analyzing the emotional data. This makes it possible to optimize the management of the progress of the conference by taking into account the emotional state of each participant, thereby improving the efficiency of the conference and the satisfaction of the participants.

[1214] The "means for setting the agenda and scheduled time of the meeting" is a means for providing a function for the user to input and save the name of each agenda item and the scheduled time of each meeting.

[1215] The "means for notifying the start and end of a conference" is a means for providing a function for notifying a user of the start and end timing of a conference.

[1216] The "means for managing the progress of a meeting based on a plan" is a means for automatically managing the progress of a meeting according to a preset meeting agenda.

[1217] "Means for recording and storing conference audio" refers to means for providing a function for recording audio during a conference and storing it in a database or the like.

[1218] The "means for searching stored recorded data" refers to a means for providing a function for searching for a specific recording using a search keyword from stored recorded data.

[1219] "Means for extracting and storing ideas from audio recordings and minutes" refers to means for providing a function for analyzing, extracting, and storing useful ideas from audio recordings and minutes.

[1220] The "means for displaying extracted ideas" is a means for providing a function for displaying accumulated ideas to a user.

[1221] The "means for analyzing the user's voice and facial expression and generating emotion data" is a means for providing a function for analyzing the content of what the user says and the facial expression and generating emotion data.

[1222] The "means for adjusting the progress of a meeting based on the generated emotion data" is a means for providing a function for adjusting the progress speed and content of a meeting by using the generated emotion data in real time.

[1223] "Means for storing and analyzing emotional data" refers to a means for storing collected emotional data in a database and providing a function for later analysis.

[1224] The system of the present invention not only manages the progress of meetings, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage meetings more effectively. Specific embodiments of this system are described below.

[1225] Meeting progress management

[1226] To manage the progress of a meeting, the user first sets up the meeting agenda using their terminal. The user logs in and enters each topic and the scheduled time on the "Meeting Agenda Settings" screen. This information is sent from the terminal to the server, and the server stores the received agenda in a database. For example, a user can set up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[1227] When a meeting starts, the terminal notifies the user that the meeting has started based on the set agenda. The terminal manages the progress of each agenda item, for example, starting a timer for "Market Analysis (30 minutes)" and notifying the user to move on to "New Product Proposal (45 minutes)" after 30 minutes. When all agenda items have been completed, the terminal notifies the user that "The meeting will end," and the user confirms the end of the meeting.

[1228] Storage and retrieval of recorded data

[1229] To store recording data for a meeting, a user enters the meeting ID into their device and starts recording. The recorded data is sent to the server and saved as a file with a timestamp, such as "meeting001_20230415103000.wav."

[1230] Users can search for past recordings by entering search keywords into their devices. The server searches the database based on the keywords and provides relevant recording files to the user. For example, if a user enters "meeting001," the server will search for and display relevant recordings.

[1231] Idea extraction and display

[1232] It also has the ability to extract useful ideas from meeting minutes and audio recordings. When users provide minutes and audio recordings to their devices, the server analyzes the data, extracts ideas, and stores them. For example, if the minutes contain "ideas for improving new product concepts," the server extracts these and stores them in a database.

[1233] A user can use a terminal to make a request to view the stored ideas, and the server will search the database for relevant ideas and display them to the user.

[1234] Emotion Engine

[1235] The emotion engine is used to analyze the user's voice and facial expressions in real time during a meeting and generate emotion data. The device analyzes the user's voice and camera footage during the meeting, generates emotion data such as "stress" and "joy," and sends it to the server.

[1236] Based on the generated emotion data, the server can adjust the progress of the meeting. For example, if the emotion data indicates "increasing stress," the device will notify the user and suggest relaxing the progress of the meeting or changing the agenda.

[1237] The server stores the emotional data in a database and analyzes it after the meeting. This allows it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past data, it can identify the impact of specific agenda items on participants and the optimal way to proceed with the meeting.

[1238] Prompt Sentence Examples

[1239] Prompt: "Please give us an overview of a system that can manage meeting progress, store recording data, extract and display ideas, and recognize emotions."

[1240] Prompt: "Tell me how to adjust meeting flow based on emotional data."

[1241] This system enables efficient management of the progress of meetings, reuses accumulated data, and adjusts the progress based on the emotions of participants, thereby improving meeting efficiency and participant satisfaction.

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

[1243] Meeting progress management implementation example

[1244] Step 1:

[1245] The user logs in to the terminal and accesses the "Meeting Agenda Settings" screen. The user enters the topic name and scheduled time for each agenda item and clicks the "Save Agenda" button. The entered information, which is the topic name and scheduled time, is sent from the terminal to the server. The server receives the data and saves it in a database. As a specific example of operation, the user enters and saves "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[1246] Step 2:

[1247] The server sends instructions to the terminal notifying the start of the meeting based on pre-set agenda information. The terminal receives the instructions and displays a meeting start notification to the user. The user clicks the "Start Meeting" button to start the meeting. The terminal then proceeds with the agenda according to the set agenda. As a specific example of operation, a timer for "Market Analysis (30 minutes)" is started, and when the timer reaches 30 minutes, a notification is sent to move on to the next item, "New Product Proposal."

[1248] Step 3:

[1249] When all the agenda items have been completed, the server sends a notification to end the meeting to the terminal, and the terminal displays "Ending the meeting." The user clicks the "Confirm End" button, and the meeting officially ends. The server records the end information in the database.

[1250] Embodiments of storing and searching audio data

[1251] Step 1:

[1252] To start recording a meeting on a device, a user enters the meeting ID and presses the "Start Recording" button. The input data is the meeting ID. The device starts recording and transfers the data to the server. The server saves the received recording data with a file name that includes a timestamp, such as "meeting001_20230415103000.wav."

[1253] Step 2:

[1254] To search for recorded data, a user enters a search keyword into the device and clicks the "Search" button. The input data is the search keyword. The server searches the database based on the received keyword and extracts related recorded data. The server returns a list of extracted recorded files to the device, which then displays it to the user. As a specific example of operation, entering "meeting001" will display related recorded data.

[1255] Idea extraction and display embodiment

[1256] Step 1:

[1257] The user uploads meeting minutes or audio recordings to the device. The input data is the minutes or audio recording files. The device transfers the data to the server, which analyzes the data and extracts useful ideas. For example, it generates tags such as "ideas for improving a new product concept" and stores them in a database.

[1258] Step 2:

[1259] A user makes a request to view ideas stored on a terminal. The input data is the view request. The server receives the request and searches the database for related ideas. The server returns the search results to the terminal, which displays them to the user. As a specific example of operation, when a user requests an "idea list," related ideas are displayed.

[1260] Embodiment of Emotion Engine

[1261] Step 1:

[1262] The system is equipped with an emotion engine that analyzes the user's voice and facial expressions in real time to generate emotion data. The input data is the user's voice and camera footage. The device analyzes this data to generate emotion data such as "stress" or "joy" and sends it to the server. As a specific example, the emotion engine analyzes the content of the user's remarks and changes in facial expressions during a meeting.

[1263] Step 2:

[1264] Based on the generated emotion data, the server adjusts the progress of the meeting. The input data is emotion data. The server analyzes the received emotion data and sends instructions to the terminal suggesting changes to the progress speed or agenda as necessary. The terminal notifies the user of the instructions. A specific example of operation is a notification that "stress is increasing" and a suggestion to ease the progress.

[1265] Step 3:

[1266] After the meeting ends, the server stores the collected emotional data in a database for later analysis. The input data is the emotional data collected during the meeting. The server analyzes the data, determines the impact that specific agenda items had on participants, and the optimal way to proceed with the meeting, and provides feedback. A specific example of how it works is to generate analysis results such as "a specific agenda item caused the most stress."

[1267] (Application example 2)

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

[1269] Conventional meeting management systems have basic functions such as agenda and progress management, recording and search, and idea extraction and display. However, they lack the ability to analyze participants' emotions in real time to optimize the progress of the meeting. This can easily lead to situations where participants feel stressed or dissatisfied, reducing the efficiency and effectiveness of the meeting. Furthermore, particularly in dynamic environments such as factory floors, flexible meeting management that can respond to emotional fluctuations is required.

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

[1271] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, and means for analyzing the emotions of participants in real time and adjusting the progress. This allows the progress of the meeting to be optimized in accordance with the emotional state of the participants, enabling efficient and satisfying meeting management.

[1272] A "means for setting the meeting agenda and scheduled time" is a device or software for predetermining and recording the main topics of a meeting and the time allotted for each topic.

[1273] The "means for notifying the start and end of a conference" refers to a device or software for notifying participants of the start and end times of a conference.

[1274] A "means for managing the progress of a meeting based on a plan" is a device or software for supervising and coordinating the progress of a meeting according to a set agenda and scheduled time.

[1275] "Means for recording and storing conference audio" refers to a device or software that records the audio during a conference and stores the data in a form that can be accessed later.

[1276] "Means for searching stored recorded data" refers to a device or software that searches stored recorded data based on specified keywords or conditions and obtains the required information.

[1277] "Means for extracting and storing ideas from audio recordings and minutes" refers to devices or software that select useful ideas from the content discussed during meetings and audio recordings, and store them in a reusable form.

[1278] The "means for displaying extracted ideas" is a device or software for visually displaying extracted ideas.

[1279] "Means for analyzing participants' emotions in real time and adjusting the progress" refers to a device or software that analyzes the voices and facial expressions of participants during a meeting and dynamically adjusts the progress of the meeting based on their emotional state.

[1280] The system of this invention is an application for managing robot operation and maintenance meetings in factories, analyzing participants' emotions in real time, and optimizing the progress of the meetings. This application is installed on smart glasses and realizes the following functions.

[1281] Setting the Meeting Agenda

[1282] Users use the smart glasses to set the meeting agenda and scheduled time. Users create a meeting agenda by entering the topic name and scheduled time for each topic through the smart glasses interface. For example, equipment maintenance can be scheduled for 30 minutes, and the proposal to introduce a new robot can be scheduled for 45 minutes.

[1283] Meeting progress management

[1284] The smart glasses notify the start of a meeting based on the set agenda. The user starts the meeting, and the smart glasses manage the progress of each agenda item according to the time allocation. For example, if equipment maintenance begins, the glasses will automatically move on to the proposal to introduce a new robot 30 minutes later.

[1285] Storage and retrieval of recorded data

[1286] The smart glasses record and store the audio of meetings. The server saves the recordings with timestamps and stores them in a searchable format. Users can easily search and view past recordings by entering search keywords.

[1287] Idea extraction and display

[1288] Users provide recorded data, and the server analyzes, extracts, and stores ideas from the data. When a user makes a viewing request, relevant ideas are displayed on the smart glasses. For example, new maintenance methods and improvement ideas recorded during a meeting can be extracted.

[1289] Use of emotion engine

[1290] An emotion engine is built into the device, and emotion data is generated by analyzing the user's voice and facial expressions in real time. The server adjusts the progress of the meeting based on the emotion data collected in real time. For example, if a participant in a meeting is feeling stressed, it may suggest slowing down the progress. After the meeting, emotion data is accumulated and analyzed, and improvement measures that will lead to increased meeting efficiency and participant satisfaction are provided.

[1291] Hardware and software used

[1292] This system uses the following hardware and software:

[1293] 1. Smart glasses: Provides data collection and user interface.

[1294] 2. Emotion engine: An AI model that analyzes speech and facial expressions (e.g., Emotional Analysis API).

[1295] 3. Recording and retrieval server: A cloud server for storing, searching, and analyzing recording data (e.g., cloud storage and search engine).

[1296] 4. Data analysis engine: An AI model (e.g., a Natural Language Processing model) that analyzes and extracts useful ideas and maintenance techniques from recorded data.

[1297] Examples and prompts

[1298] For example, a factory manager schedules a meeting and inputs the following agenda items: "Equipment maintenance (30 minutes)" and "Proposal for introducing a new robot (45 minutes)." As the meeting progresses, the smart glasses analyze the user's emotions and adjust the progress at the appropriate time.

[1299] Example prompt sentence:

[1300] "Please set up today's meeting agenda. 'Facility Maintenance' takes 30 minutes, and 'New Robot Implementation Proposal' takes 45 minutes."

[1301] "Analyze participants' emotions in real time during the meeting and adjust the pace if they are feeling stressed."

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

[1303] Step 1:

[1304] A user uses smart glasses to set the meeting agenda and scheduled time. The user inputs the agenda name and the scheduled time for each agenda item. This input data is received by the device and set as the meeting agenda. The input data can be "equipment maintenance (30 minutes)" or "proposed introduction of a new robot (45 minutes)," and the output data is the set agenda.

[1305] Step 2:

[1306] The terminal notifies the start of the conference based on the set agenda. The user confirms the start. A start signal is sent to the server, and the conference begins. The input data is the conference start confirmation from the user, and the output data is the conference start notification.

[1307] Step 3:

[1308] The terminal manages the progress of the meeting based on the time allocation of each agenda item. It notifies the start and end of each agenda item and automatically moves on to the next agenda item. The input data is the agenda setting information and elapsed time, and the output data is the start and end notification of each agenda item.

[1309] Step 4:

[1310] The smart glasses record the audio during the meeting and send the data to the server, which stores the recorded data with a timestamp. The input data is real-time audio data, and the output data is a time-stamped audio file.

[1311] Step 5:

[1312] The user inputs keywords into the terminal to search for recorded data. The server searches for recorded data based on the keywords and displays the results to the user. The input data are the search keywords, and the output data are the recorded data as search results.

[1313] Step 6:

[1314] Users provide audio recordings and minutes, and the server analyzes and extracts ideas from the data. The extracted ideas are stored in a database. The input data is the audio recordings and minutes, and the output data is the extracted ideas.

[1315] Step 7:

[1316] A user makes a request to browse stored ideas using a terminal. The server searches the database for relevant ideas and displays them to the user. The input data is the browsing request, and the output data is the displayed ideas.

[1317] Step 8:

[1318] The device uses an emotion engine to analyze the user's voice and facial expressions during the meeting and generate emotion data in real time. The input data is the user's voice and facial expression data, and the output data is the analyzed emotion data.

[1319] Step 9:

[1320] The server adjusts the progress of the meeting based on the emotion data collected in real time, adjusting the progress speed according to the emotion data and proposing changes to the agenda as necessary. The input data is the real-time emotion data, and the output data is the adjusted progress instructions.

[1321] Step 10:

[1322] After the meeting, the server analyzes the accumulated emotional data and provides feedback to improve the efficiency of the meeting and the satisfaction of the participants. The input data is the accumulated emotional data, and the output data is the feedback information.

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

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

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

[1326] [Fourth embodiment]

[1327] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

[1340] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. An example of this system is shown below.

[1341] Meeting progress management implementation example

[1342] 1. Setting the meeting agenda

[1343] Users set up a meeting agenda by entering the meeting topic and scheduled time into their terminal. This agenda includes the topic name and the scheduled time allocated to each topic. For example, a meeting topic could be "market analysis" and "new product proposal," with 30 minutes and 45 minutes allocated to each topic, respectively.

[1344] 2. Starting and managing meetings

[1345] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies that the "market analysis" agenda item has started, and notifies the user to move on to the next agenda item, "new product proposal," after 30 minutes have passed.

[1346] 3. End of meeting notification

[1347] When the conference ends, the terminal notifies the user that the conference is ending.

[1348] Embodiments of storing and searching audio data

[1349] 1. Starting recording and data accumulation

[1350] To start recording a meeting, a user enters the meeting ID into their device. The server obtains the current timestamp and combines it with the meeting ID to generate a recording filename. The recording data is saved on the server and stored in a database along with the file name and timestamp.

[1351] 2. Search for recording data

[1352] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into their device. The server searches for recording files that match the keyword and displays the results to the user. For example, if a user searches for the keyword "meeting001," a list of recording data related to this meeting ID will be displayed.

[1353] Idea extraction and display embodiment

[1354] 1. Extracting ideas from minutes and audio recordings

[1355] Users provide the minutes and audio recordings generated after the meeting to their devices. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, if the minutes contain "ideas for improving a new product concept," they will be automatically extracted.

[1356] 2. Displaying accumulated ideas

[1357] A user can use a terminal to request to view the accumulated ideas. The server searches the database for relevant ideas and displays the results in a list. This allows the user to review and reuse useful suggestions made in past meetings.

[1358] The above-described embodiments of the present invention provide a system that enables efficient management of the progress of meetings and the reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

[1359] The processing flow will be explained below.

[1360] Meeting progress management process steps

[1361] Step 1:

[1362] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[1363] Step 2:

[1364] The terminal notifies the user that the conference is about to begin. The terminal displays the message "Conference is about to begin" to notify the user that the conference is about to begin.

[1365] Step 3:

[1366] The terminal manages the progress of the meeting. Based on the agenda, the terminal displays the items in order and monitors and measures the scheduled time for each item. Users proceed with the discussion according to the displayed items.

[1367] Step 4:

[1368] When the time for each topic has elapsed, the device will notify the user to move on to the next topic. For example, when 30 minutes have elapsed for "Market Analysis," the device will display the next topic, such as "New Product Proposal."

[1369] Step 5:

[1370] When all the agenda items have been covered, the terminal notifies the user that the conference is over. The terminal displays the message "The conference is ending" to inform the user that the conference is over.

[1371] Recording data storage and retrieval processing steps

[1372] Step 1:

[1373] To start recording a conference, the user enters the conference ID into the terminal and presses the record button to start recording.

[1374] Step 2:

[1375] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording filename. The server saves the recording data in the specified directory based on the generated filename.

[1376] Step 3:

[1377] The user searches for recorded data. The user enters search keywords (such as the meeting ID or related topic) into the device and makes a search request.

[1378] Step 4:

[1379] The server searches for recorded data. The server searches for recorded files in the specified directory based on the keyword and displays a list of search results. If a recorded data matching the keyword is found, the file name and detailed information are provided to the user.

[1380] Idea extraction and display process steps

[1381] Step 1:

[1382] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[1383] Step 2:

[1384] The server extracts ideas. The server analyzes the provided text data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[1385] Step 3:

[1386] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[1387] Step 4:

[1388] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[1389] These are the specific processing steps of the system. Each step is realized through cooperation between users, terminals, and servers, and supports efficient management of the progress of meetings and the reuse of useful ideas.

[1390] Example 1

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

[1392] Conventional conference management systems can manage the progress of meetings and store recorded data, but they have difficulty efficiently extracting and reusing useful information discussed during meetings. This results in problems such as the content of meetings not being managed systematically, making it difficult to reuse information. Furthermore, meeting time management is sometimes inappropriate, which can reduce the efficiency of meetings.

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

[1394] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing useful information from the recorded data and minutes, and means for displaying the extracted useful information. This enables efficient progress management of the meeting and reuse of recorded meeting content and ideas.

[1395] A "meeting agenda" refers to the specific themes or topics that will be addressed at the meeting.

[1396] "Scheduled time" refers to the predetermined time frame for each agenda item.

[1397] The "means for notifying the start and end of a conference" refers to a function for notifying the user of the start and end times of a conference.

[1398] "Means for managing the progress of a meeting based on a plan" refers to the function of managing the progress of a meeting based on a pre-set agenda.

[1399] "Means for recording and storing conference audio" refers to the function for recording audio during a conference and saving that data.

[1400] "Means for searching stored recorded data" refers to the function of searching stored recorded data based on specific conditions.

[1401] "Means for extracting and storing useful information from audio recordings and minutes" refers to the ability to extract useful ideas and information from audio recordings and written minutes and store them in a database.

[1402] "Means for displaying extracted useful information" refers to a function for visually presenting useful information stored in the database to the user.

[1403] "Time information" refers to information that indicates the current time or the time when a specific event occurred.

[1404] The present invention is a system for effectively managing the progress of meetings and efficiently recording and reusing important discussions and proposals. A specific embodiment of this system is shown below.

[1405] Meeting progress management implementation example

[1406] The user first inputs the meeting topic and scheduled time into the terminal to set up the meeting agenda. The agenda includes the topic name and the allocated time for each topic. For example, the user may set the topics "Market Analysis" and "New Product Proposal" and allocate 30 and 45 minutes for each topic. The terminal receives the input information and generates the meeting agenda.

[1407] Next, the device notifies the user that the meeting is about to begin based on the set agenda. For example, it displays a pop-up message saying, "Please begin the meeting." Once the user starts the meeting, the device manages the progress of each agenda item according to the time allocation. Specifically, the device notifies the user that the "Market Analysis" agenda item has begun, and after 30 minutes has passed, it notifies the user, "Please move on to the next agenda item, 'New Product Proposal.'" This allows the user to proceed with the meeting under appropriate time management. When the meeting ends, the device notifies the user that "The meeting is ending," and once the user confirms the end, the recording of the meeting is officially completed.

[1408] Embodiments of storing and searching audio data

[1409] To efficiently record important discussions during a meeting, a user enters the meeting ID into their device to start recording the meeting. For example, they enter "meeting001" and click the "Start Recording" button. The server obtains the current timestamp and combines it with the meeting ID to generate a recording file name. Specifically, it generates a file name such as "meeting001_20231012_1500.wav." The recording data is saved on the server and accumulated in a database along with the file name and timestamp.

[1410] To search for past meeting recordings, a user enters a specific keyword (e.g., a meeting ID) into the terminal. For example, they enter "meeting001" into the search form and click the "Search" button. The server searches for recording files that match the keyword and displays the results to the user. Specifically, search results including "meeting001_20231012_1500.wav" are displayed in a list.

[1411] Idea extraction and display embodiment

[1412] After the meeting, the user provides the generated minutes and recording data to the device. Specifically, the user uploads the minutes text and drags and drops the meeting recording file to the device. The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database. For example, the server analyzes the minutes text to extract "ideas for improving new product concepts" and stores them in the database.

[1413] A user uses a device to request to view the stored ideas. For example, the user enters "new product proposal" into the search form and clicks the "Search" button. The server searches for related ideas and displays results including "improvement ideas for new product concepts" on the user's device.

[1414] Examples of prompt statements

[1415] For example, when setting a meeting agenda, a user might enter:

[1416] "I'd like to set aside 30 minutes for market analysis and 45 minutes for new product proposals."

[1417] Also, if you want to search for recording data for a specific meeting ID, "meeting001," enter the following:

[1418] "meeting001"

[1419] Furthermore, if you want to review the accumulated ideas, you can make a request to the generative AI model with the following prompt:

[1420] "Show me new product proposal ideas extracted from past meetings."

[1421] Through these specific operations, the system of the present invention enables efficient management of meeting progress and reuse of recorded meeting content and ideas, thereby aiming to promote efficient management and innovation in organizations.

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

[1423] Step 1:

[1424] The user inputs the agenda and scheduled time of the meeting into the terminal.

[1425] As a specific example of operation, a user inputs "market analysis," "30 minutes," "new product proposal," and "45 minutes" into an input form on a terminal.

[1426] Input: Meeting agenda (market analysis, new product proposal), estimated time for each agenda item (30 minutes, 45 minutes)

[1427] Output: Meeting agenda (market analysis: 30 minutes, new product proposal: 45 minutes)

[1428] The terminal receives the input information and generates a meeting agenda.

[1429] Step 2:

[1430] The terminal notifies the user of the start of the conference based on the set agenda.

[1431] As a specific example of how this works, a pop-up message will appear saying "Please start the meeting."

[1432] Input: Meeting agenda

[1433] Output: Notification of meeting start

[1434] The user clicks the Start Conference button.

[1435] As a specific example of operation, the user clicks the "Start" button.

[1436] Input: User action (clicking the start button)

[1437] Output:Confirmation of meeting start

[1438] Step 3:

[1439] The terminal manages the progress of each agenda item according to the time allocation.

[1440] As a specific example of operation, the terminal notifies by voice or on the screen that the topic "Market Analysis" has started.

[1441] Input: Meeting agenda, meeting start confirmation

[1442] Output: Agenda start notification (market analysis, new product proposal in 30 minutes)

[1443] After 30 minutes, a notice will be given to move on to the next agenda item, "New product proposals."

[1444] As a specific example of how it works, the terminal will display, "The next topic is 'New product proposals.'"

[1445] Input: Time passed (30 minutes)

[1446] Output: Next Agenda Notification

[1447] Step 4:

[1448] When the conference ends, the terminal notifies the user of the end of the conference.

[1449] As a specific example of operation, the message "The meeting will end" is displayed and an audio notification is also given.

[1450] Input: Meeting agenda complete, all items closed

[1451] Output: Notification of end of meeting

[1452] The user confirms the end of the conference.

[1453] As a specific example of the operation, the user clicks the "Confirm termination" button.

[1454] Input: User operation (clicking the confirmation button to exit)

[1455] Output: Official record of meeting end

[1456] Step 5:

[1457] To start recording a conference, the user enters the conference ID into the terminal.

[1458] As a specific example of operation, the user enters "meeting001" and clicks the "Start Recording" button.

[1459] Input: Meeting ID (meeting001)

[1460] Output: Recording start command

[1461] The server takes the current timestamp and combines it with the conference ID to generate the recording filename.

[1462] As a specific example of operation, the server generates a file name such as "meeting001_20231012_1500.wav".

[1463] Input: Meeting ID, current timestamp

[1464] Output: Recording file name (meeting001_20231012_1500.wav)

[1465] The recorded data is stored on the server and accumulated in a database along with the file name and timestamp.

[1466] As a specific example of operation, a recording file is generated and an entry called "meeting001_20231012_1500.wav" is saved in the database.

[1467] Input: Recording data, recording file name, timestamp

[1468] Output: Database entries

[1469] Step 6:

[1470] To search for past conference recordings, a user inputs a specific keyword (e.g., a conference ID) into the terminal.

[1471] As a specific example of operation, a user enters "meeting001" into the search form on the device and clicks the "Search" button.

[1472] Input: Search keyword (meeting001)

[1473] Output: Search results request

[1474] The server searches for recording files that match the keywords and displays the results to the user.

[1475] As a specific example of operation, the server searches the database and displays a list of search results including "meeting001_20231012_1500.wav".

[1476] Input: Search keywords, database

[1477] Output: Search results (meeting001_20231012_1500.wav)

[1478] Step 7:

[1479] The user provides the minutes and recording data generated after the meeting to the terminal.

[1480] As a specific example of operation, the user uploads the minutes text and provides the meeting recording file to the terminal by dragging and dropping it.

[1481] Input: minutes text, recording data file

[1482] Output: Data Request

[1483] The server extracts useful ideas and suggestions from the provided text data and stores them in an internal database.

[1484] As a specific example of operation, the server analyzes the text of the minutes, extracts "ideas for improving the new product concept," and stores them in a database.

[1485] Input: minutes text, audio recording data

[1486] Output: Extracted ideas, database entries

[1487] Step 8:

[1488] A user uses a terminal to make a request to view the stored ideas.

[1489] As a specific example of operation, a user enters "new product proposal" into the "idea search" form on the terminal and clicks the "search" button.

[1490] Input: Idea search keyword (new product proposal)

[1491] Output: Search results request

[1492] The server searches the database for relevant ideas and displays the results in a list.

[1493] As a specific example of operation, the server searches for related ideas and displays results including "ideas for improving new product concepts" on the user's terminal.

[1494] Input: idea search keywords, database

[1495] Output: Search results (improvement ideas for new product concepts)

[1496] (Application example 1)

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

[1498] Meetings and discussions in modern manufacturing sites require efficient progress and record management. However, many meetings have long agendas, time management is inadequate, and important proposals and ideas are often not properly recorded. Furthermore, content discussed in previous meetings is rarely reused, making efficient management difficult. In addition, the reliance on human labor to conduct meetings in manufacturing sites is an obstacle to improving efficiency.

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

[1500] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes of the meeting, means for displaying the extracted ideas, and means for cooperating with factory robots to efficiently manage the progress of meetings at the manufacturing site. This makes it possible to effectively manage meetings at the manufacturing site and easily search for and reuse past discussions and proposals.

[1501] A "meeting agenda" refers to the specific topics or themes to be discussed at a meeting.

[1502] "Scheduled Time" refers to the planned time allocated for discussion of each agenda item.

[1503] "Means of notification" refers to the method or device for announcing the start or end of a meeting or the transition of agenda items.

[1504] "Means for managing progress" refers to a system or device that supervises the progress of a meeting in an orderly manner based on a set plan or agenda.

[1505] "Means for recording and storing audio" refers to systems or devices that record meeting conversations and discussions and store them as digital data.

[1506] "Means for searching recorded data" refers to a system or device that searches for previously recorded conference audio data using specific keywords or conditions.

[1507] "Means for extracting and storing ideas" refers to systems or devices that automatically extract important suggestions and ideas from audio recordings and minutes and store them in a database.

[1508] "Factory robots" refer to autonomous robots used to assist with work and manage meeting progress in manufacturing sites.

[1509] "Manufacturing site" refers to a location where products or parts are manufactured, such as a factory or production line.

[1510] "Means for efficiently managing the progress of meetings" refers to systems and devices that ensure that meetings proceed smoothly and that time management and agenda transitions are carried out effectively.

[1511] "Past recording data" refers to audio data recorded and stored during meetings and conferences.

[1512] The present invention introduces a factory robot into a conference management system to improve the efficiency of conference progress management and recording at manufacturing sites.

[1513] System programs and hardware

[1514] The system primarily utilizes the following hardware and software:

[1515] 1. Factory robot: Supports meeting management, recording, and notifications.

[1516] 2. Server: Stores recording data and minutes, and extracts and displays ideas.

[1517] 3. Device (smartphone or PC): Used by users to set the meeting agenda and search for recording data.

[1518] DETAILED DESCRIPTION OF THE INVENTION

[1519] 1. Setting the meeting agenda

[1520] The user inputs the meeting topic and scheduled time using the terminal, and the meeting agenda is set in the system. For example, "Production line optimization: 45 minutes" and "Equipment maintenance planning: 30 minutes."

[1521] 2. Starting and managing meetings

[1522] When a meeting begins, the factory robot announces the first item on the agenda based on the set agenda and then proceeds with the meeting. At the end of each item, it automatically notifies the user to move on to the next item.

[1523] 3. Starting recording and data accumulation

[1524] A factory robot records the meeting, and the server stores the recorded data. The server manages the recording files using the meeting ID and timestamp. For example, the server combines the meeting ID "meeting001" with the timestamp "20230101123000" and saves the file with the file name "meeting001_20230101123000.wav."

[1525] 4. End of meeting notice

[1526] When the meeting ends, the factory robot announces, "The meeting is ending."

[1527] 5. Searching and reusing stored data

[1528] When a user enters a specific keyword (e.g., "production line optimization") into the terminal, the server searches for relevant audio recordings and displays the results.

[1529] 6. Idea extraction and display

[1530] The server automatically extracts useful ideas from the recordings and minutes and stores them in a database, which users can then view using their devices.

[1531] Specific examples of system processing

[1532] Program processing description

[1533] Setting the meeting agenda: The server registers the topic and scheduled time entered by the user as an agenda in the system.

[1534] Meeting progress and management: The factory robot manages the time and notifies the start and end of each agenda item, which is recorded by the server.

[1535] Recording initiation and storage: The factory robot records the meeting audio, and the server stores the data using a timestamp and the meeting ID.

[1536] Searching audio recordings: When a user enters a search keyword, the server searches the stored audio recordings and returns the results.

[1537] Idea extraction and display: The server extracts important ideas from the recording data, stores them in a database, and displays them to the user.

[1538] Hardware and software used:

[1539] Factory robot: Announces and records meeting progress.

[1540] Server: Stores data, searches, and processes idea extraction.

[1541] Device (smartphone or PC): The user sets the agenda and searches for data.

[1542] Prompt Sentence Examples

[1543] "Please extract important suggestions and ideas from the following meeting recording: Meeting ID: Production Line Optimization_20231030120000.wav"

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

[1545] Step 1:

[1546] A user uses a terminal to input the meeting agenda and scheduled time. The input agenda and scheduled time are sent to the server and registered in the system as an agenda. At this time, the agenda and time are saved in the database. Example input data: "Production line optimization: 45 minutes", "Equipment maintenance plan: 30 minutes". The output is the meeting agenda saved on the server.

[1547] Step 2:

[1548] Before the meeting starts, the server sends the agenda data to the factory robot. The factory robot performs initialization and notifies the user when the meeting starts. Specifically, the robot announces, "The meeting will start." The output is a notification that the meeting has started.

[1549] Step 3:

[1550] When the meeting begins, the factory robot announces the first topic based on the agenda and the meeting proceeds. It notifies the user by voice when each topic begins and ends, and automatically notifies the user when the next topic will be discussed after a set time has elapsed. The server records this information. At this time, the robot announces, "We will begin optimizing the production line," and after 45 minutes, announces, "We will move on to the next topic."

[1551] Step 4:

[1552] When a user inputs a command to start recording a meeting, the factory robot starts recording and sends the audio data to the server in real time. The server generates a recording file name using the meeting ID and timestamp and saves it in a database. The input is the command to start the meeting, and the output is a recording data file with a timestamp. For example, the file name might be "meeting001_20230101123000.wav."

[1553] Step 5:

[1554] When the meeting ends, the factory robot notifies the server that the meeting is ending. The server recognizes this and saves the recording file. The output is a notification that the meeting has ended and that the recording has stopped.

[1555] Step 6:

[1556] The user inputs a command into the terminal to search for audio recordings using specific keywords. The server searches the database for matching files and displays the results to the user. For example, if the user searches for "production line optimization," a list of related audio recordings is displayed. The input is the search keyword, and the output is a list of search results.

[1557] Step 7:

[1558] The server automatically extracts useful ideas from audio recordings and meeting minutes. It uses a generative AI model to do this and stores the extracted ideas in a database. Data processing involves converting the audio data into text and extracting useful information. The output is a list of ideas. As a specific example, "ideas for new products" are extracted.

[1559] Step 8:

[1560] Users can use their terminals to view the accumulated ideas. The user inputs a request into the terminal, and the server searches the database for relevant ideas and displays a list of the results. The input is a request to view ideas, and the output is a list of ideas. An example of a prompt is, "Please extract important suggestions and ideas from the following meeting recording data. Meeting ID: Production Line Optimization_20231030120000.wav."

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

[1562] The system of the present invention not only manages the progress of a meeting, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage the meeting more effectively. Specific embodiments are described below.

[1563] Meeting progress management implementation example

[1564] 1. Setting the meeting agenda

[1565] The user sets the meeting topics and scheduled times using the terminal, and creates a meeting agenda by inputting the topic name and scheduled time for each topic.

[1566] 2. Starting and managing meetings

[1567] The device notifies the start of the meeting based on the set agenda. The user starts the meeting, and the device manages the progress of each agenda item according to the time allocation. For example, the device notifies the start and end of "Agenda A," and then moves on to "Agenda B."

[1568] 3. End of meeting notification

[1569] When all the agenda items have been completed, the terminal will notify the user that the meeting will end. The user will then confirm that they wish to end the meeting.

[1570] Embodiments of storing and searching audio data

[1571] 1. Starting recording and data accumulation

[1572] To start recording a conference, the user enters the conference ID into the terminal. After recording starts, the server stores the recorded data along with a timestamp.

[1573] 2. Search for recording data

[1574] The user inputs search keywords into the terminal to search for past recorded data. The server searches for recorded data based on the specified keywords and displays the results to the user.

[1575] Idea extraction and display embodiment

[1576] 1. Extracting ideas from minutes and audio recordings

[1577] Users provide minutes and audio recordings to their devices, and the server analyzes, extracts, and stores ideas from the data.

[1578] 2. Displaying accumulated ideas

[1579] A user uses a terminal to make a request to view the stored ideas, and the server searches the database for relevant ideas and displays them to the user.

[1580] Embodiment of Emotion Engine

[1581] 1. Incorporating an emotional engine

[1582] An emotion engine is built into the system, and the device analyzes the user's voice and facial expressions in real time during the meeting to generate emotion data.

[1583] 2. Use of Emotional Data

[1584] The server adjusts the progress of the meeting based on the emotional data collected in real time. For example, if a participant is feeling stressed during the meeting, it will suggest slowing down the progress or changing the agenda.

[1585] 3. Accumulation and analysis of emotional data

[1586] The server accumulates emotional data and later analyzes it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past emotional data, it is possible to determine the impact of specific agenda items on participants and the optimal way to proceed with a meeting.

[1587] Specific examples of program processing

[1588] 1. Setting the meeting agenda

[1589] The user sets up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[1590] 2. Meeting progress management

[1591] The device will start with "market analysis" and then move on to "new product proposals" after 30 minutes.

[1592] 3. Recording and Data Storage

[1593] The server saves the recording data of the meeting with a timestamp, such as "meeting001_20230415103000.wav."

[1594] 4. Searching for Recording Data

[1595] The user searches for "meeting001" and the server displays the relevant recordings.

[1596] 5. Idea extraction

[1597] If the minutes contain "ideas for improving new product concepts," the server extracts and stores them.

[1598] 6. Emotional Recognition and Regulation

[1599] The device uses an emotion engine to recognize when the user is feeling stressed during a meeting and adjusts the progress to ease the stress.

[1600] 7. Accumulation and analysis of emotional data

[1601] After the meeting ends, the server analyzes the accumulated emotional data and uses it to help guide the next meeting.

[1602] The above is a specific embodiment of the present invention. This system has the function of efficiently managing the progress of meetings, extracting and reusing useful ideas, and optimizing meetings based on the emotions of participants.

[1603] The processing flow will be explained below.

[1604] Meeting progress management process steps

[1605] Step 1:

[1606] The user sets the meeting topic and scheduled time using the terminal. Specifically, the user inputs the topic name and scheduled time for each topic (e.g., "Market Analysis (30 minutes)") and creates a meeting agenda.

[1607] Step 2:

[1608] The terminal notifies the user that the conference is about to begin. When the conference begins, the terminal displays the message "Conference is about to begin" to prompt the user to start the conference.

[1609] Step 3:

[1610] The terminal manages the progress of the meeting. Based on the set agenda, the terminal displays the items in order and monitors the scheduled time for each item. Users can proceed with the discussion according to the displayed items.

[1611] Step 4:

[1612] The terminal will notify the user when it is time to move on to the next topic. For example, after 30 minutes of "Market Analysis," the terminal will display the message, "The next topic is 'New Product Proposal (45 minutes)'."

[1613] Step 5:

[1614] The terminal notifies the user that the conference is over. When all the agenda items have been completed, the terminal displays the message "The conference is over" to notify the user that the conference is over.

[1615] Recording data storage and retrieval processing steps

[1616] Step 1:

[1617] To start recording a meeting, the user enters the meeting ID into the terminal. Presses the Start Recording button and enters the meeting ID (e.g., "meeting001").

[1618] Step 2:

[1619] The server creates a recording file. The server takes the current timestamp and combines it with the meeting ID to generate a recording file name (e.g., "meeting001_20230415103000.wav"). The recording data is saved on the server with this file name.

[1620] Step 3:

[1621] The user searches for recorded data. The user enters a specific keyword (e.g., "meeting001") into the terminal and makes a search request.

[1622] Step 4:

[1623] The server searches for recorded data. The server searches for recorded files in the specified directory based on keywords and displays the search results to the user.

[1624] Idea extraction and display process steps

[1625] Step 1:

[1626] The user provides the minutes and audio data generated after the meeting to the terminal, and then uploads this data and sends it to the server.

[1627] Step 2:

[1628] The server extracts ideas. The server analyzes the provided text and audio data, identifies specific keywords and phrases, and extracts ideas. The extracted ideas are stored in an internal database.

[1629] Step 3:

[1630] A user makes a request to view the stored ideas. The user uses a terminal to input a command to display the stored ideas.

[1631] Step 4:

[1632] The server displays the accumulated ideas. The server searches for related ideas from its internal database and displays the results to the user. The user can review the displayed ideas and reuse them as needed.

[1633] Processing Steps of Emotion Engine Embodiments

[1634] Step 1:

[1635] The system incorporates an emotion engine that analyzes the user's voice and facial expressions to generate emotion data in real time.

[1636] Step 2:

[1637] During a meeting, users input their voice and facial expressions into the device, which then sends the voice data and camera footage to the emotion engine for analysis.

[1638] Step 3:

[1639] The server receives the emotional data and adjusts the progress of the meeting. For example, if a participant feels stressed during the meeting, the server will use that information to suggest slowing down the progress.

[1640] Step 4:

[1641] The server accumulates emotional data. After the meeting ends, the emotional data is stored on the server and can be analyzed later.

[1642] Step 5:

[1643] The server analyzes the emotional data and generates feedback based on past emotional data to improve meeting efficiency and participant satisfaction, which can be used for future meetings.

[1644] These are the specific processing steps of the system that combines the emotion engine. As a result, the system efficiently manages the progress of meetings and provides an optimal discussion environment that reflects the emotions of participants.

[1645] Example 2

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

[1647] While conventional conferencing systems provide basic functions such as meeting progress management, storing and searching recorded data, and extracting and displaying ideas, they are limited in their ability to optimize meeting progress while taking participants' emotions into account. Furthermore, they lack the ability to effectively utilize stored recorded data, reuse past discussions, or analyze participants' emotions in real time and adjust meetings accordingly. This creates challenges that make it difficult to improve meeting efficiency and participant satisfaction.

[1648] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means. In this invention, the server includes means for setting the agenda and scheduled time of the conference, means for notifying the start and end of the conference, means for managing the progress of the conference based on a plan, means for recording and storing the audio of the conference, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, means for analyzing the user's voice and facial expression to generate emotional data, means for adjusting the progress of the conference based on the generated emotional data, and means for accumulating and analyzing the emotional data. This makes it possible to optimize the management of the progress of the conference by taking into account the emotional state of each participant, thereby improving the efficiency of the conference and the satisfaction of the participants.

[1649] The "means for setting the agenda and scheduled time of the meeting" is a means for providing a function for the user to input and save the name of each agenda item and the scheduled time of each meeting.

[1650] The "means for notifying the start and end of a conference" is a means for providing a function for notifying a user of the start and end timing of a conference.

[1651] The "means for managing the progress of a meeting based on a plan" is a means for automatically managing the progress of a meeting according to a preset meeting agenda.

[1652] "Means for recording and storing conference audio" refers to means for providing a function for recording audio during a conference and storing it in a database or the like.

[1653] The "means for searching stored recorded data" refers to a means for providing a function for searching for a specific recording using a search keyword from stored recorded data.

[1654] "Means for extracting and storing ideas from audio recordings and minutes" refers to means for providing a function for analyzing, extracting, and storing useful ideas from audio recordings and minutes.

[1655] The "means for displaying extracted ideas" is a means for providing a function for displaying accumulated ideas to a user.

[1656] The "means for analyzing the user's voice and facial expression and generating emotion data" is a means for providing a function for analyzing the content of what the user says and the facial expression and generating emotion data.

[1657] The "means for adjusting the progress of a meeting based on the generated emotion data" is a means for providing a function for adjusting the progress speed and content of a meeting by using the generated emotion data in real time.

[1658] "Means for storing and analyzing emotional data" refers to a means for storing collected emotional data in a database and providing a function for later analysis.

[1659] The system of the present invention not only manages the progress of meetings, stores recorded data, and extracts and displays ideas, but also recognizes the emotions of users to manage meetings more effectively. Specific embodiments of this system are described below.

[1660] Meeting progress management

[1661] To manage the progress of a meeting, the user first sets up the meeting agenda using their terminal. The user logs in and enters each topic and the scheduled time on the "Meeting Agenda Settings" screen. This information is sent from the terminal to the server, and the server stores the received agenda in a database. For example, a user can set up "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[1662] When a meeting starts, the terminal notifies the user that the meeting has started based on the set agenda. The terminal manages the progress of each agenda item, for example, starting a timer for "Market Analysis (30 minutes)" and notifying the user to move on to "New Product Proposal (45 minutes)" after 30 minutes. When all agenda items have been completed, the terminal notifies the user that "The meeting will end," and the user confirms the end of the meeting.

[1663] Storage and retrieval of recorded data

[1664] To store recording data for a meeting, a user enters the meeting ID into their device and starts recording. The recorded data is sent to the server and saved as a file with a timestamp, such as "meeting001_20230415103000.wav."

[1665] Users can search for past recordings by entering search keywords into their devices. The server searches the database based on the keywords and provides relevant recording files to the user. For example, if a user enters "meeting001," the server will search for and display relevant recordings.

[1666] Idea extraction and display

[1667] It also has the ability to extract useful ideas from meeting minutes and audio recordings. When users provide minutes and audio recordings to their devices, the server analyzes the data, extracts ideas, and stores them. For example, if the minutes contain "ideas for improving new product concepts," the server extracts these and stores them in a database.

[1668] A user can use a terminal to make a request to view the stored ideas, and the server will search the database for relevant ideas and display them to the user.

[1669] Emotion Engine

[1670] The emotion engine is used to analyze the user's voice and facial expressions in real time during a meeting and generate emotion data. The device analyzes the user's voice and camera footage during the meeting, generates emotion data such as "stress" and "joy," and sends it to the server.

[1671] Based on the generated emotion data, the server can adjust the progress of the meeting. For example, if the emotion data indicates "increasing stress," the device will notify the user and suggest relaxing the progress of the meeting or changing the agenda.

[1672] The server stores the emotional data in a database and analyzes it after the meeting. This allows it to provide feedback to improve meeting efficiency and participant satisfaction. By analyzing past data, it can identify the impact of specific agenda items on participants and the optimal way to proceed with the meeting.

[1673] Prompt Sentence Examples

[1674] Prompt: "Please give us an overview of a system that can manage meeting progress, store recording data, extract and display ideas, and recognize emotions."

[1675] Prompt: "Tell me how to adjust meeting flow based on emotional data."

[1676] This system enables efficient management of the progress of meetings, reuses accumulated data, and adjusts the progress based on the emotions of participants, thereby improving meeting efficiency and participant satisfaction.

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

[1678] Meeting progress management implementation example

[1679] Step 1:

[1680] The user logs in to the terminal and accesses the "Meeting Agenda Settings" screen. The user enters the topic name and scheduled time for each agenda item and clicks the "Save Agenda" button. The entered information, which is the topic name and scheduled time, is sent from the terminal to the server. The server receives the data and saves it in a database. As a specific example of operation, the user enters and saves "Market Analysis (30 minutes)" and "New Product Proposal (45 minutes)."

[1681] Step 2:

[1682] The server sends instructions to the terminal notifying the start of the meeting based on pre-set agenda information. The terminal receives the instructions and displays a meeting start notification to the user. The user clicks the "Start Meeting" button to start the meeting. The terminal then proceeds with the agenda according to the set agenda. As a specific example of operation, a timer for "Market Analysis (30 minutes)" is started, and when the timer reaches 30 minutes, a notification is sent to move on to the next item, "New Product Proposal."

[1683] Step 3:

[1684] When all the agenda items have been completed, the server sends a notification to end the meeting to the terminal, and the terminal displays "Ending the meeting." The user clicks the "Confirm End" button, and the meeting officially ends. The server records the end information in the database.

[1685] Embodiments of storing and searching audio data

[1686] Step 1:

[1687] To start recording a meeting on a device, a user enters the meeting ID and presses the "Start Recording" button. The input data is the meeting ID. The device starts recording and transfers the data to the server. The server saves the received recording data with a file name that includes a timestamp, such as "meeting001_20230415103000.wav."

[1688] Step 2:

[1689] To search for recorded data, a user enters a search keyword into the device and clicks the "Search" button. The input data is the search keyword. The server searches the database based on the received keyword and extracts related recorded data. The server returns a list of extracted recorded files to the device, which then displays it to the user. As a specific example of operation, entering "meeting001" will display related recorded data.

[1690] Idea extraction and display embodiment

[1691] Step 1:

[1692] The user uploads meeting minutes or audio recordings to the device. The input data is the minutes or audio recording files. The device transfers the data to the server, which analyzes the data and extracts useful ideas. For example, it generates tags such as "ideas for improving a new product concept" and stores them in a database.

[1693] Step 2:

[1694] A user makes a request to view ideas stored on a terminal. The input data is the view request. The server receives the request and searches the database for related ideas. The server returns the search results to the terminal, which displays them to the user. As a specific example of operation, when a user requests an "idea list," related ideas are displayed.

[1695] Embodiment of Emotion Engine

[1696] Step 1:

[1697] The system is equipped with an emotion engine that analyzes the user's voice and facial expressions in real time to generate emotion data. The input data is the user's voice and camera footage. The device analyzes this data to generate emotion data such as "stress" or "joy" and sends it to the server. As a specific example, the emotion engine analyzes the content of the user's remarks and changes in facial expressions during a meeting.

[1698] Step 2:

[1699] Based on the generated emotion data, the server adjusts the progress of the meeting. The input data is emotion data. The server analyzes the received emotion data and sends instructions to the terminal suggesting changes to the progress speed or agenda as necessary. The terminal notifies the user of the instructions. A specific example of operation is a notification that "stress is increasing" and a suggestion to ease the progress.

[1700] Step 3:

[1701] After the meeting ends, the server stores the collected emotional data in a database for later analysis. The input data is the emotional data collected during the meeting. The server analyzes the data, determines the impact that specific agenda items had on participants, and the optimal way to proceed with the meeting, and provides feedback. A specific example of how it works is to generate analysis results such as "a specific agenda item caused the most stress."

[1702] (Application example 2)

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

[1704] Conventional meeting management systems have basic functions such as agenda and progress management, recording and search, and idea extraction and display. However, they lack the ability to analyze participants' emotions in real time to optimize the progress of the meeting. This can easily lead to situations where participants feel stressed or dissatisfied, reducing the efficiency and effectiveness of the meeting. Furthermore, particularly in dynamic environments such as factory floors, flexible meeting management that can respond to emotional fluctuations is required.

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

[1706] In this invention, the server includes means for setting the agenda and scheduled time of the meeting, means for notifying the start and end of the meeting, means for managing the progress of the meeting based on a plan, means for recording and storing the audio of the meeting, means for searching the stored recorded data, means for extracting and storing ideas from the recorded data and minutes, means for displaying the extracted ideas, and means for analyzing the emotions of participants in real time and adjusting the progress. This allows the progress of the meeting to be optimized in accordance with the emotional state of the participants, enabling efficient and satisfying meeting management.

[1707] A "means for setting the meeting agenda and scheduled time" is a device or software for predetermining and recording the main topics of a meeting and the time allotted for each topic.

[1708] The "means for notifying the start and end of a conference" refers to a device or software for notifying participants of the start and end times of a conference.

[1709] A "means for managing the progress of a meeting based on a plan" is a device or software for supervising and coordinating the progress of a meeting according to a set agenda and scheduled time.

[1710] "Means for recording and storing conference audio" refers to a device or software that records the audio during a conference and stores the data in a form that can be accessed later.

[1711] "Means for searching stored recorded data" refers to a device or software that searches stored recorded data based on specified keywords or conditions and obtains the required information.

[1712] "Means for extracting and storing ideas from audio recordings and minutes" refers to devices or software that select useful ideas from the content discussed during meetings and audio recordings, and store them in a reusable form.

[1713] The "means for displaying extracted ideas" is a device or software for visually displaying extracted ideas.

[1714] "Means for analyzing participants' emotions in real time and adjusting the progress" refers to a device or software that analyzes the voices and facial expressions of participants during a meeting and dynamically adjusts the progress of the meeting based on their emotional state.

[1715] The system of this invention is an application for managing robot operation and maintenance meetings in factories, analyzing participants' emotions in real time, and optimizing the progress of the meetings. This application is installed on smart glasses and realizes the following functions.

[1716] Setting the Meeting Agenda

[1717] Users use the smart glasses to set the meeting agenda and scheduled time. Users create a meeting agenda by entering the topic name and scheduled time for each topic through the smart glasses interface. For example, equipment maintenance can be scheduled for 30 minutes, and the proposal to introduce a new robot can be scheduled for 45 minutes.

[1718] Meeting progress management

[1719] The smart glasses notify the start of a meeting based on the set agenda. The user starts the meeting, and the smart glasses manage the progress of each agenda item according to the time allocation. For example, if equipment maintenance begins, the glasses will automatically move on to the proposal to introduce a new robot 30 minutes later.

[1720] Storage and retrieval of recorded data

[1721] The smart glasses record and store the audio of meetings. The server saves the recordings with timestamps and stores them in a searchable format. Users can easily search and view past recordings by entering search keywords.

[1722] Idea extraction and display

[1723] Users provide recorded data, and the server analyzes, extracts, and stores ideas from the data. When a user makes a viewing request, relevant ideas are displayed on the smart glasses. For example, new maintenance methods and improvement ideas recorded during a meeting can be extracted.

[1724] Use of emotion engine

[1725] An emotion engine is built into the device, and emotion data is generated by analyzing the user's voice and facial expressions in real time. The server adjusts the progress of the meeting based on the emotion data collected in real time. For example, if a participant in a meeting is feeling stressed, it may suggest slowing down the progress. After the meeting, emotion data is accumulated and analyzed, and improvement measures that will lead to increased meeting efficiency and participant satisfaction are provided.

[1726] Hardware and software used

[1727] This system uses the following hardware and software:

[1728] 1. Smart glasses: Provides data collection and user interface.

[1729] 2. Emotion engine: An AI model that analyzes speech and facial expressions (e.g., Emotional Analysis API).

[1730] 3. Recording and retrieval server: A cloud server for storing, searching, and analyzing recording data (e.g., cloud storage and search engine).

[1731] 4. Data analysis engine: An AI model (e.g., a Natural Language Processing model) that analyzes and extracts useful ideas and maintenance techniques from recorded data.

[1732] Examples and prompts

[1733] For example, a factory manager schedules a meeting and inputs the following agenda items: "Equipment maintenance (30 minutes)" and "Proposal for introducing a new robot (45 minutes)." As the meeting progresses, the smart glasses analyze the user's emotions and adjust the progress at the appropriate time.

[1734] Example prompt sentence:

[1735] "Please set up today's meeting agenda. 'Facility Maintenance' takes 30 minutes, and 'New Robot Implementation Proposal' takes 45 minutes."

[1736] "Analyze participants' emotions in real time during the meeting and adjust the pace if they are feeling stressed."

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

[1738] Step 1:

[1739] A user uses smart glasses to set the meeting agenda and scheduled time. The user inputs the agenda name and the scheduled time for each agenda item. This input data is received by the device and set as the meeting agenda. The input data can be "equipment maintenance (30 minutes)" or "proposed introduction of a new robot (45 minutes)," and the output data is the set agenda.

[1740] Step 2:

[1741] The terminal notifies the start of the conference based on the set agenda. The user confirms the start. A start signal is sent to the server, and the conference begins. The input data is the conference start confirmation from the user, and the output data is the conference start notification.

[1742] Step 3:

[1743] The terminal manages the progress of the meeting based on the time allocation of each agenda item. It notifies the start and end of each agenda item and automatically moves on to the next agenda item. The input data is the agenda setting information and elapsed time, and the output data is the start and end notification of each agenda item.

[1744] Step 4:

[1745] The smart glasses record the audio during the meeting and send the data to the server, which stores the recorded data with a timestamp. The input data is real-time audio data, and the output data is a time-stamped audio file.

[1746] Step 5:

[1747] The user inputs keywords into the terminal to search for recorded data. The server searches for recorded data based on the keywords and displays the results to the user. The input data are the search keywords, and the output data are the recorded data as search results.

[1748] Step 6:

[1749] Users provide audio recordings and minutes, and the server analyzes and extracts ideas from the data. The extracted ideas are stored in a database. The input data is the audio recordings and minutes, and the output data is the extracted ideas.

[1750] Step 7:

[1751] A user makes a request to browse stored ideas using a terminal. The server searches the database for relevant ideas and displays them to the user. The input data is the browsing request, and the output data is the displayed ideas.

[1752] Step 8:

[1753] The device uses an emotion engine to analyze the user's voice and facial expressions during the meeting and generate emotion data in real time. The input data is the user's voice and facial expression data, and the output data is the analyzed emotion data.

[1754] Step 9:

[1755] The server adjusts the progress of the meeting based on the emotion data collected in real time, adjusting the progress speed according to the emotion data and proposing changes to the agenda as necessary. The input data is the real-time emotion data, and the output data is the adjusted progress instructions.

[1756] Step 10:

[1757] After the meeting, the server analyzes the accumulated emotional data and provides feedback to improve the efficiency of the meeting and the satisfaction of the participants. The input data is the accumulated emotional data, and the output data is the feedback information.

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

[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 robot 414.

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

[1762] FIG. 9 is a diagram illustrating 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 actions 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[1779] The following is further disclosed regarding the above embodiment.

[1780] (Claim 1)

[1781] a means of setting meeting agendas and scheduled times;

[1782] a means for signaling the start and end of a conference;

[1783] A means of managing the progress of meetings based on a plan;

[1784] A means for recording and storing the audio of the meeting;

[1785] A means for searching the stored recording data;

[1786] A means to extract and store ideas from recordings and minutes,

[1787] a means for displaying the extracted ideas;

[1788] A system including:

[1789] (Claim 2)

[1790] 10. The system of claim 1, further comprising means for searching through stored past recording data and displaying previously discussed content in a reusable format.

[1791] (Claim 3)

[1792] 10. The system of claim 1, further comprising means for utilizing timestamps in managing the progress of the conference and storing the recorded data.

[1793] "Example 1"

[1794] (Claim 1)

[1795] a means of setting meeting agendas and scheduled times;

[1796] a means for signaling the start and end of a conference;

[1797] A means of managing the progress of meetings based on a plan;

[1798] A means for recording and storing the audio of the meeting;

[1799] A means for searching the stored recording data;

[1800] A means of extracting and storing useful information from recording data and minutes,

[1801] means for displaying the extracted useful information;

[1802] A system including:

[1803] (Claim 2)

[1804] 10. The system of claim 1, further comprising means for searching through stored past recording data and displaying previously discussed content in a reusable format.

[1805] (Claim 3)

[1806] 2. The system according to claim 1, further comprising means for utilizing time information in managing the progress of the conference and storing the recorded data.

[1807] "Application Example 1"

[1808] (Claim 1)

[1809] a means of setting meeting agendas and scheduled times;

[1810] a means for signaling the start and end of a conference;

[1811] A means of managing the progress of meetings based on a plan;

[1812] A means for recording and storing the audio of the meeting;

[1813] A means for searching the stored recording data;

[1814] A means to extract and store ideas from recordings and minutes,

[1815] a means for displaying the extracted ideas;

[1816] A means to efficiently manage meetings at manufacturing sites in cooperation with factory robots,

[1817] A system including:

[1818] (Claim 2)

[1819] 10. The system of claim 1, further comprising means for searching through stored past recording data and displaying previously discussed content in a reusable format.

[1820] (Claim 3)

[1821] 10. The system of claim 1, further comprising means for utilizing timestamps in managing the progress of the conference and storing the recorded data.

[1822] "Example 2: Combining Emotion Engines"

[1823] (Claim 1)

[1824] a means of setting meeting agendas and scheduled times;

[1825] a means for signaling the start and end of a conference;

[1826] A means of managing the progress of meetings based on a plan;

[1827] A means for recording and storing the audio of the meeting;

[1828] A means for searching the stored recording data;

[1829] A means to extract and store ideas from recordings and minutes,

[1830] a means for displaying the extracted ideas;

[1831] A means for analyzing a user's voice and facial expression to generate emotion data;

[1832] A means for adjusting the progress of a meeting based on the generated emotion data;

[1833] a means for storing and analyzing emotional data;

[1834] A system including:

[1835] (Claim 2)

[1836] 10. The system of claim 1, further comprising means for searching through stored past recording data and displaying previously discussed content in a reusable format.

[1837] (Claim 3)

[1838] 10. The system of claim 1, further comprising means for utilizing timestamps in managing the progress of the conference and storing the recorded data.

[1839] "Application example 2 when combining emotion engines"

[1840] (Claim 1)

[1841] a means of setting meeting agendas and scheduled times;

[1842] a means for announcing the start and end of a meeting;

[1843] A means of managing the progress of meetings based on a plan;

[1844] A means for recording and storing the audio of the meeting;

[1845] A means for searching the stored recording data;

[1846] A means to extract and store ideas from recordings and minutes,

[1847] a means for displaying the extracted ideas;

[1848] A means to analyze participants' emotions in real time and adjust the progress, 【18...

Claims

1. a means of setting meeting agendas and scheduled times; a means for signaling the start and end of a conference; A means of managing the progress of meetings based on a plan; A means for recording and storing the audio of the meeting; A means for searching the stored recording data; A means to extract and store ideas from recordings and minutes, a means for displaying the extracted ideas; A system including:

2. 2. The system of claim 1, further comprising means for searching through stored past recording data and displaying previously discussed content in a reusable format.

3. 2. The system according to claim 1, further comprising means for utilizing time stamps in managing the progress of the conference and storing the recorded data.

Images