Conference processing method and device, electronic equipment and storage medium

Abstract

The invention provides a conference processing method and device, electronic equipment and a storage medium, and the method comprises the steps: monitoring the equipment state of each conference client accessing a target conference, so as to determine the offline type of the conference client based on the current conference state of the target conference when the equipment state is an offline state; therefore, the corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference sharing file of the target conference according to the file deletion instruction, so that the security of the conference sharing file is improved under the condition of ensuring normal operation of the conference, the conference sharing file leakage caused by conference holding is avoided, and the conference experience is improved. The method is suitable for confidential conferences.

Description

Technical Field

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

[0002] In conference scenarios, the traditional way is to distribute paper files to participants during the meeting to achieve file sharing. However, with the continuous development of Internet technology, most of the shared files in conference scenarios have transitioned from paper files to paperless files. In the prior art, paperless file sharing in conference scenarios can be achieved through cloud storage platforms, shared file platforms, or conference software.

[0003] In some confidential meetings, it is necessary to ensure the security of shared files to prevent leaks. However, in the existing technology, when files are shared through shared file platforms or conference software, the security is low, which is easy to cause leaks and cannot meet user needs. Summary of the invention

[0004] The present application provides a conference processing method, device, electronic device and storage medium, aiming to solve the technical problems that the prior art has low security when sharing conference files in conference scenarios, is prone to conference file leakage, and is not applicable to confidential conference scenarios.

[0005] In one aspect, the present application provides a conference processing method, the method comprising:

[0006] Monitoring the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one;

[0007] If the device state is an offline state, determining the offline type of the conference client based on the current conference state of the target conference; the current conference state is used to indicate whether the target conference is in progress;

[0008] A corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference shared file of the target conference according to the file deletion instruction.

[0009] In some implementation schemes of the present application, the step of generating a corresponding file deletion instruction according to the offline type and controlling the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction includes:

[0010] If the offline type is active offline, the generated file deletion instruction is a logical deletion instruction, and the conference client is controlled to logically delete the acquired conference shared file according to the logical deletion instruction;

[0011] If the offline type is passive offline, the generated file deletion instruction is a physical deletion instruction, and the conference client is controlled to physically delete the acquired conference shared file according to the physical deletion instruction.

[0012] In some implementation schemes of the present application, if the device state is an offline state, determining the offline type of the conference client based on the current conference state of the target conference includes:

[0013] If the current conference status of the target conference is in progress, the offline type of the conference client is active offline;

[0014] If the current conference state of the target conference is that the conference is ended, the offline type of the conference client is passive offline.

[0015] In some implementation schemes of the present application, before monitoring the device status of each conference client accessing the target conference, the method further includes:

[0016] Receiving a conference access request sent by the conference client;

[0017] According to the conference access request, allowing the conference client to access the target conference;

[0018] Query whether there is a logically deleted file in the conference client;

[0019] If the logically deleted file exists in the conference client and the logically deleted file matches the target conference, the conference client is controlled to restore the logically deleted file to obtain the conference shared file of the target conference.

[0020] If the logically deleted file exists in the conference client, and the logically deleted file does not match the target conference, the conference client is controlled to physically delete the logically deleted file.

[0021] In some implementation schemes of the present application, if the device status is an offline status, after determining the offline type of the conference client based on the current conference status of the target conference, the method further includes:

[0022] Determining whether the conference shared file in the conference client is modified;

[0023] If the conference shared file is modified, obtaining the modified conference shared file from the conference client and storing it;

[0024] The generating a corresponding file deletion instruction according to the offline type, and controlling the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction, includes:

[0025] A corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference shared file of the target conference and the modified conference shared file according to the file deletion instruction.

[0026] In some implementation schemes of the present application, before monitoring the device status of each conference client accessing the target conference, the method includes:

[0027] Obtaining file permissions of each conference client accessing the target conference; the file permissions include: at least one of add, delete, modify, and check;

[0028] The conference shared file is given permission according to the file permission of the conference client, and the conference shared file after the permission setting is sent to the conference client.

