Post-meeting support system, method, and program

Abstract

Streamline post-meeting tasks. [Solution] According to one embodiment, the post-meeting business support system includes an acquisition unit that acquires text information generated from audio information of a meeting, a task processing unit that executes a plurality of tasks based on the text information, a display unit that displays the execution results of the plurality of tasks and a message input field for the user to enter a message, and a dialogue processing unit that can update the execution results based on the message entered by the user in the message input field.

Description

Technical Field

[0001] The present invention relates to a post-meeting business support system, method, and program.

Background Art

[0002] In recent years, the use of minutes tools that automatically create meeting minutes (summaries) using generative AI has been spreading. In Cited Document 1, there is described a speech information documentation device that enables easy grasping of important matters of speeches in meetings and lectures by creating summary sentences of speech information using speech classification and stages.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Generally, after a meeting, various operations (so-called post-meeting operations) such as not only creating minutes but also sending emails according to the content of the meeting, creating materials for the next meeting, and registering in a database are performed. Conventional minutes tools only automate the creation of minutes and cannot be said to sufficiently support these post-meeting operations.

[0005] The present invention has been made in view of the above problems and aims to improve the efficiency of post-meeting operations.

Means for Solving the Problems

[0006] According to one embodiment, the post-meeting business support system includes an acquisition unit that acquires text information generated from audio information of a meeting, a task processing unit that executes a plurality of tasks based on the text information, a display unit that displays the execution results of the plurality of tasks and a message input field for the user to enter a message, and a dialogue processing unit that can update the execution results based on the message entered by the user in the message input field. [Effects of the Invention]

[0007] According to one embodiment, post-meeting tasks can be streamlined. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of the configuration of the post-meeting business support system 1000. [Figure 2] This figure shows an example of the hardware configuration of the information processing device 100. [Figure 3] This figure shows an example of the functional configuration of the post-meeting work support device 1. [Figure 4] This is a diagram showing an example of meeting information 121. [Figure 5] This figure shows an example of user information 122. [Figure 6] This figure shows an example of task information 125. [Figure 7] This figure shows an example of execution result information 127. [Figure 8] This figure shows an example of message information 128. [Figure 9] This figure shows an example of the functional configuration of user terminal 2. [Figure 10] This flowchart shows an example of a method for supporting post-meeting work. [Figure 11] This is a diagram showing an example of the display screen sc1. [Figure 12] This figure shows an example of the display screen sc2. [Figure 13] This figure shows an example of the display screen sc3. [Figure 14]This is a diagram showing an example of the display screen sc4. [Figure 15] This is a diagram showing an example of the display screen sc5. [Figure 16] This is a diagram showing an example of the display screen sc6.

Embodiments for Carrying Out the Invention

[0009] Hereinafter, each embodiment of the present invention will be described with reference to the accompanying drawings. Regarding the descriptions in the specification and drawings related to each embodiment, for components having substantially the same functional configuration, the same reference numerals will be given to omit redundant descriptions.

[0010] <System Configuration> First, an overview of the post-meeting business support system 1000 (hereinafter referred to as the "support system 1000") according to this embodiment will be described. The support system 1000 is an information processing system that executes a plurality of tasks based on text information generated from the voice information of a meeting and displays the execution results. The execution results of the tasks can be updated based on the messages input by the user in the message input field. By using the support system 1000, the user can improve the efficiency of post-meeting work.

[0011] In this specification, a meeting refers to a conversation among multiple people. A meeting is not limited to an exchange of opinions or a decision-making discussion regarding a specific topic, but includes conversations such as business negotiations, sales, interviews, and face-to-face talks. A meeting may be an offline (face-to-face) meeting or an online meeting.

[0012] Post-meeting work refers to the work carried out after a meeting. Post-meeting work includes, but is not limited to, the creation of minutes, the sending of emails according to the content of the meeting, the creation of materials for the next meeting, and registration in a database. Post-meeting work varies depending on the type of meeting.

[0013] The task is work related to post - meeting operations. The task includes, for example, but is not limited to, the post - meeting operations themselves, the work necessary to perform post - meeting operations, and the work to support post - meeting operations. The task includes summarization, illustration, extraction, evaluation, acquisition of related information, and draft creation related to the meeting.

[0014] The summarization includes summarizing the content of the meeting (recording the minutes). The illustration includes illustrating the transition of the topics.

[0015] The extraction includes extraction of keywords, extraction of questions and answers (Q&A), extraction of decisions, and extraction of next actions (tasks to be performed next).

[0016] The evaluation includes evaluation of the speaker's emotions during the meeting, evaluation of the conversation speed, evaluation during the conversation and evaluation of the conversation content, and evaluation of the meeting results.

[0017] The acquisition of related information includes acquisition of related information regarding keywords, acquisition of related information regarding topics, and acquisition of related information regarding next actions.

[0018] The draft creation includes creation of email drafts, creation of drafts of documents (such as proposals) to be used in the next meeting, creation of form drafts according to the decisions, and creation of draft registration information to an external system (such as CRM (Customer Relationship Management)) according to the decisions.

[0019] FIG. 1 is a diagram showing an example of the configuration of the support system 1000. As shown in FIG. 1, the support system 1000 includes a post - meeting operation support device 1 (hereinafter referred to as "support device 1") and a user terminal 2, which are communicably connected to each other via a network N. The network N is, for example, a wired LAN (Local Area Network), a wireless LAN, the Internet, a public switched telephone network, a mobile data communication network, or a combination thereof. In the example of FIG. 1, the support system 1000 includes one support device 1 and one user terminal 2 each, but may include a plurality of each.

[0020] Support device 1 is an information processing device that performs multiple tasks based on text information generated from audio information of a meeting. Support device 1 is, for example, a PC (Personal Computer), a smartphone, a tablet terminal, a server device, or a microcomputer, but is not limited to these.

[0021] User terminal 2 is an information processing device used by users of the support system 1000. User terminal 2 may be, for example, a PC, smartphone, or tablet device, but is not limited to these.

[0022] <Hardware configuration of the information processing device 100> Next, the hardware configuration of the information processing device 100 will be described. Figure 2 shows an example of the hardware configuration of the information processing device 100. As shown in Figure 2, the information processing device 100 comprises a processor 101, memory 102, storage 103, communication I / F 104, input device 105, output device 106, and drive device 107, all interconnected via bus B.

