Conference management method, server and conference management system

Abstract

The present application provides a conference management method, a server, and a conference management system, and relates to the field of computer technology. The present application receives multiple participant information sent by a first client, binds each participant information to a corresponding electronic table card identifier, and the electronic table card corresponding to each electronic table card identifier also corresponds one-to-one with a microphone, receives the voice information sent by the target microphone, determines the target participant information according to the target electronic table card identifier corresponding to the target microphone, and generates a conference document according to the voice information and the target participant information. According to the one-to-one correspondence between the participant information, the electronic table card, and the microphone, the target participant information corresponding to the voice information is determined, and a conference document is generated according to the target participant information and the voice information, without the need for manual sorting, thereby improving sorting efficiency.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a conference management method, server, and conference management system. Background Art

[0002] With the development of society, the number of employees in various enterprises has also increased significantly. In enterprises, meetings have become an important means of communication among employees in their daily work. In order to issue tasks, improve project operation efficiency, etc., different meetings are held regularly so that participants can understand the company's development plans in a timely manner.

[0003] During a meeting, participants discuss the topic. After the meeting, a dedicated note-taker must manually organize the meeting content. However, this consumes a significant amount of staff time, is inefficient, and can result in incomplete recording of key points. Summary of the Invention

[0004] The embodiments of the present application propose a conference management method, server and conference management system to solve the problem that the existing manual organization of conference content consumes a lot of working time of staff, has low efficiency in organizing conference content, and also results in incomplete recording of key content in the meeting.

[0005] In order to solve the above problems, the present application discloses a conference management method, which is applied to a server and includes:

[0006] Receiving information of multiple participants sent by the first client;

[0007] Binding each participant's information to a corresponding electronic table card identifier, wherein each electronic table card identifier corresponds to a microphone in a one-to-one correspondence;

[0008] receiving voice information collected by at least one target microphone;

[0009] According to the target electronic table card identifier of the target electronic table card corresponding to the target microphone, determining the target participant information bound to the target electronic table card identifier;

[0010] A conference document is generated based on the voice information and the target participant information.

[0011] In order to solve the above problems, the present application also discloses a server, comprising:

[0012] A participant information receiving module is configured to receive a plurality of participant information sent by the first client;

[0013] An information binding module is configured to bind each participant's information to a corresponding electronic table card identifier, wherein the electronic table card corresponding to each electronic table card identifier also corresponds one-to-one with a microphone;

[0014] a voice information receiving module, configured to receive voice information collected by at least one target microphone;

[0015] A target participant information determination module is configured to determine the target participant information bound to the target electronic table card identifier according to the target electronic table card identifier of the target electronic table card corresponding to the target microphone;

[0016] The conference document generation module is configured to generate a conference document according to the voice information and the target participant information.

[0017] In order to solve the above problems, the present application also discloses a server, including a processor, a memory and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the above conference management method are implemented.

[0018] In order to solve the above problems, the present application also discloses a computer-readable medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above conference management method are implemented.

[0019] In order to solve the above problems, the present application also discloses a conference management system, including an electronic table card, a microphone, a first client and the above server;

[0020] Wherein, the electronic table card is configured to display the participant information bound to the electronic table card identifier corresponding to the electronic table card;

[0021] The microphone is configured to collect voice information emitted by the target participant corresponding to the target participant information;

[0022] The first client is configured to send information of multiple participants to the server.

[0023] Optionally, the conference management system further includes a second client, a third client and a fourth client;

[0024] The second client is configured to send a target message and information of designated participants corresponding to the target message to the server, and receive a receipt message sent by the server;

[0025] The third client is configured to send at least one to-be-executed task for the conference document and executor information corresponding to the task executor designated for each of the to-be-executed tasks to the server;

[0026] The fourth client is configured to receive the to-be-executed task sent by the server, and send the task progress of the to-be-executed task to the server;

[0027] The first client is further configured to send participant change information to the server;

[0028] The electronic table sign is further configured to display the target message and tasks to be performed sent by the server; and to send a receipt message to the server, and / or to control the indicator light on the electronic table sign to illuminate according to the control instructions sent by the server.

[0029] Compared with the prior art, this application has the following advantages:

[0030] In an embodiment of the present application, the participant information is bound to the electronic table card identifier in advance, and the electronic table card corresponding to the electronic table card identifier is also in one-to-one correspondence with the microphone. During the meeting, the target electronic table card identifier of the target electronic table card corresponding to the target microphone is determined according to the target microphone that sends the voice message, and then the target participant information of the target participant who sent the voice message is determined. Finally, based on the target participant information and the voice information, a conference document is directly generated without the need for manual sorting by the staff, saving the staff's working time, improving the efficiency of sorting the conference documents, and avoiding the phenomenon of incomplete records of the meeting content; and the target participant corresponding to each voice message can be identified, and the target participant information corresponding to each voice message is automatically marked in the conference document, avoiding the lack of clarity of the target participant corresponding to each voice message when viewing the conference document later, making the generated conference document clearer and more understandable.

[0031] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0033] Figure 1 The following schematically shows a flow chart of a conference management method according to an embodiment of the present application;

[0034] Figure 2 A schematic diagram of a conference reservation page for adding participant information in an embodiment of the present application is schematically shown;

[0035] Figure 3 The following schematically shows a flow chart of another conference management method according to an embodiment of the present application;

[0036] Figure 4 The flowchart of the process of allocating tasks to be executed in the embodiment of the present application is schematically shown;

[0037] Figure 5 The following schematically shows a structural block diagram of a server according to an embodiment of the present application;

[0038] Figure 6 Schematically shows a block diagram of a server for executing the method according to the present application;

[0039] Figure 7 The figure schematically shows a storage unit for storing or carrying a program code for implementing the method according to the present application. DETAILED DESCRIPTION

[0040] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0041] Reference Figure 1 , shows a flowchart of a conference management method according to an embodiment of the present application, which is applied to a server and may specifically include the following steps:

[0042] Step 101: Receive information of multiple participants sent by a first client.

[0043] In an embodiment of the present application, the staff operates the first client so that the first client sends a login request for the conference management page to the server. The server returns the login page corresponding to the conference management page to the first client based on the received login request; after receiving the login page, the first client displays the login page, and the staff enters identity information in the login page. The identity information includes information such as user name and password. Then, the first client sends the identity information to the server, and the server verifies the identity information sent by the first client. After the verification is passed, the server sends the conference management page to the first client. After receiving the conference management page, the first client displays the conference management page.

