Conference record generation method, conference system, electronic equipment and storage medium

Abstract

The invention provides a conference record generation method, a conference system, an electronic device and a storage medium, and relates to the technical field of communication, and the method comprises the steps: obtaining conference participation information of participants, and determining whether all participants join the conference system or not according to the conference participation information; after determining that all participants join the conference system, detecting whether subject confirmation information is received or not; after it is detected that the issue confirmation information is received, a conference record corresponding to the issue is obtained; and storing the conference record and the issue into the conference system together. According to the method and the device, whether the participants arrive all the time can be automatically confirmed, the conference record can be automatically recorded, the generated conference record content is refined, and the user can more efficiently know the conference content.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method for generating conference records, a conference system, an electronic device, and a storage medium. Background Art

[0002] Meetings are often held within the company. After the meeting, the meeting minutes will be recorded so that people who did not attend the meeting can read the minutes to understand the content of the meeting, and people who attended the meeting can read it again to review the content of the meeting.

[0003] In related technologies, meeting minutes are generated by converting speech from a meeting into text. Users can then review the minutes after the meeting and use search to review the meeting scenes and tasks. However, these minutes are essentially records of the conversations between participants. Recording all conversations contains too much content, which is time-consuming to read carefully. Simply skimming can easily miss important information, resulting in low reading efficiency. Summary of the Invention

[0004] In view of this, the present application provides a method for generating meeting minutes, which can automatically confirm whether all participants are present and automatically record meeting minutes. The generated meeting minutes are concise and can enable users to understand the content of the meeting more efficiently.

[0005] The first aspect of the present application provides a method for generating meeting records, including: obtaining meeting participation information of participants, and determining whether all participants have joined the conference system based on the meeting participation information; after determining that all participants have joined the conference system, detecting whether topic confirmation information has been received; after detecting that the topic confirmation information has been received, obtaining a meeting record corresponding to the topic to be discussed; and storing the meeting record and the topic to be discussed.

[0006] Compared with the related technologies, the embodiments of the present application have at least the following advantages: by obtaining the meeting participation information of the participants, it is convenient to determine whether all the participants have joined the conference system. On the one hand, the number of participants can be automatically counted, and on the other hand, it can ensure that all participants participate in the discussion of subsequent topics; by obtaining the meeting minutes corresponding to the topic after receiving the topic confirmation information, it is possible to avoid recording other content unrelated to the topic in the meeting minutes, making the meeting minutes more refined and allowing users to understand the content of the meeting more efficiently; in addition, the meeting minutes and topics are stored in the conference system together, so that users can query the meeting minutes corresponding to each topic through the conference system at any time, thereby improving the user experience.

[0007] In some possible implementations, after detecting and receiving the topic confirmation information, obtaining the meeting minutes corresponding to the topic to be discussed includes: after detecting and receiving the topic confirmation information, obtaining the discussion content of the participants in real time; after detecting and receiving the resolution generation information, generating the meeting minutes based on the discussion content of the participants.

[0008] In some possible implementations, after receiving the resolution generation information, the method further includes: detecting whether the review information is received within a preset time period, and when the review information is not received within the preset time period, executing the step of generating the meeting minutes based on the discussion content of the participants; when the review information is received within the preset time period, returning to the step of obtaining the discussion content of the participants in real time.

[0009] In some possible implementations, the method further includes: generating a to-do list based on the meeting minutes, and sending the to-do list to an office system; wherein the office system is used for daily office work of the meeting participants.

[0010] In some possible implementations, after sending the to-do list to the office system, the method further includes: receiving to-do completion information sent by the office system; and updating the to-do list according to the to-do completion information.

[0011] In some possible implementations, the method further includes: receiving customer information and project information sent by an office system; wherein the office system is used for the daily office work of the participants; confirming the target customer information corresponding to the topic to be discussed from the customer information, and confirming the target project information corresponding to the topic to be discussed from the project information; and storing the meeting minutes and the topic to be discussed includes: storing the meeting minutes, the topic to be discussed, the target customer information and the target project information.

[0012] In some possible implementations, determining whether all participants have joined the conference system based on the conference participation information includes: detecting whether the conference participation information of all participants has been received; and after detecting that the conference participation information of all participants has been received, determining that all participants have joined the conference system.

[0013] The second aspect of the present application discloses a conference system, including: a conference participant confirmation module, which is used to obtain conference participation information of participants and determine whether all participants have joined the conference system based on the conference participation information; an agenda confirmation module, which is used to detect whether agenda confirmation information has been received after the conference participant confirmation module determines that all participants have joined the conference system; a meeting record generation module, which is used to obtain meeting records corresponding to the topic to be discussed after the topic confirmation module detects that the topic confirmation information has been received; and a storage module, which is used to store the meeting records and the topic to be discussed.

