CN116171572A

CN116171572A - Conference management method, conference management device and conference management system

Info

Publication number: CN116171572A
Application number: CN202180002666.9A
Authority: CN
Inventors: 陈铁砺; 杜子龙; 赵海霞; 杨明明; 李坤
Original assignee: BOE Technology Group Co Ltd
Current assignee: BOE Technology Group Co Ltd
Priority date: 2021-09-24
Filing date: 2021-09-24
Publication date: 2023-05-26
Also published as: WO2023044747A1

Abstract

A conference management method applied to conference management equipment, comprising: responding to a conference creation operation, creating a conference, and creating a temporary folder of the conference; and storing the files related to the meeting in the temporary folder.

Description

Conference management method, conference management device and conference management system

Technical Field

The embodiment of the disclosure relates to the technical field of information processing, and in particular relates to a conference management method, conference management equipment and a conference management system.

Background

People often gain working consensus through conferences to improve the efficiency of collaborative work. In a conference scenario, operations frequently used by users include: file presentation, conference file sharing, and the like.

Disclosure of Invention

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.

The embodiment of the disclosure provides a conference management method, conference management equipment and a conference management system.

In one aspect, an embodiment of the present disclosure provides a conference management method, applied to a conference management device, including: responding to a conference creation operation, creating a conference, and creating a temporary folder of the conference; and storing the files related to the meeting in the temporary folder.

In some exemplary embodiments, the storing the files related to the meeting in the temporary folder includes at least one of: storing a first file generated by the conference management device during the duration of the conference to the temporary folder; and storing a second file received by the conference management device during the duration of the conference to the temporary folder.

In some exemplary embodiments, the first file includes at least one of: the screen capture file and the whiteboard writing file.

In some exemplary embodiments, the conference management method further includes: after the conference is finished, deleting the temporary folder in response to a conference deleting operation; or deleting the temporary folder when the ending time of the conference is longer than or equal to the set time.

In some exemplary embodiments, the conference management method further includes: and in the duration of the conference, responding to the file sharing operation, and sending the address information of the conference file selected by the file sharing operation to all the participants through the server.

In some exemplary embodiments, the conference management method further includes: after creating the conference, the conference creation information is sent to a server, and the conference two-dimensional code generated by the server according to the conference creation information is received and displayed.

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

In some exemplary embodiments, the conference management device is an all-in-one machine running an android system program.

In another aspect, an embodiment of the present disclosure provides a conference management device, including: the system comprises 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 with the processor and is suitable for providing a display interface; the input means is connected to the processor and is adapted to detect operation at the conference management device. The conference manager and system manager are configured to be executed by the processor to perform the steps of: responding to the conference creation operation, and creating a conference; and establishing a temporary folder of the conference, and storing files related to the conference in the temporary folder.

In some exemplary embodiments, the processor, when executing the hypervisor, performs at least one of: storing a first file generated during the duration of the meeting to the temporary folder; and storing a second file received during the duration of the conference to the temporary folder.

In some exemplary embodiments, the processor, when running the hypervisor, further performs one of: after the conference is finished, deleting the temporary folder in response to a conference file deleting operation; and deleting the temporary folder when the length of the meeting is longer than or equal to the set length of time.

In some exemplary embodiments, the processor, when executing the conference management program, further performs the steps of: and in the duration of the conference, responding to the file sharing operation, and sending the address information of the conference file selected by the file sharing operation to all the participants through the server.

In some exemplary embodiments, the processor, when executing the conference management program, further performs the steps of: after creating the conference, the conference creation information is sent to a server, and the conference two-dimensional code generated by the server according to the conference creation information is received and displayed.

In some exemplary embodiments, the conference management device is a touch-sensitive all-in-one machine.

In another aspect, an embodiment of the present disclosure provides a conference management system, including: conference management device, server and at least one mobile terminal. The conference management device is configured to respond to a conference creation operation, create a conference, establish a temporary folder of 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.