[0023] The processor 101 controls the various components of the information processing device 100 and realizes the functions of the information processing device 100 by loading various programs, including the OS (Operating System), stored in the storage 103, into the memory 102 and executing them. The processor 101 is, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), or a DSP (Digital Signal Processor), but is not limited to these.

[0024] Memory 102 is, for example, ROM (Read Only Memory), RAM (Random Access Memory), or a combination thereof. ROM is, for example, PROM (Programmable ROM), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), or a combination thereof. RAM is, for example, DRAM (Dynamic RAM) or SRAM (Static RAM), but is not limited to these.

[0025] Storage 103 stores various programs and data, including the OS. Storage 103 is, for example, flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or SCM (Storage Class Memories), but is not limited to these.

[0026] The communication interface 104 is an interface for connecting the information processing device 100 to an external device via the network N and controlling communication. The communication interface 104 is, for example, Bluetooth®, Wi-Fi®, ZigBee®, or Ethernet®.

[0027] The input device 105 is a device for inputting information into the information processing device 100. The input device 105 may be, but is not limited to, a mouse, keyboard, touch panel, microphone, scanner, camera, various sensors, or operation buttons.

[0028] The output device 106 is a device for outputting information from the information processing device 100. The output device 106 is, for example, a display device, a projector, a printer, a speaker, or a vibrator, but is not limited to these.

[0029] The drive device 107 is a device for reading and writing data to the recording medium 108. The drive device 107 is, for example, a magnetic disk drive, an optical disk drive, a magneto-optical disk drive, or an SD card reader, but is not limited thereto. The recording medium 108 is, for example, a CD (Compact Disc), a DVD (Digital Versatile Disc), an FD (Floppy Disk), an MO (Magneto-Optical disk), a BD (Blu-ray® Disc), a USB® memory, or an SD card, but is not limited thereto.

[0030] In this embodiment, the program may be written to the memory 102 or storage 103 during the manufacturing stage of the information processing device 100, or it may be provided to the information processing device 100 via the network N, or it may be provided to the information processing device 100 via a non-temporary, computer-readable recording medium such as the recording medium 108.

[0031] <Functional configuration of support device 1> Next, the functional configuration of the support device 1 will be described. Figure 3 is a diagram showing an example of the functional configuration of the support device 1. As shown in Figure 3, the support device 1 comprises a communication unit 11, a storage unit 12, and a control unit 13.

[0032] The communication unit 11 is implemented by the communication interface 104. The communication unit 11 sends and receives information with the user terminal 2 via the network N.

[0033] The memory unit 12 is implemented by memory 102 and storage 103. The memory unit 12 stores meeting information 121, user information 122, voice information 123, text information 124, task information 125, machine learning model 126, execution result information 127, and message information 128.

[0034] Meeting information 121 is information related to the meeting and post-meeting tasks. Meeting information 121 is set by the user via user terminal 2.

[0035] Figure 4 shows an example of meeting information 121. The meeting information 121 in Figure 4 includes the following information items: "MID", "Meeting Name", "GID", "Group Name", "Date and Time", "Type", "UID", and "Authority".

[0036] "MID" is an identifier that uniquely identifies a meeting. Hereafter, meetings with the identifier M0X may be referred to as Meeting M0X. This also applies to other identifiers. "Meeting Name" is the name of the meeting. "GID" is an identifier that uniquely identifies the group to which the meeting belongs. Groups can be arbitrarily defined, such as the meeting's theme (e.g., project), the duration of the meeting (e.g., fiscal year 2024), the department hosting the meeting (e.g., sales department), or the participants (e.g., customers). "Group Name" is the name of the group.

[0037] "Date and Time" is the date and time the meeting will be held. "Type" is the type of meeting. Meeting types include, but are not limited to, business negotiations, sales meetings, interviews, and consultations. "UID" is the identifier of the user participating in post-meeting tasks. "Permissions" is the permissions set for the user participating in post-meeting tasks. Depending on the permissions, the operations that can be performed and the information displayed on the support system 1000 will differ. Permissions include, but are not limited to, administrators, members, and guests. Note that "UID" and "Permissions" may be set for each meeting or for each group.

[0038] In the example in Figure 4, meeting M01 has the following details: "Meeting Name" is "Meeting 1", "GID" is "G01", "Group Name" is "Project X", "Date and Time" is "2024 / 11 / 8, 12:00~13:00", "Type" is "Deal", "UID" is "U01, U02, U03", and "Permissions" are "Administrator, Member, Guest". This indicates that meeting M01 (Meeting 1) was a deal related to Project X held from 12:00 to 13:00 on 2024 / 11 / 8, and that users U01, U02, and U03 participated in the post-meeting activities of this meeting, with users U01, U02, and U03 having administrator, member, and guest permissions, respectively.

[0039] Note that meeting information 121 is not limited to the example above. Meeting information 121 may include information items other than those listed above, or it may not include some of the information items listed above.

[0040] User information 122 is information about the user. User information 122 is set by the user via user terminal 2.

[0041] Figure 5 shows an example of user information 122. The user information 122 in Figure 5 includes the following information items: "UID", "Username", "Contact Information", and "Attributes". The "Attributes" include "Job Title", "Position", and "Authority".

[0042] "UID" is an identifier that uniquely identifies a user. "Username" is the user's full name. "Contact" is the user's contact information. In the example in Figure 5, the contact information is an email address, but it is not limited to this. "Attributes" are the user's attributes. "Job title" is the user's job title. "Position" is the user's position. "Permissions" are the permissions set for the user. Note that user attributes are not limited to job title, position, and permissions.

[0043] In the example in Figure 5, user U01 has the following characteristics: "Username" is "a", "Contact" is "a@xxx.com", "Job Title" is "Sales", and "Position" is "Department Manager". This indicates that user U01(a) has the contact address a@xxx.com, is a sales department manager, and is the administrator of group G01.

[0044] Note that user information 122 is not limited to the example above. User information 122 may include information items other than those listed above, or it may not include some of the information items listed above.

[0045] Audio information 123 is audio information that is a recording of the meeting's audio. Audio information 123 is received from user terminal 2.

[0046] Text information 124 is text information generated from audio information 123. Text information 124 is generated from audio information 123 by speech recognition processing. Text information 124 may be generated by the support device 1 or received from the user terminal 2.

[0047] Task information 125 is information about a task. Task information 125 may be pre-configured or may be configured by the user via the user terminal 2.

[0048] Figure 6 shows an example of task information 125. The task information 125 in Figure 6 includes the following information items: "TID", "Task Name", "Prompt", "Meeting Type", and "Attributes".

