Conference management method, conference management equipment and system

Abstract

A meeting management method, applied to a meeting management device, includes: in response to a meeting creation operation, creating a meeting and establishing a temporary folder for the meeting; and storing the files involved in the meeting in the temporary folder.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to, but are not limited to, the field of information processing technology, and in particular to a conference management method, conference management device, and system. Background Art

[0002] People usually reach a consensus on work through meetings to improve the efficiency of collaborative work. In meeting scenarios, users often use operations such as: file display, meeting file sharing, etc. Summary of the invention

[0003] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0004] The embodiments of the present disclosure provide a conference management method, conference management device, and system.

[0005] On the one hand, an embodiment of the present disclosure provides a conference management method, which is applied to a conference management device, including: creating a conference in response to a conference creation operation, and establishing a temporary folder for the conference; storing files involved in the conference in the temporary folder.

[0006] In some exemplary embodiments, storing the files involved in the meeting in the temporary folder includes at least one of the following: storing a first file generated by the meeting management device during the meeting in the temporary folder; storing a second file received by the meeting management device during the meeting in the temporary folder.

[0007] In some exemplary embodiments, the first file includes at least one of the following: a screenshot file, a whiteboard writing file.

[0008] In some exemplary embodiments, the above-mentioned conference management method further includes: after the end of the conference, in response to a conference deletion operation, deleting the temporary folder; or, when the duration of the end of the conference is greater than or equal to a set duration, deleting the temporary folder.

[0009] In some exemplary embodiments, the conference management method further includes: during the duration of the conference, in response to a file sharing operation, sending address information of the conference file selected by the file sharing operation to all conference participants via a server.

[0010] In some exemplary embodiments, the conference management method further includes: after the conference is created, sending conference creation information to a server, and receiving and displaying a conference QR code generated by the server according to the conference creation information.

[0011] In some exemplary embodiments, the conference creation information includes: conference name, conference start time, and conference end time.

[0012] In some exemplary embodiments, the conference management device is an all-in-one device running an Android system program.

[0013] On the other hand, an embodiment of the present disclosure provides a conference management device, comprising: a display panel, an input device, a processor, and a memory storing a conference management program and a system management program. The display panel is connected to the processor and is suitable for providing a display interface; the input device is connected to the processor and is suitable for detecting operations on the conference management device. The conference management program and the system management program are configured to be executed by the processor to perform the following steps: create a conference in response to a conference creation operation; establish a temporary folder for the conference, and store files related to the conference in the temporary folder.

[0014] In some exemplary embodiments, the processor executes at least one of the following when running the system management program: storing a first file generated during the duration of the meeting in the temporary folder; storing a second file received during the duration of the meeting in the temporary folder.

[0015] In some exemplary embodiments, the first file includes at least one of the following: a screenshot file, a whiteboard writing file.

[0016] In some exemplary embodiments, the processor further executes one of the following when running the system management program: after the meeting ends, in response to a meeting file deletion operation, deleting the temporary folder; when the duration at the end of the meeting is greater than or equal to a set duration, deleting the temporary folder.

[0017] In some exemplary embodiments, the processor further executes the following steps when running the conference management program: during the duration of the conference, in response to a file sharing operation, sending address information of the conference file selected by the file sharing operation to all conference participants via the server.

[0018] In some exemplary embodiments, the processor further executes the following steps when running the conference management program: after creating a conference, sending conference creation information to a server, and receiving and displaying a conference QR code generated by the server according to the conference creation information.

[0019] In some exemplary embodiments, the conference management device is a touch-screen all-in-one computer.

[0020] On the other hand, an embodiment of the present disclosure provides a conference management system, comprising: a conference management device, a server, and at least one mobile terminal. The conference management device is configured to create a conference in response to a conference creation operation, establish a temporary folder for the conference, and store files related to the conference in the temporary folder. The mobile terminal is configured to interact with the conference management device through the server.

[0021] In some exemplary embodiments, the conference management device is further configured to send conference creation information to the server after the conference is created. The server is configured to generate a conference QR code according to the conference creation information. The mobile terminal is configured to join the conference by scanning the conference QR code.

[0022] In some exemplary embodiments, the server is configured to receive a second file transmitted by the mobile terminal and transmit the second file to the conference management device, and is further configured to send address information of the conference file shared by the conference management device to the mobile terminal.