[0044] When staff makes a meeting reservation on the meeting management page, they will be redirected to the following page: Figure 2 The meeting reservation page shown includes a meeting name input box, a contact input box, a conference room selection box, a meeting date input box, a number of participants input box, a contact information input box, and a meeting time input box; the staff enters the meeting name corresponding to the meeting to be held in the meeting name input box, enters the corresponding contact name in the contact input box, selects the conference room where the meeting will be held in the conference room selection box, and enters the corresponding meeting date in the meeting date input box. The format of the meeting date is yy-mm-dd, such as if the meeting date is 2020-12-09, enter the number of participants in the meeting in the number of participants input box, enter the corresponding contact number of the contact in the contact information input box, and enter the meeting time in the meeting time input box. The meeting time includes the meeting start time and the meeting end time, and its format is hh:mm, such as if the meeting start time is 14:00 and the meeting end time is 15:30.

[0045] And, in Figure 2 The shown meeting reservation page also displays information input boxes corresponding to the participants, including the participant's name input box, the participant's position input box, the participant's department input box and the participant's company input box, etc. The staff enters the name of the participant attending the meeting in the participant's name input box, enters the participant's position in the participant's position input box, enters the name of the participant's department in the participant's department input box, and enters the name of the participant's company in the participant's company input box. In addition, a participant's email input box can also be displayed on the meeting reservation page, and the staff can enter the participant's email account in the participant's email input box.

[0046] In addition, Figure 2 The conference reservation page shown also displays a delete control, a participant addition control, a cancel control, and a submit control. By triggering the delete control, the corresponding participant information can be deleted. By triggering the participant addition control, an information input box corresponding to the participant can be added. By triggering the cancel control, the scheduled meeting can be canceled. By triggering the submit control, the information entered in the conference reservation page can be sent to the server.

[0047] Therefore, the first client can receive multiple participant information entered by the staff in the meeting reservation page, and the participant information includes the participant's name, participant's email account, participant's position, participant's department and participant's company. Then, the first client receives the staff's touch operation on the submit control and sends the multiple participant information to the server, and the server receives the multiple participant information sent by the first client.

[0048] For example, the server receives four participant information sent by the first client. The first participant information includes the participant name "Zhang San", the second participant information includes the participant name "Li Si", the third participant information includes the participant name "Wang Wu", and the fourth participant information includes the participant name "Zhao Liu".

[0049] The first client in the embodiment of the present application may be a browser or an application deployed on a terminal device, where the application refers to an application for conference management.

[0050] Step 102: Bind each participant's information with the corresponding electronic table card identifier. The electronic table card corresponding to each electronic table card identifier also corresponds to a microphone one-to-one.

[0051] In an embodiment of the present application, after receiving multiple participant information sent by the first client, the server randomly binds each participant information with an unused electronic table card identifier, and the electronic table card corresponding to each electronic table card identifier also corresponds one-to-one with a microphone.

[0052] In actual products, the electronic table card and the microphone can be two independent devices, and each microphone has a unique microphone ID. Therefore, each electronic table card ID needs to be bound to the corresponding microphone ID in advance, so that the electronic table card corresponding to each electronic table card ID corresponds to the microphone one-to-one. At this time, the participant information, electronic table card ID and microphone ID are bound one by one.

[0053] Of course, the microphone can be set on the electronic table card, that is, the electronic table card and the microphone are an integrated structure. At this time, the electronic table card and the microphone are one-to-one corresponding. By binding the participant information with the electronic table card identification, the participant information, electronic table card and microphone can be one-to-one corresponding.

[0054] For example, the unused electronic table card identifiers include electronic table card identifier A1, electronic table card identifier A2, electronic table card identifier A3, electronic table card identifier A4, electronic table card identifier A5 and electronic table card identifier A6. The participant's name "Zhang San" is bound to the electronic table card identifier A1, the participant's name "Li Si" is bound to the electronic table card identifier A2, the participant's name "Wang Wu" is bound to the electronic table card identifier A3, and the participant's name "Zhao Liu" is bound to the electronic table card identifier A4; and, the electronic table card identifier A1 is also bound to the microphone identifier B1, the electronic table card identifier A2 is also bound to the microphone identifier B2, the electronic table card identifier A3 is also bound to the microphone identifier B3, and the electronic table card identifier A4 is also bound to the microphone identifier B4.

[0055] If the electronic table card and the microphone are two independent devices, the binding relationship between the electronic table card identifier and the microphone identifier can also be modified during actual use. At this time, the staff modifies the binding relationship between the electronic table card identifier and the microphone identifier in the conference management page displayed by the first client, and the first client sends the modification request to the server, and the server modifies the binding relationship between the electronic table card identifier and the microphone identifier according to the modification request.

[0056] For example, the staff modifies the binding relationship between the electronic table card identifier A1 and the microphone identifier B1, which is used to unbind the electronic table card identifier A1 from the microphone identifier B1, and rebind the electronic table card identifier A1 from the microphone identifier B5. Therefore, after receiving the modification request sent by the first client, the server unbinds the electronic table card identifier A1 from the microphone identifier B1, and rebinds the unbound electronic table card identifier A1 from the microphone identifier B5.

[0057] It should be noted that the process of receiving multiple participant information sent by the first client in step 101 and the process of binding the participant information with the electronic table card identification in step 102 are both performed before the meeting starts; of course, according to actual usage requirements, the server can also receive the participant information sent by the first client and bind the participant information with the electronic table card identification during the meeting.

[0058] Step 103: Receive voice information collected by at least one target microphone.

[0059] In an embodiment of the present application, after binding the participant information with the electronic table card identification, the staff will place the electronic table card corresponding to the electronic table card identification and the microphone corresponding to the microphone identification, or the electronic table card with an integrated microphone, according to the actual required placement positions.

[0060] Before a meeting begins, when the time difference between the meeting start time and the scheduled time difference is equal to a preset time difference, the server sends the attendee information associated with each electronic table sign to the corresponding electronic table sign. The electronic table sign then displays the attendee information, such as the attendee's name, position, and department. Before the meeting begins, the electronic table sign displays attendee information to ensure that attendees are seated in the correct seats. The preset time difference can be set to 10 minutes, 30 minutes, or other values.

[0061] For example, if the meeting start time is 14:00, when the time difference from the meeting start time is equal to the preset time difference of 10 minutes, that is, 13:50, the server sends the participant information to the electronic table card, and the electronic table card displays the participant information.