[0029] In some implementation schemes of the present application, before obtaining the file permissions of the conference client, the method further includes:

[0030] receiving a conference access request from the conference client, wherein the conference access request includes: a client identifier and a device access identifier of the conference client;

[0031] If the conference access request meets a preset condition, a conference identifier is sent to the conference client, so that the conference client accesses the target conference based on the conference identifier.

[0032] On the other hand, an embodiment of the present application provides a conference processing device, the conference processing device comprising:

[0033] A monitoring module, used to monitor the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one;

[0034] A type determination module, configured to determine the offline type of the conference client based on the current conference state of the target conference if the device state is an offline state; the current conference state is used to indicate whether the target conference is in progress;

[0035] The control module is used to generate a corresponding file deletion instruction according to the offline type, and control the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction.

[0036] On the other hand, an embodiment of the present application provides an electronic device, the electronic device comprising:

[0037] one or more processors;

[0038] Memory; and

[0039] One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the processor to implement the steps in any one of the conference processing methods described above.

[0040] On the other hand, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is loaded by a processor to execute the steps in the conference processing method as described in any one of the above items.

[0041] The present application provides a conference processing method, device, electronic device and storage medium, which monitor the device status of each conference client accessing a target conference, and when the device status is offline, determine the offline type of the conference client based on the current conference status of the target conference, thereby generating a corresponding file deletion instruction according to the offline type, and controlling the conference client to delete the acquired conference shared files of the target conference according to the file deletion instruction, thereby improving the security of conference shared files while ensuring the normal operation of the conference, avoiding the leakage of conference shared files due to the convening of the meeting, and is suitable for confidential meetings. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0043] Figure 1 It is a scenario diagram of the conference processing method provided in the embodiment of the present application;

[0044] Figure 2 It is one of the flowcharts of the conference processing method provided in the embodiment of the present application;

[0045] Figure 3 This is the second flowchart of the conference processing method provided in the embodiment of the present application;

[0046] Figure 4 It is a flowchart of an embodiment of the conference processing method provided in the embodiments of the present application;

[0047] Figure 5 is a structural diagram of a conference processing device provided in an embodiment of the present application;

[0048] Figure 6 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0050] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, which are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0051] In the embodiment of the present application, "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / ", unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.

[0052] In this application, the word "exemplary" is used to mean "serving as an example, illustration, or illustration." Any embodiment described in this application as "exemplary" is not necessarily to be construed as being preferred or advantageous over other embodiments. The following description is given to enable any person skilled in the art to implement and use the invention. In the following description, details are listed for the purpose of explanation. It should be understood that a person of ordinary skill in the art can recognize that the invention can be implemented without using these specific details. In other instances, well-known structures and processes are not elaborated in detail to avoid obscuring the description of the invention with unnecessary details. Therefore, the present invention is not intended to be limited to the embodiments shown, but is consistent with the widest scope consistent with the principles and features disclosed in this application.

[0053] As can be seen from the background technology, in the prior art, paperless file sharing in conference scenarios is usually achieved through cloud storage platforms, shared file platforms or conference software. However, although cloud storage platforms and conference sharing platforms provide convenient cloud storage and multi-person collaborative editing functions, in conference scenarios, it is often necessary to upload the files to be shared to the cloud storage platform or conference sharing platform in advance so that participants can download the shared files through the cloud storage platform or conference sharing platform. This process is also prone to data leakage. Although conference software provides convenient and fast file and screen sharing functions, there are also certain security risks. The shared files are often not recyclable, resulting in file leakage.

[0054] Based on this, in order to improve the security of file sharing in conference scenarios, the embodiments of the present application provide a conference processing method, device, electronic device and storage medium, which are described in detail below.

[0055] The conference processing method provided in the embodiment of the present application is applied to a conference processing device, which is arranged in an electronic device, and one or more processors, memories, and one or more applications are arranged in the electronic device, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the conference processing method provided in the embodiment of the present application. The above-mentioned electronic device can be a terminal, or it can be a device such as a server. Among them, the above-mentioned server can be an independent server, or it can be a server network or server cluster composed of servers, which includes but is not limited to a computer, a network host, a single network server, a plurality of network servers or a cloud server composed of a plurality of servers. Among them, the cloud server is composed of a large number of computers or network servers based on cloud computing. The above-mentioned terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop computer, a game console, or a personal computer (Personal Computer, PC) and other devices.