[0049] "TID" is an identifier that uniquely identifies a task. "Task Name" is the name of the task. "Prompt" is the prompt used to execute the task. The prompt corresponds to an instruction to the generating AI. "Meeting Type" is the type of meeting in which the task will be performed. "Display Attribute" is the attribute of the user who will see the task's execution results. In the example in Figure 6, the display attribute is the user's permission, but it is not limited to this. The display attribute can be any attribute of the user, such as the user's job title or position. Also, if "Display Attribute" is "-", it means that the display attribute has not been set, i.e., the execution results will be displayed to all users participating in the post-meeting work.

[0050] In the example in Figure 6, task T01 has the following characteristics: "Task Name" is "Summary", "Prompt" is "t01", "Meeting Type" is "Sales Opportunity, Job Interview", and "Display Attribute" is "-". This indicates that task T01 (Summary) is executed by prompt t01 when it is a sales opportunity or job interview, and the result of its execution is displayed to all users participating in post-meeting tasks.

[0051] Note that Task Information 125 is not limited to the example above. Task Information 125 may include information items other than those listed above, or it may not include some of the information items listed above.

[0052] The machine learning model 126 is a generative AI that performs tasks. When a prompt instructing it to perform a task is input, it outputs the result of executing the task according to the prompt. The machine learning model 126 is, but is not limited to, a Large Language Model (LLM) or a Large Multimodal Model. There may be only one machine learning model 126, or different models may be prepared for each task.

[0053] In this embodiment, the case in which the machine learning model 126 is stored in the support device 1 is described as an example, but the machine learning model 126 does not have to be stored in the support device 1. For example, the machine learning model 126 may be stored in an external device connected to the support device 1 via the network N, and prompts and execution results may be sent and received via an API.

[0054] Execution result information 127 is information indicating the execution result of the task. The execution result is generated by the machine learning model 126.

[0055] Figure 7 shows an example of execution result information 127. The execution result information 127 in Figure 7 includes the information items "RID", "MID", "TID", "Execution Date and Time", and "Execution Result".

[0056] "RID" is an identifier that uniquely identifies the result of the task's execution. "MID" is an identifier for the meeting in which the task was executed. "TID" is an identifier for the task that was executed. "Execution Date and Time" is the date and time the task was executed. "Execution Result" is the result of the task's execution.

[0057] In the example in Figure 7, the execution result R01 has "MID" as "M01", "TID" as "T01", "Execution Date and Time" as "2024 / 11 / 8, 14:00", and "Execution Result" as "r01". This indicates that the execution result RT01 is the execution result of task T01, which was executed for meeting M01 at 14:00 on 2024 / 11 / 8, and its content is r01.

[0058] Note that the execution result information 127 is not limited to the example above. The execution result information 127 may include information items other than those mentioned above, or it may not include some of the information items mentioned above.

[0059] Message information 128 is information indicating messages exchanged between the user and the support device 1. Message information 128 includes information indicating messages sent by the support device 1 to the user and information indicating messages sent by the user to the support device 1.

[0060] Figure 8 shows an example of message information 128. The message information 128 in Figure 8 includes the following information items: "CID", "MID", "TID", "Sending Date and Time", "UID", and "Message".

[0061] "CID" is an identifier that uniquely identifies the message. "MID" is an identifier of the meeting in which the dialogue took place. "TID" is an identifier of the task that was the subject of the dialogue. "Send Date and Time" is the date and time the message was sent. "UID" is an identifier of the user who sent the message. If "UID" is "-", it indicates that support device 1 sent the message. "Message" is the content (text) of the sent message.

[0062] In the example in Figure 8, message C01 has the following characteristics: "MID" is "M01", "TID" is "T01", "Sent Date and Time" is "2024 / 11 / 8, 14:03", "UID" is "U01", and "Message" is "c01". This indicates that message C01 is a message sent by user U01 on 2024 / 11 / 8 at 14:03 regarding task T01 performed for conference M01, and its content is c01.

[0063] Note that message information 128 is not limited to the example above. Message information 128 may include information items other than those listed above, or it may not include some of the information items listed above.

[0064] The control unit 13 is realized by the processor 101 reading and executing a program from the memory 102 and cooperating with other hardware components. The control unit 13 controls the overall operation of the support device 1. The control unit 13 comprises an acquisition unit 131, a task processing unit 132, and an interaction processing unit 133.

[0065] The acquisition unit 131 acquires text information 124 generated from the audio information 123 of the meeting. The acquisition unit 131 may acquire text information 124 generated by the user terminal 2, or it may acquire audio information 123 from the user terminal 2 and generate text information 124 from the acquired audio information 123.

[0066] The task processing unit 132 executes multiple tasks based on the text information 124. Specifically, the task processing unit 132 may execute a set of pre-configured tasks, a task set by the user, or a task depending on the type of meeting. When executing a task depending on the type of meeting, the type of meeting may be set by the user, or the task processing unit 132 may estimate it based on the text information 124.

[0067] The task processing unit 132 refers to the task information 125 to obtain the prompt for the task to be executed, inputs the prompt to the machine learning model 126, obtains the output of the machine learning model 126 as the task execution result, stores information indicating the execution result as execution result information 127 in the storage unit 12, and sends the execution result information 127 to the user terminal 2. At this time, the task processing unit 132 refers to the text information 124 to generate a prompt that includes the text indicated in the text information 124.

[0068] The dialogue processing unit 133 interacts with the user via the user terminal 2. Specifically, the dialogue processing unit 133 obtains the message entered by the user in the message input field displayed on the user terminal 2, generates a prompt, inputs the prompt to the machine learning model 126, obtains the output of the machine learning model 126 as a message to respond to the user, stores information indicating the obtained message as message information 128 in the storage unit 12, and sends the message information 128 to the user terminal 2. At this time, the dialogue processing unit 133 generates a prompt that includes a message from the user.

[0069] Furthermore, if the user's message requests an update to the execution result, the dialogue processing unit 133 updates the execution result in response to the user's message. Updating the execution result includes modifying, adding, changing, and deleting at least a portion of the execution result. Specifically, the dialogue processing unit 133 obtains the message entered by the user in the message input field displayed on the user terminal 2, generates a prompt, inputs the prompt to the machine learning model 126, obtains the output of the machine learning model 126 as the updated execution result, stores information indicating the updated execution result as execution result information 127 in the storage unit 12, and sends the execution result information 127 to the user terminal 2. At this time, the dialogue processing unit 133 generates a prompt that includes the user's message, the task's execution result, and the text indicated by the text information 124.