[0062] During a meeting, if at least one target participant speaks on the meeting topic, a target microphone located at the target participant's location will capture their voice information. The target microphone then sends the voice information to the server, which then receives the voice information captured by the at least one target microphone. The target participant is the speaker among the multiple meeting participants, and the target microphone is the microphone that captures the target participant's voice information.

[0063] The electronic table card in the embodiment of the present application may be an electronic ink screen table card, which communicates with the server through a gateway. The communication method may be Wi-Fi (WIreless-Fidelity), 433MHZE (a wireless transmission communication), etc. The embodiment of the present application does not limit the communication method between the electronic table card and the server.

[0064] Step 104 : determining target participant information bound to the target electronic table card identifier according to the target electronic table card identifier of the target microphone.

[0065] In an embodiment of the present application, after receiving the voice information sent by the target microphone, the server determines the target electronic table card identifier of the target electronic table card corresponding to the target microphone based on the one-to-one correspondence between the microphone and the electronic table card, and then determines the target participant information bound to the target electronic table card identifier, that is, identifies the target participant corresponding to each voice information.

[0066] For example, the electronic table card and the microphone are two independent devices. The target microphone identifier corresponding to the target microphone that collects voice information is microphone identifier B2, then the target electronic table card identifier bound to the target microphone identifier B2 is determined to be electronic table card identifier A2, and then the participant name in the target participant information bound to the target electronic table card identifier A2 is determined to be "Li Si". Of course, the participant's email account, participant's position, participant's department name, and participant's company name in the target participant information bound to the target electronic table card identifier A2 can also be determined.

[0067] Step 105: Generate a conference document based on the voice information and the target participant information.

[0068] In an embodiment of the present application, after determining the target participant information, the server generates a conference document based on the voice information collected by the target microphone and the target participant information.

[0069] Specifically, the target participant information is automatically added before each voice message to generate a conference document. Therefore, the target participant information corresponding to each voice message will be automatically marked in the conference document, avoiding the problem of being unclear about the target participant corresponding to each voice message when viewing the conference document later, making the generated conference document clearer and more understandable; and it also avoids the problem that the staff is unclear about the speaker name corresponding to each voice message, resulting in the inability to manually add the target participant information corresponding to each voice message.

[0070] During the meeting, the voice information collected by the target microphone is received in real time, and the target participant information corresponding to the target participant who sent the voice information is determined. The target participant information is added before each voice message, and a conference document containing each voice message and the corresponding target participant information is generated in chronological order. The conference document is stored in the server.

[0071] Furthermore, after step 105, it also includes: extracting associated user information corresponding to associated users associated with this meeting based on the meeting document; the associated user information includes participant information and user information corresponding to the users involved in the meeting; and sending the meeting document based on the associated user information.

[0072] In an embodiment of the present application, after generating a conference document, the server can automatically extract the associated user information corresponding to the associated user associated with the current conference based on the conference document. Specifically, the participant information corresponding to the conference document can be automatically extracted from the server. The participant information is sent by the first client and stored in the server. In this case, the associated user is the participant who participated in the current conference. The user information corresponding to the user mentioned in the current conference can also be automatically obtained from the conference document. The user name corresponding to the user mentioned in the current conference and other information corresponding to the user name are used as the associated user information. For example, the user name, user gender, user department name, and other information are used as the associated user information. In this case, the associated user is the user mentioned in the current conference.

[0073] Then, the server sends the conference document to the client corresponding to the associated user according to the associated user information, and the associated users can view the conference document in their respective corresponding clients.

[0074] Of course, after generating the conference document, the server may also only store the conference document. The associated user may log in to the conference management page and send a conference document viewing request to the server to view the conference document.

[0075] After the meeting, the staff member logs in to the meeting management page through the first client, performs operations on the meeting management page, and sends a request to the server to view the meeting document. The server returns the meeting document to the first client based on the request. After receiving the meeting document from the server, the first client displays the meeting document. The staff member organizes the meeting document in the first client and extracts the key content to obtain the meeting minutes. The first client then sends the finalized meeting minutes to the server. The server can then send the meeting minutes based on the determined associated user information. Alternatively, associated users can log in to the meeting management page through their respective clients and send a meeting minutes viewing request to the server to view the meeting minutes.

[0076] In an embodiment of the present application, the participant information is bound to the electronic table card identifier in advance, and the electronic table card corresponding to the electronic table card identifier is also in one-to-one correspondence with the microphone. During the meeting, the target electronic table card identifier of the target electronic table card corresponding to the target microphone is determined according to the target microphone that sends the voice message, and then the target participant information of the target participant who sent the voice message is determined. Finally, based on the target participant information and the voice information, a conference document is directly generated without the need for manual sorting by the staff, saving the staff's working time, improving the efficiency of sorting the conference documents, and avoiding the phenomenon of incomplete records of the meeting content; and the target participant corresponding to each voice message can be identified, and the target participant information corresponding to each voice message is automatically marked in the conference document, avoiding the lack of clarity of the target participant corresponding to each voice message when viewing the conference document later, making the generated conference document clearer and more understandable.

[0077] Reference Figure 3 , shows a flowchart of another conference management method according to an embodiment of the present application, which is applied to a server and may specifically include the following steps:

[0078] Step 301: Receive information of multiple participants sent by a first client.

[0079] This step is similar to the principle of step 101 above and will not be described again here.

[0080] In step 302, each participant's information is bound to a corresponding electronic table card identifier, and each electronic table card identifier corresponds to a microphone.

[0081] In an embodiment of the present application, the server randomly binds each participant information to an unused electronic table card identifier, and the electronic table card corresponding to each electronic table card identifier also corresponds one-to-one with a microphone. At this time, the participant information, electronic table card and microphone correspond one-to-one.

[0082] Optionally, before step 303, it also includes: receiving participant change information sent by the first client; the participant change information includes a target input box identifier and the changed participant information entered in the target input box corresponding to the target input box identifier; changing the participant information to be changed pre-entered in the target input box corresponding to the target input box identifier to the changed participant information, and binding the changed participant information to the electronic table card identifier corresponding to the participant information to be changed.

[0083] In an embodiment of the present application, before the meeting starts or during the meeting, when the participants change temporarily, the staff logs in to the meeting management page through the first client, and jumps from the meeting management page to the meeting reservation page, deletes the participant information to be changed in the target input box in the meeting reservation page, and re-enters the changed participant information, the first client sends the target input box identifier corresponding to the target input box and the changed participant information re-entered in the target input box to the server, the server determines the participant information to be changed previously entered in the target input box corresponding to the target input box identifier based on the target input box identifier, and then changes the participant information to be changed to the changed participant information, and binds the changed participant information to the electronic table card identifier corresponding to the participant information to be changed. At this time, the participant information to be changed and its corresponding electronic table card identifier are also unbound accordingly.