[0014] The third aspect of the present application discloses an electronic device, which includes a processor and a memory, wherein the memory is used to store instructions, and the processor is used to call the instructions in the memory so that the electronic device executes the above-mentioned meeting record generation method.

[0015] The fourth aspect of the present application discloses a storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned method for generating meeting records.

[0016] It can be understood that the conference system of the second aspect, the electronic device of the third aspect, and the storage medium of the fourth aspect provided above all correspond to the method of the first aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A schematic diagram of the functional modules of a conference system provided in one embodiment of the present application;

[0018] Figure 2 A flowchart of a method for generating meeting records provided in one embodiment of the present application;

[0019] Figure 3 A flowchart of a method for generating meeting records provided in one embodiment of the present application;

[0020] Figure 4 A diagram illustrating the interaction process between a conference system and an office system provided in one embodiment of the present application;

[0021] Figure 5 A flowchart of a method for generating meeting records provided in one embodiment of the present application;

[0022] Figure 6 A schematic diagram of the hardware structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0023] In order to more clearly understand the above-mentioned objectives, features and advantages of the present application, the present application is described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present application and the features therein can be combined with each other in the absence of conflict.

[0024] In the following description, many specific details are set forth to facilitate a full understanding of the present application. The described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application pertains. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0026] It should be further noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0027] In this application, "at least one" means one or more, and "more than one" means two or more than two. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims and drawings of this application are used to distinguish similar objects, rather than to describe a specific order or sequence.

[0028] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0029] Please refer to Figure 1, which is a schematic diagram of the functional modules of the conference system provided in an embodiment of the present application. The conference system 100 provides functions such as voice-to-text, chat, and screenshot, and supports automatic conference records. It can automatically obtain information from voice-to-text, chat, and screenshot information streams, and automatically organize them into meeting records. In this embodiment, the conference system 100 includes: a conference attendance confirmation module 1, an agenda confirmation module 2, a conference record generation module 3, and a storage module 4. It should be noted that the division of modules in this embodiment is a logical division based on different functions, rather than a fixed division of modules. In an actual conference system, the modules may overlap or call each other when executing functions.

[0030] In some embodiments, the conference system 100 can be a TCFR (Teams Cross Function Review Records) system. TCFR is a file co-editing system developed based on Teams. The system enables RD teams to jointly edit meeting minutes in design review meetings at various stages of the project, and ultimately generates a review meeting record.

[0031] Specifically, the conference participant confirmation module 1 is used to obtain conference participant information and determine whether all conference participants have joined the conference system 100 according to the conference participant information.

[0032] In some embodiments, the conference system 100 includes a sign-in module. After logging into the conference system 100, participants sign in through the sign-in module. For example, assume there are 20 participants participating in a conference. After each participant signs in through the sign-in module, the sign-in module sends conference participation information to the conference confirmation module 1. It will be understood that the participant's identity information is bound to the conference system 100. Therefore, the conference participation information sent by each participant after signing in will include their identity information. In this way, the conference confirmation module 1 can determine which participants have not joined the conference system 100.

[0033] In some embodiments, employees store a list of participants for meeting one in the conference system 100 in advance. When the conference system 100 detects that employee A has joined the meeting, it automatically obtains the meeting participation information corresponding to employee A, and detects whether employee A is a participant of meeting one through the list of participants, and in this way detects whether all participants of meeting one are present.

[0034] The topic confirmation module 2 is used to detect whether topic confirmation information is received after the participant confirmation module 1 determines that all participants have joined the conference system 100 .

[0035] The meeting record generating module 3 is used to obtain the meeting record corresponding to the topic after detecting and receiving the topic confirmation information.

[0036] The storage module 4 is used to store the meeting minutes and the agenda together in the conference system 100 .

[0037] For ease of understanding, the following describes in detail the process of generating conference records by the conference system 100 of this embodiment:

[0038] 1. Assume that there are 30 participants in a conference. When each participant joins the conference system 100, the conference system 100 obtains the corresponding conference participation information of the participant. After the conference system 100 obtains the 30 conference participation information, the conference system 100 determines that all participants have joined.

[0039] 2. The conference system 100 has an agenda confirmation function. For example, the conference system 100 is downloaded to the terminal device of the participant in the form of an APP. The APP corresponding to the conference system 100 is provided with an agenda confirmation button. After the participant clicks the agenda confirmation button, the conference system 100 will receive the agenda confirmation information.

[0040] 3. After receiving the topic confirmation information, the conference system 100 starts recording the meeting minutes discussed by the participants and stores the meeting minutes and the topics matching the meeting minutes.

[0041] Please refer to Figure 2 , is a flow chart of the conference record generation method provided in the embodiment of the present application. This embodiment is applied to the conference system of the above embodiment, such as Figure 2 As shown, the following steps are included:

[0042] Step 101: Acquire conference participation information of conference participants, and determine whether all conference participants have joined the conference system based on the conference participation information.

[0043] In some embodiments, conference participants automatically generate conference participation information after joining the conference system through identity authentication. When the conference system detects that a person has joined, it obtains the person's conference participation information.

[0044] In some embodiments, the conference system has a sign-in function. After a participant passes identity authentication and joins the conference system, he or she clicks a sign-in button to generate conference participation information so that the conference system can obtain the participant's conference participation information.

[0045] In some embodiments, the conference system pre-stores a list of participants in the meeting to be discussed, and the conference participation information carries the identity information of the participants, so that the conference system can detect the identities of the participants based on the list of participants and detect which participants have not joined the conference system.

[0046] In some embodiments, determining whether all conference participants have joined the conference system based on the conference participation information includes: detecting whether conference participation information from all conference participants has been received; and determining that all conference participants have joined the conference system after detecting that the conference participation information from all conference participants has been received. In other words, determining that all conference participants have joined the conference system after the conference system receives conference participation information from all conference participants in the conference participant list.

[0047] Step 102: After confirming that all participants have joined the conference system, check whether the topic confirmation information has been received.

[0048] In some embodiments, the conference system has an agenda confirmation function. For example, the conference system is downloaded to the terminal device of the participant in the form of an APP. The APP corresponding to the conference system is provided with an agenda confirmation button. After the participant clicks the agenda confirmation button, the conference system will receive the agenda confirmation information.

[0049] Step 103: After detecting and receiving the topic confirmation information, obtain the meeting record corresponding to the topic to be discussed.

[0050] In some embodiments, after receiving the topic confirmation information, the conference system obtains the discussion content of the participants in real time, and after receiving the resolution generation information, generates a meeting record based on the discussion content of the participants.

[0051] In some embodiments, after receiving the resolution generation information, the conference system further detects whether a review message has been received within a preset time period. If no review message has been received within the preset time period, the conference system proceeds to generate the meeting minutes based on the discussion content of the participants. If the review message is received within the preset time period, the conference system returns to the step of obtaining the discussion content of the participants in real time. In this way, the conference minutes are not generated until all participants have no objection to the discussion topic, ensuring the accuracy of the conference minutes.

[0052] Step 104: Store the meeting minutes and topics to be discussed.

[0053] Compared with the related technologies, the embodiments of the present application have at least the following advantages: by obtaining the meeting participation information of the participants, it is convenient to determine whether all the participants have joined the conference system. On the one hand, the number of participants can be automatically counted, and on the other hand, it can ensure that all participants participate in the discussion of subsequent topics; by obtaining the meeting minutes corresponding to the topic after receiving the topic confirmation information, it is possible to avoid recording other content unrelated to the topic in the meeting minutes, making the meeting minutes more refined and allowing users to understand the content of the meeting more efficiently; in addition, the meeting minutes and topics are stored in the conference system together, so that users can query the meeting minutes corresponding to each topic through the conference system at any time, thereby improving the user experience.

[0054] Please refer to Figure 3 , which is a flow chart of a method for generating meeting records provided in an embodiment of the present application. This embodiment is a further improvement on the aforementioned embodiment, with the main improvement being that: in this embodiment, the method further comprises: generating a to-do list based on the meeting records, and sending the to-do list to an office system; wherein the office system is used for the daily office work of the meeting participants. In this way, meeting participants can directly query the to-do list of the meeting they previously participated in through the office system used for daily office work, so that meeting participants can directly complete the to-do items corresponding to the meeting records through the office system, thereby improving the work efficiency of employees.

[0055] This embodiment is applied to the conference system of the above embodiment, such as Figure 3 As shown, the following steps are included:

[0056] Step 201: Acquire conference participation information of conference participants, and determine whether all conference participants have joined the conference system based on the conference participation information.

[0057] Step 202: After confirming that all participants have joined the conference system, check whether the topic confirmation information has been received.

[0058] Step 203: After detecting and receiving the topic confirmation information, obtain the meeting record corresponding to the topic to be discussed.

[0059] Step 204: Store the meeting minutes and topics to be discussed.

