WO2023044747A1 - 会议管理方法、会议管理设备及系统 - Google Patents

会议管理方法、会议管理设备及系统 Download PDF

Info

Publication number
WO2023044747A1
WO2023044747A1 PCT/CN2021/120295 CN2021120295W WO2023044747A1 WO 2023044747 A1 WO2023044747 A1 WO 2023044747A1 CN 2021120295 W CN2021120295 W CN 2021120295W WO 2023044747 A1 WO2023044747 A1 WO 2023044747A1
Authority
WO
WIPO (PCT)
Prior art keywords
conference
meeting
file
management device
server
Prior art date
Application number
PCT/CN2021/120295
Other languages
English (en)
French (fr)
Inventor
陈铁砺
杜子龙
赵海霞
杨明明
李坤
Original Assignee
京东方科技集团股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司 filed Critical 京东方科技集团股份有限公司
Priority to PCT/CN2021/120295 priority Critical patent/WO2023044747A1/zh
Priority to CN202180002666.9A priority patent/CN116171572A/zh
Publication of WO2023044747A1 publication Critical patent/WO2023044747A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/15—Conference systems

Definitions

  • Embodiments of the present disclosure relate to but are not limited to the field of information processing technology, especially a conference management method, conference management device and system.
  • Embodiments of the present disclosure provide a conference management method, conference management equipment and system.
  • 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 of the conference; storing files involved in the conference in The temporary folder.
  • the storing the files involved in the meeting in the temporary folder includes at least one of the following: a first file to be generated by the meeting management device during the duration of the meeting, storing into the temporary folder; storing the second file received by the conference management device during the duration of the conference into the temporary folder.
  • the first file includes at least one of the following: screenshot files, whiteboard writing files.
  • the above meeting management method further includes: after the meeting is over, deleting the temporary folder in response to a meeting delete operation; or, when the end time of the meeting is greater than or equal to the set time length , delete the temporary folder.
  • the above meeting management method further includes: during the duration of the meeting, in response to the file sharing operation, sending the address information of the meeting file selected by the file sharing operation to all participants through the server end.
  • the conference management method further includes: after the conference is created, sending conference creation information to a server, receiving and displaying a conference QR code generated by the server according to the conference creation information.
  • the conference creation information includes: a conference name, a conference start time, and a conference end time.
  • the conference management device is an all-in-one machine running an Android system program.
  • an embodiment of the present disclosure provides a conference management device, including: 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 adapted to provide a display interface;
  • the input device is connected to the processor and is adapted to detect 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 of the conference, and store files involved in the conference in the above the temporary folder.
  • the processor executes at least one of the following when running the system management program: storing the first file generated during the meeting into the temporary folder; The second file received during the duration of the meeting is stored in the temporary folder.
  • the first file includes at least one of the following: screenshot files, whiteboard writing files.
  • the processor further executes one of the following when running the system management program: after the meeting ends, delete the temporary folder in response to a meeting file deletion operation; If the end time is greater than or equal to the set time, the temporary folder is deleted.
  • the following step is further performed: during the duration of the meeting, in response to the file sharing operation, share the meeting file selected by the file sharing operation.
  • the address information is sent to all participants through the server.
  • the processor runs the conference management program, the following steps are further performed: after the conference is created, the conference creation information is sent to the server, and the server receives and displays the conference creation information based on the conference creation information. Generated conference QR code.
  • the conference management device is a touch all-in-one machine.
  • an embodiment of the present disclosure provides a conference management system, including: a conference management device, a server, and at least one mobile terminal.
  • the conference management device is configured to, in response to a conference creation operation, create a conference, establish a temporary folder of the conference, and store files involved in the conference in the temporary folder.
  • the mobile terminal is configured to interact with the conference management device through the server.
  • 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 meeting by scanning the two-dimensional code of the meeting.
  • 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 share the The address information of the conference file is sent to the mobile terminal.
  • the server is further configured to manage a conference group, and the conference group includes user information associated with the same conference identifier.
  • the server is further configured to delete the conference group when the end time of the conference is longer than or equal to a set duration.
  • an embodiment of the present disclosure also provides a non-transitory computer-readable storage medium storing a computer program, and when the computer program is executed, the steps of the above conference management method are implemented.
  • FIG. 1 is a flowchart of a conference management method in at least one embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a conference management device according to at least one embodiment of the present disclosure
  • Fig. 3 is a working schematic diagram 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 according to at least one embodiment of the present disclosure.
  • Fig. 5 is a schematic diagram of interaction of a conference management system according to at least one embodiment of the present disclosure.
  • Embodiments of the present disclosure will be described in detail below in conjunction with the accompanying drawings. Embodiments may be embodied in many different forms. Those skilled in the art can easily understand the fact that the manner and contents can be changed into one or more forms without departing from the spirit and scope of the present disclosure. Therefore, the present disclosure should not be interpreted as being limited only to the contents described in the following embodiments. In the case of no conflict, the embodiments in the present disclosure and the features in the embodiments can be combined arbitrarily with each other.
  • connection should be interpreted in a broad sense unless otherwise specified and limited. For example, it may be a fixed connection, or a detachable connection, or an integral connection; it may be a mechanical connection, or an electrical connection; it may be a direct connection, or an indirect connection through an intermediate piece, or an internal communication between two components.
  • connection should be interpreted in a broad sense unless otherwise specified and limited. For example, it may be a fixed connection, or a detachable connection, or an integral connection; it may be a mechanical connection, or an electrical connection; it may be a direct connection, or an indirect connection through an intermediate piece, or an internal communication between two components.
  • the files generated during the meeting will be scattered and stored in different paths, which is inconvenient to use and manage. For example, if a file is uploaded to a meeting application, unless the user manually modifies it, the uploaded file will be stored in the default path of the meeting application. Most users who temporarily use the all-in-one machine for meetings 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 meeting whiteboard will be stored in the whiteboard software directory. It can be seen that when users want to download or 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.
  • At least one embodiment of the present disclosure provides a conference management method, a conference management device, and a system.
  • a conference management method By uniformly storing and managing files generated during a conference, the inconvenience caused by scattered storage of files generated during a conference in different paths can be improved.
  • FIG. 1 is a flowchart of a conference management method according to at least one embodiment of the present disclosure. As shown in Figure 1, the conference management method provided by this embodiment includes the following steps:
  • Step 101 in response to a conference creation operation, create a conference and create a temporary folder of the conference;
  • Step 102 storing the files involved in the meeting in a temporary folder.
  • the meeting management method provided in this embodiment by creating a corresponding temporary folder for the meeting on the meeting management device, and storing all the files involved in the meeting in the temporary folder, can realize the unified storage of meeting files, and facilitate the storage of meeting files Use and management, so as to improve the efficiency of the use and management of meeting documents.
  • 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.
  • the meeting initiator or meeting organizer can open the meeting management program on the meeting management device, create a meeting through the meeting management program, and the Android system program will create a temporary folder locally for the created meeting, so that in subsequent meetings During the process, all the files involved in the meeting are stored in the temporary folder.
  • this embodiment does not limit it.
  • the all-in-one can also run other system programs.
  • the conference management device may be applied to an offline meeting scenario, or may be applied to an online meeting scenario.
  • this embodiment does not limit it.
  • the conference management method of this embodiment may further include: after the conference is created, sending the conference creation information to the server, receiving and displaying the conference QR code generated by the server according to the conference creation information.
  • the meeting creation information may include: meeting name, meeting start time, and meeting end time.
  • the meeting creation information may only include: meeting name and meeting start time, or, meeting start time and meeting end time.
  • the conference start time may be a time point, or may be a time range; the conference end time may be a time point, or may be a time range.
  • the participants can scan the QR code of the meeting through the meeting application program (APP) or WeChat applet installed on the mobile terminal to enter the meeting.
  • the server may generate a conference identifier (ID).
  • participants use mobile terminals to scan the conference QR code to enter the conference, the server can create a conference group, save the conference ID and the user information of the participants entering the conference (for example, the user information of the participants registered in the conference APP ).
  • 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 file download address information pushed by the conference management device.
  • the conference management device creates an online conference, and after the participants enter the conference by using the mobile terminal, they can interact with the conference organizer who uses the conference management device to create the conference through the server, such as transmitting audio and video information.
  • this embodiment does not limit it.
  • step 102 may include at least one of the following: storing the first file generated by the conference management device during the duration of the conference in a temporary folder; storing the first file received by the conference management device during the duration of the conference
  • the second file stored in a temporary folder.
  • 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 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 the participant through the mobile terminal.
  • this embodiment does not limit it. 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, so as to realize the unified storage of meeting files.
  • the meeting management method provided in this embodiment may further include: after the meeting ends, in response to the meeting delete operation, deleting the temporary folder of the meeting; or, at the end of the meeting, the length is greater than or equal to When setting the duration, delete the temporary folder of the meeting.
  • all files involved in the meeting may be cleared through a user manual operation, that is, the temporary folder may be deleted.
  • the meeting management device may automatically delete the temporary folder to clear all the files involved in the meeting.
  • the set duration may be 12 hours, or 24 hours. However, this embodiment does not limit it.
  • the meeting files can be cleared in time, so as to meet the confidentiality requirements of the meeting files, and can avoid occupying too much storage space of the meeting management device, so as to Improve the operating efficiency of conference management equipment.
  • the server may delete the conference group corresponding to the conference when the end duration of the conference reaches a set duration.
  • a conference group may include user information associated with the same conference ID.
  • a meeting group may include information about all users who join the meeting through the meeting QR code.
  • the effective storage duration of the conference group on the server may be roughly the same as the effective storage duration of the temporary conference folder of the conference management device. This example can meet the confidentiality requirements of the meeting by clearing the meeting groups on the server in time, and protect user information to avoid leakage of user information.
  • the meeting management method of this embodiment may further include: during the duration of the meeting, in response to the file sharing operation, sending the address information of the meeting file selected by the file sharing operation to all participants through the server end.
  • the conference participant terminal may be a mobile terminal (eg, a mobile phone, a tablet computer and other portable devices) used by the participants.
  • 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.
  • the conference management device pushes the address information of the file to all participants through the server, and can use the conference management mechanism combined with the push message mechanism to quickly share the conference files with the participants.
  • Fig. 2 is a schematic diagram of a conference management device provided by at least one embodiment of the present disclosure.
  • 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 adapted to provide a display interface;
  • the input device 204 is connected to the processor 201 and is adapted to detect operations on the conference management device.
  • the memory 202 stores a conference management program and a system management program.
  • the meeting management program and the system management program are configured to be executed by the processor 201 to perform the following steps: create a meeting in response to a meeting creation operation; establish a temporary folder of the meeting, and store files involved in the meeting in the temporary file folder.
  • the processor 201 , the memory 202 , the input device 204 and the display panel 203 may be connected through a bus.
  • the structure of the conference management device shown in FIG. 2 is not limited to the conference management device, and may include more or less components than shown in the figure, or combine certain components, or provide different component arrangements.
  • the processor 201 may include, but 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 can store software programs and modules of application software, and the processor 201 executes various 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 this embodiment.
  • the 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.
  • the storage 202 may include storages that are remotely located relative to the processor 201, and these remote storages may be connected to the conference management device through a network.
  • Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • input device 204 may be adapted to receive input information.
  • the input device 204 may include a touch panel (or called a touch screen) and other input devices (such as a mouse, a keyboard, a joystick, etc.).
  • the display panel 203 may be adapted to display information input by the user or information provided to the user.
  • the display panel 203 is, for example, a liquid crystal display, an organic light emitting diode display panel, or the like.
  • the touch panel can be covered on the display panel. When the touch panel detects a touch operation on or near it, it transmits to the processor 201 to determine the type of the touch event, and then the processor 201 Type provides corresponding visual output on the display panel.
  • the touch panel and the display panel can 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 can be integrated together to implement the input and output functions. However, this embodiment does not limit it.
  • the conference management device is a touch all-in-one machine.
  • the touch panel and the display panel can be integrated to realize input and output functions.
  • this embodiment does not limit it.
  • the system management program may be an Android system program. However, this embodiment does not limit it.
  • the processor 201 executes at least one of the following when running the system management program: storing the first file generated during the meeting into the temporary folder;
  • the second file received during the duration is stored in the temporary folder.
  • the first file may include at least one of the following: a screenshot file, a whiteboard writing file.
  • the processor 201 when the processor 201 runs the system management program, it also performs one of the following: after the meeting ends, in response to the meeting delete operation, delete the temporary folder; , delete the temporary folder.
  • the processor 201 also executes the following steps when running the conference management program: during the duration of the conference, in response to the file sharing operation, send the address information of the conference file selected by the file sharing operation to all Participant end.
  • the processor 201 also executes the following steps when running the conference management program: after the conference is created, send the conference creation information to the server, receive and display the conference two-dimensional information generated by the server according to the conference creation information code.
  • Fig. 3 is a working schematic diagram of a conference management device according to at least one embodiment of the present disclosure.
  • the conference management device includes the following working procedures.
  • Step 301 the conference management program creates a conference in response to a conference creation operation.
  • the conference management device has a display panel and an input device (for example, 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 on the display interface provided by the display panel, then selects the conference creation button, and fills in the conference creation information (for example, including the conference name, conference start time and conference end time, etc.) in the displayed dialog box. information). In some examples, the meeting start time may be required and the remainder may be optional.
  • the conference management program can send the conference creation information to the system management program and the server.
  • Step 302 the system management program creates a temporary folder of the meeting.
  • the system management program after receiving the conference creation information, creates a corresponding temporary folder for the conference.
  • the system management program can use the conference creation information (for example, at least one of the conference name and the conference start time) to name the temporary folder, so as to establish a corresponding relationship between the conference and the temporary folder. All subsequent files of the meeting are set to be saved in this temporary folder.
  • the meeting creation information includes the meeting end time, and the system management program can determine the clearing time of the temporary folder according to the meeting end time.
  • the meeting creation information includes the meeting start time, but does not include the meeting end time
  • the system management program can set the clearing time of the temporary folder according to the meeting starting time, for example, the automatic clearing time of the temporary folder It is obtained by adding the conference start time to the set duration.
  • this embodiment does not limit it.
  • Step 303 displaying the conference QR code on the display interface.
  • the conference management program sends the conference creation information to the server, and the server generates a conference identifier according to 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 a display interface.
  • participants can scan the conference QR code displayed on the conference management device to join the conference group, so as to subsequently realize file transfer with the conference management device.
  • Conference groups can be managed by the server.
  • a meeting group may include user information associated with the same meeting ID. That is, users joining the same conference form a conference group.
  • 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 system management program saves the second file to a temporary folder.
  • the second file is transmitted to the server by the participants joining the meeting through the mobile terminal, and the server transmits the second file to the conference management program after receiving the second file, and the conference management program transmits the second file to the system management program to be stored in in the temporary folder.
  • the second file may be a text file, a picture or a video file.
  • this embodiment does not limit the type of the second file.
  • the size of the second file can be limited. For example, the participant's mobile terminal can only upload the second file whose file size is smaller than the threshold, so as to avoid occupying too much storage space on the conference management device. However, this embodiment does not limit it.
  • Step 306 the conference management program generates the first file, and transmits the first file to the system management program.
  • Step 307 the system management program saves the first file to a temporary folder.
  • the user can perform screen capture 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.
  • 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.
  • the screenshot file and the whiteboard writing file are saved in the same temporary folder. Users only need to open the temporary folder to find all the files related to the meeting, which can improve the efficiency of meeting file management.
  • step 308 the conference management program can share the conference files with the participants.
  • the user can trigger a file sharing operation by clicking a one-key share button on the display interface, so as to share the conference files saved in the temporary folder with all the participants in the conference group.
  • the conference management program can send the address information of the conference file to be shared to the server, and the server sends it to the mobile terminals of the participants who have joined the conference group through a push message.
  • the process of uploading and saving the second file, generating and saving the first file, and sharing the conference file are all optional steps.
  • the uploading and saving of the second file, the generation and saving of the first file, and the sharing process of the conference file are performed in no necessary order. This embodiment does not limit it.
  • the meeting management device may manually or automatically clear the temporary folder of the meeting, so as to meet the confidentiality requirements of the meeting and avoid occupying the storage space of the meeting management device.
  • Step 309 In response to the meeting file deletion operation, the system management program deletes the temporary folder.
  • the user can select a one-key clear button on the display interface to trigger the system management program to delete the temporary folder.
  • Step 310 the system management program automatically deletes the temporary folder.
  • the user does not perform a meeting file deletion operation after the meeting ends.
  • the system management program can judge whether the meeting end time is overtime according to the set time length (that is, whether the meeting end time is greater than the set time length), if overtime, the system management program can automatically delete the temporary folder to release the storage space.
  • step 309 and step 310 may be an optional step. After step 309 is executed, step 310 is not executed again. Step 310 is executed when step 309 is not executed.
  • the conference management device provided in this exemplary embodiment can improve the management efficiency of conference files by uniformly storing and managing the files generated during the conference.
  • FIG. 4 is a schematic diagram of a conference management system according to at least one embodiment of the present disclosure.
  • the conference management system provided in this embodiment includes: a conference management device 401 , a server 402 and at least one mobile terminal (for example, mobile terminals 403 a to 403 c ).
  • the conference management device 401 is configured to, in response to the conference creation operation, create a conference, establish a temporary folder of the conference, and store files involved in the conference in the temporary folder.
  • the mobile terminal is configured to interact with the conference management device 401 through the server 402 .
  • the conference management device 401 is configured to send the 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 meeting by scanning the two-dimensional code of the meeting.
  • the mobile terminal may run a conference application or a WeChat applet.
  • the mobile terminal can use the conference application program or WeChat applet to join the conference group by scanning the conference QR code, so as to exchange files with the conference management device through the server.
  • the server is configured to receive the second file transmitted by the mobile terminal, 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.
  • the server is further configured to manage conference groups, and the conference groups include user information associated with the same conference identifier.
  • the server is further configured to delete the conference group when the end time of the conference is greater than or equal to the set duration.
  • Fig. 5 is a schematic diagram of an interaction process of a conference management system according to at least one embodiment of the present disclosure.
  • the conference management system may include: a conference management device, a server, and a mobile terminal.
  • a mobile terminal is taken as an example for illustration.
  • the conference management device may be a touch-control all-in-one computer running an Android system program.
  • the mobile terminal can be installed with a conference application program or a WeChat applet.
  • the mobile terminal may be, for example, a portable device such as a mobile phone or a tablet computer.
  • the application of the conference management system to offline conferences is taken as an example for illustration.
  • the conference organizer can be responsible for operating the conference management equipment and managing the conference process.
  • Other participants can operate the conference management device for on-screen operations, such as taking screenshots or writing on the whiteboard.
  • the interaction process of the conference management system may include the following processes.
  • step 501 the conference management device creates a conference and creates a temporary folder in response to a conference creation operation.
  • the process of creating a conference and creating a temporary folder by the conference management device can be referred to as shown in FIG. 3 , so details are not repeated here.
  • 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.
  • Step 503 the conference management device displays the conference QR code on the display interface.
  • Step 504 the participant uses the mobile terminal to scan the QR code of the meeting to sign in.
  • the participants can use their mobile phone numbers and verification codes to log in to the conference application on the mobile terminal, or to log in to the WeChat Mini Program through WeChat authorization.
  • the user information is sent to the server.
  • the user information may include: the user information of the participants registered in the conference application program.
  • this embodiment does not limit it.
  • Step 505 After receiving the user information of the participant, the server adds the participant to the conference group, so that the participant can use the file transfer function.
  • a meeting group can include user information associated with the same meeting ID. That is, users joining the same conference form a conference group.
  • the conference organizer completes the conference creation, the participants join the conference, and can use the file transfer function.
  • 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.
  • 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.
  • Step 507 after the mobile terminal of the participant scans the QR code of the meeting to join the meeting group, the second file can be uploaded.
  • the server receives the second file uploaded by the mobile terminal.
  • 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.
  • Step 510 the conference management device shares the conference files 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. Users can view the meeting documents shared by the meeting organizer according to the address information carried in the push message.
  • the meeting management device may execute step 513 to delete the temporary folder.
  • the conference management device may delete the temporary folder according to user operations, or may delete the temporary folder automatically.
  • the conference management device is in charge of creating a conference, creating a temporary folder, saving conference files, sharing conference files, clearing conference files, and the like.
  • Conference management equipment can open up the management mechanism of conferences and documents, and realize the integrated management of conferences and documents. All the files related to a meeting are centrally stored in the same temporary folder, which is convenient for users to operate.
  • the participants' mobile terminals participate in the transmission of meeting files through a meeting application program or a WeChat applet.
  • the conference application is relatively stable and can receive messages in a timely manner, while the WeChat applet does not need to install the application program, can receive messages through WeChat, and can quickly share the received files with WeChat friends, which is conducive to improving the conference experience.
  • the server can establish a connection between the conference management device and the participant's mobile terminal, so as to implement the file transfer and conference management mechanism. Moreover, after the conference management device creates a conference, the server will generate a conference ID, so that the conference management device can generate a conference QR code. The server creates a meeting group for the participants who are associated with the same meeting ID by scanning the meeting QR code. After the meeting ends or a set time period (for example, 12 hours) after the meeting ends, the server can delete the meeting ID and the meeting group to ensure information security. In this example, the server does not need to operate and maintain user data. Once the end time of the meeting expires (for example, more than 12 hours), the information related to the meeting will be deleted, so as to ensure the information security of the meeting files.
  • At least one embodiment of the present disclosure further provides a non-transitory computer-readable storage medium storing a computer program, and when the computer program is executed, the steps of the above conference management method are implemented.
  • the functional modules or units in the system, and the device can be implemented as software, firmware, hardware, and an appropriate combination thereof.
  • 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 composed of several physical components. Components cooperate to execute.
  • 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).
  • computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • 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 may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种会议管理方法，应用于会议管理设备，包括：响应于会议创建操作，创建会议，并建立所述会议的临时文件夹；将所述会议涉及的文件存储在所述临时文件夹。