In some exemplary embodiments, 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 two-dimensional code according to the conference creation information. The mobile terminal is configured to join the conference by scanning the conference two-dimensional code.

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

In some exemplary embodiments, the server is further configured to manage a conference group including user information associated with the same conference identification. The server is further configured to delete the conference group when the end time period of the conference is greater than or equal to a set time period.

In another aspect, the disclosed embodiments also provide a non-transitory computer-readable storage medium storing a computer program that, when executed, implements the steps of the conference management method as described above.

Other aspects will become apparent upon reading and understanding the accompanying drawings and detailed description.

Drawings

The accompanying drawings are included to provide a further understanding of the disclosed embodiments and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain, without limitation, the embodiments of the disclosure. The shape and size of one or more of the components in the drawings do not reflect true proportions, and are intended to illustrate the disclosure only.

FIG. 1 is a flow chart of a method of conference management in accordance with at least one embodiment of the present disclosure;

fig. 2 is a schematic diagram of a conference management device in accordance with at least one embodiment of the present disclosure;

fig. 3 is a schematic diagram illustrating the operation of a conference management device according to at least one embodiment of the present disclosure;

FIG. 4 is a schematic diagram of a conference management system in accordance with at least one embodiment of the present disclosure;

fig. 5 is an interaction diagram of a conference management system in accordance with at least one embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Embodiments may be implemented in a number of different forms. One of ordinary skill in the art will readily recognize the fact that the patterns and matters may be changed into one or more forms without departing from the spirit and scope of the present disclosure. Accordingly, the present disclosure should not be construed as being limited to the following description of the embodiments. Embodiments of the present disclosure and features of embodiments may be combined with each other arbitrarily without conflict.

In the drawings, the size of one or more constituent elements, thicknesses of layers or regions may be exaggerated for clarity. Accordingly, one aspect of the present disclosure is not necessarily limited to this dimension, and the shapes and sizes of the various components in the drawings do not reflect actual proportions. Further, the drawings schematically show ideal examples, and one mode of the present disclosure is not limited to the shapes or numerical values shown in the drawings, and the like.

The ordinal terms such as "first," "second," "third," and the like in the present disclosure are provided to avoid intermixing of constituent elements, and are not intended to be limiting in number. The term "plurality" in this disclosure means two or more than two numbers.

In the present disclosure, for convenience, terms such as "middle", "upper", "lower", "front", "rear", "vertical", "horizontal", "top", "bottom", "inner", "outer", and the like are used to describe positional relationships of the constituent elements with reference to the drawings, only for convenience in describing the present specification and simplifying the description, and do not indicate or imply that the apparatus or elements to be referred to must have a specific orientation, be constructed and operated in a specific orientation, and thus should not be construed as limiting 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, the present invention is not limited to the words described in the specification, and may be appropriately replaced according to circumstances.

In this disclosure, the terms "mounted," "connected," and "connected" are to be construed broadly, unless otherwise specifically indicated and defined. For example, it may be a fixed connection, a removable connection, or an integral connection; may be a mechanical connection, or an electrical connection; may be directly connected, or indirectly connected through intermediate members, or may be in communication with the interior of two elements. The meaning of the above terms in the present disclosure can be understood by one of ordinary skill in the art as appropriate.

Taking a conference scene using an all-in-one machine as an example, files generated in a conference can be stored in different paths in a scattered manner, so that the use and management are inconvenient. For example, a file is uploaded into a conferencing application, and unless manually modified by a user, the uploaded file is stored under the default path of the conferencing application. Most users who temporarily use the all-in-one session will choose to store the file in the default path. However, taking the android system running by the integrated machine as an example, the screen capture file generated in the conference process is stored under the screen path of the android system by default, and the writing content of the conference whiteboard is stored under the whiteboard software directory. Thus, when a user wants to download, share or clean the files, the user needs to access a plurality of folders, which is inconvenient to use and manage, and the problems of omission and inefficiency in the process of sharing and cleaning the files exist.

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

At least one embodiment of the present disclosure provides a conference management method applied to a conference management device. Fig. 1 is a flow chart of a conference management method in accordance with at least one embodiment of the present disclosure. As shown in fig. 1, the conference management method provided in this embodiment includes the following steps:

step 101, responding to a conference creation operation, creating a conference, and creating a temporary folder of the conference;

step 102, storing the files related to the conference in a temporary folder.

According to the conference management method, the corresponding temporary folder is created for the conference in the conference management device, and files related to the conference are stored in the temporary folder, so that unified storage of conference files can be realized, the use and management of the conference files are facilitated, and the use and management efficiency of the conference files can be improved.

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, a conference initiator or conference organizer may open a conference management program on a conference management device, create a conference through the conference management program, and create a temporary folder locally for the created conference by the android system program, so that files involved in the conference are all stored in the temporary folder during a subsequent conference. However, the present embodiment is not limited thereto. For example, an all-in-one machine may also run other system programs.

In some exemplary embodiments, the conference management device may be applied to an off-line conference scene or may be applied to an on-line conference scene. However, the present embodiment is not limited thereto.

In some exemplary embodiments, the conference management method of the present embodiment may further include: after creating the conference, the conference creation information is sent to the server, and the conference two-dimensional code generated by the server according to the conference creation information is received and displayed. In some examples, the meeting creation information may include: conference name, conference start time, conference end time. However, the present embodiment is not limited thereto. For example, the conference creation information may include only: conference name and conference start time, or conference start time and conference end time. In some examples, the meeting start time may be a point in time, or may be a range of times; the conference end time may be a point in time or may be a range of times.

In some examples, a participant may scan a conference two-dimensional code through a mobile terminal-installed conference Application (APP) or a WeChat applet to enter a conference. The server may generate a conference Identification (ID) after receiving the conference creation information transmitted by the conference management device. After a participant enters a meeting using a mobile terminal scanning a meeting two-dimensional code, the server may establish a meeting group, save the meeting ID and user information of the participant entering the meeting (e.g., user information of the participant registered at the meeting APP).

In some examples, the conference management device creates an offline conference, and after the participant enters the conference using the mobile terminal, the participant may transmit a file to the conference management device through the server and obtain file download address information pushed by the conference management device. In other examples, the conference management device creates an online conference, and after a participant enters the conference using the mobile terminal, the participant may interact with a conference organizer that creates the conference using the conference management device, such as transmitting audiovisual information, through the server. However, the present embodiment is not limited thereto.

In some exemplary embodiments, step 102 may include at least one of: storing a first file generated by the conference management device during the duration of the conference to a temporary folder; and storing the second file received by the conference management device of the persistent device of the conference in the temporary folder. In some examples, the files involved in the meeting may include: a first file generated during the conference and a second file received during the conference. The first file may comprise, for example, at least one of: the screen capture file and the whiteboard writing file. The second file may be a file uploaded by the participant to the conference management device via the mobile terminal. However, the present embodiment is not limited thereto. In this example, regardless of the type of file generated or received during the conference, the file is uniformly stored in the temporary folder corresponding to the conference, so as to realize uniform storage of the conference file.

In some exemplary embodiments, the conference management method provided in this embodiment may further include: after the conference is finished, deleting the temporary folder of the conference in response to a conference deleting operation; or deleting the temporary folder of the conference when the ending time of the conference is longer than or equal to the set time. In some examples, after the meeting is over, all files involved in the meeting may be purged, i.e., the temporary folder may be deleted, by manual operation by the user. In some examples, after the conference is ended, the user does not manually clear the files related to the conference, and after the conference end time reaches the set time, the conference management device may automatically delete the temporary folder to clear all files related to the conference. In some examples, the set duration may be 12 hours, or 24 hours. However, the present embodiment is not limited thereto. In the example, the temporary folder is cleared by providing a manual mode and an automatic mode, so that the conference file can be cleared timely, the confidentiality requirement of the conference file is met, and excessive storage space of the conference management equipment can be prevented from being occupied, so that the operation efficiency of the conference management equipment is improved.

In some exemplary embodiments, the server may delete the conference group corresponding to the conference when the ending time of the conference reaches the set time. The meeting group can include user information associated with the same meeting identification. For example, a conference group may include all user information joining a conference through a conference two-dimensional code. In this example, the effective storage time period of the conference group at the server may be approximately the same as the effective storage time period of the temporary folder of the conference management device. The conference group of the server is cleared timely, so that the security requirement of the conference can be met, the user information is protected, and leakage of the user information is avoided.

In some exemplary embodiments, the conference management method of the present embodiment may further include: and in the duration of the conference, responding to the file sharing operation, and sending the address information of the conference file selected by the file sharing operation to all the participants through the server. In this example, the participant may be a mobile terminal (e.g., a portable device such as a cell phone, tablet computer, etc.) used by the participant. In some examples, the file sharing operation may include a one-touch sharing operation triggered by the user at the conference management device, i.e., an operation of sharing all or part of the files within the temporary folder to all of the participants. In this example, since the files related to the conference are all stored in the temporary folder, it is not necessary to access different paths to search for the conference file to be shared, and rapid sharing of the conference file can be achieved. Moreover, the conference management device can adopt a conference management mechanism and combine a push message mechanism to quickly share the conference file to the participants by pushing the address information of the file to all the participants through the server.

Fig. 2 is a schematic diagram of a conference management device according to at least one embodiment of the present disclosure. In some exemplary embodiments, as shown in fig. 2, the conference management device of the present embodiment includes: a display panel 203, an input device 204, a processor 201, and a memory 202. The display panel 203 is connected with the processor 201 and is suitable for providing a display interface; an input device 204 is connected to the processor 201 and is adapted to detect operation at the conference management device. The memory 202 stores a conference management program and a system management program. The conference manager and the hypervisor are configured to be executed by the processor 201 to perform the steps of: responding to the conference creation operation, and creating a conference; and establishing a temporary folder of the conference, and storing files related to the conference in the temporary folder.

In some examples, as shown in fig. 2, the processor 201, the memory 202, the input device 204, and the display panel 203 may be connected by a bus. The configuration of the conference management device shown in fig. 2 does not constitute a limitation of the conference management device, and may include more or less components than illustrated, or combine certain components, or provide different arrangements of components.

In some examples, the processor 201 may include, but is not limited to, a microprocessor (MCU, microcontroller Unit), a programmable logic device (FPGA, field Programmable Gate Array), or the like. The memory 202 may store software programs and modules of application software, and the processor 201 executes various functional applications and data processing, such as implementing the conference management method provided in the present embodiment, by running the software programs and modules stored in the memory 202. Memory 202 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 202 may include memory remotely located with respect to processor 201, which may be connected to the conference management device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

In some examples, the input device 204 may be adapted to receive input information. By way of example, the input device 204 may include a touch panel (or referred to as a touch screen) and other input devices (e.g., a mouse, keyboard, joystick, etc.). The display panel 203 may be adapted to display information entered 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, or the like. For example, the touch panel may be overlaid on the display panel, and when the touch panel detects a touch operation thereon or thereabout, the touch panel is transmitted to the processor 201 to determine the type of touch event, and the processor 201 then provides a corresponding visual output on the display panel according to the type of touch event. For example, the touch panel and the display panel may be implemented as two separate components to implement input and output functions of the terminal device, or the touch panel and the display panel may be integrated together to implement input and output functions. However, the present embodiment is not limited thereto.

In some exemplary embodiments, the conference management device is a touch-enabled all-in-one machine. The touch panel and the display panel may be integrated together to realize an input-output function. However, the present embodiment is not limited thereto.

In some example embodiments, the hypervisor may be an android system program. However, the present embodiment is not limited thereto.

In some exemplary embodiments, the processor 201, when executing the hypervisor, performs at least one of the following: storing a first file generated during the duration of the meeting to the temporary folder; and 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 screen capture file and the whiteboard writing file.

In some exemplary embodiments, the processor 201, when running the hypervisor, also performs one of the following: after the conference is finished, deleting the temporary folder in response to a conference deleting operation; and deleting the temporary folder when the length of the meeting is longer than or equal to the set length of time at the end of the meeting.

In some exemplary embodiments, the processor 201, when running the conference management program, also performs the following steps: and in the duration of the conference, responding to the file sharing operation, and sending the address information of the conference file selected by the file sharing operation to all the participants through the server.

In some exemplary embodiments, the processor 201, when running the conference management program, also performs the following steps: after creating the conference, the conference creation information is sent to the server, and the conference two-dimensional code generated by the server according to the conference creation information is received and displayed.

Fig. 3 is a schematic operation diagram of a conference management device according to at least one embodiment of the present disclosure. In some exemplary embodiments, as shown in fig. 3, the conference management device includes the following working procedures.

Step 301, the conference management program responds to the conference creation operation to create a conference.

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

Step 302, the hypervisor establishes a temporary folder for the conference.

In some examples, after the hypervisor receives the meeting creation information, a corresponding temporary folder is established for the meeting. The hypervisor may name the temporary folder using meeting creation information (e.g., at least one of a meeting name and a meeting start time) to establish correspondence between the meeting and the temporary folder. All files of the subsequent meeting are set to be saved in the temporary folder. In some examples, the meeting creation information includes a meeting end time, and the hypervisor may determine a time of the clearing of the temporary folder based on the meeting end time. In other examples, the meeting creation information includes a meeting start time, but does not include a meeting end time, the hypervisor may set a time to clear the temporary folder based on the meeting start time, e.g., the time to automatically clear the temporary folder is derived from the meeting start time plus the set time period. However, the present embodiment is not limited thereto.

And 303, displaying the conference two-dimensional code on a display interface.

In some examples, the conference management program sends the conference creation information to a server, the server generates a conference identification from the conference creation information, and generates a conference two-dimensional code based on the conference identification and the conference creation information. The server sends the generated conference two-dimension code to conference management equipment, and the conference management equipment displays the conference two-dimension code on a display interface. In some examples, when the online meeting scene uses the meeting management device, the participant may join the meeting group by scanning the meeting two-dimensional code displayed by the meeting management device for subsequent file transfer between the meeting management device. The conference group may be managed by a server. The conference group may include user information associated with the same conference ID. That is, users joining the same meeting form a meeting group.

In some exemplary embodiments, after the conference starts, the conference management device may perform the following operations.

Step 304, the conference management program receives the second file transmitted by the server, and transmits the second file to the system management program.

Step 305, the hypervisor saves the second file to the temporary folder.

In some examples, the second file is transmitted by the participant joining the conference via the mobile terminal to the server, which receives the second file and transmits it to the conference management program, which transmits the second file to the hypervisor for saving in the temporary folder. For example, the second file may be a text file, a picture, or a video file. However, the present embodiment is not limited to the type of the second file. In some examples, the size of the second file may be limited. For example, the mobile terminal of the participant can only upload the second file with the file size smaller than the threshold value, so that excessive storage space is avoided being occupied in the conference management device. However, the present embodiment is not limited thereto.

Step 306, the conference management program generates a first file and transmits the first file to the system management program.

Step 307, the hypervisor saves the first file to a temporary folder.

In some examples, during a meeting, a user may perform screen shots and whiteboard writing operations on a display interface of the meeting management device. The first file may include: the screen capture file and the whiteboard writing file. Compared with some implementations, the screen capture file is stored under the screen capture path of the android system, the whiteboard writing file is stored under the whiteboard software directory, in the example, the screen capture file and the whiteboard writing file are stored under the same temporary folder, and a user can find all files related to the conference only by opening the temporary folder, so that the conference file management efficiency can be improved.

Step 308, the conference management program may share the conference file with the participant.

In some examples, during a meeting, a user may trigger a file sharing operation by clicking a one-touch sharing button of the display interface to share meeting files stored in the temporary folder to all participants joining the meeting group. For example, the conference management program may send address information of the conference file to be shared to a server, which sends the address information to mobile terminals of participants who have joined the conference group through push messages.

In this example, the uploading and saving of the second file, the generating and saving of the first file, and the sharing of the conference file are all optional steps. The uploading and the storage of the second file, the generation and the storage of the first file and the execution of the sharing process of the conference file do not have a necessary sequence. The present embodiment is not limited thereto.

In some exemplary embodiments, after the conference is over, the conference management device may manually or automatically clear the temporary folder of the conference to meet conference privacy requirements and avoid occupying memory space of the conference management device.

Step 309, in response to the conference file delete operation, the hypervisor deletes the temporary folder.

In some examples, after the meeting ends, the user may select a one-touch clear button on the display interface to trigger the hypervisor to delete the temporary folder.

Step 310, the system management program automatically deletes the temporary folder.

In some examples, after the meeting ends, the user does not perform a meeting file deletion operation. The hypervisor can judge whether the conference ending time is overtime or not (namely, whether the conference ending time is longer than the set time) according to the set time, and if so, the hypervisor can automatically delete the temporary folder and release the storage space.

In this example, step 309 and step 310 may be alternative steps. After step 309 is performed, step 310 is not performed. Step 310 is performed when step 309 is not performed.

The conference management device provided by the exemplary embodiment can improve the management efficiency of conference files by uniformly storing and managing the files generated in the conference process.

Fig. 4 is a schematic diagram of a conference management system in accordance with at least one embodiment of the present disclosure. As shown in fig. 4, the conference management system provided in this embodiment includes: a conference management device 401, a server 402, and at least one mobile terminal (e.g., mobile terminals 403a to 403 c). The conference management device 401 is configured to create a conference in response to a conference creation operation, create a temporary folder of the conference, and store files related to the conference in the temporary folder. The mobile terminal is configured to interact with the meeting management device 401 through the server 402.

In some exemplary embodiments, the conference management device 401 is configured to send conference creation information to the server 402 after creating the conference. The server 402 is configured to generate a conference two-dimensional code according to the conference creation information. The mobile terminal is configured to join the conference by scanning the conference two-dimensional code. In some examples, the mobile terminal may be running a conferencing application or a WeChat applet. The mobile terminal can join the conference group by scanning the conference two-dimensional code by using a conference application program or a WeChat applet so as to perform file interaction with the conference management device through the server.

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

In some example embodiments, the server is further configured to manage a conference group including user information associated with the same conference identification. The server is further configured to delete the conference group when the end time of the conference is greater than or equal to a set time.

Fig. 5 is a schematic diagram of an interaction flow of a conference management system according to at least one embodiment of the present disclosure. In some exemplary embodiments, as shown in fig. 5, the conference management system may include: conference management device, server and mobile terminal. In this example, a mobile terminal is illustrated as an example. The conference management device may be a touch control integrated machine running an android system program. The mobile terminal may be installed with a conferencing application or a WeChat applet. The mobile terminal may be, for example, a mobile phone, a tablet computer, or other portable devices.

In some examples, the conference management system is illustrated as applied to an offline conference. The meeting organizer may be responsible for operating the meeting management device and for managing the meeting flow. Other participants may operate the conference management device for on-screen operations, such as screen shots or whiteboard writing, etc.

In some examples, as shown in fig. 5, the interaction flow of the conference management system may include the following.

In step 501, the conference management device responds to the conference creation operation to create a conference and create a temporary folder. The process of creating a conference and creating a temporary folder with respect to the conference management device may be described with reference to fig. 3, and thus will not be described again.

Step 502, the conference management device sends conference creation information to a server, and the server generates a conference ID and generates a conference two-dimensional code based on the conference ID and the conference creation information. And the server sends the generated conference two-dimensional code to conference management equipment.

Step 503, the conference management device displays the conference two-dimensional code on the display interface.

Step 504, the participant scans the conference two-dimensional code sign-in by using the mobile terminal. In some examples, the participant may log into the conferencing application of the mobile terminal using the mobile phone number and the authentication code, or log into the WeChat applet through the micropignal authorization. And the participant scans the conference two-dimensional code by using the mobile terminal and then sends the user information to the server. For example, the user information may include: user information registered by the participant with the conferencing application. However, the present embodiment is not limited thereto.

Step 505, after receiving the user information of the participant, the server joins the participant in the conference group, so that the participant uses the file transfer function. The conference group may include user information associated with the same conference ID. That is, users joining the same meeting form a meeting group.

Through the steps, the conference organizer completes conference creation, and the participants join the conference and can use a file transmission function.

In some exemplary embodiments, the conference management device stores all files involved in the conference in a temporary folder and interacts with the participant's mobile terminal through a server for the duration of the conference.

Step 506, the conference management device saves the first file generated during the conference to the temporary folder. The first files include, for example, screen capture files and whiteboard write files.

Step 507, after the mobile terminal of the participant scans the conference two-dimensional code to join the conference group, the second file may be uploaded. 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 stores the second file in the temporary folder. The embodiment is not limited to the type of the second file transmitted by the mobile terminal.

Step 510, the conference management device shares the conference file with the participant. And the conference management equipment 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. And the user can view the meeting file shared by the meeting organizer according to the address information carried by the push message.

In some exemplary embodiments, after the conference is ended, the conference management device may perform step 513, deleting the temporary folder. Wherein the conference management device may delete the temporary folder according to a user operation, or may automatically delete the temporary folder.

The above description of the interaction process of the conference management device may refer to the description of the embodiment shown in fig. 3, so that the description is omitted here.

In the present exemplary embodiment, the conference management apparatus is responsible for processing such as conference creation, temporary folder creation, conference file saving, conference file sharing, and conference file cleaning. The conference management device can open the management mechanism of the conference and the file, and realize the integrated management of the conference and the file. All files related to one conference are stored in the same temporary folder in a centralized mode, and user operation can be facilitated.

In the present exemplary embodiment, the mobile terminal of the participant participates in the transmission of the conference file through the conference application or the WeChat applet. The conference application program is stable, can receive the information in time, and the WeChat applet does not need to install the application program, can receive the information through WeChat, can rapidly share the received file to WeChat friends, and is beneficial to improving conference use experience.

In the present exemplary embodiment, the server may establish a connection between the conference management device and the participant's mobile terminal to implement file transfer and conference management mechanisms. Also, after the conference management apparatus creates one conference, the server generates a conference ID so that the conference management apparatus generates a conference two-dimensional code. The server establishes a conference group for the participants associated with the same conference ID by scanning the conference two-dimensional code. After the conference is ended or the conference is ended for a set period of time (for example, 12 hours), the server can delete the conference ID and the conference group to ensure information security. In this example, the server does not need to operate and maintain user data, and once the conference end time period exceeds a period of time (for example, more than 12 hours), the information related to the conference is deleted, so that the information security of the conference file is ensured.

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

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules or units in the apparatus, or methods disclosed above, may be implemented as software, firmware, hardware, or any suitable combination thereof. In a hardware implementation, the division between functional modules or units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is 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 tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies 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 includes any information delivery media.