[0084] For example, the target input box identifier sent by the first client to the server is target input box identifier 1, the changed participant information includes the participant name "Li Er", the participant name previously entered in the target input box corresponding to target input box identifier 1 is "Zhang San", and the participant name "Zhang San" is bound to the electronic table card identifier A1. Therefore, the server changes the participant information from the information corresponding to "Zhang San" to the information corresponding to "Li Er", and binds the participant name "Li Er" to the electronic table card identifier A1.

[0085] Before the meeting begins, the server sends the changed attendee information to the electronic table cards, which then display the changed attendee information. Conventional technology displays attendee information on paper table cards, which require reprinting and replacing paper table cards when attendee information changes. However, the present embodiment displays attendee information on electronic table cards. When attendees change, simply sending a message to the electronic table cards via the server can modify the display content. This simplifies operation and minimizes waste.

[0086] When determining the speaker name corresponding to the voice information later, the changed participant information is also retrieved, and the meeting document is generated based on the changed participant information and voice information, which is more flexible and practical.

[0087] Step 303: Receive voice information collected by at least one target microphone.

[0088] This step is similar in principle to the above step 103 and will not be described again here.

[0089] Step 304 : determining target participant information bound to the target electronic table card identifier according to the target electronic table card identifier of the target microphone.

[0090] This step is similar in principle to the above step 104 and will not be described again here.

[0091] Step 305: convert the voice information to generate text information.

[0092] In the embodiment of the present application, after the server receives the voice information sent by the microphone, the server recognizes the voice information through voice conversion technology and converts the voice information into text information.

[0093] Furthermore, the server converts the voice information according to a preset language type and generates text information corresponding to the preset language type. The preset language type can be set manually, and it can be one or more; or, the server converts the voice information according to the target language type corresponding to the voice information sent by all target microphones received, and generates text information corresponding to the target language type.

[0094] For example, the preset language types are English and Chinese, the voice information is converted, and the generated text information includes: text information in English and text information in Chinese; or, the target language types corresponding to the voice information sent by all target microphones received by the server include: English, Chinese and Korean, then the voice information is converted, and the generated text information includes: text information in English, text information in Chinese and text information in Korean.

[0095] Step 306: Generate a conference document based on the target participant information and the text information.

[0096] In an embodiment of the present application, after converting the voice information to generate text information, the server generates a conference document based on the target participant information and the text information.

[0097] Step 307: During the conference, a target message and designated participant information corresponding to the target message are received from the second client.

[0098] In an embodiment of the present application, during a meeting, participants generally do not check their mobile phone messages in a timely manner. When there is an event to be processed that requires notification to a designated participant, in order to avoid disturbing the order of the venue, the message sender will log in to the conference management page through a second client. The message sender finds the information of the designated participants participating in the meeting on the conference management page and enters the target message to be notified on the conference management page. The second client will then send the entered target message and the selected designated participant information to the server. The server will receive the target message sent by the second client and the designated participant information corresponding to the target message. The login process of the second client is similar to that of the first client and will not be repeated here.

[0099] The second client may be a browser or an application deployed on a terminal device, and the application may be an application for conference management.

[0100] Step 308: Determine the designated electronic table card identifier bound to the designated participant information.

[0101] In an embodiment of the present application, after receiving the target message sent by the second client and the designated participant information corresponding to the target message, the server determines the designated electronic table card identifier bound to the designated participant information based on the binding relationship between the participant information and the electronic table card identifier.

[0102] For example, if the participant name in the designated participant information is "Wang Wu", the designated electronic table card identifier bound to the designated participant information is determined to be the electronic table card identifier A3.

[0103] Step 309: Send the target message to the designated electronic table card corresponding to the designated electronic table card identifier.

[0104] In an embodiment of the present application, after the server determines the designated electronic table card identifier bound to the designated participant information, the server sends the target message to the designated electronic table card corresponding to the designated electronic table card identifier. After receiving the target message, the designated electronic table card displays the target message on the display screen included in the designated electronic table card.

[0105] Each electronic table card includes two screens positioned opposite each other. The screen facing away from the attendees displays attendee information, while the screen facing the attendees displays attendee information or conference-related content. Upon receiving a target message from the server, the designated electronic table card displays the target message on the screen facing the attendee, replacing the previously displayed content.

[0106] Step 310: Receive a receipt message sent by the designated electronic table card.

[0107] In an embodiment of the present application, two reply buttons are provided on the base of each electronic table card, namely a first reply button and a second reply button. The first reply button is used to send a confirmation message to the server, and the second reply button is used to send a rejection message to the server.

[0108] After the designated electronic table card displays the target message on the display screen it includes, if the designated participant sees the target message, he or she can press the reply button set on the designated electronic table card to make a simple reply. Then, the designated electronic table card sends the receipt message of the designated participant to the server, and the server receives the receipt message sent by the designated electronic table card.

[0109] Step 311: Send the receipt message to the second client.

[0110] In an embodiment of the present application, after the server receives the receipt message sent by the designated electronic table card, the server returns the receipt message to the second client. After receiving the receipt message, the second client displays the receipt message. The message sender can then understand the designated participant's handling opinions on the event through the receipt message.

[0111] Step 312: When no receipt message is received from the designated electronic table card within a preset time period, a control instruction is sent to the designated electronic table card to control the indicator light on the designated electronic table card to light up.

[0112] In an embodiment of the present application, after the server sends the target message to the designated electronic table card, the target message is displayed on the display screen included in the designated electronic table card. If the server does not receive the receipt message sent by the designated electronic table card within a preset time period, it is determined that the designated participant has not seen the target message in time. The server then sends a control instruction to the designated electronic table card. After receiving the control instruction, the designated electronic table card controls the indicator light set on the designated electronic table card to light up, and the designated participant is reminded to check the target message by the indicator light set on the designated electronic table card.

[0113] In the actual product, an indicator light is set on the side of each electronic table card facing the participants, and the indicator light set on the designated electronic table card is controlled to light up. The indicator light can be controlled to flash at a fixed frequency or to be continuously lit.

[0114] It should be noted that steps 307 to 312 are executed during the conference, and there is no fixed order between them and steps 303 to 306.