Description

会议管理方法、会议管理设备及系统 技术领域
本公开实施例涉及但不限于信息处理技术领域，尤指一种会议管理方法、会议管理设备及系统。
背景技术
人们通常通过会议取得工作上的共识，以提高协同工作的效率。在会议场景中，用户经常使用的操作包括：文件展示、会议文件分享等。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本公开实施例提供一种会议管理方法、会议管理设备及系统。
一方面，本公开实施例提供一种会议管理方法，应用于会议管理设备，包括：响应于会议创建操作，创建会议，并建立所述会议的临时文件夹；将所述会议涉及的文件存储在所述临时文件夹。
在一些示例性实施方式中，所述将所述会议涉及的文件存储在所述临时文件夹，包括以下至少之一：将在所述会议的持续期间所述会议管理设备生成的第一文件，存储至所述临时文件夹；将在所述会议的持续期间所述会议管理设备接收到的第二文件，存储至所述临时文件夹。
在一些示例性实施方式中，所述第一文件包括以下至少之一：截屏文件、白板书写文件。
在一些示例性实施方式中，上述会议管理方法还包括：在所述会议结束后，响应于会议删除操作，删除所述临时文件夹；或者，在所述会议的结束时长大于或等于设定时长时，删除所述临时文件夹。
在一些示例性实施方式中，上述会议管理方法还包括：在所述会议的持续期间，响应于文件分享操作，将所述文件分享操作所选择的会议文件的地 址信息通过服务器发送给所有参会端。
在一些示例性实施方式中，上述会议管理方法还包括：在创建会议之后，将会议创建信息发送给服务器，接收并显示由所述服务器根据所述会议创建信息生成的会议二维码。
在一些示例性实施方式中，所述会议创建信息包括：会议名称、会议起始时间、会议结束时间。
在一些示例性实施方式中，所述会议管理设备为运行安卓系统程序的一体机。
另一方面，本公开实施例提供一种会议管理设备，包括：显示面板、输入装置、处理器以及存储有会议管理程序和系统管理程序的存储器。所述显示面板连接所述处理器，适于提供显示界面；所述输入装置连接所述处理器，适于检测在所述会议管理设备的操作。所述会议管理程序和系统管理程序配置为被所述处理器运行以执行以下步骤：响应于会议创建操作，创建会议；建立所述会议的临时文件夹，将所述会议涉及的文件存储在所述临时文件夹。
在一些示例性实施方式中，所述处理器运行所述系统管理程序时执行以下至少之一：将在所述会议的持续期间生成的第一文件，存储至所述临时文件夹；将在所述会议的持续期间接收到的第二文件，存储至所述临时文件夹。
在一些示例性实施方式中，所述第一文件包括以下至少之一：截屏文件、白板书写文件。
在一些示例性实施方式中，所述处理器运行所述系统管理程序时还执行以下之一：在所述会议结束后，响应于会议文件删除操作，删除所述临时文件夹；在所述会议的结束时长大于等于设定时长，删除所述临时文件夹。
在一些示例性实施方式中，所述处理器运行所述会议管理程序时还执行下列步骤：在所述会议的持续期间，响应于文件分享操作，将所述文件分享操作所选择的会议文件的地址信息通过服务器发送给所有参会端。
在一些示例性实施方式中，所述处理器运行所述会议管理程序时还执行下列步骤：在创建会议之后，将会议创建信息发送给服务器，接收并显示由所述服务器根据所述会议创建信息生成的会议二维码。
在一些示例性实施方式中，所述会议管理设备为触摸一体机。
另一方面，本公开实施例提供一种会议管理系统，包括：会议管理设备、服务器以及至少一个移动终端。所述会议管理设备，配置为响应于会议创建操作，创建会议，建立所述会议的临时文件夹，并将所述会议涉及的文件存储在所述临时文件夹。所述移动终端，配置为通过所述服务器与所述会议管理设备交互。
在一些示例性实施方式中，所述会议管理设备还配置为在创建会议之后，将会议创建信息发送给所述服务器。所述服务器配置为根据所述会议创建信息，生成会议二维码。所述移动终端，配置为通过扫描所述会议二维码加入所述会议。
在一些示例性实施方式中，所述服务器配置为接收所述移动终端传输的第二文件，并将所述第二文件传输给所述会议管理设备，还配置为将所述会议管理设备分享的会议文件的地址信息发送给所述移动终端。
在一些示例性实施方式中，所述服务器还配置为管理会议群组，所述会议群组包括与同一会议标识关联的用户信息。所述服务器还配置为在所述会议的结束时长大于或等于设定时长时，删除所述会议群组。
另一方面，本公开实施例还提供一种非瞬态计算机可读存储介质，存储有计算机程序，所述计算机程序被执行时实现如上所述的会议管理方法的步骤。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
附图用来提供对本公开技术方案的进一步理解，并且构成说明书的一部分，与本公开的实施例一起用于解释本公开的技术方案，并不构成对本公开的技术方案的限制。附图中一个或多个部件的形状和大小不反映真实比例，目的只是示意说明本公开内容。
图1为本公开至少一实施例的会议管理方法的流程图；
图2为本公开至少一实施例的会议管理设备的示意图；
图3为本公开至少一实施例的会议管理设备的工作示意图；
图4为本公开至少一实施例的会议管理系统的示意图；
图5为本公开至少一实施例的会议管理系统的交互示意图。
具体实施方式
下面将结合附图对本公开实施例进行详细说明。实施方式可以以多个不同形式来实施。所属技术领域的普通技术人员可以很容易地理解一个事实，就是方式和内容可以在不脱离本公开的宗旨及其范围的条件下被变换为一种或多种形式。因此，本公开不应该被解释为仅限定在下面的实施方式所记载的内容中。在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互任意组合。
在附图中，有时为了明确起见，夸大表示了一个或多个构成要素的大小、层的厚度或区域。因此，本公开的一个方式并不一定限定于该尺寸，附图中多个部件的形状和大小不反映真实比例。此外，附图示意性地示出了理想的例子，本公开的一个方式不局限于附图所示的形状或数值等。
本公开中的“第一”、“第二”、“第三”等序数词是为了避免构成要素的混同而设置，而不是为了在数量方面上进行限定的。本公开中的“多个”表示两个或两个以上的数量。
在本公开中，为了方便起见，使用“中部”、“上”、“下”、“前”、“后”、“竖直”、“水平”、“顶”、“底”、“内”、“外”等指示方位或位置关系的词句以参照附图说明构成要素的位置关系，仅是为了便于描述本说明书和简化描述，而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作，因此不能理解为对本公开的限制。构成要素的位置关系根据描述构成要素的方向适当地改变。因此，不局限于在说明书中说明的词句，根据情况可以适当地更换。
在本公开中，除非另有明确的规定和限定，术语“安装”、“相连”、“连接”应做广义理解。例如，可以是固定连接，或可拆卸连接，或一体地连接；可以是机械连接，或电连接；可以是直接相连，或通过中间件间接相 连，或两个元件内部的连通。对于本领域的普通技术人员而言，可以根据情况理解上述术语在本公开中的含义。
以使用一体机的会议场景为例，会议中产生的文件会分散存储在不同路径下，不便于使用和管理。例如，文件上传至会议应用内，除非用户手动修改，上传的文件会存储在此会议应用的默认路径下。大多数临时使用一体机开会的用户会选择默认路径存储文件。然而，以一体机运行安卓系统为例，会议过程中产生的截屏文件会默认存储在安卓系统的screenshot路径下，会议白板书写内容又会存储在白板软件目录下。由此可见，当用户想要将这些文件下载或分享或清理时，需要访问多个文件夹，不便于使用和管理，且文件分享和清理过程中会存在遗漏和低效的问题。
本公开至少一实施例提供一种会议管理方法、会议管理设备及系统，通过对会议过程产生的文件进行统一存储和管理，可以改善会议中产生的文件分散存储在不同路径导致的不便。
本公开至少一实施例提供一种会议管理方法，应用于会议管理设备。图1为本公开至少一实施例的会议管理方法的流程图。如图1所示，本实施例提供的会议管理方法，包括以下步骤：
步骤101、响应于会议创建操作，创建会议，并建立所述会议的临时文件夹；
步骤102、将所述会议涉及的文件存储在临时文件夹。
本实施例提供的会议管理方法，通过在会议管理设备给会议创建对应的临时文件夹，并将会议涉及的文件均存储在该临时文件夹，可以实现对会议文件的统一存储，便于会议文件的使用和管理，从而可以提高会议文件的使用和管理效率。
在一些示例性实施方式中，会议管理设备可以是运行安卓系统程序的一体机。会议管理设备可以安装有会议管理程序。在一些示例中，会议发起者或会议组织者可以在会议管理设备上打开会议管理程序，通过会议管理程序创建会议，并由安卓系统程序给创建的会议在本地建立临时文件夹，以便在后续会议过程中，将所述会议涉及的文件均存储在该临时文件夹内。然而， 本实施例对此并不限定。例如，一体机还可以运行其他系统程序。
在一些示例性实施方式中，会议管理设备可以应用于线下会议场景，或者，可以应用于线上会议场景。然而，本实施例对此并不限定。
在一些示例性实施方式中，本实施例的会议管理方法还可以包括：在创建会议之后，将会议创建信息发送给服务器，接收并显示由服务器根据会议创建信息生成的会议二维码。在一些示例中，会议创建信息可以包括：会议名称、会议起始时间、会议结束时间。然而，本实施例对此并不限定。例如，会议创建信息可以仅包括：会议名称和会议起始时间，或者，会议起始时间和会议结束时间。在一些示例中，会议起始时间可以为一个时间点，或者可以为一个时间范围；会议结束时间可以为一个时间点，或者，可以为一个时间范围。
在一些示例中，参会者可以通过移动终端安装的会议应用程序(APP)或者微信小程序扫描会议二维码，以进入会议。服务器在接收到会议管理设备发送的会议创建信息之后，可以生成会议标识(ID)。在参会者利用移动终端扫描会议二维码进入会议之后，服务器可以建立会议群组，保存会议ID和进入该会议的参会者的用户信息(例如，参会者在会议APP注册的用户信息)。
在一些示例中，会议管理设备创建线下会议，参会者利用移动终端进入会议之后，可以通过服务器向会议管理设备传输文件，并获取会议管理设备推送的文件下载地址信息。在另一些示例中，会议管理设备创建线上会议，参会者利用移动终端进入会议之后，可以通过服务器与利用会议管理设备创建会议的会议组织者进行交互，例如传输音视频信息。然而，本实施例对此并不限定。
在一些示例性实施方式中，步骤102可以包括以下至少之一：将在会议的持续期间会议管理设备生成的第一文件，存储至临时文件夹；将在会议的持续器件会议管理设备接收到的第二文件，存储至临时文件夹。在一些示例中，会议涉及的文件可以包括：会议过程中生成的第一文件以及会议过程中接收到的第二文件。第一文件例如可以包括以下至少之一：截屏文件、白板书写文件。第二文件可以为由参会者通过移动终端上传至会议管理设备的文 件。然而，本实施例对此并不限定。在本示例中，不管会议过程中产生或接收的文件是何种类型，均统一存储至该会议对应的临时文件夹，以实现会议文件的统一存储。
在一些示例性实施方式中，本实施例提供的会议管理方法还可以包括：在会议结束后，响应于会议删除操作，删除所述会议的临时文件夹；或者，在会议的结束时长大于或等于设定时长时，删除所述会议的临时文件夹。在一些示例中，在会议结束之后，可以通过用户手动操作清除会议涉及的所有文件，即删除临时文件夹。在一些示例中，在会议结束之后，用户没有手动清除会议涉及的文件，则在会议结束时长达到设定时长之后，会议管理设备可以自动删除临时文件夹，以清除会议涉及的所有文件。在一些示例中，设定时长可以为12小时，或者，24小时。然而，本实施例对此并不限定。在本示例中，通过提供手动和自动两种方式对临时文件夹进行清除，可以及时对会议文件进行清除，从而满足会议文件的保密要求，而且可以避免占用会议管理设备的过多存储空间，以提高会议管理设备的运行效率。
在一些示例性实施方式中，服务器在会议的结束时长达到设定时长时，可以删除会议对应的会议群组。会议群组可以包括与同一会议标识关联的用户信息。例如，会议群组可以包括通过会议二维码加入会议的所有用户信息。在本示例中，会议群组在服务器的有效存储时长与会议管理设备的会议的临时文件夹的有效存储时长可以大致相同。本示例通过对服务器的会议群组进行及时清除，可以满足会议的保密要求，并对用户信息进行保护，避免用户信息的泄露。
在一些示例性实施方式中，本实施例的会议管理方法还可以包括：在会议的持续期间，响应于文件分享操作，将文件分享操作所选择的会议文件的地址信息通过服务器发送给所有参会端。在本示例中，参会端可以为参会者所使用的移动终端(例如，手机、平板电脑等可携式设备)。在一些示例中，文件分享操作可以包括用户在会议管理设备触发的一键分享操作，即，将临时文件夹内的全部或部分文件分享给全部参会者的操作。在本示例中，由于会议涉及的文件均存储在临时文件夹内，无需访问不同路径查找待分享的会议文件，可以实现快速分享会议文件。而且，会议管理设备通过服务器向所 有参会者推送文件的地址信息，可以采用会议管理机制并结合推送消息机制，将会议文件快速地分享给参会者。
图2为本公开至少一实施例提供的会议管理设备的示意图。在一些示例性实施方式中，如图2所示，本实施例的会议管理设备包括：显示面板203、输入装置204、处理器201以及存储器202。显示面板203连接处理器201，适于提供显示界面；输入装置204连接处理器201，适于检测在会议管理设备的操作。存储器202存储有会议管理程序和系统管理程序。会议管理程序和系统管理程序配置为被处理器201运行以执行以下步骤：响应于会议创建操作，创建会议；建立所述会议的临时文件夹，将所述会议涉及的文件存储在所述临时文件夹。
在一些示例中，如图2所示，处理器201、存储器202、输入装置204以及显示面板203可以通过总线连接。图2中所示的会议管理设备的结构并不构成对会议管理设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者提供不同的部件布置。
在一些示例中，处理器201可以包括但不限于微处理器(MCU，Microcontroller Unit)或可编程逻辑器件(FPGA，Field Programmable Gate Array)等的处理装置。存储器202可以存储应用软件的软件程序以及模块，处理器201通过运行存储在存储器202内的软件程序以及模块，从而执行多种功能应用以及数据处理，比如实现本实施例提供的会议管理方法。存储器202可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些示例中，存储器202可包括相对于处理器201远程设置的存储器，这些远程存储器可以通过网络连接至会议管理设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
在一些示例中，输入装置204可以适于接收输入的信息。示例性地，输入装置204可以包括触控面板(或称为触摸屏)以及其他输入设备(比如，鼠标、键盘、操作杆等)。显示面板203可以适于显示用户输入的信息或提供给用户的信息。显示面板203例如为液晶显示器、有机发光二极管显示面板等。示例性地，触控面板可以覆盖在显示面板上，当触控面板检测到在其 上或附近的触摸操作后，传输给处理器201以确定触摸事件的类型，随后处理器201根据触摸事件的类型在显示面板上提供相应的视觉输出。示例性地，触控面板和显示面板可以作为两个独立的部件来实现终端设备的输入和输出功能，或者，触控面板和显示面板可以集成在一起来实现输入和输出功能。然而，本实施例对此并不限定。
在一些示例性实施方式中，会议管理设备为触摸一体机。触控面板和显示面板可以集成在一起实现输入输出功能。然而，本实施例对此并不限定。
在一些示例性实施方式中，系统管理程序可以为安卓系统程序。然而，本实施例对此并不限定。
在一些示例性实施方式中，处理器201运行系统管理程序时执行以下至少之一：将在所述会议的持续期间生成的第一文件，存储至所述临时文件夹；将在所述会议的持续期间接收到的第二文件，存储至所述临时文件夹。例如，第一文件可以包括以下至少之一：截屏文件、白板书写文件。
在一些示例性实施方式中，处理器201运行系统管理程序时还执行以下之一：在会议结束后，响应于会议删除操作，删除所述临时文件夹；在会议的结束时长大于等于设定时长，删除所述临时文件夹。
在一些示例性实施方式中，处理器201运行会议管理程序时还执行下列步骤：在会议的持续期间，响应于文件分享操作，将文件分享操作所选择的会议文件的地址信息通过服务器发送给所有参会端。
在一些示例性实施方式中，处理器201运行会议管理程序时还执行下列步骤：在创建会议之后，将会议创建信息发送给服务器，接收并显示由服务器根据所述会议创建信息生成的会议二维码。
图3为本公开至少一实施例的会议管理设备的工作示意图。在一些示例性实施方式中，如图3所示，会议管理设备包括以下工作过程。
步骤301、会议管理程序响应于会议创建操作，创建会议。
在一些示例中，会议管理设备具有显示面板和输入装置(例如，触控面板)，用户可以通过输入装置对显示面板显示的内容进行操作。例如，用户在显示面板提供的显示界面打开会议管理程序图标，然后，选中会议创建按 钮，并在显示的对话框内填入会议创建信息(例如包括会议名称、会议起始时间和会议结束时间等信息)。在一些示例中，会议起始时间可以为必填项，其余内容可以为选填项。会议管理程序可以将会议创建信息发送给系统管理程序和服务器。
步骤302、系统管理程序建立会议的临时文件夹。
在一些示例中，系统管理程序接收到会议创建信息之后，给会议建立对应的临时文件夹。系统管理程序可以利用会议创建信息(例如会议名称和会议起始时间中至少一项)给临时文件夹命名，以建立会议和临时文件夹的对应关系。后续该会议的所有文件均设置为保存在该临时文件夹内。在一些示例中，会议创建信息包括会议结束时间，则系统管理程序可以根据会议结束时间确定临时文件夹的清除时刻。在另一些示例中，会议创建信息包括会议起始时间，但不包括会议结束时间，则系统管理程序可以根据会议起始时间，设置临时文件夹的清除时刻，例如，临时文件夹的自动清除时刻由会议起始时间加上设定时长得到。然而，本实施例对此并不限定。
步骤303、在显示界面显示会议二维码。
在一些示例中，会议管理程序将会议创建信息发送给服务器，服务器根据会议创建信息，生成会议标识，并基于会议标识和会议创建信息生成会议二维码。服务器将生成的会议二维码发送给会议管理设备，会议管理设备在显示界面显示会议二维码。在一些示例中，在线下会议场景使用会议管理设备时，参会者可以通过扫描会议管理设备显示的会议二维码加入会议群组，以便后续实现与会议管理设备之间的文件传输。会议群组可以由服务器管理。会议群组可以包括与同一会议ID关联的用户信息。即，加入同一会议的用户组成一个会议群组。
在一些示例性实施方式中，在会议开始之后，会议管理设备可以执行以下操作。
步骤304、会议管理程序接收服务器传输的第二文件，并将第二文件传输至系统管理程序。
步骤305、系统管理程序将第二文件保存至临时文件夹。
在一些示例中，第二文件由加入会议的参会者通过移动终端传输给服务器，服务器接收第二文件后传输给会议管理程序，会议管理程序将第二文件传输给系统管理程序，以保存在临时文件夹内。例如，第二文件可以为文本文件、图片或者视频文件。然而，本实施例对于第二文件的类型并不限定。在一些示例中，可以限制第二文件的大小。例如，参会者的移动终端仅可以上传文件大小小于阈值的第二文件，避免在会议管理设备占用过多的存储空间。然而，本实施例对此并不限定。
步骤306、会议管理程序生成第一文件，并将第一文件传输给系统管理程序。
步骤307、系统管理程序将第一文件保存至临时文件夹。
在一些示例中，在会议过程中，用户可以在会议管理设备的显示界面进行截屏和白板书写操作。第一文件可以包括：截屏文件、白板书写文件。相较于一些实现方式中，将截屏文件保存在安卓系统的screenshot路径下，将白板书写文件保存至白板软件目录下，本示例中将截屏文件和白板书写文件保存至同一个临时文件夹下，用户只需打开该临时文件夹即可找到会议相关的所有文件，可以提高会议文件管理效率。
步骤308、会议管理程序可以向参会端分享会议文件。
在一些示例中，在会议过程中，用户通过点选显示界面的一键分享按钮，可以触发文件分享操作，以将临时文件夹内保存的会议文件分享给加入会议群组的所有参会者。例如，会议管理程序可以将待分享的会议文件的地址信息发送给服务器，由服务器通过推送消息发送给已加入会议群组的参会者的移动终端。
在本示例中，第二文件的上传和保存、第一文件的生成和保存、会议文件的分享过程均为可选步骤。第二文件的上传和保存、第一文件的生成和保存、会议文件的分享过程的执行没有必然的先后顺序。本实施例对此并不限定。
在一些示例性实施方式中，在会议结束之后，会议管理设备可以通过手动或自动方式清除会议的临时文件夹，以满足会议保密要求，并避免占满会 议管理设备的存储空间。
步骤309、响应于会议文件删除操作，系统管理程序删除临时文件夹。
在一些示例中，在会议结束之后，用户可以在显示界面选择一键清除按钮，以触发系统管理程序删除临时文件夹。
步骤310、系统管理程序自动删除临时文件夹。
在一些示例中，在会议结束之后，用户未执行会议文件删除操作。系统管理程序可以根据设定时长来判断会议结束时长是否超时(即，会议结束时长是否大于设定时长)，若超时，则系统管理程序可以自动删除临时文件夹，释放存储空间。
在本示例中，步骤309和步骤310可以为择一步骤。在执行步骤309之后，不再执行步骤310。在未执行步骤309时执行步骤310。
本示例性实施方式提供的会议管理设备，通过对会议过程产生的文件进行统一存储和管理，可以提高会议文件的管理效率。
图4为本公开至少一实施例的会议管理系统的示意图。如图4所示，本实施例提供的会议管理系统，包括：会议管理设备401、服务器402以及至少一个移动终端(例如，移动终端403a至403c)。会议管理设备401配置为响应于会议创建操作，创建会议，建立所述会议的临时文件夹，并将所述会议涉及的文件存储在所述临时文件夹。移动终端配置为通过服务器402与会议管理设备401交互。
在一些示例性实施方式中，会议管理设备401配置为在创建会议之后，将会议创建信息发送给服务器402。服务器402配置为根据所述会议创建信息，生成会议二维码。移动终端配置为通过扫描所述会议二维码加入所述会议。在一些示例中，移动终端可以运行有会议应用程序或者微信小程序。移动终端可以利用会议应用程序或微信小程序，通过扫描会议二维码加入会议群组，以通过服务器与会议管理设备进行文件交互。
在一些示例性实施方式中，服务器配置为接收移动终端传输的第二文件，并将第二文件传输给会议管理设备，还配置为将会议管理设备分享的会议文件的地址信息发送给移动终端。
在一些示例性实施方式中，服务器还配置为管理会议群组，会议群组包括与同一会议标识关联的用户信息。服务器还配置为在所述会议的结束时长大于或等于设定时长时，删除所述会议群组。
图5为本公开至少一实施例的会议管理系统的交互流程示意图。在一些示例性实施方式中，如图5所示，会议管理系统可以包括：会议管理设备、服务器以及移动终端。在本示例中，以一个移动终端为例进行说明。会议管理设备可以为运行有安卓系统程序的触控一体机。移动终端可以安装有会议应用程序或者微信小程序。移动终端例如可以为手机、平板电脑等可携式设备。
在一些示例中，以会议管理系统应用于线下会议为例进行说明。会议组织者可以负责操作会议管理设备，负责管理会议流程。其他参会者可以操作会议管理设备进行屏上操作，例如，截屏或白板书写等。
在一些示例中，如图5所示，会议管理系统的交互流程可以包括以下过程。
步骤501、会议管理设备响应于会议创建操作，创建会议，并建立临时文件夹。关于会议管理设备创建会议和建立临时文件夹的过程可以参照图3所示，故于此不再赘述。
步骤502、会议管理设备将会议创建信息发送给服务器，服务器生成会议ID，并基于会议ID和会议创建信息生成会议二维码。服务器将生成的会议二维码发送给会议管理设备。
步骤503、会议管理设备在显示界面显示会议二维码。
步骤504、参会者利用移动终端扫描会议二维码签到。在一些示例中，参会者可以使用手机号码和验证码登录移动终端的会议应用程序，或者通过微信号授权登录微信小程序。参会者利用移动终端扫描会议二维码后，将用户信息发送给服务器。例如，用户信息可以包括：参会者在会议应用程序注册的用户信息。然而，本实施例对此并不限定。
步骤505、服务器接收到参会者的用户信息之后，将参会者加入会议群组，以便于参会者使用文件传输功能。会议群组可以包括与同一会议ID关 联的用户信息。即，加入同一会议的用户组成一个会议群组。
通过上述步骤，会议组织者完成会议创建，参会者加入会议，可以使用文件传输功能。
在一些示例性实施方式中，在会议的持续期间，会议管理设备将会议涉及的所有文件存储在临时文件夹内，并通过服务器与参会者的移动终端进行交互。
步骤506、会议管理设备将会议期间生成的第一文件保存到临时文件夹。第一文件例如包括截屏文件和白板书写文件。
步骤507、参会者的移动终端在扫描会议二维码加入会议群组之后，可以上传第二文件。步骤508、服务器接收移动终端上传的第二文件。步骤509、会议管理设备接收服务器传输的第二文件，并将第二文件保存至临时文件夹。本实施例对于移动终端传输的第二文件的类型并不限定。
步骤510、会议管理设备向参会者分享会议文件。会议管理设备将待分享的会议文件的地址信息发送给服务器。步骤511、服务器接收到地址信息后，向会议群组内的用户信息发送携带会议文件的地址信息的推送消息。步骤512、移动终端接收推送消息。用户可以根据推送消息携带的地址信息查看会议组织者分享的会议文件。
在一些示例性实施方式中，在会议结束之后，会议管理设备可以执行步骤513，删除临时文件夹。其中，会议管理设备可以根据用户操作来删除临时文件夹，或者可以自动删除临时文件夹。
上述交互过程中关于会议管理设备的工作过程的说明可以参照图3所示实施例的描述，故于此不再赘述。
在本示例性实施方式中，会议管理设备负责会议创建、临时文件夹建立、会议文件保存、会议文件分享以及会议文件清除等处理。会议管理设备可以打通会议和文件的管理机制，实现会议和文件的一体管理。将一场会议相关的文件全部集中存储在同一临时文件夹下，可以方便用户操作。
在本示例性实施方式中，参会者的移动终端通过会议应用程序或微信小程序参与会议文件的传输。其中，会议应用程序较为稳定，可以及时接收消 息，而微信小程序无需安装应用程序，可以通过微信接收消息，并可以将接收的文件快速分享给微信好友，有利于提高会议使用体验。
在本示例性实施方式中，服务器可以建立会议管理设备和参会者的移动终端之间的连接，以实现文件传输和会议管理机制。而且，在会议管理设备创建一个会议之后，服务器会生成会议ID，以便会议管理设备生成会议二维码。服务器给通过扫描会议二维码，与同一个会议ID关联的参会者建立会议群组。在会议结束或者会议结束设定时长(例如12小时)后，服务器可以将会议ID和会议群组删除，以保证信息安全性。在本示例中，服务器无需运营维护用户数据，一旦会议结束时长超期(例如，超过12小时)，会议相关的信息均会被删除，从而保证会议文件的信息安全。
此外，本公开至少一实施例还提供一种非瞬态计算机可读存储介质，存储有计算机程序，该计算机程序被执行时实现上述会议管理方法的步骤。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块或单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块或单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递 送介质。
以上显示和描述了本公开的基本原理、主要特征和本公开的优点。本公开不受上述实施例的限制，上述实施例和说明书中描述的只是说明本公开的原理，在不脱离本公开精神和范围的前提下，本公开还会有多种变化和改进，这些变化和改进都落入要求保护的本公开的范围内。