The foregoing has shown and described the basic principles, principal features, and advantages of the present disclosure. The present disclosure is not limited to the above-described embodiments, and the above-described embodiments and descriptions merely illustrate the principles of the disclosure, which may be subject to various changes and modifications without departing from the spirit and scope of the disclosure, which are all within the scope of the disclosure as claimed.

Claims

A conference management method applied to conference management equipment, comprising:

responding to a conference creation operation, creating a conference, and creating a temporary folder of the conference;

and storing the files related to the meeting in the temporary folder.
The method of claim 1, wherein the storing the files related to the meeting in the temporary folder comprises at least one of:

storing a first file generated by the conference management device during the duration of the conference to the temporary folder;

and storing a second file received by the conference management device during the duration of the conference to the temporary folder.
The method of claim 2, wherein the first file comprises at least one of: the screen capture file and the whiteboard writing file.
A method according to claim 2 or 3, further comprising:

after the conference is finished, deleting the temporary folder in response to a conference deleting operation; or alternatively, the process may be performed,

and deleting the temporary folder when the ending time of the conference is longer than or equal to the set time.
The method of claim 4, further comprising:

and in the duration of the conference, responding to the file sharing operation, and sending the address information of the conference file selected by the file sharing operation to all the participants through the server.
The method of any one of claims 1 to 5, further comprising:

after creating the conference, the conference creation information is sent to a server, and the conference two-dimensional code generated by the server according to the conference creation information is received and displayed.
The method of claim 6, wherein the meeting creation information comprises: conference name, conference start time, conference end time.
The method of any of claims 1 to 7, wherein the conference management device is an all-in-one machine running an android system program.
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 with the processor and is suitable for providing a display interface; the input device is connected with the processor and is suitable for detecting the operation of the conference management equipment; the conference manager and system manager are configured to be executed by the processor to perform the steps of:

Responding to the conference creation operation, and creating a conference;

and establishing a temporary folder of the conference, and storing files related to the conference in the temporary folder.
The conference management device of claim 9, wherein said processor, when executing said hypervisor, performs at least one of:

storing a first file generated during the duration of the meeting to the temporary folder;

and storing a second file received during the duration of the conference to the temporary folder.
The conference management device of claim 10, wherein the first file comprises at least one of: the screen capture file and the whiteboard writing file.
The conference management device of claim 10 or 11, wherein the processor when running the hypervisor further performs one of:

after the conference is finished, deleting the temporary folder in response to a conference file deleting operation;

and deleting the temporary folder when the length of the meeting is longer than or equal to the set length of time.
The conference management device of claim 12, wherein said processor when executing said conference management program further performs the steps of: and in the duration of the conference, responding to the file sharing operation, and sending the address information of the conference file selected by the file sharing operation to all the participants through the server.
The conference management device of claim 13, wherein said processor when executing said conference management program further performs the steps of: after creating the conference, the conference creation information is sent to a server, and the conference two-dimensional code generated by the server according to the conference creation information is received and displayed.
The conference management device of any one of claims 9 to 14, wherein the conference management device is a touch-sensitive all-in-one machine.
A conference management system, comprising: conference management equipment, a server and at least one mobile terminal;

the conference management device is configured to respond to conference creation operation, create a conference, establish a temporary folder of 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.
The system of claim 16, wherein the conference management device is further configured to send conference creation information to the server after creating a conference;

the server is configured to generate a conference two-dimensional code according to the conference creation information;

the mobile terminal is configured to join the conference by scanning the conference two-dimensional code.
The system of claim 16, wherein 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 further configured to send address information of a conference file shared by the conference management device to the mobile terminal.
The system of any of claims 16 to 18, wherein the server is further configured to manage a conference group, the conference group comprising user information associated with the same conference identification;

the server is further configured to delete the conference group when the end time period of the conference is greater than or equal to a set time period.
A non-transitory computer readable storage medium storing a computer program which, when executed, implements the steps of the conference management method as claimed in any one of claims 1 to 8.