[0070] The machine learning model 126 used by the dialogue processing unit 133 for dialogue, the machine learning model 126 used by the dialogue processing unit 133 to update the execution results, and the machine learning model 126 used by the task processing unit 132 for task execution may be the same or different.

[0071] The functional configuration of support device 1 is not limited to the example above. For example, support device 1 may have some of the above functional configurations, with the user terminal 2 having the remainder. Support device 1 may also have functional configurations other than those described above. Furthermore, each functional configuration of support device 1 may be implemented by software as described above, or by hardware such as an IC chip, SoC (System on Chip), LSI (Large Scale Integration), or microcomputer.

[0072] <Functional Configuration of User Terminal 2> Next, the functional configuration of the user terminal 2 will be described. Figure 3 is a diagram showing an example of the functional configuration of the user terminal 2. As shown in Figure 3, the user terminal 2 comprises a communication unit 21, a storage unit 22, and a control unit 23.

[0073] The communication unit 21 is implemented by the communication interface 104. The communication unit 21 transmits and receives information with the support device 1 via the network N.

[0074] The memory unit 22 is implemented by memory 102 and storage 103. The memory unit 22 stores voice information 221, execution result information 222, and message information 223.

[0075] Audio information 221 is audio information that is a recording of the meeting.

[0076] Execution result information 222 is execution result information 127 received from support device 1.

[0077] Message information 223 is information indicating messages exchanged between the user and the support device 1. Message information 223 includes information indicating messages sent by the support device 1 to the user and information indicating messages sent by the user to the support device 1. Since message information 223 is the same as message information 128, its explanation is omitted.

[0078] The control unit 23 is realized by the processor 101 reading and executing a program from the memory 102 and cooperating with other hardware components. The control unit 23 controls the overall operation of the user terminal 2. The control unit 23 includes a display unit 231.

[0079] The display unit 231 controls the display device of the user terminal 2 and displays various screens on the user terminal 2. Specifically, the display unit 231 displays the results of multiple tasks and a message input field for the user to enter a message.

[0080] The functional configuration of user terminal 2 is not limited to the example above. For example, user terminal 2 may have some of the above functional configurations and the rest. User terminal 2 may also have functional configurations other than those described above. Furthermore, each functional configuration of user terminal 2 may be implemented by software as described above, or by hardware such as IC chips, SoCs, LSIs, microcomputers, etc.

[0081] <Methods for supporting post-meeting tasks> Next, we will describe the post-meeting work support method performed by the support system 1000. Figure 10 is a flowchart showing an example of a post-meeting work support method. The following explanation will use the case where meeting M01 is held as an example. At the start of the flowchart, it is assumed that meeting information 121, user information 122, task information 125, and machine learning model 126 are stored in the storage unit 12 of the support device 1.

[0082] (Step S101) After the meeting M01 ends, the user transmits audio information 221, which is a recording of the audio from the meeting M01, from the user terminal 2 to the support device 1. The acquisition unit 131 of the support device 1 acquires the audio information 221 received from the user terminal 2 and stores it as audio information 123 in the storage unit 12.

[0083] (Step S102) The acquisition unit 131 generates text information 124 from the audio information 123 of the meeting M01 through speech recognition processing and stores it in the storage unit 12.

[0084] (Step S103) The task processing unit 132 refers to the meeting information 121 to obtain the type of meeting M01 (business negotiation), and refers to the task information 125 to select a task (summary, evaluation) corresponding to the type of meeting M01. Note that if the task is to be executed uniformly regardless of the type of meeting, step S103 can be omitted.

[0085] (Step S104) The task processing unit 132 executes the task (summarization, evaluation) selected in step S103. Specifically, the task processing unit 132 refers to the task information 125 to obtain the prompts (t01, t02) for the task (summarization, evaluation) selected in step S103, generates prompts containing the text indicated by the text information 124 of meeting M01, and inputs the generated prompts to the machine learning model 126. The task processing unit 132 obtains the output of the machine learning model 126 as execution results (r01, r02) and saves information indicating the execution results as execution result information 127 in the storage unit 12 (see Figure 7).

[0086] (Step S105) The task processing unit 132 refers to the meeting information 121 to identify the users (U01, U02, U03) who will participate in the post-meeting tasks for meeting M01, i.e., the users to whom the execution result information 127 will be sent. It then refers to the user information 122 to obtain the attributes (administrator, member, guest) of each user, compares the obtained user attributes with the display attributes of the task information 125, and selects the task to which the execution result information 127 will be sent for each user. In the example in Figure 6, the display attribute for the deal summary is "-" and the display attribute for the deal evaluation is "administrator". Therefore, the summary and evaluation are selected as the tasks to which the execution result information 127 will be sent for user U01, and the summary is selected as the task to which the execution result information 127 will be sent for users U02 and U03. Note that if the task execution result information 127 is to be sent uniformly regardless of the user's attributes, step S105 can be omitted.

[0087] (Step S106) The task processing unit 132 sends the execution result information 127 of the task selected in step S105 to each user (U01, U02, U03) participating in the post-meeting work for meeting M01. Each user's terminal 2 stores the execution result information 127 received from the support device 1 as execution result information 222 in the storage unit 22. As a result, the storage unit 22 of user U01's terminal 2 stores the execution result information 127 of the summary and evaluation of meeting M01, and the storage unit 22 of users U02 and U03's terminal 2 stores the execution result information 127 of the summary of meeting M01.

[0088] The task processing unit 132 may also send the following to the user terminal 2 along with the execution result information 127: meeting information 121 for meeting M01, user information 122 for participants in post-meeting tasks for meeting M01, text information 123 for meeting M01, text information 124 for meeting M01, etc.

[0089] (Step S107) The display unit 231 of the user terminal 2 displays the task execution result indicated by the execution result information 127, along with a message input field, on the user terminal 2. In this case, the display unit 231 may also display information such as the meeting information 121 of meeting M01 received from the support device 1, the user information 122 of the participants in the post-meeting tasks of meeting M01, and the text information 124 of meeting M01, along with the task execution result. The method of displaying the task execution result will be described later.

[0090] (Step S108) The user enters a message in the message input field. The content of the message is optional and may include a request for an update to the execution results or a question about the execution results.

[0091] (Step S109) The user terminal 2 stores message information 223, which indicates the message entered by the user, in the storage unit 22 in response to the user's operation, and transmits the message information 223 to the support device 1. The support device 1 stores the message information 223 received from the user terminal 2 as message information 128 in the storage unit 12.