[0060] Steps 201 to 204 of this embodiment are similar to steps 101 to 104 of the aforementioned embodiment, and are not described again here to avoid repetition.

[0061] Step 205: Generate a to-do list based on the meeting minutes, and send the to-do list to the office system; wherein the office system is used for daily office work of the participants.

[0062] In some embodiments, the office system is a TC system, which can track various to-do items generated in the conference system, urge RD teams to complete the to-do items in a timely manner through email reminders, and send the to-do results back to the conference system.

[0063] Step 206: Receive the to-do item completion information sent by the office system, and update the to-do item list according to the to-do item completion information.

[0064] For ease of understanding, the following example takes the conference system as the TCFR system and the office system as the TC system. Figure 4 The interaction process between the conference system and the office system of this embodiment is described in detail:

[0065] Please refer to Figure 4 , a diagram of the interaction process between the conference system and office system provided in an embodiment of this application. The TCFR system and the TC system have multiple interfaces: the TC system synchronizes project information with the TCFR system via interface 1; the TCFR system queries client information via interface 2; the TCFR system transmits meeting minutes, to-do lists, and other information to the YC system via interface 3; and the TC system transmits to-do completion results back to the TCFR system. This allows the TCFR system to synchronously update to-do lists, ensuring the real-time and accuracy of information.

[0066] Compared with the related technologies, the embodiments of the present application have at least the following advantages: by obtaining the meeting participation information of the participants, it is convenient to determine whether all the participants have joined the conference system. On the one hand, the number of participants can be automatically counted, and on the other hand, it can ensure that all participants participate in the discussion of subsequent topics; by obtaining the meeting minutes corresponding to the topic after receiving the topic confirmation information, it is possible to avoid recording other content unrelated to the topic in the meeting minutes, making the meeting minutes more refined and allowing users to understand the content of the meeting more efficiently; in addition, the meeting minutes and topics are stored in the conference system together, so that users can query the meeting minutes corresponding to each topic through the conference system at any time, thereby improving the user experience.

[0067] Please refer to Figure 5, which is a flow chart of a method for generating meeting records provided in one embodiment of the present application. This embodiment is a further improvement on the aforementioned embodiment, with the main improvement being that: in this embodiment, the method further comprises: receiving customer information and project information sent by an office system; wherein the office system is used for the daily office work of the meeting participants; confirming the target customer information corresponding to the topic from the customer information, and confirming the target project information corresponding to the topic from the project information; and storing the meeting record, the topic, the target customer information, and the target project information into the meeting system. In this way, meeting participants can query the customer information and project information of the topic to be discussed directly through the meeting system without going through the office system, thereby improving the work efficiency of the meeting participants.

[0068] This embodiment is applied to the conference system of the above embodiment, such as Figure 5 As shown, the following steps are included:

[0069] Step 301: Receive customer information and project information sent by the office system; wherein the office system is used for daily office work of the participants.

[0070] In some embodiments, the office system sends all client information and project information of the topics to the conference system, so that participants can directly query relevant information of the topics through the conference system.

[0071] Step 302: Confirm target customer information corresponding to the topic to be discussed from the customer information, and confirm target project information corresponding to the topic to be discussed from the project information.

[0072] Step 303: Acquire conference participation information of the conference participants, and determine whether all the conference participants have joined the conference system based on the conference participation information.

[0073] Step 304: After confirming that all participants have joined the conference system, check whether the topic confirmation information has been received.

[0074] Step 305: After detecting and receiving the topic confirmation information, obtain the meeting record corresponding to the topic to be discussed.

[0075] Step 306: Store meeting records, topics to be discussed, target customer information, and target project information.

[0076] Steps 303 to 306 of this embodiment are similar to steps 101 to 104 of the aforementioned embodiment, and are not described again here to avoid repetition.

[0077] Compared with the related technologies, the embodiments of the present application have at least the following advantages: by obtaining the meeting participation information of the participants, it is convenient to determine whether all the participants have joined the conference system. On the one hand, the number of participants can be automatically counted, and on the other hand, it can ensure that all participants participate in the discussion of subsequent topics; by obtaining the meeting minutes corresponding to the topic after receiving the topic confirmation information, it is possible to avoid recording other content unrelated to the topic in the meeting minutes, making the meeting minutes more refined and allowing users to understand the content of the meeting more efficiently; in addition, the meeting minutes and topics are stored in the conference system together, so that users can query the meeting minutes corresponding to each topic through the conference system at any time, thereby improving the user experience.

