Conference security method and device, conference system and computer readable storage medium

Abstract

The invention relates to the technical field of data security, and discloses a conference security method, which comprises the following steps: determining a conference storage user under the condition that a conference is ended; acquiring and storing characteristics of conference storage users; under the condition that the conference is restarted, obtaining the characteristics of a restarting user; and determining the use permission of the conference according to a comparison result of the features of the restarting user and the features of the historical conference storage user. Thus, if the comparison result represents that the use of the restart user on the conference is limited, it means that the restart user cannot obtain the conference details corresponding to the limited function, and then the security of the conference information is improved. The invention also discloses a device for conference security, a conference system and a computer readable storage medium.

Description

Technical Field

[0001] The present application relates to the field of data security technology, for example, to a method, device, conference system and computer-readable storage medium for conference security. Background Art

[0002] In current conference scenarios, compared with traditional conference projection products (LED splicing screens, projectors, etc.), all-in-one conference machines are favored by users due to their diverse functions and convenient operation. However, as the products become more and more popular, more and more problems are exposed.

[0003] When the meeting ends, one way to save the meeting is that participants can choose to save the meeting content locally and manually operate the meeting product to automatically generate a link or QR code. Participants can view the meeting content on their mobile phones through the link or QR code. Another way is more traditional, which requires manually saving the meeting content to a local file, but no related links and QR codes can be generated. When viewing the content of the previous meeting, you need to enter the location where the local file is saved to view it.

[0004] In the process of implementing the embodiments of the present disclosure, it is found that there are at least the following problems in the related art:

[0005] After the related technology saves the meeting, anyone can view the meeting files, which has poor security.

[0006] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0007] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0008] The embodiments of the present disclosure provide a method, device, conference system and computer-readable storage medium for conference security, so as to improve the security of conference information.

[0009] In some embodiments, the method for conference security includes: when the meeting ends, determining the user who saved the meeting; obtaining and saving the characteristics of the user who saved the meeting; when the meeting is restarted, obtaining the characteristics of the restarting user; and determining the use rights of the meeting based on the comparison results of the characteristics of the restarting user with the characteristics of the users who saved the historical meetings.

[0010] In some embodiments, the apparatus for conference security includes: a processor and a memory storing program instructions, and the processor is configured to execute the aforementioned method for conference security when running the program instructions.

[0011] In some embodiments, the conference system includes: a conference system body; and the aforementioned device for conference security installed in the conference system body.

[0012] In some embodiments, the computer-readable storage medium stores program instructions, and when the program instructions are run, the aforementioned method for conference security is executed.

[0013] The method, device, conference system, and computer-readable storage medium for conference security provided by the embodiments of the present disclosure can achieve the following technical effects:

[0014] When the meeting ends, the user who saved the meeting is determined, and then the characteristics of the user who saved the meeting are obtained and saved. When the next meeting is restarted, the characteristics of the restarted user are obtained, and then the characteristics of the restarted user are compared with the characteristics of the historical meeting saved user. Based on the comparison result, the restarted user's right to use the meeting is determined. In this way, if the comparison result indicates that the restarted user's use of the meeting is restricted, it means that the restarted user cannot obtain the meeting details corresponding to the restricted function, thereby improving the security of the meeting information.

[0015] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] One or more embodiments are exemplarily described by corresponding drawings, which do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the drawings do not constitute a scale limitation, and wherein:

[0017] Figure 1 is a schematic diagram of a conference system provided by an embodiment of the present disclosure;

[0018] Figure 2 is a schematic diagram of a method for conference security provided by an embodiment of the present disclosure;

[0019] Figure 3 is a schematic diagram of another method for conference security provided by an embodiment of the present disclosure;

[0020] Figure 4 is a schematic diagram of another method for conference security provided by an embodiment of the present disclosure;

[0021] Figure 5 is a schematic diagram of another method for conference security provided by an embodiment of the present disclosure;

[0022] Figure 6 is a schematic diagram of an application for conference security provided by an embodiment of the present disclosure;

[0023] Figure 7 is a schematic diagram of a device for conference security provided by an embodiment of the present disclosure;

[0024] Figure 8 is a schematic diagram of another device for conference security provided by an embodiment of the present disclosure;

[0025] Fig. 9 It is a schematic diagram of another conference system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] In order to be able to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and devices can be simplified for display.

[0027] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0028] Unless otherwise stated, the term "plurality" means two or more.

[0029] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.