[0056] like Figure 1 As shown, Figure 1 A scene diagram of the conference processing method provided in the embodiment of the present application, wherein the conference scene provided in the embodiment of the present application includes: multiple conference clients 100, an electronic device 200 (the electronic device 200 is integrated with a conference processing device), and a computer storage medium corresponding to the conference processing method is run in the electronic device 200 to execute the steps in the conference processing method. The conference client 100 corresponds to the participant one by one, and the files in the conference are shared with the participant through the conference client 100. The conference client can be a terminal, such as a tablet computer, a personal computer, and other devices.

[0057] Understandably, Figure 1The number and types of devices of the conference client 100 included in the scenario of the conference processing method described in the present application are not specifically limited and can be adjusted according to actual conditions.

[0058] The electronic device 200 in the embodiment of the present application is mainly used to: monitor the device status of each conference client 100 accessing the target conference; if the device status is offline, determine the offline type of the conference client 100 based on the current conference status of the target conference, and then generate a corresponding file deletion instruction based on the offline type of the conference client 100, and control the conference client to delete the acquired conference shared files of the target conference according to the file deletion instruction.

[0059] Understandably, Figure 1 The application scenario shown in the figure is only one application scenario of the present application solution and does not constitute a limitation on the application scenario of the present application solution. Other application scenarios may also include Figure 1 More or less meeting clients as shown in, for example Figure 1 Only three conference clients are shown, and it is understandable that the scenario of the conference processing method can also include more conference clients, which are not specifically limited. In addition, the embodiment of the present application does not specifically limit the device types of conference clients and electronic devices, and can be adjusted according to actual conditions.

[0060] In addition, the electronic device 200 may further include a memory, and may be provided with a display device, or the electronic device 200 may not be provided with a display device and may be connected to an external display device in a communication manner, and the display device may be used to output the result of the execution of the conference processing method in the electronic device. The electronic device 200 may also access a background server, and the background server stores information related to the conference processing method. It is understandable that the background server may be local to the electronic device or may be provided in the cloud.

[0061] It should be noted that Figure 1 The scenario diagram of the conference processing method shown is merely an example. The scenario of the conference processing method described in the embodiment of the present application is intended to more clearly illustrate the technical solution of the embodiment of the present application and does not constitute a limitation on the technical solution provided in the embodiment of the present application.

[0062] like Figure 2 As shown, Figure 2 The following is a flow chart of a conference processing method provided in an embodiment of the present application. The conference processing method includes at least the following steps:

[0063] S201, monitoring the device status of each conference client accessing the target conference.

[0064] This embodiment is described by taking the application of the conference processing method to an electronic device as an example, and the type of the electronic device is not specifically limited.

[0065] The device status of the conference client includes an offline status and an online status. The offline status indicates that the conference client has left the target conference, and the online status indicates that the conference client is in the target conference. In addition, as can be seen from the foregoing, the conference client and the participants of the target conference correspond one to one.

[0066] In an embodiment of the present application, the electronic device monitors each conference client accessing the target conference in real time to obtain the device status of each conference client.

[0067] In addition, before monitoring the device status of each conference client accessing the target conference, the electronic device sends a conference shared file to the conference client accessing the target conference so that the participants can participate in the target conference. It is understandable that the electronic device can send a conference sharing request to each conference client accessing the target conference, or it can only send a conference shared file to the conference client that sent the conference file request, which is not specifically limited in the embodiments of the present application.

[0068] It should be noted that the electronic device can monitor multiple target conferences at the same time, and the conference processing method provided by the embodiment of the present application can be used for each target conference, and the number of target conferences that the electronic device can monitor is not limited in the embodiment of the present application. Of course, an electronic device can also correspond to only one target conference.