[0078] Please refer to Figure 6 , is a schematic diagram of the hardware structure of the electronic device 1000 provided in the embodiment of the present application. Figure 6 As shown, electronic device 1000 may include a processor 1001 and a memory 1002. Memory 1002 is configured to store one or more computer programs 1003. One or more computer programs 1003 are configured to be executed by processor 1001. The one or more computer programs 1003 include instructions, which may be used to implement the above-described method for generating meeting records in electronic device 1000.

[0079] It is understood that the structure shown in this embodiment does not constitute a specific limitation on the electronic device 1000. In other embodiments, the electronic device 1000 may include more or fewer components than shown, or combine or separate some components, or arrange the components differently.

[0080] The processor 1001 may include one or more processing units. For example, the processor 1001 may include an application processor (AP), a modem, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0081] Processor 1001 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 1001 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 1001. If processor 1001 needs to use the same instruction or data again, it can directly access it from this memory. This avoids duplicate accesses, reduces the waiting time of processor 1001, and thus improves system efficiency.

[0082] In some embodiments, the processor 1001 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a USB interface.

[0083] In some embodiments, memory 1002 may include high-speed random access memory and may also include non-volatile memory, such as a hard disk, memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0084] This embodiment also provides a computer-readable storage medium, which stores computer instructions. When the instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the meeting record generation method in the above-mentioned embodiment.

[0085] Among them, the electronic device and computer storage medium provided in this embodiment are used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0086] In practical applications, the above functions can be distributed to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0087] In the several embodiments provided in this application, the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are schematic. For example, the division of the modules or units is a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0088] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0089] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0090] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0091] The above description is only a specific implementation method of the present application, but the protection scope of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in the present application should be included in the protection scope of the present application.

Claims

1. A method for generating meeting records, characterized in that: Applied to a conference system, the method includes: Acquiring conference participation information of conference participants, and determining whether all conference participants have joined the conference system based on the conference participation information; After confirming that all participants have joined the conference system, checking whether the topic confirmation information has been received; After detecting and receiving the topic confirmation information, obtaining the meeting minutes corresponding to the topic to be discussed; The meeting minutes and the topics to be discussed are stored.

2. The method for generating conference records according to claim 1, wherein: After detecting and receiving the topic confirmation information, obtaining the meeting record corresponding to the topic to be discussed includes: After detecting and receiving the topic confirmation information, obtaining the discussion content of the participants in real time; After detecting and receiving the resolution generation information, the meeting record is generated according to the discussion content of the participants.

3. The method for generating conference records according to claim 2, wherein: After receiving the resolution generation information, the method further includes: detecting whether the reconsideration information is received within a preset time period, and if the reconsideration information is not received within the preset time period, generating the meeting record according to the discussion content of the participants; When the review information is received within the preset time period, the process returns to the step of obtaining the discussion content of the conference participants in real time.

4. The method for generating conference records according to claim 1, wherein: The method further comprises: A to-do list is generated based on the meeting minutes, and the to-do list is sent to an office system; wherein the office system is used for the daily office work of the participants.

5. The method for generating conference records according to claim 4, wherein: After sending the to-do list to the office system, the method further includes: Receiving to-do item completion information sent by the office system; The to-do list is updated according to the to-do completion information.

6. The method for generating conference records according to claim 1, wherein: The method further comprises: Receive customer information and project information sent by the office system; wherein the office system is used for the daily office work of the participants; Confirming target customer information corresponding to the topic to be discussed from the customer information, and confirming target project information corresponding to the topic to be discussed from the project information; The storing of the meeting minutes and the topics to be discussed includes: The meeting minutes, the topics to be discussed, the target customer information and the target project information are stored.

7. The method for generating conference records according to claim 1, wherein: The determining whether all participants have joined the conference system according to the conference participation information includes: Check whether the conference participation information of all participants has been received; After detecting and receiving conference participation information of all conference participants, it is determined that all conference participants have joined the conference system.

8. A conference system, characterized in that: include: A conference confirmation module, which is used to obtain conference participation information of conference participants and determine whether all conference participants have joined the conference system based on the conference participation information; A topic confirmation module, which is used to detect whether topic confirmation information has been received after the participant confirmation module determines that all participants have joined the conference system; A meeting record generation module, configured to obtain a meeting record corresponding to an agenda item after the agenda item confirmation module detects and receives the agenda item confirmation information; A storage module is used to store the meeting minutes and the agenda.

9. An electronic device, characterized in that: The electronic device includes a processor and a memory, the memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the meeting record generation method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The method comprises computer instructions, which, when executed on an electronic device, enable the electronic device to execute the method for generating meeting records according to any one of claims 1 to 7.

Images