Claims (20)

  1. 一种会议管理方法，应用于会议管理设备，包括：
    响应于会议创建操作，创建会议，并建立所述会议的临时文件夹；
    将所述会议涉及的文件存储在所述临时文件夹。
  2. 根据权利要求1所述的方法，其中，所述将所述会议涉及的文件存储在所述临时文件夹，包括以下至少之一：
    将在所述会议的持续期间所述会议管理设备生成的第一文件，存储至所述临时文件夹；
    将在所述会议的持续期间所述会议管理设备接收到的第二文件，存储至所述临时文件夹。
  3. 根据权利要求2所述的方法，其中，所述第一文件包括以下至少之一：截屏文件、白板书写文件。
  4. 根据权利要求2或3所述的方法，还包括：
    在所述会议结束后，响应于会议删除操作，删除所述临时文件夹；或者，
    在所述会议的结束时长大于或等于设定时长时，删除所述临时文件夹。
  5. 根据权利要求4所述的方法，还包括：
    在所述会议的持续期间，响应于文件分享操作，将所述文件分享操作所选择的会议文件的地址信息通过服务器发送给所有参会端。
  6. 根据权利要求1至5中任一项所述的方法，还包括：
    在创建会议之后，将会议创建信息发送给服务器，接收并显示由所述服务器根据所述会议创建信息生成的会议二维码。
  7. 根据权利要求6所述的方法，其中，所述会议创建信息包括：会议名称、会议起始时间、会议结束时间。
  8. 根据权利要求1至7中任一项所述的方法，其中，所述会议管理设备为运行安卓系统程序的一体机。
  9. 一种会议管理设备，包括：显示面板、输入装置、处理器以及存储有 会议管理程序和系统管理程序的存储器；所述显示面板连接所述处理器，适于提供显示界面；所述输入装置连接所述处理器，适于检测在所述会议管理设备的操作；所述会议管理程序和系统管理程序配置为被所述处理器运行以执行以下步骤：
    响应于会议创建操作，创建会议；
    建立所述会议的临时文件夹，将所述会议涉及的文件存储在所述临时文件夹。
  10. 根据权利要求9所述的会议管理设备，其中，所述处理器运行所述系统管理程序时执行以下至少之一：
    将在所述会议的持续期间生成的第一文件，存储至所述临时文件夹；
    将在所述会议的持续期间接收到的第二文件，存储至所述临时文件夹。
  11. 根据权利要求10所述的会议管理设备，其中，所述第一文件包括以下至少之一：截屏文件、白板书写文件。
  12. 根据权利要求10或11所述的会议管理设备，其中，所述处理器运行所述系统管理程序时还执行以下之一：
    在所述会议结束后，响应于会议文件删除操作，删除所述临时文件夹；
    在所述会议的结束时长大于等于设定时长，删除所述临时文件夹。
  13. 根据权利要求12所述的会议管理设备，其中，所述处理器运行所述会议管理程序时还执行下列步骤：在所述会议的持续期间，响应于文件分享操作，将所述文件分享操作所选择的会议文件的地址信息通过服务器发送给所有参会端。
  14. 根据权利要求13所述的会议管理设备，其中，所述处理器运行所述会议管理程序时还执行下列步骤：在创建会议之后，将会议创建信息发送给服务器，接收并显示由所述服务器根据所述会议创建信息生成的会议二维码。
  15. 根据权利要求9至14中任一项所述的会议管理设备，其中，所述会议管理设备为触摸一体机。
  16. 一种会议管理系统，包括：会议管理设备、服务器以及至少一个移 动终端；
    所述会议管理设备，配置为响应于会议创建操作，创建会议，建立所述会议的临时文件夹，并将所述会议涉及的文件存储在所述临时文件夹；
    所述移动终端，配置为通过所述服务器与所述会议管理设备交互。
  17. 根据权利要求16所述的系统，其中，所述会议管理设备还配置为在创建会议之后，将会议创建信息发送给所述服务器；
    所述服务器配置为根据所述会议创建信息，生成会议二维码；
    所述移动终端，配置为通过扫描所述会议二维码加入所述会议。
  18. 根据权利要求16所述的系统，其中，所述服务器配置为接收所述移动终端传输的第二文件，并将所述第二文件传输给所述会议管理设备，还配置为将所述会议管理设备分享的会议文件的地址信息发送给所述移动终端。
  19. 根据权利要求16至18中任一项所述的系统，其中，所述服务器还配置为管理会议群组，所述会议群组包括与同一会议标识关联的用户信息；
    所述服务器还配置为在所述会议的结束时长大于或等于设定时长时，删除所述会议群组。
  20. 一种非瞬态计算机可读存储介质，存储有计算机程序，所述计算机程序被执行时实现如权利要求1至8中任一项所述的会议管理方法的步骤。