[0023] In some exemplary embodiments, the server is further configured to manage a conference group, the conference group including user information associated with the same conference identifier. The server is further configured to delete the conference group when the duration of the conference is greater than or equal to a set duration.

[0024] On the other hand, an embodiment of the present disclosure further provides a non-transitory computer-readable storage medium storing a computer program, which implements the steps of the conference management method described above when executed.

[0025] Other aspects will be apparent upon reading and understanding the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings are used to provide a further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure. The shape and size of one or more components in the accompanying drawings do not reflect the actual proportions and are only intended to illustrate the contents of the present disclosure.

[0027] Figure 1 A flowchart of a conference management method according to at least one embodiment of the present disclosure;

[0028] Figure 2 A schematic diagram of a conference management device according to at least one embodiment of the present disclosure;

[0029] Figure 3 A working diagram of a conference management device according to at least one embodiment of the present disclosure;

[0030] Figure 4 A schematic diagram of a conference management system according to at least one embodiment of the present disclosure;

[0031] Figure 5 The diagram is an interactive diagram of a conference management system according to at least one embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The embodiments of the present disclosure will be described in detail below in conjunction with the accompanying drawings. The embodiments can be implemented in a plurality of different forms. A person skilled in the art can easily understand the fact that the method and content can be transformed into one or more forms without departing from the purpose and scope of the present disclosure. Therefore, the present disclosure should not be interpreted as being limited to the contents described in the following embodiments. In the absence of conflict, the embodiments in the present disclosure and the features in the embodiments can be combined with each other arbitrarily.

[0033] In the drawings, the size of one or more components, the thickness of a layer, or an area is sometimes exaggerated for the sake of clarity. Therefore, one embodiment of the present disclosure is not necessarily limited to the size, and the shapes and sizes of the components in the drawings do not reflect the true proportions. In addition, the drawings schematically show ideal examples, and one embodiment of the present disclosure is not limited to the shapes or values ​​shown in the drawings.

[0034] The ordinal numbers such as "first", "second", and "third" in the present disclosure are provided to avoid confusion of constituent elements, and are not intended to limit the quantity. The "plurality" in the present disclosure means a quantity of two or more than two.

[0035] In the present disclosure, for the sake of convenience, the words and phrases indicating the orientation or positional relationship, such as "middle", "upper", "lower", "front", "back", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., are used to illustrate the positional relationship of the constituent elements with reference to the drawings. This is only for the convenience of describing the present specification and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operate in a specific orientation, and therefore cannot be understood as a limitation of the present disclosure. The positional relationship of the constituent elements is appropriately changed according to the direction in which the constituent elements are described. Therefore, it is not limited to the words and phrases described in the specification, and can be appropriately replaced according to the situation.

[0036] In the present disclosure, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection, or an electrical connection; it can be a direct connection, or an indirect connection through an intermediate, or the internal communication of two elements. For ordinary technicians in this field, the meanings of the above terms in the present disclosure can be understood according to the circumstances.

[0037] Taking the conference scenario using an all-in-one machine as an example, the files generated during the meeting will be stored in different paths, which is not convenient for use and management. For example, when a file is uploaded to a conference application, unless the user manually modifies it, the uploaded file will be stored in the default path of this conference application. Most users who temporarily use an all-in-one machine for a meeting will choose the default path to store files. However, taking the all-in-one machine running the Android system as an example, the screenshot files generated during the meeting will be stored in the screenshot path of the Android system by default, and the content written on the conference whiteboard will be stored in the whiteboard software directory. It can be seen that when users want to download, share or clean up these files, they need to access multiple folders, which is not convenient for use and management, and there will be omissions and inefficiencies in the file sharing and cleaning process.

[0038] At least one embodiment of the present disclosure provides a conference management method, conference management device and system, which can improve the inconvenience caused by the scattered storage of files generated in the conference in different paths by uniformly storing and managing the files generated in the conference process.

[0039] At least one embodiment of the present disclosure provides a conference management method, which is applied to a conference management device. Figure 1 FIG. 1 is a flow chart of a conference management method according to at least one embodiment of the present disclosure. Figure 1 As shown, the conference management method provided in this embodiment includes the following steps:

[0040] Step 101: In response to a conference creation operation, a conference is created and a temporary folder for the conference is established;

[0041] Step 102: Store the files involved in the meeting in a temporary folder.

[0042] The conference management method provided in this embodiment can achieve unified storage of conference files by creating a corresponding temporary folder for the conference on the conference management device and storing all files related to the conference in the temporary folder, thereby facilitating the use and management of conference files, thereby improving the use and management efficiency of conference files.

[0043] In some exemplary embodiments, the conference management device may be an all-in-one machine running an Android system program. The conference management device may be installed with a conference management program. In some examples, the conference initiator or conference organizer may open the conference management program on the conference management device, create a conference through the conference management program, and the Android system program may create a temporary folder locally for the created conference, so that in the subsequent conference process, all files involved in the conference are stored in the temporary folder. However, this embodiment is not limited to this. For example, the all-in-one machine may also run other system programs.

[0044] In some exemplary implementations, the conference management device may be applied to an offline conference scenario, or may be applied to an online conference scenario. However, this embodiment is not limited to this.

[0045] In some exemplary embodiments, the conference management method of this embodiment may further include: after creating a conference, sending conference creation information to a server, receiving and displaying a conference QR code generated by the server according to the conference creation information. In some examples, the conference creation information may include: conference name, conference start time, and conference end time. However, this embodiment is not limited to this. For example, the conference creation information may only include: conference name and conference start time, or conference start time and conference end time. In some examples, the conference start time may be a time point, or a time range; the conference end time may be a time point, or a time range.

[0046] In some examples, participants can enter the meeting by scanning the conference QR code through a conference application (APP) installed on a mobile terminal or a WeChat applet. After receiving the conference creation information sent by the conference management device, the server can generate a conference identification (ID). After the participant enters the meeting by scanning the conference QR code using the mobile terminal, the server can establish a conference group and save the conference ID and the user information of the participant entering the meeting (for example, the user information registered by the participant in the conference APP).

[0047] In some examples, the conference management device creates an offline conference, and after the participants enter the conference using a mobile terminal, they can transfer files to the conference management device through the server and obtain the file download address information pushed by the conference management device. In other examples, the conference management device creates an online conference, and after the participants enter the conference using a mobile terminal, they can interact with the conference organizer who created the conference using the conference management device through the server, such as transmitting audio and video information. However, this embodiment is not limited to this.

[0048] In some exemplary embodiments, step 102 may include at least one of the following: storing a first file generated by a conference management device during the duration of the meeting in a temporary folder; storing a second file received by the conference management device during the duration of the meeting in a temporary folder. In some examples, the files involved in the meeting may include: a first file generated during the meeting and a second file received during the meeting. The first file may, for example, include at least one of the following: a screenshot file, a whiteboard writing file. The second file may be a file uploaded to the conference management device by a participant via a mobile terminal. However, this embodiment is not limited to this. In this example, regardless of the type of files generated or received during the meeting, they are all stored in a temporary folder corresponding to the meeting to achieve unified storage of meeting files.

[0049] In some exemplary embodiments, the conference management method provided in this embodiment may also include: after the end of the meeting, in response to the conference deletion operation, deleting the temporary folder of the meeting; or, when the length of the end of the meeting is greater than or equal to the set duration, deleting the temporary folder of the meeting. In some examples, after the end of the meeting, all files involved in the meeting can be cleared by manual operation of the user, that is, the temporary folder is deleted. In some examples, after the end of the meeting, if the user does not manually clear the files involved in the meeting, the conference management device can automatically delete the temporary folder to clear all files involved in the meeting after the end of the meeting reaches the set duration. In some examples, the set duration can be 12 hours, or 24 hours. However, this embodiment is not limited to this. In this example, by providing manual and automatic methods to clear the temporary folder, the conference files can be cleared in time, thereby meeting the confidentiality requirements of the conference files, and it can avoid occupying too much storage space of the conference management device to improve the operating efficiency of the conference management device.

[0050] In some exemplary embodiments, the server may delete the conference group corresponding to the conference when the end time of the conference reaches a set time. The conference group may include user information associated with the same conference identifier. For example, the conference group may include all user information that joins the conference through the conference QR code. In this example, the effective storage time of the conference group on the server may be roughly the same as the effective storage time of the temporary folder of the conference of the conference management device. This example can meet the confidentiality requirements of the meeting by clearing the conference group of the server in a timely manner, and protect user information to avoid leakage of user information.