[0115] Reference Figure 4 , which shows a flowchart of the process of allocating tasks to be executed in an embodiment of the present application, which may specifically include the following steps:

[0116] Step 401: for the conference document, determine at least one task to be executed and executor information corresponding to the task executor designated for each task to be executed.

[0117] In an embodiment of the present application, during or after a meeting, for a generated meeting document, at least one task to be performed and executor information corresponding to the task executor designated for each task to be performed are automatically or manually determined.

[0118] In an optional implementation manner, step 401 includes: receiving at least one to-be-executed task for the conference document, and executor information corresponding to task executors designated for each of the to-be-executed tasks, sent by a third client.

[0119] After the meeting ends, other participants can log in to the meeting management page using their respective third-party clients. To view the meeting document, the third-party client sends a request to the server to view the meeting document. The server sends the meeting document to the corresponding third-party client based on the request. The third-party client receives and displays the document. The third-party client login process is similar to that of the first client and will not be further described here.

[0120] Participants can enter corresponding message information in the conference management page of the third-party client to express their opinions on the meeting. The third-party client will send the message information to the server, and the server will manage the content of the current meeting in the form of a forum. Other participants can view the message information after logging into the conference management page.

[0121] Participants can also manually enter the corresponding tasks to be executed in the conference management page of the third client, and manually select the executor information corresponding to the task executors specified for each task to be executed. After the meeting, the third client will send at least one task to be executed for the conference document and the executor information corresponding to the task executors specified for each task to be executed to the server, and the server will receive the at least one task to be executed for the conference document and the executor information corresponding to the task executors specified for each task to be executed sent by the third client.

[0122] It should be noted that, during the meeting, a meeting document can be generated in real time based on the target participant information and voice information. Other relevant personnel manually enter the corresponding tasks to be executed in the meeting management page of the third client, and manually select the executor information corresponding to the task executors specified for each task to be executed. Then, during the meeting, the server receives at least one task to be executed for the meeting document and the executor information corresponding to the task executors specified for each task to be executed sent by the third client.

[0123] In another optional embodiment, step 401 includes: extracting at least one task to be executed from the meeting document, and the executor information of the task executor corresponding to each task to be executed.

[0124] During the meeting, participants may directly assign tasks in the meeting. The voice information collected by the target microphone contains information about the tasks to be executed and the executors. Therefore, after the meeting document is generated, the meeting document will also contain information about the tasks to be executed and the executors. The server directly and automatically extracts at least one task to be executed from the meeting document, as well as the executor information of the task executors corresponding to each task to be executed.

[0125] At this time, participants do not need to log in to the conference management page through a third client and enter the tasks to be executed and the executor information on the conference management page, making the task allocation process simpler.

[0126] Of course, in actual use, the executor information may also include at least one participant information, that is, the task executor may be at least one participant attending the meeting. Therefore, step 401 includes: during the meeting, for the meeting document, determining at least one task to be executed and the executor information corresponding to the task executor specified for each task to be executed; the executor information includes at least one participant information.

[0127] During the meeting, the server may determine the executor information corresponding to at least one task to be executed and each task executor specified for the task to be executed based on at least one task to be executed sent by a third client, and the executor information corresponding to each task executor specified for the task to be executed, or the server may automatically extract at least one task to be executed and the executor information corresponding to each task executor specified for the task to be executed from the meeting document, and the executor information includes at least one participant information.

[0128] Step 402: Send the task to be executed according to the executor information.

[0129] In an embodiment of the present application, after obtaining the task to be executed and the executor information, the server sends the task to be executed to the task executor corresponding to the executor information according to the executor information.

[0130] Specifically, step 402 includes sub-step S4021:

[0131] Sub-step S4021: sending the task to be executed to the electronic table card corresponding to the participant information in the executor information.

[0132] When during the meeting, it is determined that the executor information includes at least one participant information, that is, the task executor is at least one participant attending the meeting, the server determines the electronic table sign identifier bound to the participant information in the executor information, and then sends the task to be executed to the electronic table sign corresponding to the electronic table sign identifier. The electronic table sign then displays the task to be executed, so that the participant assigned the task to be executed can see the task to be executed through the electronic table sign at his or her location, so that the participant assigned the task to be executed can record the assigned task to be executed in time.

[0133] Specifically, step 402 includes sub-step S4022:

[0134] Sub-step S4022: sending the to-be-executed task to a fourth client corresponding to the task executor according to the executor information.

[0135] In an embodiment of the present application, the server determines the corresponding task executor based on the executor information, and then sends the assigned task to be executed to the fourth client corresponding to the task executor. After receiving the task to be executed, the fourth client stores the task to be executed locally. After the task executor subsequently logs in to the conference management page, the fourth client directly retrieves the locally stored task to be executed and displays the task to be executed. The task executor can then check the assigned task to be executed.

[0136] Furthermore, after sub-step S4022, it also includes: receiving the task progress for the task to be executed sent by each of the fourth clients; the task progress includes the task status; when the task status of all the tasks to be executed is completed, the task execution status for the conference document is changed to completed.

[0137] In an embodiment of the present application, the task executor processes the task to be executed and enters the execution progress of the task to be executed on the conference management page. The fourth client then sends the task progress of the task to be executed to the server, and the server receives the task progress for the task to be executed sent by the fourth client.

[0138] The task progress includes the task status and the task execution progress description. The task status includes completed status, ongoing status, unprocessed status, etc.

[0139] When all task executors have completed the processing of the pending tasks, that is, when the task status in the task progress sent by each fourth client to the server is all in the completed state, the server determines that the task status of all pending tasks is in the completed state, and automatically changes the task execution status for the meeting document from the unfinished state to the completed state.

[0140] If only some of the tasks to be executed have a task status of completed, and some of the tasks to be executed have a task status of unprocessed or in progress, the task execution status of the meeting document remains uncompleted.

[0141] The task progress of each task to be executed is sent to the server through the fourth client, and other personnel can timely learn the task progress of each task to be executed by logging into the conference management page.

[0142] It should be noted that step 401 and step 402 are executed in sequence after step 105. Furthermore, the first client, the second client, the third client, and the fourth client may be the same client or different clients.

[0143] The third client and the fourth client in the embodiment of the present application can be browsers or applications deployed on the terminal device. The application can be an application for conference management or other applications for message notification, such as a mailbox application.

[0144] In the embodiment of the present application, by pre-binding the participant information with the electronic table card identifier, and the electronic table card corresponding to the electronic table card identifier is also in one-to-one correspondence with the microphone, during the meeting, according to the target microphone sending the voice information, the target electronic table card identifier of the target microphone corresponding to the target microphone is determined, and then the target participant information of the target participant who sent the voice information is determined, and finally, according to the target participant information and the voice information, the meeting document is directly generated without the need for manual sorting by the staff, thus saving the staff's working time, improving the efficiency of sorting the meeting documents, and avoiding the phenomenon of incomplete records of the meeting content; Moreover, the target participant corresponding to each voice message can be identified, and the target participant information corresponding to each voice message can be automatically marked in the conference document to avoid being unclear about the target participant corresponding to each voice message when viewing the conference document later, making the generated conference document clearer and more understandable; in addition, the second client, server and designated electronic table signs can be used in conjunction to handle pending events in a timely manner during the meeting to avoid delays in handling pending events due to the meeting; tasks can also be assigned to the conference document during or after the meeting, making it convenient for task executors to understand their assigned pending tasks.

[0145] Reference Figure 5 , shows a structural block diagram of a server in an embodiment of the present application.

[0146] The server 500 of the embodiment of the present application includes:

[0147] The participant information receiving module 501 is configured to receive a plurality of participant information sent by the first client;

[0148] The information binding module 502 is configured to bind each participant's information to a corresponding electronic table card identifier, wherein the electronic table card corresponding to each electronic table card identifier also corresponds to a microphone on a one-to-one basis;

[0149] The voice information receiving module 503 is configured to receive voice information collected by at least one target microphone;

[0150] The target participant information determination module 504 is configured to determine the target participant information bound to the target electronic table card identifier according to the target electronic table card identifier of the target electronic table card corresponding to the target microphone;

[0151] The conference document generation module 505 is configured to generate a conference document according to the voice information and the target participant information.

[0152] Optionally, the conference document generation module 505 includes:

[0153] A text information generation submodule is configured to convert the voice information into text information;

[0154] The conference document generation submodule is configured to generate a conference document according to the target participant information and the text information.

[0155] Optionally, the server 500 further includes:

[0156] a participant change information receiving module configured to receive participant change information sent by the first client; the participant change information includes a target input box identifier and the changed participant information entered in the target input box corresponding to the target input box identifier;

[0157] The participant information changing module is configured to change the participant information to be changed that is pre-entered in the target input box corresponding to the target input box identifier to the changed participant information, and bind the changed participant information to the electronic table card identifier corresponding to the participant information to be changed.

[0158] Optionally, the server 500 further includes:

[0159] a target message receiving module configured to receive a target message and designated participant information corresponding to the target message sent by a second client during a meeting;

[0160] a designated electronic table card identification determination module, configured to determine the designated electronic table card identification bound to the designated participant information;

[0161] The target message sending module is configured to send the target message to the designated electronic table card corresponding to the designated electronic table card identifier.

[0162] Optionally, the server 500 further includes:

[0163] a receipt message receiving module, configured to receive a receipt message sent by the designated electronic table card;

[0164] The receipt message sending module is configured to send the receipt message to the second client.

[0165] Optionally, the server 500 further includes:

[0166] The control instruction sending module is configured to send a control instruction to the designated electronic table card to control the indicator light on the designated electronic table card to emit light when no receipt message sent by the designated electronic table card is received within a preset time period.

[0167] Optionally, the server 500 further includes:

[0168] A task assignment module is configured to determine, for the conference document, at least one task to be performed and executor information corresponding to a task executor designated for each task to be performed;

[0169] The to-be-executed task sending module is configured to send the to-be-executed task according to the executor information.

[0170] Optionally, the task assignment module includes:

[0171] The task assignment submodule is configured to determine, during a meeting, for the meeting document, at least one task to be performed and executor information corresponding to the task executor designated for each task to be performed; the executor information includes at least one participant information;

[0172] The to-be-executed task sending module includes:

[0173] The first sending submodule of the task to be executed is configured to send the task to be executed to the electronic table card corresponding to the participant information in the executor information.

[0174] Optionally, the task assignment module includes:

[0175] a to-be-executed task receiving submodule, configured to receive at least one to-be-executed task for the conference document, and executor information corresponding to task executors designated for each of the to-be-executed tasks, sent by a third client;

[0176] or,

[0177] The to-be-executed task extraction submodule is configured to extract at least one to-be-executed task and executor information of a task executor corresponding to each to-be-executed task from the conference document.

[0178] Optionally, the to-be-executed task sending module includes:

[0179] The second sending submodule of the task to be executed is configured to send the task to be executed to the fourth client corresponding to the task executor according to the executor information;

[0180] The server 500 further includes:

[0181] A task progress receiving module is configured to receive the task progress for the to-be-executed task sent by each of the fourth clients; the task progress includes a task status;

[0182] The task execution status changing module is configured to change the task execution status of the conference document to the completed state when the task statuses of all the tasks to be executed are in the completed state.

[0183] Optionally, the server further includes:

[0184] The associated user information extraction module is configured to extract associated user information corresponding to associated users associated with the current meeting based on the meeting document; the associated user information includes participant information and user information corresponding to the users involved in the current meeting;

[0185] The conference document sending module is configured to send the conference document according to the associated user information.

[0186] In an embodiment of the present application, the participant information is bound to the electronic table card identifier in advance, and the electronic table card corresponding to the electronic table card identifier is also in one-to-one correspondence with the microphone. During the meeting, the target electronic table card identifier of the target electronic table card corresponding to the target microphone is determined according to the target microphone that sends the voice message, and then the target participant information of the target participant who sent the voice message is determined. Finally, based on the target participant information and the voice information, a conference document is directly generated without the need for manual sorting by the staff, saving the staff's working time, improving the efficiency of sorting the conference documents, and avoiding the phenomenon of incomplete records of the meeting content; and the target participant corresponding to each voice message can be identified, and the target participant information corresponding to each voice message is automatically marked in the conference document, avoiding the lack of clarity of the target participant corresponding to each voice message when viewing the conference document later, making the generated conference document clearer and more understandable.

[0187] Correspondingly, an embodiment of the present application also provides a server, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the above-mentioned conference management method when executed by the processor.

[0188] An embodiment of the present application further provides a computer-readable medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned conference management method are implemented.

[0189] The embodiment of the present application further provides a conference management system, including an electronic table sign, a microphone, a first client, and the above-mentioned server 500.

[0190] Wherein, the electronic table card is configured to display the participant information bound to the electronic table card identifier corresponding to the electronic table card;