[0069] For example, electronic device A monitors target conference 1 and target conference 2 at the same time. The conference clients accessing target conference 1 include conference clients B1~Bn, and the conference clients accessing target conference 2 include conference clients D1~Dn. Then electronic device A simultaneously monitors the device status of conference clients B1~Bn accessing target conference 1 and conference clients D1~Dn accessing target conference 2.

[0070] For another example, electronic device A1 monitors target conference 1, and electronic device A2 monitors target conference 2. Then electronic device A1 monitors the device status of conference clients B1~Bn accessing target conference 1, and electronic device A2 monitors the device status of conference clients D1~Dn accessing target conference 2.

[0071] S202: If the device state is offline, determine the offline type of the conference client based on the current conference state of the target conference.

[0072] The current conference status is used to indicate whether the target conference is in progress. In the embodiment of the present application, the current conference status may include: conference in progress, conference ended. The above offline types include: active offline, passive offline.

[0073] Specifically, if the current conference state of the target conference is conference in progress, the offline type of the conference client is active offline; if the current conference state of the target conference is conference ended, the offline type of the conference client is passive offline.

[0074] It should be noted that as long as the device status of the conference client is offline and the current conference status of the target conference is in progress, regardless of whether the conference client leaves the target conference due to network reasons or the user controls the conference client to leave the target conference, the offline type of the conference client is active offline. If the conference client leaves the target conference due to the end of the target conference, regardless of whether the end of the target conference is premature or automatic, the offline type of the conference client is passive offline.

[0075] S203, generating a corresponding file deletion instruction according to the offline type, and controlling the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction.

[0076] In some embodiments of the present application, if the offline type is active offline, the file deletion instruction generated is a logical deletion instruction, and the conference client is controlled to logically delete the acquired conference shared files according to the logical deletion instruction; if the offline type is passive offline, the file deletion instruction generated is a physical deletion instruction, and the conference client is controlled to physically delete the acquired conference shared files according to the physical deletion instruction.

[0077] In an embodiment of the present application, if the offline type of the conference client is active offline, the electronic device can generate a first destruction instruction (i.e., a logical deletion instruction) and send it to the conference client, and the conference client logically deletes the conference shared files according to the first destruction instruction; if the offline type of the conference client is passive offline, the electronic device can generate a second destruction instruction (i.e., a physical deletion instruction) and send it to the conference client, and the conference client physically deletes the conference shared files according to the second destruction instruction.

[0078] The above logical deletion means that the file is not actually deleted, but the first byte of the file name is changed to a character that the operating system cannot recognize. This deletion operation is reversible, that is, the deleted file can be restored through appropriate files or tools. The above physical deletion means that the magnetic storage area used for file storage is actually erased or cleared. This deleted file is irreversible.

[0079] It can be understood that if the offline type of the conference client is active offline, it means that the target conference accessed by the conference client has not ended at this time. Therefore, the conference shared files in the conference client can be logically deleted so that the subsequent conference client can access the target conference again; if the offline type of the conference client is passive offline, it means that the target conference has ended at this time and can be directly physically deleted, thereby further improving the user experience while ensuring the security of the conference shared files.

[0080] The conference processing method provided in the embodiment of the present application monitors the device status of each conference client accessing the target conference, and when the device status is offline, determines the offline type of the conference client based on the current conference status of the target conference, thereby generating a corresponding file deletion instruction according to the offline type, and controlling the conference client to delete the acquired conference shared files of the target conference according to the file deletion instruction, thereby improving the security of conference shared files while ensuring the normal operation of the meeting, avoiding the leakage of conference shared files due to the convening of the meeting, and is suitable for confidential meetings.

[0081] In some embodiments of the present application, if the device status is offline, after determining the offline type of the conference client based on the current conference status of the target conference, the conference processing method provided by the embodiments of the present application may also include: determining whether the conference shared file in the conference client has been modified; if the conference shared file has been modified, obtaining the modified conference shared file from the conference client and storing it.

[0082] At this time, the above-mentioned control of the conference client to perform corresponding deletion operations on the acquired target conference shared files based on the offline type includes: based on the offline type, controlling the conference client to perform corresponding deletion operations on the acquired target conference shared files and the modified conference shared files.

[0083] In some actual scenarios, participants can make corresponding modifications to the conference shared files through the corresponding conference client, such as adding annotations or adding highlight marks, etc. In this case, when the conference processing method provided in the embodiment of the present application determines that the device status of the conference client is offline, the electronic first determines whether the conference shared file of the conference client accessing the target conference has been modified. If the conference shared file has been modified, the modified conference shared file is obtained and stored; after the electronic device stores the modified conference shared file, based on the offline type of the conference client, the conference client is controlled to delete the acquired conference shared file and the modified conference shared file. Through the above embodiment, the conference shared files modified by the conference client can be backed up for subsequent operations in the meeting to improve the user experience; in addition, the modified conference shared files in the conference client are also deleted, thereby further improving the security of the conference shared files in the conference scenario.

[0084] In an actual conference scenario, after the target conference starts, the electronic device may send the conference shared file to the conference client connected to the target conference. However, in some special scenarios, the conference client allows modification by some or all participants.

[0085] Therefore, in some embodiments of the present application, before monitoring the device status of each conference client accessing the target conference, the conference processing method may also include: obtaining file permissions of each conference client accessing the target conference, setting permissions for conference shared files according to the file permissions of the conference client, and sending the conference shared files after permission settings to the conference client.

[0086] The file permissions include at least one of add, delete, modify, and check.

[0087] It can be understood that adding means adding new data to the conference shared file, deleting means deleting the existing data in the conference shared file, modifying means updating the existing data in the conference shared file, and checking means reading the existing data in the conference shared file. In addition, the conference client that receives the conference shared file has the file permission of "checking", that is, the participants of the conference client that receives the conference shared file can view the conference shared file.

[0088] In an embodiment of the present application, corresponding file permissions may be pre-configured for each conference client. Specifically, the device identification of the conference client may be associated with the file permissions configured for the conference client to determine the corresponding file permissions through the device identification of the conference client.

[0089] For conference shared files that have been set with permissions, only the permitted file permission operations can be performed in the conference client. For example, if the file permission of conference shared file M of conference client B1 is "check" and "add", conference client B1 can only check the conference shared file M and add new data to the conference shared file M, such as annotating the conference shared file M. For another example, if the file permission of conference shared file M of conference client B2 is "check", conference client B2 can only check the conference shared file M and cannot perform other operations on the conference shared file.

[0090] In an embodiment of the present application, permissions are set for conference shared files according to the file permissions of the conference client accessing the target conference, thereby further improving the security of the conference shared files and preventing them from being tampered with at will.

[0091] Furthermore, before obtaining the file permissions of the conference client, the conference processing method provided in the embodiment of the present application also includes: receiving a conference access request from the conference client, the conference access request including: a client identifier and a device access identifier of the conference client; if the conference access request meets the preset conditions, sending the conference identifier to the conference client so that the conference client can access the target conference based on the conference identifier.

[0092] The above-mentioned client identifier is used to indicate a unique conference client, such as a serial number (SN). The device access identifier is entered by the participant in the conference client. In an embodiment of the present application, the electronic device can pre-generate a preset connection identifier and send it to the participant's user terminal (such as a mobile phone, tablet computer, etc.), and the participant enters the received preset connection identifier in the conference client as the device connection identifier.

[0093] Furthermore, if the client identifier in the conference access request is a preset device identifier and the device access identifier is a preset connection identifier, it means that the conference access request meets the preset condition, otherwise it does not meet the preset condition.

[0094] In the embodiment of the present application, double verification is performed through the client identification and the device identification, thereby further improving the security of conference shared files.

[0095] In some optional embodiments, before monitoring the device status of each conference client accessing the target conference, such as Figure 3 As shown, the conference processing method at least includes steps S301-S305:

[0096] S301: Receive a conference access request sent by a conference client.

[0097] S302: Allow the conference client to access the target conference according to the conference access request.

[0098] In the embodiment of the present application, the foregoing embodiment may be referred to to determine whether to allow the conference client to access the target conference, which will not be described in detail here.

[0099] S303, query whether there is a logically deleted file in the conference client.

[0100] The logically deleted file is a file obtained by logically deleting the conference shared file, and the logically deleted file cannot be recognized by the operating system.

[0101] S304: If there is a logically deleted file in the conference client, and the logically deleted file matches the target conference, the conference client is controlled to restore the logically deleted file to obtain the conference shared file of the target conference.

[0102] In an embodiment of the present application, after controlling the conference client to logically delete the conference shared file, the obtained logically deleted file can be associated with the conference identifier of the target conference, for example, the conference identifier of the target conference is used as a label for the logically deleted file.

[0103] At this time, when there is a logically deleted file in the conference client, first determine the conference identifier corresponding to the logically deleted file, and then if the conference identifier of the logically deleted file matches the conference identifier of the target conference, it means that the logically deleted file matches the target conference, otherwise it does not match. If the logically deleted file matches the target conference, there is no need to reapply for the conference shared file of the target conference, and the conference client is directly controlled to restore the logically deleted file, and the conference shared file of the target conference is directly obtained, which reduces communication and further reduces the risk of conference shared files being leaked.

[0104] S305: If the logically deleted file exists in the conference client, and the logically deleted file does not match the target conference, the conference client is controlled to physically delete the logically deleted file.

[0105] In an embodiment of the present application, if there is a logically deleted file in the conference client and the logically deleted file does not match the target conference, the conference client can be directly controlled to physically delete the logically deleted file, thereby further improving the security of the conference shared files.

[0106] Based on this, Figure 4 A schematic diagram of a scenario of an embodiment of a conference processing method provided in an embodiment of the present application, such as Figure 4 As shown, the process of the conference processing method includes: the electronic device pre-generates a device connection identifier as a preset connection identifier, the user enters the device connection identifier in the corresponding conference client, the conference client terminal generates a conference access request according to the device connection identifier and the client identifier, the electronic device determines whether the conference client is configured according to the conference access request, and if the conference client is configured, sends a connection token and a conference number to the conference client; the conference client accesses the target conference according to the connection token and the conference number, and checks whether there is a logically deleted file. If there is no logically deleted file or the logically deleted file does not match the target conference, a conference file request is sent to the electronic device; the electronic device determines the file permissions of the conference client according to the conference file request, and sends the conference shared file after the permission is set through the file permissions to the conference client; after the target conference ends, the electronic device checks whether the conference shared file in the conference client is modified, and if it is modified, controls the conference client to upload the modified conference shared file for file backup, and then controls the conference client to delete the conference shared file and the modified conference shared file.

[0107] like Figure 5 As shown, Figure 5 This is a structural diagram of a conference processing device provided in an embodiment of the present application. The conference processing device 500 includes:

[0108] Monitoring module 510, used to monitor the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one;

[0109] The type determination module 520 is used to determine the offline type of the conference client based on the current conference state of the target conference if the device state is an offline state; the current conference state is used to indicate whether the target conference is in progress;

[0110] The control module 530 is used to control the conference client to perform a corresponding deletion operation on the acquired conference shared file of the target conference based on the offline type.

[0111] In some embodiments of the present application, the control module 530 is specifically used to:

[0112] If the offline type is active offline, the generated file deletion instruction is a logical deletion instruction, and the conference client is controlled to logically delete the acquired conference shared file according to the logical deletion instruction;

[0113] If the offline type is passive offline, the generated file deletion instruction is a physical deletion instruction, and the conference client is controlled to physically delete the acquired conference shared file according to the physical deletion instruction.

[0114] In some embodiments of the present application, the type determination module 520 is specifically used to:

[0115] If the current conference status of the target conference is in progress, the offline type of the conference client is active offline;

[0116] If the current conference state of the target conference is that the conference is ended, the offline type of the conference client is passive offline.

[0117] In some embodiments of the present application, the conference processing device further includes an access management module 540 and a file management module 550;

[0118] The access management module 540 is used to receive a conference access request sent by the conference client; and to allow the conference client to access the target conference according to the conference access request;

[0119] The file management module 550 is used to query whether there is a logically deleted file in the conference client; if the logically deleted file exists in the conference client and the logically deleted file matches the target conference, then control the conference client to restore the logically deleted file to obtain the conference shared file of the target conference; and if the logically deleted file exists in the conference client and the logically deleted file does not match the target conference, then control the conference client to physically delete the logically deleted file.

[0120] In some embodiments of the present application, the file management module 550 is further used to determine whether the conference shared file in the conference client is modified; and if the conference shared file is modified, obtain and store the modified conference shared file from the conference client.

[0121] At this time, the control module 530 is specifically used to generate a corresponding file deletion instruction according to the offline type, and control the conference client to delete the acquired conference shared file of the target conference and the modified conference shared file according to the file deletion instruction.

[0122] In some embodiments of the present application, the conference processing device 500 also includes a file permission management module 560, which is used to obtain the file permissions of each of the conference clients accessing the target conference; the file permissions include: at least one of: add, delete, modify, and check; and is used to set permissions for the conference shared files according to the file permissions of the conference client, and send the conference shared files with permission settings to the conference client.

[0123] In some embodiments of the present application, the access management module 540 is also used to receive a conference access request from the conference client, the conference access request including: a client identifier and a device access identifier of the conference client; and to send a conference identifier to the conference client if the conference access request meets a preset condition, so that the conference client accesses the target conference based on the conference identifier.

[0124] The embodiment of the present invention further provides an electronic device, such as Figure 6 As shown, Figure 6 1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application, wherein the electronic device comprises:

[0125] one or more processors;

[0126] Memory; and

[0127] One or more applications, wherein the one or more applications are stored in the memory and are configured so that the processor executes the steps of the conference processing method described in any of the above embodiments.

[0128] Specifically, the electronic device may include one or more processing core processors 601, one or more computer storage media memories 602, a power supply 603, an input unit 604 and other components. Those skilled in the art will understand that Figure 6 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0129] The processor 601 is the control center of the electronic device. It uses various interfaces and lines to connect various parts of the entire electronic device. By running or executing software programs and / or modules stored in the memory 602, and calling data stored in the memory 602, it executes various functions of the electronic device and processes data, thereby monitoring the electronic device as a whole. Optionally, the processor 601 may include one or more processing cores; preferably, the processor 601 may integrate an application processor and a modem processor, wherein the application processor mainly processes performance adjustment systems, user interfaces, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 601.

[0130] The memory 602 can be used to store software programs and modules. The processor 601 executes various functional applications and data processing by running the software programs and modules stored in the memory 602. The memory 602 may mainly include a program storage area and a data storage area, wherein the program storage area may store a performance adjustment system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 602 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 602 may also include a memory controller to provide the processor 601 with access to the memory 602.

[0131] The electronic device also includes a power supply 603 for supplying power to each component. Preferably, the power supply 603 can be logically connected to the processor 601 through a power management system, so as to manage charging, discharging, power consumption and other functions through the power management system. The power supply 603 can also include one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, power status indicators and other arbitrary components.

[0132] The electronic device may further include an input unit 604, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0133] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically in this embodiment, the processor 601 in the electronic device will load the executable files corresponding to the processes of one or more applications into the memory 602 according to the following instructions, and the processor 601 will run the conference processing application stored in the memory 602; thereby realizing various functions, as follows:

[0134] Monitoring the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one;

[0135] If the device state is an offline state, determining the offline type of the conference client based on the current conference state of the target conference; the current conference state is used to indicate whether the target conference is in progress;

[0136] A corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference shared file of the target conference according to the file deletion instruction.

[0137] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be accomplished by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer storage medium and loaded and executed by a processor.

[0138] To this end, an embodiment of the present invention provides a computer storage medium, which may include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in any conference processing method provided in the embodiment of the present invention. For example, the computer program can be loaded by the processor to execute the following steps:

[0139] Monitoring the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one;

[0140] If the device state is an offline state, determining the offline type of the conference client based on the current conference state of the target conference; the current conference state is used to indicate whether the target conference is in progress;

[0141] A corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference shared file of the target conference according to the file deletion instruction.

[0142] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the detailed description of other embodiments above, and will not be repeated here.

[0143] In specific implementation, the above units or structures can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units or structures can refer to the previous method embodiments, which will not be repeated here.

[0144] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0145] The above is a detailed introduction to a conference processing method provided in an embodiment of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A conference processing method, characterized in that: The method comprises: Monitoring the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one; If the device state is an offline state, determining the offline type of the conference client based on the current conference state of the target conference; the current conference state is used to indicate whether the target conference is in progress; A corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference shared file of the target conference according to the file deletion instruction.

2. The conference processing method according to claim 1, characterized in that: The generating a corresponding file deletion instruction according to the offline type, and controlling the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction, comprises: If the offline type is active offline, the generated file deletion instruction is a logical deletion instruction, and the conference client is controlled to logically delete the acquired conference shared file according to the logical deletion instruction; If the offline type is passive offline, the generated file deletion instruction is a physical deletion instruction, and the conference client is controlled to physically delete the acquired conference shared file according to the physical deletion instruction.

3. The conference processing method according to claim 1, characterized in that: If the device state is an offline state, determining the offline type of the conference client based on the current conference state of the target conference includes: If the current conference status of the target conference is in progress, the offline type of the conference client is active offline; If the current conference state of the target conference is that the conference is ended, the offline type of the conference client is passive offline.

4. The conference processing method according to claim 1, characterized in that: Before monitoring the device status of each conference client accessing the target conference, the method further includes: Receiving a conference access request sent by the conference client; According to the conference access request, allowing the conference client to access the target conference; Query whether there is a logically deleted file in the conference client; If the logically deleted file exists in the conference client, and the logically deleted file matches the target conference, controlling the conference client to restore the logically deleted file to obtain the conference shared file of the target conference; If the logically deleted file exists in the conference client, and the logically deleted file does not match the target conference, the conference client is controlled to physically delete the logically deleted file.

5. The conference processing method according to claim 1, characterized in that: If the device state is an offline state, after determining the offline type of the conference client based on the current conference state of the target conference, the method further includes: Determining whether the conference shared file in the conference client is modified; If the conference shared file is modified, obtaining the modified conference shared file from the conference client and storing it; The generating a corresponding file deletion instruction according to the offline type, and controlling the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction, includes: A corresponding file deletion instruction is generated according to the offline type, and the conference client is controlled to delete the acquired conference shared file of the target conference and the modified conference shared file according to the file deletion instruction.

6. The conference processing method according to claim 1, characterized in that: Before monitoring the device status of each conference client accessing the target conference, the method includes: Obtaining file permissions of each conference client accessing the target conference; the file permissions include: at least one of add, delete, modify, and check; The conference shared file is given permission according to the file permission of the conference client, and the conference shared file after the permission setting is sent to the conference client.

7. The conference processing method according to claim 6, characterized in that: Before obtaining the file permissions of each conference client accessing the target conference, the method further includes: receiving a conference access request from the conference client, wherein the conference access request includes: a client identifier and a device access identifier of the conference client; If the conference access request meets a preset condition, a conference identifier is sent to the conference client, so that the conference client accesses the target conference based on the conference identifier.

8. A conference processing device, characterized in that: The conference processing device comprises: A monitoring module, used to monitor the device status of each conference client accessing the target conference; the conference client and the participants of the target conference correspond one to one; A type determination module, configured to determine the offline type of the conference client based on the current conference state of the target conference if the device state is an offline state; the current conference state is used to indicate whether the target conference is in progress; The control module is used to generate a corresponding file deletion instruction according to the offline type, and control the conference client to delete the acquired conference shared file of the target conference according to the file deletion instruction.

9. An electronic device, characterized in that: The electronic device comprises: one or more processors; Memory; and One or more applications, wherein the one or more applications are stored in the memory and are configured to be executed by the processor to implement the steps in the conference processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the conference processing method according to any one of claims 1 to 7.

Images