[0030] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0031] The term "correspondence" may refer to an association relationship or a binding relationship. The correspondence between A and B means that there is an association relationship or a binding relationship between A and B.

[0032] Combination Figure 1As shown, the embodiment of the present disclosure provides a conference system, including: a conference system body and a feature collection module. After the meeting is over, the user who operates the conference save is defined as the conference save user, and the user who restarts the meeting is defined as the restart user. The feature collection module is used to collect the conference save instruction and the features of the conference save user at the end of the meeting, and to collect the features of the restart user when the meeting is restarted. The conference system body is installed with conference software, and restarting the meeting means restarting the conference software.

[0033] The acquisition function of the feature acquisition module matches the feature. For example, if the feature acquisition module is an image acquisition module, the user's facial features and gestures are collected. If the feature acquisition module is a sound acquisition module, the user's voiceprint is collected. If the feature acquisition module is a fingerprint acquisition module, the user's fingerprint is collected.

[0034] The feature collection module is connected to the conference system body in communication to send the collected features to the conference system body. The conference system processor compares and analyzes the received features to determine whether the features of the restarting user match the features of the user saved in the historical conference, and determines the restarting user's access rights to the conference based on the comparison results.

[0035] Based on the above conference system, combined with Figure 2 As shown, the embodiment of the present disclosure provides a method for conference security, including:

[0036] S101: When a conference ends, the processor determines to save a user in the conference.

[0037] S102: The processor obtains and saves the characteristics of the conference saving user.

[0038] S103: When the conference system is restarted, the processor obtains the characteristics of the restarting user.

[0039] S104: The processor determines the use authority of the conference according to a comparison result between the characteristics of the restarting user and the characteristics of the user saved in the historical conference.

[0040] The processor ends the meeting when receiving an instruction from the user to end the meeting. When the meeting ends, the user who saved the meeting is determined. Then, the characteristics of the user who saved the meeting and the meeting content are obtained, the characteristics of the user who saved the meeting are associated with the meeting content one-to-one, and the characteristics of the user who saved the meeting, the meeting content, and the associated information of the two are saved to the memory. The characteristics of the user who saved the meeting include one or more of facial features, gesture features, voiceprints, fingerprints, etc.

[0041] When the processor receives a request to restart a conference, it obtains the features of the restarting user through the feature collection module. The features of the restarting user are compared with the features of the user saved in the historical conference, and the restarting user's access to the conference is determined based on the comparison results. Some operations of the restarting user on the conference may not be performed, that is, the use is restricted. However, whether it is restricted or not needs to be determined after comparing with the features of the user saved in the historical conference.

[0042] By using the method for conference security provided by the embodiment of the present disclosure, when the meeting ends, the user who saved the meeting is determined, and then the characteristics of the user who saved the meeting are obtained and saved. When the next meeting is restarted, the characteristics of the restarted user are obtained, and then the characteristics of the restarted user are compared with the characteristics of the historical meeting saved user. Based on the comparison result, the restarted user's right to use the meeting is determined. In this way, if the comparison result indicates that the restarted user's use of the meeting is restricted, it means that the restarted user cannot obtain the meeting details corresponding to the restricted functions, thereby improving the security of the meeting information.

[0043] Optionally, the processor determines the conference saving user in the following manner:

[0044] When obtaining a request in a preset form, the processor determines the user who makes the request in the preset form as the conference saving user.

[0045] The processor obtains the request made by the user through the feature acquisition module. The preset request includes: a request expressed in the form of gesture, a request expressed in the form of sound, a request expressed in the form of fingerprint, or one or more of the following.

[0046] When the request received from the user is a request in a preset form, the user who made the request in the preset form is determined as the conference saving user. For example, if the request in the preset form is a specific gesture (such as a fist, an "OK" gesture, etc.), the image acquisition module collects the user screen of the venue in real time and sends the collected screen to the processor in real time. The processor analyzes the received screen, and when it is analyzed that there is a specific gesture in the screen, it determines the user who made the specific gesture, and determines the user as the conference saving user, and then saves the content of the meeting.

[0047] In this way, the conference saving user is determined through a preset request, and the characteristics of the conference saving user and the restarting user are compared to determine the restarting user's permission to use the conference, thus avoiding cumbersome operations.

[0048] Optionally, after determining the user who made the request in the preset form, the identity of the user is further determined. When the identity of the user is the conference host, the user is determined as the conference saving user. In this way, the identity of the conference saving user is limited to prevent any person from having the authority to save the meeting, so as to further improve the security of the conference information.