[0051] In some exemplary embodiments, the conference management method of this embodiment may also include: during the duration of the conference, in response to the file sharing operation, the address information of the conference file selected by the file sharing operation is sent to all participating terminals through the server. In this example, the participating terminal can be a mobile terminal used by the participant (for example, a portable device such as a mobile phone or a tablet computer). In some examples, the file sharing operation may include a one-click sharing operation triggered by the user on the conference management device, that is, an operation of sharing all or part of the files in the temporary folder to all participants. In this example, since the files involved in the meeting are stored in a temporary folder, there is no need to access different paths to find the conference files to be shared, and fast sharing of conference files can be achieved. Moreover, the conference management device pushes the address information of the file to all participants through the server, and the conference management mechanism can be used in combination with the push message mechanism to quickly share the conference files with the participants.

[0052] Figure 2 A schematic diagram of a conference management device provided by at least one embodiment of the present disclosure. In some exemplary implementations, Figure 2 As shown, the conference management device of this embodiment includes: a display panel 203, an input device 204, a processor 201 and a memory 202. The display panel 203 is connected to the processor 201 and is suitable for providing a display interface; the input device 204 is connected to the processor 201 and is suitable for detecting operations on the conference management device. The memory 202 stores a conference management program and a system management program. The conference management program and the system management program are configured to be run by the processor 201 to perform the following steps: in response to a conference creation operation, create a conference; establish a temporary folder for the conference, and store the files involved in the conference in the temporary folder.

[0053] In some examples, such as Figure 2 As shown, the processor 201, the memory 202, the input device 204 and the display panel 203 may be connected via a bus. Figure 2 The structure of the conference management device shown in the figure does not constitute a limitation of the conference management device, and the conference management device may include more or less components than shown in the figure, or combine certain components, or provide different component arrangements.

[0054] In some examples, the processor 201 may include, but is not limited to, a processing device such as a microprocessor (MCU, Microcontroller Unit) or a programmable logic device (FPGA, Field Programmable Gate Array). The memory 202 may store software programs and modules of application software, and the processor 201 executes multiple functional applications and data processing by running the software programs and modules stored in the memory 202, such as implementing the conference management method provided in the present embodiment. The memory 202 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 202 may include a memory remotely arranged relative to the processor 201, and these remote memories may be connected to the conference management device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0055] In some examples, the input device 204 may be suitable for receiving input information. Exemplarily, the input device 204 may include a touch panel (or referred to as a touch screen) and other input devices (e.g., a mouse, a keyboard, a joystick, etc.). The display panel 203 may be suitable for displaying information input by a user or information provided to a user. The display panel 203 is, for example, a liquid crystal display, an organic light emitting diode display panel, etc. Exemplarily, the touch panel may be covered on the display panel, and when the touch panel detects a touch operation on or near it, it is transmitted to the processor 201 to determine the type of the touch event, and then the processor 201 provides corresponding visual output on the display panel according to the type of the touch event. Exemplarily, the touch panel and the display panel may be used as two independent components to implement the input and output functions of the terminal device, or the touch panel and the display panel may be integrated together to implement the input and output functions. However, this embodiment is not limited to this.

[0056] In some exemplary embodiments, the conference management device is a touch integrated device. The touch panel and the display panel can be integrated together to realize input and output functions. However, this embodiment is not limited to this.

[0057] In some exemplary implementations, the system management program may be an Android system program. However, this embodiment is not limited to this.

[0058] In some exemplary embodiments, the processor 201 executes at least one of the following when running the system management program: storing a first file generated during the duration of the conference to the temporary folder; storing a second file received during the duration of the conference to the temporary folder. For example, the first file may include at least one of the following: a screenshot file, a whiteboard writing file.

[0059] In some exemplary embodiments, the processor 201 also executes one of the following when running the system management program: after the meeting ends, in response to a meeting deletion operation, deleting the temporary folder; when the meeting ends and the duration is greater than or equal to a set duration, deleting the temporary folder.

[0060] In some exemplary embodiments, the processor 201 further executes the following steps when running the conference management program: during the duration of the conference, in response to the file sharing operation, the address information of the conference file selected by the file sharing operation is sent to all conference participants via the server.

[0061] In some exemplary embodiments, the processor 201 further executes the following steps when running the conference management program: after creating a conference, sending conference creation information to the server, and receiving and displaying a conference QR code generated by the server according to the conference creation information.

[0062] Figure 3 FIG. 1 is a schematic diagram of the working of a conference management device according to at least one embodiment of the present disclosure. Figure 3 As shown, the conference management device includes the following working processes.

[0063] Step 301: The conference management program creates a conference in response to a conference creation operation.

[0064] In some examples, the conference management device has a display panel and an input device (e.g., a touch panel), and the user can operate the content displayed on the display panel through the input device. For example, the user opens the conference management program icon in the display interface provided by the display panel, then selects the conference creation button and fills in the conference creation information (e.g., including the conference name, conference start time, and conference end time) in the displayed dialog box. In some examples, the meeting start time may be a required item, and the rest of the content may be optional. The conference management program may send the conference creation information to the system management program and the server.

[0065] Step 302: The system management program creates a temporary folder for the meeting.

[0066] In some examples, after receiving the meeting creation information, the system management program creates a corresponding temporary folder for the meeting. The system management program can use the meeting creation information (such as at least one of the meeting name and the meeting start time) to name the temporary folder to establish a corresponding relationship between the meeting and the temporary folder. All subsequent files of the meeting are set to be saved in the temporary folder. In some examples, the meeting creation information includes the meeting end time, and the system management program can determine the clearing time of the temporary folder based on the meeting end time. In other examples, the meeting creation information includes the meeting start time but does not include the meeting end time, and the system management program can set the clearing time of the temporary folder based on the meeting start time. For example, the automatic clearing time of the temporary folder is obtained by adding the meeting start time to the set duration. However, this embodiment is not limited to this.

[0067] Step 303: Display the conference QR code on the display interface.

[0068] In some examples, the conference management program sends the conference creation information to the server, and the server generates a conference identifier based on the conference creation information, and generates a conference QR code based on the conference identifier and the conference creation information. The server sends the generated conference QR code to the conference management device, and the conference management device displays the conference QR code on the display interface. In some examples, when the conference management device is used in an offline conference scenario, participants can join the conference group by scanning the conference QR code displayed by the conference management device, so as to subsequently realize file transfer between the conference management device and the conference management device. The conference group can be managed by the server. The conference group can include user information associated with the same conference ID. That is, users joining the same conference form a conference group.

[0069] In some exemplary embodiments, after the meeting starts, the meeting management device may perform the following operations.

[0070] Step 304: The conference management program receives the second file transmitted by the server, and transmits the second file to the system management program.

[0071] Step 305: The system management program saves the second file to a temporary folder.

[0072] In some examples, the second file is transmitted to the server by the participant who joins the meeting through the mobile terminal. After receiving the second file, the server transmits it to the conference management program. The conference management program transmits the second file to the system management program to be saved in a temporary folder. For example, the second file can be a text file, a picture or a video file. However, this embodiment does not limit the type of the second file. In some examples, the size of the second file can be limited. For example, the mobile terminal of the participant can only upload the second file whose file size is less than a threshold value to avoid taking up too much storage space in the conference management device. However, this embodiment does not limit this.

[0073] Step 306: The conference management program generates a first file and transmits the first file to the system management program.

[0074] Step 307: The system management program saves the first file to a temporary folder.

[0075] In some examples, during a meeting, a user can perform screenshot and whiteboard writing operations on the display interface of the conference management device. The first file may include: a screenshot file, a whiteboard writing file. Compared to some implementations, the screenshot file is saved in the screenshot path of the Android system and the whiteboard writing file is saved in the whiteboard software directory. In this example, the screenshot file and the whiteboard writing file are saved in the same temporary folder. The user only needs to open the temporary folder to find all the files related to the meeting, which can improve the efficiency of meeting file management.

[0076] Step 308: The conference management program can share conference files with the participants.

[0077] In some examples, during a meeting, a user can trigger a file sharing operation by clicking a one-touch sharing button on the display interface to share the meeting file saved in the temporary folder with all participants who have joined the meeting group. For example, the meeting management program can send the address information of the meeting file to be shared to the server, and the server sends it to the mobile terminals of the participants who have joined the meeting group via a push message.

[0078] In this example, the uploading and saving of the second file, the generation and saving of the first file, and the sharing of the conference file are all optional steps. There is no necessary order for the execution of the uploading and saving of the second file, the generation and saving of the first file, and the sharing of the conference file. This embodiment does not limit this.

[0079] In some exemplary embodiments, after the meeting ends, the meeting management device may manually or automatically clear the temporary folder of the meeting to meet the confidentiality requirements of the meeting and avoid filling up the storage space of the meeting management device.

[0080] Step 309: In response to the conference file deletion operation, the system management program deletes the temporary folder.

[0081] In some examples, after the meeting ends, the user can select a one-click clear button on the display interface to trigger the system management program to delete the temporary folder.

[0082] Step 310: The system management program automatically deletes the temporary folder.

[0083] In some examples, after the meeting ends, the user does not perform the meeting file deletion operation. The system management program can determine whether the meeting end time has exceeded (i.e., whether the meeting end time is greater than the set time) according to the set time. If it has exceeded, the system management program can automatically delete the temporary folder to release storage space.

[0084] In this example, step 309 and step 310 may be selected as one of the steps. After step 309 is executed, step 310 is no longer executed. When step 309 is not executed, step 310 is executed.

[0085] The conference management device provided in this exemplary embodiment can improve the management efficiency of conference files by uniformly storing and managing files generated during the conference.

[0086] Figure 4 FIG. 1 is a schematic diagram of a conference management system according to at least one embodiment of the present disclosure. Figure 4 As shown, the conference management system provided by this embodiment includes: a conference management device 401, a server 402, and at least one mobile terminal (for example, mobile terminals 403a to 403c). The conference management device 401 is configured to create a conference in response to a conference creation operation, establish a temporary folder for the conference, and store files related to the conference in the temporary folder. The mobile terminal is configured to interact with the conference management device 401 through the server 402.

[0087] In some exemplary embodiments, the conference management device 401 is configured to send conference creation information to the server 402 after the conference is created. The server 402 is configured to generate a conference QR code according to the conference creation information. The mobile terminal is configured to join the conference by scanning the conference QR code. In some examples, the mobile terminal may run a conference application or a WeChat applet. The mobile terminal may use the conference application or WeChat applet to join the conference group by scanning the conference QR code to interact with the conference management device through the server.

[0088] In some exemplary embodiments, the server is configured to receive the second file transmitted by the mobile terminal and transmit the second file to the conference management device, and is further configured to send address information of the conference file shared by the conference management device to the mobile terminal.

[0089] In some exemplary embodiments, the server is further configured to manage a conference group, the conference group including user information associated with the same conference identifier. The server is further configured to delete the conference group when the duration of the conference is greater than or equal to a set duration.

[0090] Figure 5 FIG. 1 is a schematic diagram of an interactive process of a conference management system according to at least one embodiment of the present disclosure. Figure 5 As shown, the conference management system may include: a conference management device, a server, and a mobile terminal. In this example, a mobile terminal is used as an example for illustration. The conference management device may be a touch-screen all-in-one machine running an Android system program. The mobile terminal may be installed with a conference application or a WeChat applet. The mobile terminal may be, for example, a portable device such as a mobile phone or a tablet computer.

[0091] In some examples, the application of the conference management system to offline conferences is used as an example. The conference organizer can be responsible for operating the conference management device and managing the conference process. Other participants can operate the conference management device to perform on-screen operations, such as taking screenshots or writing on a whiteboard.

[0092] In some examples, such as Figure 5 As shown, the interaction flow of the conference management system may include the following processes.

[0093] Step 501: The conference management device creates a conference and establishes a temporary folder in response to the conference creation operation. The process of the conference management device creating a conference and establishing a temporary folder can be referred to in Figure 3 As shown, I will not repeat it here.

[0094] Step 502: The conference management device sends the conference creation information to the server, and the server generates a conference ID and generates a conference QR code based on the conference ID and the conference creation information. The server sends the generated conference QR code to the conference management device.

[0095] Step 503: The conference management device displays the conference QR code on the display interface.

[0096] Step 504: The participant uses a mobile terminal to scan the conference QR code to sign in. In some examples, the participant can use a mobile phone number and a verification code to log in to the conference application of the mobile terminal, or authorize to log in to the WeChat applet through a WeChat account. After the participant uses a mobile terminal to scan the conference QR code, the user information is sent to the server. For example, the user information may include: the user information registered by the participant in the conference application. However, this embodiment is not limited to this.

[0097] Step 505: After receiving the user information of the participant, the server adds the participant to a conference group so that the participant can use the file transfer function. The conference group may include user information associated with the same conference ID. That is, users who join the same conference form a conference group.

[0098] Through the above steps, the meeting organizer completes the meeting creation, and the participants join the meeting and can use the file transfer function.

[0099] In some exemplary embodiments, during the duration of the conference, the conference management device stores all files involved in the conference in a temporary folder, and interacts with the mobile terminals of the participants through the server.

[0100] Step 506: The conference management device saves the first file generated during the conference to a temporary folder. The first file includes, for example, a screenshot file and a whiteboard writing file.

[0101] Step 507: After the participant's mobile terminal scans the conference QR code to join the conference group, it can upload the second file. Step 508: The server receives the second file uploaded by the mobile terminal. Step 509: The conference management device receives the second file transmitted by the server and saves the second file to a temporary folder. This embodiment does not limit the type of the second file transmitted by the mobile terminal.

[0102] Step 510: The conference management device shares the conference file with the participants. The conference management device sends the address information of the conference file to be shared to the server. Step 511: After receiving the address information, the server sends a push message carrying the address information of the conference file to the user information in the conference group. Step 512: The mobile terminal receives the push message. The user can view the conference file shared by the conference organizer according to the address information carried in the push message.

[0103] In some exemplary implementations, after the conference ends, the conference management device may execute step 513 to delete the temporary folder. The conference management device may delete the temporary folder according to a user operation, or may automatically delete the temporary folder.

[0104] For the description of the working process of the conference management device during the above interaction, please refer to Figure 3 The description of the embodiment shown is therefore not repeated here.

[0105] In this exemplary embodiment, the conference management device is responsible for the creation of conferences, establishment of temporary folders, storage of conference files, sharing of conference files, and clearing of conference files. The conference management device can connect the management mechanism of conferences and files to achieve integrated management of conferences and files. All files related to a conference are stored in the same temporary folder, which can facilitate user operations.

[0106] In this exemplary embodiment, the mobile terminal of the participant participates in the transmission of conference files through the conference application or WeChat applet. Among them, the conference application is relatively stable and can receive messages in time, while the WeChat applet does not need to install the application, can receive messages through WeChat, and can quickly share the received files with WeChat friends, which is conducive to improving the conference experience.

[0107] In this exemplary embodiment, the server can establish a connection between the conference management device and the mobile terminal of the participant to implement file transfer and conference management mechanism. Moreover, after the conference management device creates a meeting, the server will generate a conference ID so that the conference management device can generate a conference QR code. The server establishes a conference group for participants who are associated with the same conference ID by scanning the conference QR code. After the meeting ends or the meeting ends for a set period of time (for example, 12 hours), the server can delete the conference ID and conference group to ensure information security. In this example, the server does not need to operate and maintain user data. Once the meeting ends for a period of time exceeding the expiration date (for example, more than 12 hours), all information related to the meeting will be deleted, thereby ensuring the information security of the meeting files.

[0108] In addition, at least one embodiment of the present disclosure further provides a non-transitory computer-readable storage medium storing a computer program, which implements the steps of the above-mentioned conference management method when executed.

[0109] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules or units in the disclosed methods above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules or units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all components may be implemented as software executed by a processor, such as a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0110] The above shows and describes the basic principles, main features and advantages of the present disclosure. The present disclosure is not limited by the above embodiments. The above embodiments and descriptions are only for explaining the principles of the present disclosure. Without departing from the spirit and scope of the present disclosure, the present disclosure may have various changes and improvements, which all fall within the scope of the present disclosure to be protected.

Claims

1. A conference management method, applied to a conference management device, wherein the conference management device is an integrated machine that runs a conference management program and a system management program, wherein the system management program is an Android system program, and the conference management method comprises: In response to a conference creation operation, a conference is created, and a temporary folder of the conference is locally established, wherein the conference is created by the conference management program, and the temporary folder of the conference is established by the system management program; Storing the files involved in the conference in the temporary folder includes: storing the screenshot files generated by the screenshot operation performed on the conference management device during the duration of the conference and the whiteboard writing files generated by the whiteboard writing operation performed on the conference management device in the temporary folder; The second file received by the conference management device during the duration of the conference is stored in the temporary folder, and the second file is sent to the conference management device by the participating mobile terminal through the server.

2. The method according to claim 1, further comprising: After the meeting ends, in response to a meeting deletion operation, deleting the temporary folder; or, When the duration of the conference is greater than or equal to the set duration, the temporary folder is deleted.

3. The method according to claim 2, further comprising: During the duration of the conference, in response to a file sharing operation, the address information of the conference file selected by the file sharing operation is sent to all participating mobile terminals via the server.

4. The method according to claim 1, further comprising: After the meeting is created, the meeting creation information is sent to the server, and the meeting QR code generated by the server according to the meeting creation information is received and displayed.

5. The method according to claim 4, wherein: The conference creation information includes: conference name, conference start time, and conference end time.

6. A conference management device, comprising: A display panel, an input device, a processor, and a memory storing a conference management program and a system management program; The system management program is an Android system program; The display panel is connected to the processor and is suitable for providing a display interface; the input device is connected to the processor and is suitable for detecting the operation of the conference management device; the conference management program and the system management program are configured to be run by the processor to perform the following steps: In response to the conference creation operation, creating a conference; A temporary folder for the meeting is established locally, and files related to the meeting are stored in the temporary folder; storing the files related to the meeting in the temporary folder includes: storing a screenshot file generated by a screenshot operation performed on the meeting management device during the meeting and a whiteboard writing file generated by a whiteboard writing operation performed on the meeting management device in the temporary folder; storing a second file received by the meeting management device during the meeting in the temporary folder, wherein the second file is sent to the meeting management device by the participating mobile terminal through the server; The conference is created through the conference management program, and the temporary folder of the conference is established through the system management program.

7. The device according to claim 6, wherein: When the processor runs the system management program, it further performs one of the following: After the meeting ends, in response to a meeting file deletion operation, deleting the temporary folder; When the duration of the meeting is greater than or equal to the set duration, the temporary folder is deleted.

8. The device according to claim 7, wherein: When the processor runs the conference management program, the processor also performs the following steps: during the duration of the conference, in response to a file sharing operation, sending the address information of the conference file selected by the file sharing operation to all conference participants through the server.

9. The conference management device according to claim 8, wherein: When the processor runs the conference management program, the processor also performs the following steps: after creating a conference, sending conference creation information to a server, and receiving and displaying a conference QR code generated by the server according to the conference creation information.

10. The conference management device according to any one of claims 6 to 9, wherein: The conference management device is a touch-screen all-in-one machine.

11. A conference management system, comprising: Conference management equipment, a server and at least one mobile terminal; The conference management device is configured to create a conference in response to a conference creation operation, establish a temporary folder for the conference locally, and store files related to the conference in the temporary folder; storing the files related to the conference in the temporary folder includes: storing a screenshot file generated by a screenshot operation performed on the conference management device during the duration of the conference and a whiteboard writing file generated by a whiteboard writing operation performed on the conference management device in the temporary folder; and storing a second file received by the conference management device during the duration of the conference in the temporary folder; The conference management device is an integrated machine that runs a conference management program and a system management program, the system management program is an Android system program, the conference is created through the conference management program, and the temporary folder of the conference is established through the system management program; The mobile terminal is configured to interact with the conference management device through the server; The server is configured to receive a second file transmitted by the mobile terminal, and transmit the second file to the conference management device.

12. The system according to claim 11, wherein: The conference management device is further configured to send conference creation information to the server after creating the conference; The server is configured to generate a conference QR code according to the conference creation information; The mobile terminal is configured to join the conference by scanning the conference QR code.

13. The system according to claim 11, wherein: The server is also configured to send address information of the conference file shared by the conference management device to the mobile terminal.

14. A system according to any one of claims 11 to 13, wherein: The server is further configured to manage a conference group, the conference group including user information associated with the same conference identifier; The server is also configured to delete the conference group when the duration of the conference is greater than or equal to a set duration at the end of the conference.

15. A non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed, implements the steps of the conference management method according to any one of claims 1 to 5.

Images