[0191] The microphone is configured to collect voice information emitted by the target participant corresponding to the target participant information;

[0192] The first client is configured to send information of multiple participants to the server.

[0193] In an embodiment of the present application, a meeting reservation is required before the meeting begins. A staff member logs in to the meeting management page on a first client and navigates to the meeting reservation page. The staff member then enters information about multiple attendees on the meeting reservation page. The first client then sends the information to a server, which then binds the attendee information to the electronic table sign. The attendee information includes the attendee's name, email address, position, department, and company.

[0194] Before the meeting starts, when the time difference between the meeting start time and the preset time difference is equal to the server, the server will send the participant information bound to each electronic table card identifier to the electronic table card corresponding to the electronic table card identifier, and the electronic table card will display the participant information bound to the electronic table card identifier corresponding to the electronic table card.

[0195] During the meeting, the target participant will speak on the meeting topic, and the target microphone at the target participant's location will collect the voice information emitted by the target participant. Then, the target microphone will send the voice information to the server, so that the server can generate a meeting document based on the voice information and the target participant information.

[0196] Furthermore, the conference management system further includes a second client, a third client, and a fourth client;

[0197] The second client is configured to send a target message and information of designated participants corresponding to the target message to the server, and receive a receipt message sent by the server;

[0198] The third client is configured to send at least one to-be-executed task for the conference document and executor information corresponding to the task executor designated for each of the to-be-executed tasks to the server;

[0199] The fourth client is configured to receive the to-be-executed task sent by the server, and send the task progress of the to-be-executed task to the server;

[0200] The first client is further configured to send participant change information to the server;

[0201] The electronic table sign is further configured to display the target message and tasks to be performed sent by the server; and to send a receipt message to the server, and / or to control the indicator light on the electronic table sign to illuminate according to the control instructions sent by the server.

[0202] Before the meeting starts or during the meeting, when there is a temporary change in the attendees, the staff enters the meeting reservation page through the first client and changes the attendee information on the meeting reservation page. The first client then sends the attendee change information to the server, so that the server changes the attendee information to be changed to the changed attendee information, and binds the changed attendee information to the electronic table card identifier corresponding to the attendee information to be changed.

[0203] During the meeting, when there are pending events that need to be notified to the participants, in order to avoid disturbing the order of the venue, the message sender will log in to the conference management page through the second client, select the designated participant information on the conference management page, and enter the target message to be notified on the conference management page. The second client then sends the target message and the designated participant information corresponding to the target message to the server; the server determines the designated electronic table sign identifier bound to the designated participant information based on the designated participant information, and sends the target message to the designated electronic table sign corresponding to the designated electronic table sign identifier. The designated electronic table sign then receives and displays the target message sent by the server.

[0204] The designated participant can then respond to the target message. The designated electronic table card will send a reply message from the designated participant to the server, which will then send the reply message to the second client. The second client can then receive the reply message from the server. Of course, the designated participant may not have noticed the target message. If the server does not receive a reply message from the designated electronic table card within a preset time period, it will determine that the designated participant did not see the target message in time. The server will then send a control instruction to the designated electronic table card. The designated electronic table card will then control the indicator light on the designated electronic table card to illuminate according to the control instruction sent by the server. The designated electronic table card can be any one or more electronic table cards used in the meeting.

[0205] During a meeting, the server identifies at least one pending task and the corresponding executor information for each task's designated executor. This executor information includes information about at least one attendee. The server then determines the electronic table sign associated with the attendee information in the executor information and sends the pending task to the electronic table sign associated with the electronic table sign. The electronic table sign receives the pending task sent by the server and displays it.

[0206] Alternatively, during or after the meeting, participants or other staff members log in to the meeting management page through their respective third clients, enter the corresponding tasks to be executed on the meeting management page of the third client, and select the executor information corresponding to the task executors specified for each task to be executed. The third client will then send at least one task to be executed for the meeting document and the executor information corresponding to the task executors specified for each task to be executed to the server; the server determines the corresponding task executor based on the executor information sent by the third client, and then sends the assigned task to be executed to the fourth client corresponding to the task executor, and the fourth client receives the task to be executed sent by the server.

[0207] The task executor processes the task to be executed and inputs the execution progress of the task to be executed on the conference management page, and the fourth client sends the task progress of the task to be executed to the server.

[0208] In an embodiment of the present application, the participant information is bound to the electronic table card identifier in advance, and the electronic table card corresponding to the electronic table card identifier is also in one-to-one correspondence with the microphone. During the meeting, the target electronic table card identifier of the target electronic table card corresponding to the target microphone is determined according to the target microphone that sends the voice message, and then the target participant information of the target participant who sent the voice message is determined. Finally, based on the target participant information and the voice information, a conference document is directly generated without the need for manual sorting by the staff, saving the staff's working time, improving the efficiency of sorting the conference documents, and avoiding the phenomenon of incomplete records of the meeting content; and the target participant corresponding to each voice message can be identified, and the target participant information corresponding to each voice message is automatically marked in the conference document, avoiding the lack of clarity of the target participant corresponding to each voice message when viewing the conference document later, making the generated conference document clearer and more understandable.

[0209] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0210] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0211] The various component embodiments of the present application can be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. It will be appreciated by those skilled in the art that a microprocessor or a digital signal processor (DSP) can be used in practice to implement some or all of the functions of some or all of the components in the server according to an embodiment of the present application. The application can also be implemented as a device or apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0212] For example, Figure 6 A server is shown that can implement the method according to the present application. The server conventionally includes a processor 610 and a computer program product or computer-readable medium in the form of a memory 620. The memory 620 can be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read-only memory), an EPROM, a hard disk or a ROM. The memory 620 has a storage space 630 for program code 631 for executing any method step in the above method. For example, the storage space 630 for program code can include individual program codes 631 for implementing various steps in the above method respectively. These program codes can be read from or written to one or more computer program products. These computer program products include program code carriers such as a hard disk, a compact disk (CD), a memory card or a floppy disk. Such a computer program product is typically as described in reference to Figure 7 The portable or fixed storage unit. The storage unit may have Figure 6 The memory 620 in the server is similarly arranged as a storage segment, storage space, etc. The program code can be compressed, for example, in an appropriate form. Typically, the storage unit includes computer-readable code 631', i.e., code that can be read by a processor such as 610, which, when executed by the server, causes the server to perform the steps of the method described above.

[0213] References herein to "one embodiment," "an embodiment," or "one or more embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Furthermore, please note that instances of the phrase "in one embodiment" do not necessarily all refer to the same embodiment.