[0049] Optionally, the restarting user's features are of the same type as the features of the user saved in the historical conference. For example, if the features of the user saved in the historical conference are facial features, then the restarting user's features are also facial features. In this way, the accuracy of the comparison result can be guaranteed, and the restarting user's access rights to the conference can be accurately determined.

[0050] Combination Figure 3 As shown, the embodiment of the present disclosure provides another method for conference security, including:

[0051] S101: When a conference ends, the processor determines to save a user in the conference.

[0052] S102: The processor obtains and saves the characteristics of the conference saving user.

[0053] S103: When the conference system is restarted, the processor obtains the characteristics of the restarting user.

[0054] S114: When the feature of the restarting user matches the feature of the user who saved the historical conference, the processor determines that the conference usage rights are to start a new conference and view the historical conferences associated with the restarting user.

[0055] S124: When the characteristics of the restarting user do not match the characteristics of the user saved in the historical conference, the processor determines that the use permission of the conference is to start a new conference.

[0056] If the comparison result shows that the restarting user's features match the features of the user saved in the historical meeting, it is determined that the restarting user has two rights to use the meeting, namely: opening a new meeting and viewing historical meetings associated with the restarting user. If the comparison result shows that the restarting user's features do not match the features of the user saved in the historical meeting, it is determined that the restarting user has only one right to use the meeting: opening a new meeting. Optionally, when the user's features include multiple types of features, such as facial features and voice features, the features of the restarting user match those of the user saved in the historical meeting when all features are consistent.

[0057] In this way, when the characteristics of the restarting user match the characteristics of the user who saved the historical meeting, the restarting user has the authority to retrieve the historical meeting records, otherwise he only has the authority to start a new meeting. In this way, the people who can access the historical meeting records are restricted, and the security of the meeting information is improved. Moreover, the historical meeting records that the restarting user can retrieve are associated with the restarting user, that is, when the saver of the historical meeting records is the current restarting user, the historical meeting records can be retrieved. In other words, the restarting user cannot retrieve meeting records that are not associated with him. In this way, the scope of the restarting user's access is further limited, and the security of the meeting information is further improved.

[0058] Combination Figure 4 As shown, the embodiment of the present disclosure provides another method for conference security, including:

[0059] S101: When a conference ends, the processor determines to save a user in the conference.

[0060] S102: The processor obtains and saves the characteristics of the conference saving user.

[0061] S103: When the conference system is restarted, the processor obtains the characteristics of the restarting user.

[0062] S104: The processor determines the use authority of the conference according to a comparison result between the characteristics of the restarting user and the characteristics of the user saved in the historical conference.

[0063] S105: The processor controls the running of the conference according to the usage rights of the conference.

[0064] After the processor determines the restarting user's permission to use the meeting, it further controls the operation of the meeting based on the permission to use, thereby facilitating user use. Specifically, if the restarting user has multiple permissions to use, the control conference system will prompt the restarting user with multiple permissions in the form of a pop-up window, such as "whether to retrieve historical meeting records" and "whether to start a new meeting." If the restarting user's permission only allows the user to start a new meeting, the user will only be prompted "whether to start a new meeting" or the new meeting will be started directly. In addition, the prompt method can also be a voice prompt.

[0065] Combination Figure 5 As shown, the embodiment of the present disclosure provides another method for conference security, including:

[0066] S101: When a conference ends, the processor determines to save a user in the conference.

[0067] S102: The processor obtains and saves the characteristics of the conference saving user.

[0068] S103: When the conference system is restarted, the processor obtains the characteristics of the restarting user.

[0069] S104: The processor determines the use authority of the conference according to a comparison result between the characteristics of the restarting user and the characteristics of the user saved in the historical conference.

[0070] S115: The processor determines the target usage intention of the restarting user according to the feedback information of the restarting user.

[0071] S125: The processor controls the conference system to execute a function corresponding to the target usage intention according to the target usage intention.

[0072] After the processor determines the restarting user's permission to use the conference, it prompts the restarting user which permission to use. Optionally, the restarting user can feedback the usage intention to the conference system by clicking the screen, gestures, voice, etc. After the conference system receives the feedback information from the restarting user, the processor analyzes the feedback information and obtains the target usage intention of the restarting user. Then, according to the target usage intention, the conference system is controlled to run the function corresponding to the target usage intention.

[0073] Optionally, no matter the usage permission of the restarting user includes multiple permissions or a single permission, the target usage intention of the restarting user can be determined in the above manner.

[0074] Optionally, when the restarting user's usage authority includes a unique authority, the conference system is controlled to run a function corresponding to the unique usage authority. This omits prompting and asking the user, saves time, and enables the user to use the conference function without feeling.

[0075] Optionally, at S125, the processor controls the conference system to execute a function corresponding to the target usage intention according to the target usage intention, including:

[0076] When the target usage intention is to call the historical meeting record, the processor obtains the target historical meeting record associated with the restarting user.

[0077] The processor sorts the target historical meeting records according to the meeting date and feeds back to the restarting user.

[0078] The processor retrieves the corresponding historical meeting records according to the target calling intention of the restarting user.

[0079] When the target usage intention is to call historical meeting records, historical meeting records associated with the restarting user are obtained, and these historical meeting records are defined as target historical meeting records. It should be noted that when the saver of the historical meeting record is the restarting user, the historical meeting record is associated with the restarting user.

[0080] There may be multiple target historical meeting records. When feeding back these target historical meeting records to the restarting user, the processor sorts the target historical meeting records in order from the most recent to the most distant according to the meeting date of the target historical meeting records, and then feeds them back to the restarting user in the form of a list. In this way, it is convenient for the restarting user to view.

[0081] The restarting user can feedback the target call intention to the conference system by clicking the screen, gestures, voice, etc. The processor retrieves the corresponding historical meeting records according to the target intention for the user to review.

[0082] In practical applications, such as Figure 6 As shown:

[0083] S601, meeting in progress.

[0084] S602: The meeting ends and the user makes a specific gesture.

[0085] S603, the camera recognizes a specific gesture and captures facial features of the user making the specific gesture.

[0086] S604: The processor associates the recognized facial features with the current meeting, and saves the recognized facial features and the content of the current meeting together.

[0087] S605, the user restarts the whiteboard software, the camera identifies the facial features of the current restarting user, and compares them with the facial features stored in the facial feature library. If the comparison is consistent, execute S606. If the comparison is inconsistent, execute S608.

[0088] S606: The processor calls the historical meeting record associated with the restarting user according to the will of the restarting user, or starts a new meeting, and then executes S607.

[0089] S607: The processor sorts the historical meeting records according to their dates.

[0090] S608: The processor starts a new conference.

[0091] In this way, the specific gesture is used as a positioning signal, and the face and other features are used as a link for a specific call, and the two are used in combination. The specific face recognition and feature comparison with the face database are implemented using AI (Artificial Intelligence) algorithms.

[0092] In this way, the face is intelligently locked through gesture recognition, and then the locked face is stored in the local face library. Each face is used as an information retrieval unit. When a specific gesture is recognized, the meeting content will be automatically saved to the relevant folder according to the locked face. When you enter the whiteboard software again next time, the camera will first capture the operator's face and perform feature comparison with the face library through the AI ​​algorithm. When the face comparison with the face library is successful, the system will enter the storage unit under the face and let the operator call the specified meeting content according to the meeting date. If the comparison is unsuccessful or the operator chooses to hold a new meeting after the comparison is successful, the whiteboard will be entered to start a new meeting.

[0093] In this way, the face can be intelligently locked through a specific gesture and the meeting content can be automatically saved to the relevant folder, without manual operation. The face is used as an information retrieval unit and storage and call credentials. Each person's meeting content is saved separately and can only be called by themselves, ensuring the security of meeting information and the convenience of operation.

[0094] Combination Figure 7 As shown, the embodiment of the present disclosure provides a device 70 for conference security, including: a first determination module 71, a first acquisition module 72, a second acquisition module 73, and a second determination module 74. The first determination module 71 is configured to determine the user who saved the conference when the conference ends. The first acquisition module 72 is configured to acquire and save the characteristics of the user who saved the conference. The second acquisition module 73 is configured to acquire the characteristics of the restarting user when the conference is restarted. The second determination module 74 is configured to determine the use authority of the conference based on the comparison result of the characteristics of the restarting user and the characteristics of the historical conference saved user.

[0095] By using the device 70 for conference security provided by the embodiment of the present disclosure, when the meeting ends, the user who saved the meeting is determined, and then the characteristics of the user who saved the meeting are obtained and saved. When the next meeting is restarted, the characteristics of the restarted user are obtained, and then the characteristics of the restarted user are compared with the characteristics of the historical meeting saved user. Based on the comparison result, the restarted user's right to use the meeting is determined. In this way, if the comparison result indicates that the restarted user's use of the meeting is restricted, it means that the restarted user cannot obtain the meeting details corresponding to the restricted function, thereby improving the security of the meeting information.

[0096] Combination Figure 8As shown, the embodiment of the present disclosure provides a device 80 for conference security, including a processor 81 and a memory 82. Optionally, the device 80 may also include a communication interface 83 and a bus 84. The processor 81, the communication interface 83, and the memory 82 may communicate with each other through the bus 84. The communication interface 83 may be used for information transmission. The processor 81 may call the logic instructions in the memory 82 to execute the method for conference security of the above embodiment.

[0097] In addition, the logic instructions in the memory 82 described above may be implemented in the form of software functional units and when sold or used as independent products, may be stored in a computer-readable storage medium.

[0098] The memory 82 is a computer-readable storage medium that can be used to store software programs and computer executable programs, such as program instructions / modules corresponding to the method in the embodiment of the present disclosure. The processor 81 executes the function application and data processing by running the program instructions / modules stored in the memory 82, that is, the method for conference security in the above embodiment is implemented.

[0099] The memory 82 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory 82 may include a high-speed random access memory and may also include a non-volatile memory.

[0100] Combination Fig. 9 As shown, the present disclosure embodiment provides a conference system 90, including: a conference system body 、 Feature collection module, and the above-mentioned device 70 (80) for conference security. The device 70 (80) for conference security is installed in the conference system body. The installation relationship described here is not limited to placement inside the conference system body, but also includes installation connections with other components of the conference system 90, including but not limited to physical connections, electrical connections or signal transmission connections. It can be understood by those skilled in the art that the device 70 (80) for conference security can be adapted to a feasible product body, thereby realizing other feasible embodiments.

[0101] An embodiment of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to execute the above-mentioned method for conference security.

[0102] The technical solution of the embodiment of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium and includes one or more instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiment of the present disclosure. The aforementioned storage medium may be a non-transient storage medium, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes.

[0103] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent only possible changes. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

[0104] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. The technicians may use different methods for each specific application to implement the described functions, but such implementations should not be considered to exceed the scope of the embodiments of the present disclosure. The technicians may clearly understand that, for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above may refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0105] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.

[0106] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and the block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based system that performs the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.

Claims

1. A method for conference security, characterized in that: include: When the meeting ends, determine the user who saved the meeting; Get and save the characteristics of the user who saved the meeting; In case of conference restart, obtain the characteristics of the restarting user; The use rights of the conference are determined based on the comparison results between the characteristics of the restarting user and the characteristics of the user who saved the historical conference.

2. The method according to claim 1, characterized in that Determine the user who saved the meeting by: When a request in a preset form is obtained, the user who makes the request in the preset form is determined as the conference saving user.

3. The method according to claim 1, characterized in that The restart user's features are the same as the features of the historical session saved user.

4. The method according to claim 1, characterized in that: Based on the comparison between the restarting user's characteristics and the characteristics of the user who saved the historical conference, the conference usage rights are determined, including: When the characteristics of the restarting user match the characteristics of the user who saved the historical conference, the conference usage permission is determined to be starting a new conference and viewing the historical conferences associated with the restarting user; When the characteristics of the restarting user do not match the characteristics of the user who saved the historical conference, the use permission of the conference is determined to be to start a new conference.

5. The method according to any one of claims 1 to 4, characterized in that After determining the use rights of the conference, the method further includes: Control the conference operation according to the conference usage permissions.

6. The method according to claim 5, characterized in that Control the operation of the conference according to the conference usage rights, including: Determine the target usage intention of the restarting user according to the feedback information of the restarting user; According to the target usage intention, the conference system is controlled to run the function corresponding to the target usage intention.

7. The method according to claim 6, characterized in that According to the target usage intent, control the conference software to run the functions corresponding to the target usage intent, including: When the target usage intention is to call historical conference records, obtain the target historical conference records associated with the restarting user; Sort the target historical meeting records by meeting date and provide feedback to the restarting user; According to the target calling intention of the restarting user, the corresponding historical meeting records are retrieved.

8. A device for conference security, comprising a processor and a memory storing program instructions, characterized in that: The processor is configured to execute the method for conference security according to any one of claims 1 to 7 when running the program instructions.

9. A conference system, characterized in that: include: Conference system body; The feature collection module is connected to the conference system body for collecting the features of the conference saving user and the features of the restarting user; The device for conference security as described in claim 8 is installed in the conference system body.

10. A computer-readable storage medium storing program instructions, characterized in that: When the program instructions are executed, the computer is used to execute the method for conference security according to any one of claims 1 to 7.

Images