PCT/CN2021/120295 2021-09-24 2021-09-24 会议管理方法、会议管理设备及系统 WO2023044747A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/120295 WO2023044747A1 (zh) 2021-09-24 2021-09-24 会议管理方法、会议管理设备及系统
CN202180002666.9A CN116171572A (zh) 2021-09-24 2021-09-24 会议管理方法、会议管理设备及系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/120295 WO2023044747A1 (zh) 2021-09-24 2021-09-24 会议管理方法、会议管理设备及系统

Publications (1)

Publication Number Publication Date
WO2023044747A1 true WO2023044747A1 (zh) 2023-03-30

Family

ID=85719841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/120295 WO2023044747A1 (zh) 2021-09-24 2021-09-24 会议管理方法、会议管理设备及系统

Country Status (2)

Country Link
CN (1) CN116171572A (zh)
WO (1) WO2023044747A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101344905A (zh) * 2007-07-13 2009-01-14 夏普株式会社 电子会议服务器装置和电子会议系统
US20140074932A1 (en) * 2012-09-13 2014-03-13 Akihiro Mihara Communication system, information processing device, and terminal
CN107479811A (zh) * 2016-06-08 2017-12-15 南京跃豚智能科技有限公司 在会话期间建立与管理会议、记录会议的方法以及移动终端
CN112997206A (zh) * 2018-11-02 2021-06-18 微软技术许可有限责任公司 用于对会议内容进行共享的主动建议

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101344905A (zh) * 2007-07-13 2009-01-14 夏普株式会社 电子会议服务器装置和电子会议系统
US20140074932A1 (en) * 2012-09-13 2014-03-13 Akihiro Mihara Communication system, information processing device, and terminal
CN107479811A (zh) * 2016-06-08 2017-12-15 南京跃豚智能科技有限公司 在会话期间建立与管理会议、记录会议的方法以及移动终端
CN112997206A (zh) * 2018-11-02 2021-06-18 微软技术许可有限责任公司 用于对会议内容进行共享的主动建议