[0092] (Step S110) If the message information 128 received from user terminal 2 indicates a message (message from the user) requesting an update to the execution result (step S110: YES), the process proceeds to step S111. If the message information 128 received from user terminal 2 indicates a message requesting an update to the execution result (step S110: NO), the process proceeds to step S112.

[0093] (Step S111) The dialogue processing unit 133 updates the execution result in response to a message from the user. Specifically, the dialogue processing unit 133 generates a prompt that includes the message from the user and the execution result that was requested to be updated, inputs the prompt to the machine learning model 126, obtains the output of the machine learning model 126 as the updated execution result, and stores information indicating the updated execution result as execution result information 127 in the storage unit 12.

[0094] (Step S112) The dialogue processing unit 133 generates a message in response to a message from the user. Specifically, the dialogue processing unit 133 generates a prompt containing the message from the user, inputs the prompt to the machine learning model 126, obtains the output of the machine learning model 126 as a message in response to the user, and stores message information 128 indicating the obtained message in the storage unit 12.

[0095] For example, if a user message requests an update to the execution results, a message explaining the update will be generated for the user. Also, if a user message asks a question about the execution results, a message answering the question will be generated.

[0096] (Step S113) The dialogue processing unit 133 sends execution result information 127, which indicates the execution result updated in step S111, and message information 128, which indicates the message generated in step S112, to the user terminal 2. The user terminal 2 stores the execution result information 127 and message information 128 received from the support device 1 in the storage unit 22 as execution result information 222 and message information 223.

[0097] The dialogue processing unit 133 may send the execution result information 127 and message information 128 only to the user terminal 2 of the user who sent the message to the support device 1, but it is preferable to send the execution result information 127 and message information 128 to the user terminal 2 of all users whose requested execution results are displayed. This allows the update of the task execution results to be shared among the participants of the post-meeting work.

[0098] (Step S114) The display unit 231 of the user terminal 2 displays the updated execution result indicated by the execution result information 222 and the message from the support device 1 indicated by the message information 223 on the user terminal 2. It is also possible to configure the system so that the message from the support device 1 indicated by the message information 223 is not displayed.

[0099] <How to display task execution results> Here, we will explain how to display the task execution results. In the following, the screen displaying the task execution results will be referred to as the display screen (sc).

[0100] (Method 1 for displaying execution results) Figure 11 shows an example of a display screen sc1 shown using the first display method. The display screen sc1 in Figure 11 includes a meeting information display area sc11, an audio playback unit sc12, an execution result display area sc13, and a message input field sc14.

[0101] The meeting information display area sc11 is the area that displays the meeting information indicated by meeting information 121. In the example in Figure 11, the group name (Project X), meeting name (Meeting 1), date and time (2024 / 11 / 8, 12:00~13:00), and the identifiers of the participants in the post-meeting tasks (U1, U2, U3) are displayed for meeting M1.

[0102] The audio playback unit sc12 is a UI component (audio player) for playing the audio from the audio information 221. In the example in Figure 11, operating the audio playback unit sc12 will play the audio from meeting M1.

[0103] The execution result display area sc13 is the area that displays the execution results of a task. In the example in Figure 11, the execution result R1 of task T1 (summary) and the execution result R2 of task T2 (evaluation) are displayed.

[0104] The message input field sc14 is a UI component (text box) for the user to enter a message. The user can update the specified execution result by entering a message in the message input field sc14 requesting an update and sending it to the support device 1.

[0105] In the example shown in Figure 11, the message m1, "Please shorten R1," is entered in the message input field sc14 (Figure 11, top). When the user terminal 2 sends message information 223 indicating message m1 to the support device 1, the support device 1 updates the execution result R1 according to message m1 and sends execution result information 222 indicating the updated execution result R1' to the user terminal 2. The display unit 231 of the user terminal 2 displays the updated execution result R1' in the execution result display area sc13 of the display screen sc1 (Figure 11, bottom).

[0106] As described above, the display screen sc1 shows the execution results of multiple tasks along with a single message input field sc14. This allows the user to update the execution results of multiple tasks from a single message input field sc14. Furthermore, when the user requests the support device 1 to update the execution results on the display screen sc1, the updated execution result R1' is displayed instead of the execution result R1 before the update. This ensures that the user terminal 2 always displays the latest execution results.

[0107] (Method 2 for displaying execution results) Figure 12 shows an example of the display screen sc2 as displayed using the second display method. The display screen sc2 in Figure 12 includes a meeting information display area sc21, an audio playback unit sc22, an execution result display area sc23, and message input fields sc24 and sc25. The meeting information display area sc21, the audio playback unit sc22, and the execution result display area sc23 are the same as the meeting information display area sc11, the audio playback unit sc12, and the execution result display area sc13, so their explanation is omitted.

[0108] The message input field sc24 is a UI component for the user to enter a message regarding the execution result R1 of task T1. The user can update the execution result R1 by entering a message requesting an update in the message input field sc24 and sending it to the support device 1.

[0109] The message input field sc25 is a UI component for the user to enter a message regarding the execution result R2 of task T2. The user can update the execution result R2 by entering a message requesting an update in the message input field sc25 and sending it to the support device 1.

[0110] In the example in Figure 12, the message m2, "Please shorten it," is entered in the message input field sc24 (Figure 12, top). When the user terminal 2 sends message information 223 indicating message m2 to the support device 1, the support device 1 updates the execution result R1 according to message m2 and sends execution result information 222 indicating the updated execution result R1' to the user terminal 2. The display unit 231 of the user terminal 2 displays the updated execution result R1' in the execution result display area sc23 of the display screen sc2 (Figure 12, bottom).

[0111] As described above, the display screen sc2 shows the execution results of multiple tasks, along with multiple message input fields corresponding to each execution result. This allows the user to update the execution results of tasks without having to specify the execution result of the task to be updated. Furthermore, when the user requests the support device 1 to update the execution results on the display screen sc2, the updated execution result R1' is displayed instead of the execution result R1 before the update. This ensures that the user terminal 2 always displays the latest execution results.

[0112] (Method 3 for displaying execution results) Figure 13 shows an example of a display screen sc3 as shown by the third display method. The display screen sc3 in Figure 13 includes a meeting information display area sc31, an audio playback unit sc32, an execution result display area sc33, a message input field sc34, and a thread sc35. The meeting information display area sc31, the audio playback unit sc32, and the execution result display area sc33 are the same as the meeting information display area sc11, the audio playback unit sc12, and the execution result display area sc13, so their explanation is omitted.

[0113] The message input field sc34 is a UI component for users to enter messages. Users can update the specified execution result by entering a message in the message input field sc34 requesting an update, specifying the execution result, and sending it to the support device 1.

[0114] In the example shown in Figure 13, the message m31, "Please shorten R1," is entered in the message input field sc34 (Figure 13, top). When the user terminal 2 sends message information 223 indicating message m31 to the support device 1, the support device 1 updates the execution result R1 in accordance with message m31 and sends execution result information 222 indicating the updated execution result R1' to the user terminal 2. The display unit 231 of the user terminal 2 displays the updated execution result R1' in the execution result display area sc33 of the display screen sc3 (Figure 13, bottom).

[0115] Thread sc35 is an area that displays the interaction between the user and assistive device 1 in a chat format. Thread sc35 includes a message input field sc34 and displays messages from the user to assistive device 1 and messages from assistive device 1 to the user.

[0116] In the example shown in Figure 13, message m31 sent by the user to the support device 1 and message m32 sent by the support device 1 to the user in response to message m31 are displayed in thread sc35. Message m32 is sent to the user terminal 2 by the dialogue processing unit 133 along with the execution result R1'.

[0117] As described above, display screen sc3 shows a single message input field along with the execution results of multiple tasks. This allows the user to update task execution results without having to specify the execution result of the task to be updated. Furthermore, when the user requests an update of the execution results from support device 1 on display screen sc3, the updated execution result R1' is displayed instead of the execution result R1 before the update. This ensures that the user terminal 2 always displays the latest execution results. Additionally, on display screen sc3, the user and support device 1 communicate in a chat format within thread sc35. This allows the user to update execution results and ask questions about the execution results while interacting with support device 1.

[0118] (Method 4 for displaying execution results) Figure 14 shows an example of the display screen sc4 as displayed by the fourth display method. The display screen sc4 in Figure 14 has a meeting information display area sc41, an audio playback unit sc42, an execution result display area sc43, message input fields sc44 and sc45, and threads sc46 and sc47. The meeting information display area sc41, the audio playback unit sc42, and the execution result display area sc43 are the same as the meeting information display area sc11, the audio playback unit sc12, and the execution result display area sc13, so their explanation is omitted.

[0119] The message input field sc44 is a UI component for the user to enter a message regarding the execution result R1 of task T1. The user can update the execution result R1 by entering a message requesting an update in the message input field sc44 and sending it to the support device 1.

[0120] The message input field sc45 is a UI component for the user to enter a message regarding the execution result R2 of task T2. The user can update the execution result R2 by entering a message requesting an update in the message input field sc45 and sending it to the support device 1.

[0121] In the example in Figure 14, the message m41, "Please shorten it," is entered in the message input field sc44 (Figure 14, top). When the user terminal 2 sends message information 223 indicating message m41 to the support device 1, the support device 1 updates the execution result R1 in accordance with message m41 and sends execution result information 222 indicating the updated execution result R1' to the user terminal 2. The display unit 231 of the user terminal 2 displays the updated execution result R1' in the execution result display area sc43 of the display screen sc2 (Figure 14, bottom).

[0122] Thread sc46 is an area that displays the interaction between the user and the support device 1 regarding the execution result R1 of task T1 in a chat format. Thread sc46 includes a message input field sc44 and displays messages from the user to the support device 1 and messages from the support device 1 to the user.

[0123] Thread sc47 is an area that displays the interaction between the user and the support device 1 regarding the execution result R2 of task T2. Thread sc47 includes a message input field sc45 and displays messages from the user to the support device 1 and messages from the support device 1 to the user.

[0124] In the example shown in Figure 14, message m41 sent by the user to the support device 1 and message m42 sent by the support device 1 to the user in response to message m41 are displayed in thread sc46 (bottom of Figure 14). Message m42 is sent to the user terminal 2 by the dialogue processing unit 133 along with the execution result R1'.

[0125] As described above, display screen sc4 shows the execution results of multiple tasks, along with multiple message input fields corresponding to each execution result. This allows the user to update task execution results without specifying the execution result of the task to be updated. Furthermore, when the user requests an update of the execution results from support device 1 on display screen sc4, the updated execution result R1' is displayed instead of the execution result R1 before the update. This ensures that user terminal 2 always displays the latest execution results. Additionally, on display screen sc4, the user and support device 1 communicate in a chat format within threads sc46 and sc47. This allows the user to update execution results and ask questions about the execution results while interacting with support device 1.

[0126] (5 methods for displaying execution results) Figure 15 shows an example of a display screen sc5 as shown by the fifth display method. The display screen sc5 in Figure 15 includes a meeting information display area sc51, an audio playback unit sc52, an execution result display area sc53, a message input field sc54, and a thread sc55. The meeting information display area sc51, the audio playback unit sc52, and the execution result display area sc53 are the same as the meeting information display area sc11, the audio playback unit sc12, and the execution result display area sc13, so their explanation is omitted.

[0127] The message input field sc54 is a UI component for users to enter messages. Users can update the specified execution result by entering a message in the message input field sc54 requesting an update, specifying the execution result, and sending it to the support device 1.

[0128] In the example shown in Figure 15, the message m51, "Please shorten R1," is entered in the message input field sc54 (Figure 15, top). When the user terminal 2 sends message information 223 indicating message m51 to the support device 1, the support device 1 updates the execution result R1 in accordance with message m51 and sends execution result information 222 indicating the updated execution result R1' to the user terminal 2. The display unit 231 of the user terminal 2 displays the updated execution result R1' in the execution result display area sc53 of the display screen sc5 (Figure 15, bottom).

[0129] Thread sc55 is an area that displays the interaction between the user and the assistive device 1 in a chat format. Thread sc55 includes the execution result display area sc53 and the message input field sc54, and displays messages from the user to the assistive device 1 and messages from the assistive device 1 to the user. In the example in Figure 15, the message from the assistive device 1 to the user includes the task execution result. That is, the task execution result is displayed in thread sc55 as a message from the assistive device 1 to the user.

[0130] In the example shown in Figure 15, the execution results R1 and R2, message m51 sent by the user to the support device 1, message m52 sent by the support device 1 to the user in response to message m51, and the execution result R1' updated according to message m51 are all displayed in thread sc55 (bottom of Figure 15). Message m52 is sent to the user terminal 2 by the dialogue processing unit 133 along with the execution result R1'.

[0131] As described above, display screen sc5 shows a single message input field along with the execution results of multiple tasks. This allows the user to update task execution results without having to specify the execution result of the task to be updated. Furthermore, when the user requests an update of the execution results from support device 1 on display screen sc5, the updated execution result R1' is displayed along with the execution result R1 before the update. This allows user terminal 2 to view the execution result update history. In addition, on display screen sc5, the user and support device 1 communicate in a chat format within thread sc55. This allows the user to update execution results and ask questions about the execution results while interacting with support device 1.

[0132] (6 methods for displaying execution results) Figure 16 shows an example of a display screen sc6 displayed using the sixth display method. The display screen sc6 in Figure 16 includes a meeting information display area sc61, an audio playback unit sc62, an execution result display area sc63, message input fields sc64 and sc65, and threads sc66 and sc67. The meeting information display area sc61, the audio playback unit sc62, and the execution result display area sc63 are the same as the meeting information display area sc11, the audio playback unit sc12, and the execution result display area sc13, so their explanation is omitted.

[0133] The message input field sc64 is a UI component for the user to enter a message regarding the execution result R1 of task T1. The user can update the execution result R1 by entering a message requesting an update in the message input field sc64 and sending it to the support device 1.

[0134] The message input field sc65 is a UI component for the user to enter a message regarding the execution result R2 of task T2. The user can update the execution result R2 by entering a message requesting an update in the message input field sc65 and sending it to the support device 1.

[0135] In the example shown in Figure 16, the message m61, "Please shorten it," is entered in the message input field sc64 (Figure 16, top). When the user terminal 2 sends message information 223 indicating message m61 to the support device 1, the support device 1 updates the execution result R1 in accordance with message m61 and sends execution result information 222 indicating the updated execution result R1' to the user terminal 2. The display unit 231 of the user terminal 2 displays the updated execution result R1' in the execution result display area sc63 of the display screen sc2 (Figure 16, bottom).

[0136] Thread sc66 is an area that displays the interaction between the user and the support device 1 regarding the execution result R1 of task T1 in a chat format. Thread sc66 includes the execution result display area sc63 and the message input field sc64, and displays messages from the user to the support device 1 and messages from the support device 1 to the user. In the example in Figure 16, the message from the support device 1 to the user includes the execution result of task T1. That is, the execution result of task T1 is displayed in thread sc66 as a message from the support device 1 to the user.

[0137] Thread sc67 is an area that displays the interaction between the user and the support device 1 regarding the execution result R2 of task T2 in a chat format. Thread sc67 includes the execution result display area sc63 and the message input field sc65, and displays messages from the user to the support device 1 and messages from the support device 1 to the user. In the example in Figure 16, the message from the support device 1 to the user includes the execution result of task T2. That is, the execution result of task T2 is displayed in thread sc67 as a message from the support device 1 to the user.

[0138] In the example shown in Figure 16, the execution result R1, the message m61 sent by the user to the support device 1, the message m62 sent by the support device 1 to the user in response to message m61, and the execution result R1' updated according to message m61 are all displayed in thread sc66 (bottom of Figure 16). Message m62 is sent to the user terminal 2 by the dialogue processing unit 133 along with the execution result R1'.

[0139] As described above, the display screen sc6 shows the execution results of multiple tasks, along with multiple message input fields corresponding to each execution result. This allows the user to update the execution results of tasks without having to specify the execution result of the task to be updated. Furthermore, when the user requests the support device 1 to update the execution results on the display screen sc6, the updated execution result R1' is displayed along with the execution result R1 before the update. This allows the user terminal 2 to view the execution result update history. In addition, the display screen sc6 allows the user and the support device 1 to communicate in a chat format within threads sc66 and sc67. This allows the user to update execution results and ask questions about execution results while interacting with the support device 1.

[0140] <Summary> As described above, according to this embodiment, a support system 1000 can be realized that includes an acquisition unit 131 that acquires text information 124 generated from audio information 123 of a meeting, a task processing unit 132 that executes multiple tasks based on the text information 124, a display unit 231 that displays the execution results of the multiple tasks and a message input field for the user to enter a message, and a dialogue processing unit 133 that can update the execution results based on the message entered by the user in the message input field.

[0141] The support system 1000 can automate various tasks related to post-meeting operations, thereby streamlining post-meeting processes.

[0142] In this embodiment, the example of executing a task based on the text information 124 of one meeting was described, but the task processing unit 132 may execute a task based on the text information 124 of multiple meetings or the execution results of tasks for multiple meetings.

[0143] For example, the task processing unit 132 can determine the progress of the work and execute a task to visualize it (e.g., create a diagram) based on the next actions from the previous meeting included in the same group (the result of executing a task to extract the next actions) and the text information 124 from the current meeting.

[0144] Furthermore, the task processing unit 132 can also perform a task to visualize (for example, illustrate) the changes in decisions by comparing the decisions made at the previous meeting (the result of the task to extract decisions) that are included in the same group.

[0145] Note that the above example is not the only way to perform a task based on text information from multiple meetings 124 or the results of tasks performed in multiple meetings.

[0146] Furthermore, the task processing unit 132 may perform processing in response to user requests for execution of the task execution results. For example, if the task is draft creation, the task processing unit 132 may perform processing in response to the execution request, such as sending an email, outputting documents such as proposals (sending, printing, sharing, etc.), outputting forms (sending, printing, sharing, etc.), or registering with an external system. The execution request may also be made by the user selecting an execution request button (for example, a send button) displayed along with the execution results, or by the user entering a message requesting the execution of the process in the message input field (e.g., "Please send an email with this content"). The processing in response to the execution request can be arbitrarily set depending on the type of task.

[0147] <Summary> As described above, according to this embodiment, when the subject information captured by the support device 1 satisfies the shooting conditions, the shooting range of the user terminal 2 is controlled to include the subject corresponding to the shooting conditions, and a second image is captured.

[0148] <Note> This embodiment includes the following disclosures.

[0149] (Note 1) An acquisition unit that acquires text information generated from the audio information of a meeting, A task processing unit that performs multiple tasks based on the aforementioned text information, A display unit that displays the results of the execution of the aforementioned multiple tasks and a message input field for the user to enter a message, A dialogue processing unit capable of updating the execution result based on a message entered by the user in the message input field, A post-meeting support system equipped with these features.

[0150] (Note 2) The display unit displays the message input field for each task. The post-meeting support system described in Appendix 1.

[0151] (Note 3) The display unit displays one message input field. The post-meeting support system described in Appendix 1.

[0152] (Note 4) The display unit displays the thread including the message input field. The dialogue processing unit interacts with the user within the thread. The post-meeting support system described in Appendix 1.

[0153] (Note 5) The execution result will be displayed within the thread. The post-meeting support system described in Appendix 1.

[0154] (Note 6) The display unit displays the execution result after the update, along with the execution result before the update. The post-meeting support system described in Appendix 1.

[0155] (Note 7) The display unit displays the updated execution result instead of the execution result before the update. The post-meeting support system described in Appendix 1.

[0156] (Note 8) The task processing unit estimates the type of meeting and executes a task corresponding to the estimated type. The post-meeting support system described in Appendix 1.

[0157] (Note 9) The task processing unit executes tasks according to the type of meeting set by the user. The post-meeting support system described in Appendix 1.

[0158] (Note 10) The task processing unit executes tasks set by the user. The post-meeting support system described in Appendix 1.

[0159] (Note 11) The display unit displays the execution results of the task according to the user's attributes. The post-meeting support system described in Appendix 1.

[0160] (Note 12) The aforementioned attributes include job title, position, and authority. The post-meeting support system described in Appendix 11.

[0161] (Note 13) The aforementioned tasks include summarizing, illustrating, extracting, evaluating, acquiring relevant information, and drafting related information concerning the aforementioned meeting. The post-meeting support system described in Appendix 1.

[0162] (Note 14) The task processing unit generates a prompt corresponding to the task, inputs the prompt to the machine learning model, and obtains the output of the machine learning model as the execution result. The post-meeting support system described in Appendix 1.

[0163] (Note 15) The aforementioned machine learning model is a large-scale language model. The post-meeting support system described in Appendix 14.

[0164] (Note 16) The acquisition unit acquires audio information of the meeting and generates text information from the acquired audio information. The post-meeting support system described in Appendix 1.

[0165] (Note 17) The task processing unit executes the task based on the text information of the multiple meetings or the execution results of the multiple meetings. The post-meeting support system described in Appendix 1.

[0166] (Note 18) The task processing unit executes processing in response to user requests for execution of the task execution results. The post-meeting support system according to claim 1.

[0167] (Note 19) A post-meeting support method implemented by an information processing system, The process of obtaining text information generated from the audio information of a meeting, Based on the aforementioned text information, a process is performed to execute multiple tasks, A process for displaying the execution results of the aforementioned multiple tasks and a message input field for the user to enter a message, A process to update the execution result based on the message entered by the user in the message input field, Post-meeting work support methods, including those mentioned above.

[0168] (Note 20) In the information processing system, The process of obtaining text information generated from the audio information of a meeting, Based on the aforementioned text information, a process is performed to execute multiple tasks, A process for displaying the execution results of the aforementioned multiple tasks and a message input field for the user to enter a message, A process to update the execution result based on the message entered by the user in the message input field, A program that implements post-meeting work support methods, including those mentioned above.

[0169] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not in the sense described above, and is intended to include all modifications in the sense and scope equivalent to the claims. Furthermore, the present invention is not limited to the embodiments described above, and various modifications are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. [Explanation of Symbols]

[0170] 1: Post-meeting support device 2: User terminal 121: Meeting Information 122: User Information 123: Audio Information 124: Text Information 125: Task Information 126: Machine Learning Models 127: Execution result information 128: Message Information 131: Acquisition Department 132: Task Processing Unit 133: Dialogue Processing Unit

Claims

1. An acquisition unit that acquires text information generated from the audio information of a meeting, A task processing unit that performs multiple tasks based on the aforementioned text information, A display unit that displays the results of the execution of the aforementioned multiple tasks and a message input field for the user to enter a message, A dialogue processing unit capable of updating the execution result based on a message entered by the user in the message input field, A post-meeting support system equipped with these features.

2. The display unit displays the message input field for each task. The post-meeting support system according to claim 1.

3. The display unit displays one message input field. The post-meeting support system according to claim 1.

4. The display unit displays the thread including the message input field. The dialogue processing unit interacts with the user within the thread. The post-meeting support system according to claim 1.

5. The execution result will be displayed within the thread. The post-meeting support system according to claim 1.

6. The display unit displays the execution result after the update, along with the execution result before the update. The post-meeting support system according to claim 1.

7. The display unit displays the updated execution result instead of the execution result before the update. The post-meeting support system according to claim 1.

8. The task processing unit estimates the type of meeting and executes a task corresponding to the estimated type. The post-meeting support system according to claim 1.

9. The task processing unit executes tasks according to the type of meeting set by the user. The post-meeting support system according to claim 1.

10. The task processing unit executes tasks set by the user. The post-meeting support system according to claim 1.

11. The display unit displays the execution results of the task according to the user's attributes. The post-meeting support system according to claim 1.

12. The aforementioned attributes include job title, position, and authority. The post-meeting support system according to claim 11.

13. The aforementioned tasks include summarizing, illustrating, extracting, evaluating, acquiring relevant information, and drafting related information concerning the aforementioned meeting. The post-meeting support system according to claim 1.

14. The task processing unit generates a prompt corresponding to the task, inputs the prompt to the machine learning model, and obtains the output of the machine learning model as the execution result. The post-meeting support system according to claim 1.

15. The aforementioned machine learning model is a large-scale language model. The post-meeting support system according to claim 14.

16. The acquisition unit acquires audio information of the meeting and generates text information from the acquired audio information. The post-meeting support system according to claim 1.

17. The task processing unit executes the task based on the text information of the multiple meetings or the execution results of the multiple meetings. The post-meeting support system according to claim 1.

18. The task processing unit executes processing in response to user requests for execution of the task execution results. The post-meeting support system according to claim 1.

19. A post-meeting support method implemented by an information processing system, The process of obtaining text information generated from the audio information of a meeting, Based on the aforementioned text information, a process is performed to execute multiple tasks, A process for displaying the execution results of the aforementioned multiple tasks and a message input field for the user to enter a message, A process to update the execution result based on the message entered by the user in the message input field, Post-meeting work support methods, including those mentioned above.

20. In the information processing system, The process of obtaining text information generated from the audio information of a meeting, Based on the aforementioned text information, a process is performed to execute multiple tasks, A process for displaying the execution results of the aforementioned multiple tasks and a message input field for the user to enter a message, A process to update the execution result based on the message entered by the user in the message input field, A program that implements post-meeting work support methods, including those mentioned above.

Images