[0214] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of this description.

[0215] In the claims, any reference signs placed between brackets shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in the claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present application may be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third etc. does not indicate any order. These words may be interpreted as names.

[0216] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A conference management method, characterized in that: Applied to a server, the method includes: Receiving information of multiple participants sent by the first client; Binding each participant's information to a corresponding electronic table card identifier, wherein each electronic table card identifier corresponds to a microphone in a one-to-one correspondence; receiving voice information collected by at least one target microphone; According to the target electronic table card identifier of the target electronic table card corresponding to the target microphone, determining the target participant information bound to the target electronic table card identifier; Generate a conference document based on the voice information and the target participant information; Each of the microphones has a unique microphone identifier; and the steps of achieving a one-to-one correspondence between the electronic table card corresponding to each of the electronic table card identifiers and the microphones include: Each electronic table card identifier is pre-bound to the corresponding microphone identifier.

2. The method according to claim 1, characterized in that The step of generating a conference document based on the voice information and the target participant information includes: Converting the voice information to generate text information; A conference document is generated according to the target participant information and the text information.

3. The method according to claim 1, characterized in that Before the step of receiving voice information collected by at least one target microphone, the method further includes: Receiving participant change information sent by the first client; the participant change information includes a target input box identifier and the changed participant information input in the target input box corresponding to the target input box identifier; The participant information to be changed pre-entered in the target input box corresponding to the target input box identifier is changed to the changed participant information, and the changed participant information is bound to the electronic table card identifier corresponding to the participant information to be changed.

4. The method according to claim 1, wherein After the step of binding each participant's information with the corresponding electronic table card identifier, the method further includes: During the meeting, receiving a target message and designated participant information corresponding to the target message sent by a second client; Determine the designated electronic table sign identifier that is bound to the designated participant information; The target message is sent to the designated electronic table card corresponding to the designated electronic table card identifier.

5. The method according to claim 4, characterized in that After the step of sending the target message to the designated electronic table card corresponding to the designated electronic table card identifier, the method further includes: Receiving a receipt message sent by the designated electronic table card; Send the receipt message to the second client.

6. The method according to claim 4, characterized in that After the step of sending the target message to the designated electronic table card corresponding to the designated electronic table card identifier, the method further includes: When no receipt message is received from the designated electronic table card within a preset time period, a control instruction is sent to the designated electronic table card to control the indicator light on the designated electronic table card to emit light.

7. The method according to claim 1, characterized in that After the step of generating a conference document according to the voice information and the target participant information, the method further includes: For the conference document, determining at least one task to be executed and executor information corresponding to a task executor designated for each task to be executed; Send the task to be executed according to the executor information.

8. The method according to claim 7, characterized in that The step of determining, for the conference document, at least one task to be performed and executor information corresponding to a task executor designated for each task to be performed includes: During a meeting, for the meeting document, determining at least one task to be executed and executor information corresponding to a task executor designated for each task to be executed; the executor information includes at least one participant information; The step of sending the task to be executed according to the executor information includes: The task to be executed is sent to the electronic table card corresponding to the participant information in the executor information.

9. The method according to claim 7, characterized in that The step of determining, for the conference document, at least one task to be performed and executor information corresponding to a task executor designated for each task to be performed includes: receiving at least one to-be-executed task for the conference document and executor information corresponding to the task executors designated for each of the to-be-executed tasks, sent by a third client; or, At least one to-be-executed task and executor information of task executors corresponding to each of the to-be-executed tasks are extracted from the conference document.

10. The method according to claim 7, characterized in that The step of sending the task to be executed according to the executor information includes: Sending the task to be executed to a fourth client corresponding to the task executor according to the executor information; After the step of sending the task to be executed to the fourth client corresponding to the task executor according to the executor information, the method further includes: receiving a task progress for the to-be-executed task sent by each of the fourth clients, wherein the task progress includes a task status; When the task statuses of all the tasks to be executed are in the completed state, the task execution status of the conference document is changed to the completed state.

11. The method according to claim 1, wherein After the step of generating a conference document according to the voice information and the target participant information, the method further includes: Extracting associated user information corresponding to associated users associated with the current meeting based on the meeting document; the associated user information includes participant information and user information corresponding to the users involved in the current meeting; The conference document is sent according to the associated user information.

12. A server, characterized in that: include: A participant information receiving module is configured to receive a plurality of participant information sent by the first client; An information binding module is configured to bind each participant's information to a corresponding electronic table card identifier, wherein the electronic table card corresponding to each electronic table card identifier also corresponds one-to-one with a microphone; a voice information receiving module, configured to receive voice information collected by at least one target microphone; A target participant information determination module is configured to determine the target participant information bound to the target electronic table card identifier according to the target electronic table card identifier of the target electronic table card corresponding to the target microphone; A conference document generation module is configured to generate a conference document based on the voice information and the target participant information; Each of the microphones has a unique microphone identifier; the information binding module is further configured to pre-bind each of the electronic table card identifiers with the corresponding microphone identifier.

13. A server, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the conference management method according to any one of claims 1 to 11 when executed by the processor.

14. A computer-readable medium, characterized in that The computer readable medium stores a computer program, and when the computer program is executed by a processor, the steps of the conference management method according to any one of claims 1 to 11 are implemented.

15. A conference management system, characterized in that: comprising an electronic table card, a microphone, a first client, and a server as claimed in claim 12; Wherein, the electronic table card is configured to display the participant information bound to the electronic table card identifier corresponding to the electronic table card; The microphone is configured to collect voice information emitted by the target participant corresponding to the target participant information; The first client is configured to send information of multiple participants to the server; Each of the microphones has a unique microphone identifier; and each of the electronic table card identifiers is pre-bound to the corresponding microphone identifier.

16. The system according to claim 15, wherein: The conference management system further includes a second client, a third client and a fourth client; The second client is configured to send a target message and information of designated participants corresponding to the target message to the server, and receive a receipt message sent by the server; The third client is configured to send at least one to-be-executed task for the conference document and executor information corresponding to the task executor designated for each of the to-be-executed tasks to the server; The fourth client is configured to receive the to-be-executed task sent by the server, and send the task progress of the to-be-executed task to the server; The first client is further configured to send participant change information to the server; The electronic table sign is further configured to display the target message and tasks to be performed sent by the server; and to send a receipt message to the server, and / or to control the indicator light on the electronic table sign to illuminate according to the control instructions sent by the server.

Images