Also Published As

Publication number Publication date
CN116171572A (zh) 2023-05-26

Similar Documents

Publication Publication Date Title
JP6055731B2 (ja) メンバー追加を拡張するためのメッセージングサービスシステム及びその方法
CN111277487B (zh) 消息处理方法、装置、计算机可读存储介质和计算机设备
US10721085B2 (en) Terminal device, conference management system, storage medium and conference management method
JP6357760B2 (ja) 端末装置、プログラム、画面共有方法及び画面共有システム
US10089604B2 (en) Method and apparatus for managing a joint slide show with one or more remote user terminals
US20130246525A1 (en) Instant transition from a public conversation thread to a private chat or instant message environment
TW201537357A (zh) 經由電子使用者介面之協作共同編寫
JP6229360B2 (ja) 通信サーバ、通信システム、プログラム及び通信方法
KR20080064824A (ko) 데이터를 공유하기 위한 협업 시스템에서의 방법 및공유되는 클립보드를 제공하는 협업 애플리케이션에 대한명령어를 포함하는 컴퓨터 판독가능 매체
US10237210B2 (en) Information processing system and method of processing information
TW201537483A (zh) 用以支援多個工作流程之電子通訊式文件儲存
US20130326362A1 (en) Electronic communicating
JP6728950B2 (ja) 情報処理システム、端末装置及びプログラム
CN110597472A (zh) 白板内容显示方法、装置、白板设备和服务器
JP2014063325A (ja) サーバ装置、方法、および、システム
US20120296987A1 (en) Lightweight Messaging with Location Between Users of a Social Networking System
CN102523289A (zh) 一种网络存储截图的方法和系统
JP2014179806A (ja) 通信システム、通信管理装置、及びプログラム
CN110019058B (zh) 文件操作的共享方法和装置
JP2013232819A (ja) 電子会議システム
US20160142361A1 (en) Image with audio conversation system and method utilizing social media communications
KR100874337B1 (ko) 이동통신단말기를 이용한 사진 공유 방법
TWI533243B (zh) 用於整合行事曆系統及雲端儲存系統之整合設備及其整合方法
WO2023044747A1 (zh) 会议管理方法、会议管理设备及系统
JP6729123B2 (ja) 通信システム、リソース管理方法、及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21957880

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE