Conference access control method, device, server and storage medium

Abstract

The present application provides a conference access control method, device, server and storage medium, the method comprising: obtaining a conference access request initiated by a first conference client, the conference access request carries information of a target conference credential and a logged-in user of the first conference client, the target conference credential is used to indicate the target network conference requested for access by the conference access request; obtaining a conference member list of the target network conference, the conference member list includes information of conference participants set in the target network conference; if the logged-in user of the first conference client does not belong to the conference members in the conference member list, querying whether the target network conference belongs to a stored network conference with a credential sharing mark; if the target network conference belongs to a stored network conference with a credential sharing mark, responding to the access content requested by the conference access request. The scheme of the present application can improve the security of conference data related to network conferences.

Description

Technical Field

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

[0002] With the continuous development of network technology, network conferencing is increasingly widely used. In actual applications, users can initiate and join network conferencing through conference applications (such as network conferencing applications or instant messaging applications that support network conferencing).

[0003] Since online conferences are relatively open, as long as the conference credential information (such as conference ID, etc.) of the online conference is obtained, a certain created online conference can be accessed through the conference application. For example, the client of the conference application uses the conference ID of a certain created online conference to join the online conference or obtain the conference information of the online conference. It can be seen that once the conference credential information of the online conference is cracked, it is easy to cause the conference data related to the online conference to be leaked, affecting the security of the conference data of the online conference. Summary of the invention

[0004] In view of this, the present application provides a conference access control method, device, server and storage medium to improve the security of conference data related to network conferences.

[0005] To achieve the above objectives, on the one hand, the present application provides a conference access control method, which is applied to a conference server, comprising:

[0006] Obtaining a conference access request initiated by a first conference client, wherein the conference access request carries a target conference credential and information about a logged-in user of the first conference client, wherein the target conference credential is used to indicate a target network conference requested to be accessed by the conference access request;

[0007] Obtaining a conference member list of the target network conference, wherein the conference member list includes information of conference participants set in the target network conference;

[0008] If the logged-in user of the first conference client does not belong to the participating member in the conference member list, query whether the target network conference belongs to a stored network conference with a credential sharing mark, wherein the credential sharing mark of the network conference is the mark information generated by the conference server for the network conference after confirming that the conference initiating client of the network conference shares the conference credential of the network conference;

[0009] If the target network conference is a network conference with a credential sharing mark, respond to the access content requested by the conference access request.

[0010] In a possible implementation, before responding to the access content requested by the conference access request, the method further includes:

[0011] Obtaining a total number of conference accesses by the first conference client, where the total number of conference accesses is the total number of network conferences accessed by the first conference client within a recently set period of time;

[0012] If the target network conference is a network conference with a credential sharing mark, the access content requested in response to the conference access request includes:

[0013] If the target network conference is a network conference with a credential sharing mark, and the total number of conference accesses by the first conference client does not exceed the set number, respond to the access content requested by the conference access request. In another possible implementation, the credential sharing mark of the network conference is generated by:

[0014] Obtaining a credential sharing request initiated by a conference initiating client of a network conference, wherein the credential sharing request is used to request sharing of conference credentials of the network conference;

[0015] Based on the credential sharing request, executing a sharing operation on the conference credential of the network conference;

[0016] After the sharing operation is performed, a credential sharing mark corresponding to the network conference is generated and stored.

[0017] In yet another possible implementation, the target conference credential includes: a conference identifier of the target network conference;

[0018] Before obtaining the conference access request initiated by the first conference client, the method further includes:

[0019] Obtaining a conference creation request initiated by a second conference client, wherein the conference creation request is used to request creation of the target network conference;

[0020] Generate a random number with a first set number of digits, and a timestamp sequence with a second set number of digits for representing the current moment;

[0021] Generate a conference identifier including the random number and a timestamp sequence;

[0022] A target network conference with the conference identifier is constructed for the second conference client.

[0023] In yet another possible implementation, the conference access request is used to request to obtain conference information of a target network conference;

[0024] Before responding to the access content requested by the conference access request, the method further includes:

[0025] Detecting whether the target network conference is a network conference that has ended and whose ending duration exceeds a set duration;

[0026] If the target network conference is a network conference with a credential sharing mark, the access content requested in response to the conference access request includes:

[0027] If the target network conference is a network conference with a credential sharing mark and the target network conference meets the set conditions, the conference information requested by the conference access request is obtained, and the obtained conference information is returned to the first conference client, and the set conditions include: the target network conference has not ended; or the target network conference has ended and the end time does not exceed the set time threshold.

[0028] In another aspect, the present application further provides a conference access control device, applied to a conference server, comprising:

[0029] An access obtaining unit, configured to obtain a conference access request initiated by a first conference client, wherein the conference access request carries a target conference credential and information about a logged-in user of the first conference client, wherein the target conference credential is used to indicate a target network conference requested to be accessed by the conference access request;

[0030] A list obtaining unit, configured to obtain a conference member list of the target network conference, wherein the conference member list includes information of conference participants set in the target network conference;

[0031] A sharing query unit, for querying whether the target network conference belongs to a stored network conference with a credential sharing mark if the logged-in user of the first conference client does not belong to the participating member in the conference member list, wherein the credential sharing mark of the network conference is the mark information generated by the conference server for the network conference after confirming that the conference initiating client of the network conference shares the conference credential of the network conference;

[0032] The access response unit is used to respond to the access content requested by the conference access request if the target network conference belongs to a stored network conference with a credential sharing mark.

[0033] In another aspect, the present application further provides a server, comprising a memory and a processor;

[0034] Wherein, the memory is used to store programs;

[0035] The processor is used to execute the program, and when the program is executed, it is specifically used to implement any one of the conference access control methods described above.

[0036] On the other hand, the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are loaded and executed by a processor, the conference access control method as described in any one of the above is implemented.

[0037] Through the above technical solution, it can be known that after determining the network conference requested to be accessed by the conference access request initiated by the conference client, if it is determined that the logged-in user on the conference client side does not belong to the participating members of the network conference, it will determine whether the network conference belongs to a stored network conference with a credential sharing mark. If the network conference is not a network conference with a credential sharing mark, it means that the initiating client of the network conference has not shared the conference credentials of the network conference. Therefore, the conference client obtained the conference credentials through illegal cracking. It can be seen from this that the present application will only respond to the conference access request if the network conference belongs to a network conference with a credential sharing mark, thereby reducing the risk of leakage of the conference data of the network conference due to the illegal cracking of the conference credentials of the network conference, thereby improving the security of the conference data of the network conference. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] 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 merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0039] Figure 1 A schematic diagram of a composition architecture of a conference access control system provided by an embodiment of the present application is shown;

[0040] Figure 2 A schematic diagram of a process flow of a conference access control method provided by an embodiment of the present application is shown;

[0041] Figure 3 Another flow chart of the conference access control method provided by the embodiment of the present application is shown;

[0042] Figure 4 A schematic diagram of a process of creating a conference logo provided in an embodiment of the present application is shown;

[0043] Figure 5 A schematic diagram of the composition structure of a conference logo provided in an embodiment of the present application is shown;

[0044] Figure 6 A schematic diagram of a process interaction of a conference access control method provided by an embodiment of the present application is shown;

[0045] Figure 7 A schematic diagram showing a composition structure of an application scenario applicable to the conference access control method of an embodiment of the present application is shown;

[0046] Figure 8 A schematic diagram of process interaction of a conference access control method provided by an embodiment of the present application in an application scenario is shown;

[0047] Fig. 9 A schematic diagram of the structure of a conference access control device provided in an embodiment of the present application is shown;

[0048] Fig.10 A schematic diagram of the composition structure of a server of the present application is shown. DETAILED DESCRIPTION

[0049] The conference access control method of the present application is applicable to the access control of any network conference built based on the network conference application, so as to improve the security of the conference data of the network conference.

[0050] The network conferencing application mentioned in the present application may be one or more applications that can support network conferencing such as video conferencing and Internet telephone conferencing (Voice over Internet Protocol, VOIP).

[0051] Among them, the network conferencing application can be an application that only supports network conferencing, or it can be an instant messaging application or other types of applications equipped with network conferencing functions, and this application does not impose any restrictions on this.

[0052] To facilitate understanding, the system composition architecture to which the solution of the present application is applicable is first introduced below.

[0053] like Figure 1 As shown, it shows a schematic diagram of the composition architecture of a conference access control system to which the present application solution is applicable.

[0054] Depend on Figure 1 It can be seen that the system may include: a conference service platform 110 and at least one conference client 120 .

[0055] The conference service platform 110 is a service platform for network conference applications, which may include at least one conference server 111 .

[0056] The conference client may be a terminal where the network conference application is located. For example, in one example, if the network conference application is an enterprise WeChat application, the conference client may be an enterprise WeChat client.

[0057] The conference server and the conference client can communicate with each other through the network.

[0058] The conference client may initiate a network conference establishment request to the conference server of the conference service platform. The conference establishment request may carry conference attribute information of the network conference requested to be established by the conference client.

[0059] For example, the conference attribute information may include one or more of the following information: the conference theme, conference time, conference host, conference member list, and conference attachment information of the requested online conference. The conference member list may include information of at least one participant of the online conference. The conference host is the user responsible for hosting the online conference. The conference attachment information is information such as text and documents that can be viewed in the online conference.

[0060] Accordingly, the conference server responds to the web conference establishment request initiated by the conference client, generates a conference credential for the requested web conference, stores the conference credential and the conference details of the web conference, and returns the conference credential to the conference client to complete the creation of the web conference. The conference details information may include the conference attribute information of the web conference, and may also include conference content such as conference video and conference audio generated after the start of the web conference, without limitation.

[0061] It is understandable that the conference server can locally store the conference credentials and related conference details of the created network conference.

[0062] In an optional manner, the conference service platform may further include a storage server 112, which may be used to store the network conferences created by the conference service platform for each conference client and the conference details related to the network conferences. Accordingly, the conference server may store the conference credentials of the created network conferences and the conference details related to the network conferences to the storage server.

[0063] Understandably, Figure 1 This is only a schematic diagram of a composition architecture of the conference access control system of the present application. In actual applications, the conference access control system may have other possible composition forms, which are not limited to this.

[0064] The conference access control method of the present application is introduced below with reference to the flowchart.

[0065] like Figure 2 As shown, it shows a flow chart of an embodiment of a conference access control method provided by an embodiment of the present application. The method of this embodiment can be applied to a conference server of the above conference access control system.

[0066] The method of this embodiment may include:

[0067] S201: Obtain a conference access request initiated by a first conference client.

[0068] The conference access request carries the target conference credential and information of the logged-in user of the first conference client.

[0069] The first conference client is a conference client that initiates the conference access request. The login user of the first conference client is a user who logs in to the conference service platform based on the first conference client.

[0070] The target conference credential is used to indicate the target network conference requested for access by the conference access request and is also an access credential that allows access to the target network conference.

[0071] For example, in some relatively developed online conferences, it may be possible to participate in the online conference by simply using the conference ID of the online conference. In this case, the conference credential of the online conference may be the conference ID of the online conference. For another example, in the case where the conference ID and password of the online conference are required to participate in the online conference, the conference credential of the online conference may be the conference ID and password of the online conference.

[0072] It can be understood that, for the sake of distinction, the present application refers to the network conference requested to be accessed by the conference access request as the target network conference, and the conference credential of the target network conference as the first target conference credential.

[0073] There are many possibilities for the content requested by the conference access request. For example, in one possible case, the conference access request to the target network conference may be a conference joining request to join the target network conference.

[0074] In another possible case, the conference access request may be an information acquisition request for obtaining conference information of the target network conference. For example, the conference access request may be an information acquisition request initiated by the target conference client before joining the target network conference to request obtaining conference attribute information of the target network conference; or, the information acquisition request may be an information acquisition request initiated by the first conference client after joining the target network conference, and the information acquisition request may request conference attribute information of the target network conference and related data generated during the conference.

[0075] S202: Obtain a list of conference members of the target network conference.

[0076] The conference member list includes information of the conference members set in the target network conference. For example, the conference member list may record the names of the conference members or nicknames or account names in the conference application.

[0077] For example, in one possible scenario, the conference initiating client that initiates the target network conference (i.e., the conference client that initiates the target network conference) can select and set the information of the participants of the target network conference. When the conference initiating client initiates a conference creation request for the target network conference to the conference server, the conference attribute information including the conference member list will be carried in the conference creation request.

[0078] In another possible scenario, after creating the target network conference, the conference initiating client may add information of conference participants in the conference operation interface of the target network conference displayed by the conference initiating client, and send the information of each conference participant as conference attribute information of the target network conference to the conference server, so that the conference server saves the list of conference members in the conference attribute information.

[0079] In the above two possible situations, the conference server can store the conference attribute information of the target network conference locally or in a storage server. Correspondingly, the conference server can query the conference member list of the target network conference from the conference attribute information.

[0080] For example, when the target conference credentials in the conference access request include the conference identifier of the target network conference, the stored conference details of the target network conference can be queried based on the conference identifier of the target network conference, and the list of conference members of the target network conference can be obtained from the conference details. It can be understood that no matter how the conference initiating client of the target network conference sets the participants of the target network conference, the participants are all users set by the conference initiating client and need to send a conference joining invitation, which is used to invite users to join the target network conference as participants.

[0081] After the user as a conference participant receives the conference joining invitation of the target network conference through his conference client, if the conference participant agrees to join the target network conference, the conference client of the conference participant accesses the target network conference corresponding to the conference joining invitation based on the instruction input by the conference participant to agree to join the target network conference.

[0082] Similarly, if a conference participant wishes to view conference information such as conference details of the target network conference through his / her conference client, the conference participant's conference client can view the conference information of the target network conference by clicking the details link associated with the conference join invitation based on the conference join request.

[0083] It can be seen that the conference client of the participating members does not need to obtain the conference credentials of the target network conference manually entered by the participants, nor does it need to use the conference credentials to initiate a conference access request. It can directly join the target network conference or access the conference information of the target network conference through the conference joining invitation.

[0084] For example, taking the case where a participant joins a target network conference as an example, in one implementation, after obtaining the participant of the target network conference and confirming that the target network conference has started, the conference server sends a conference joining invitation to the conference client of the participant. For example, after the conference server obtains a scheduled conference initiated by a conference initiating client, based on the information of the participant set in the scheduled conference, when the scheduled conference starts, the conference server sends a conference joining invitation to the conference client of the participant; or, after the conference server obtains an instant conference initiated by a conference initiating client, the conference server creates a network conference for the conference initiating client, and if the conference initiating client subsequently sends a conference invitation indication for at least one participant, the conference server can send a conference joining invitation to the conference client of each participant.

[0085] The conference joining invitation is used to prompt the participants to join the target network conference as participants of the target network conference. The conference joining invitation is associated with the link address of the target network conference. Of course, the conference joining invitation can also indicate the initiator and subject of the target network conference.

[0086] Accordingly, the conference client of the conference member will display a conference joining page containing a conference joining invitation. The conference joining page includes a conference joining option for agreeing to join the target network conference. On this basis, if the conference member agrees to join the target network conference, the conference client of the conference member will send a conference joining instruction to the conference server for agreeing to join the target network conference. The conference joining instruction is used to indicate joining the target network conference. Accordingly, the conference server responds to the conference joining instruction and connects the conference client of the conference member to the target network conference.

[0087] Of course, in actual applications, the conference initiating client can also send the conference credential of the target network conference to the conference client of the conference member directly or through the conference server, for example, the conference credential can be included in the conference joining invitation or sent separately. On this basis, if the conference member refuses the conference joining invitation or fails to join the target network conference through the conference joining invitation in time, the conference member can also apply to join the target network conference by entering the conference credential.

[0088] In addition, after the conference client of the participant joins the target network conference, if the participant needs to view the conference information such as the conference details of the target network conference, the conference access request initiated by the conference client of the participant also needs to carry at least the conference credential of the conference ID of the target network conference.

[0089] S203: If the logged-in user of the first conference client does not belong to the conference member in the conference member list, query whether the target network conference belongs to a stored network conference with a credential sharing mark.

[0090] The web conference credential sharing mark is the mark information generated by the conference server for the web conference after confirming that the conference initiating client of the web conference shares the conference credential of the web conference. The conference initiating client of the web conference refers to the conference client that initiates (or applies to create) the web conference.

[0091] The conference initiating client sharing the conference credential of the network conference means that the conference initiating client sends the conference credential of the network conference to at least one shared user's terminal directly or through the conference server. It can be seen that the network conference has a credential sharing mark indicating that the conference credential of the network conference is shared by the conference initiating client to at least one shared user.

[0092] The at least one shared user may include non-participating members other than the participating members of the target network conference, or may include participating members of the target network conference.

[0093] In one possible scenario, after confirming that the conference initiating client of the network conference has shared the conference credential of the network conference, the conference server can add a credential sharing mark to the conference details information corresponding to the conference credential of the network conference. Accordingly, the conference server can query whether the stored conference details of the target network conference have recorded the credential sharing mark.

[0094] For example, based on the target conference voucher of the target network conference, it is queried whether the conference details information corresponding to the target conference voucher records the information of the voucher sharing mark. If the conference details information corresponding to the target conference voucher records the voucher sharing mark, it means that the target network conference belongs to a stored network conference with the voucher sharing mark.

[0095] There are multiple ways for the conference server to determine that the conference initiating client of the network conference shares the conference credential of the network conference.

[0096] In one example, after obtaining a credential sharing request sent by the conference initiating client that initiates the online conference, the conference server can perform a sharing operation on the conference credential of the online conference based on the credential sharing request, and after performing the sharing operation, generate and store a credential sharing mark corresponding to the online conference.

[0097] The sharing operation performed based on the credential sharing request is to enable the conference initiating client to share the conference credential of the network conference with at least one shared user's terminal, which will be described in detail later in conjunction with an embodiment and will not be repeated here.

[0098] It is understandable that if the logged-in user of the first conference client is a participant in the conference member list of the target network conference, it means that the logged-in user is definitely a user allowed to access the target network conference, and on this basis, the conference access request can be directly responded to.

[0099] If the logged-in user of the first conference client is not a participant of the target network conference, then the first conference client can only apply for access to the target network conference through the conference credentials of the target network conference. On this basis, the only legal way for the first conference client to obtain the target conference credentials of the target network conference is to obtain the target conference credentials of the target network conference shared by the first conference client. It can be seen that if the target network conference does not belong to a network conference with a credential sharing mark, it means that the conference initiating client of the target network conference has never shared the conference credentials of the target network conference with non-participants. Therefore, the first conference client can only have obtained the conference credentials of the target network conference through illegal means.

[0100] S204: If the target network conference is a network conference with a credential sharing mark, respond to the access content requested by the conference access request.

[0101] For example, if the conference access request is a conference joining request for requesting to join the target network conference, then responding to the conference access request may be allowing the first conference client to join the target network conference.

[0102] For another example, if the conference access request is a conference information request for requesting to obtain conference information (such as conference attribute information or conference details, etc.) of the target network conference, then the response to the conference access request is to obtain the conference information of the target network conference based on the conference information request, and return the obtained conference information to the first conference client.

[0103] As can be seen from the foregoing description, if the target network conference does not belong to a network conference with a credential sharing mark, the conference access request will be rejected to avoid using illegally cracked target conference credentials to access the target network conference.

[0104] From the above, it can be seen that after determining the network conference requested to be accessed by the conference access request initiated by the conference client, if it is determined that the logged-in user on the conference client side is not a participant in the network conference, it will determine whether the network conference belongs to a stored network conference with a credential sharing mark. If the network conference is not a network conference with a credential sharing mark, it means that the conference client obtained the conference credentials of the network conference through illegal means. Therefore, the present application will only respond to the conference access request if the network conference belongs to a stored network conference with a credential sharing mark, thereby reducing the risk of leakage of the network conference data due to the cracking of the network conference credentials, thereby improving the security of the network conference data.

[0105] It is understandable that if a terminal maliciously cracks network credentials, the terminal may frequently simulate the conference client to initiate conference access requests for different network conferences in order to obtain conference information of certain network conferences. Therefore, if the frequency of conference access requests initiated by the conference client is too high, it means that the conference client is using multiple network credentials that are constantly maliciously cracked to frequently access different network conferences.

[0106] On this basis, in order to further improve the access security of the network conference, this application can also obtain the total number of conference accesses of the first conference client before responding to the access content requested by the conference access request. The total number of conference accesses is the total number of network conferences that the first conference client has accessed within the most recent set time period. Correspondingly, if the total number of conference accesses exceeds the set number, the conference access request initiated by the first conference client will also be rejected.

[0107] Accordingly, only when the first network conference is a network conference with conference sharing credentials and the total number of conference accesses by the first conference client does not exceed the set number, the conference server will respond to the access content requested by the conference access request. For ease of understanding, the following is an implementation method for sharing the conference credentials of the network conference by the conference initiating client of the network conference, such as Figure 3 As shown, it shows another flow chart of a conference access control method of the present application. The method of this embodiment may include:

[0108] S301, obtaining a credential sharing request initiated by a conference initiating client of a network conference.

[0109] The credential sharing request is used to request the sharing of the conference credential of the network conference. The conference initiating client of the network conference refers to the conference client that initiates the network conference.

[0110] It is understandable that the conference voucher requested to be shared in the voucher sharing request refers to the conference voucher of the network conference created by the conference initiating client, and the conference service platform will save the conference voucher and other related information of the network conference.

[0111] It can be understood that the online conference can be any online conference that has been created by the conference service platform.

[0112] S302: Based on the credential sharing request, a sharing operation of the conference credential of the network conference is performed.

[0113] The sharing operation of the conference credential of the network conference may be performed by the conference server performing an operation related to sharing the conference credential.

[0114] There are many possible implementation forms of the sharing operation:

[0115] For example, in one possible scenario, the conference server may generate sharing information including the conference credential of the network conference in response to the credential sharing request. Accordingly, the conference server may return the sharing information to the conference initiating client, so that the conference initiating client of the network conference sends the sharing information to at least one terminal of the shared user.

[0116] The specific form of the shared information may be in many possible forms, such as a QR code containing the conference voucher of the online conference; or a text message containing the conference voucher and a conference link pointing to the online conference. Of course, the specific form of the shared information may be in other possible forms, which are not limited thereto.

[0117] It can be understood that only when the user of the conference initiating client wants to share the conference credentials, will a conference sharing request be initiated to the conference server through the conference initiating client. Therefore, after the conference server returns the sharing information to the conference initiating client based on the conference sharing request, it can be confirmed that the conference initiating client sends the conference credentials to at least one terminal of the shared user to complete the sharing of the conference credentials of the network conference.

[0118] After obtaining the shared information, the conference initiating client can output the shared information so that the user on the conference initiating client side can send the shared information through email or instant messaging. Alternatively, after obtaining the shared information, the conference initiating client can automatically construct an email containing the shared information to send the shared information to the email addresses of different users set or input by the conference initiating client; or, the conference initiating client can publish a message containing the shared information in a designated instant messaging window, etc., without limitation.

[0119] In another possible scenario, the credential sharing request initiated by the conference initiating client may indicate at least one shared user with whom the conference credential of the network conference needs to be shared. For example, after the conference initiating client selects at least one user to be shared or an instant messaging group or instant messaging account containing at least one user, etc., it may initiate a credential sharing request, so that the credential sharing request indicates information of the at least one user selected by the user on the conference initiating client side. Accordingly, the conference server may send sharing information containing the conference credential of the network conference to the terminal of the at least one shared user based on the at least one shared user indicated in the credential sharing request.

[0120] The terminal of the at least one shared user may be a terminal where a conference client, an instant messaging application or a mailbox of the at least one shared user is located.

[0121] Among them, the specific form of the shared information can be as described above, which will not be repeated here. For example, take the conference service platform of this application as an enterprise instant messaging platform, and the conference client as an enterprise instant messaging application client as an example. The enterprise instant messaging application client can choose to initiate a credential sharing request to a certain friend group, then the conference server can send a sharing message belonging to the friend group to the instant messaging application client of each user in the friend group based on the credential sharing request, and the sharing message contains the sharing information.

[0122] Of course, executing the sharing operation may also include the two situations mentioned above at the same time.

[0123] S303: Generate a credential sharing mark for the network conference, and add the credential sharing mark to the conference details information of the network conference.

[0124] For example, when the conference certificate of a network conference includes the conference identifier of the network conference, a certificate sharing mark information can be added to the conference details information corresponding to the conference identifier based on the conference identifier of the network conference. Therefore, if the certificate sharing mark is recorded in the conference details information corresponding to the conference identifier, it means that the network conference represented by the conference identifier belongs to a network conference with a certificate sharing mark.

[0125] It should be noted that the above S301 to S303 are embodiments of the conference server initiating a conference sharing request based on the conference initiating client of the network conference, and adding a credential sharing mark to the network conference initiated by the conference initiating client. This part of the content is for the purpose of understanding the subsequent query whether the network conference belongs to a network conference with a credential sharing mark. Moreover, since the network conference in steps S301 and S303 can be any network conference, steps S301 to S303 are not necessarily executed before step S304, and steps S301 and S303 can be executed at any time after the network conference is created.

[0126] S304: Obtain a conference access request initiated by a conference access client.

[0127] The conference access request carries the target conference credential requested to be accessed and information of a logged-in user of the conference access client, and the target conference credential is used to indicate the target network conference requested to be accessed by the conference access request.

[0128] It should be noted that the conference access client refers to the conference client that initiates the conference access request. In this application, in order to facilitate the distinction from the conference initiating client of the network conference, the conference access client is also referred to as the first conference client. Similarly, in this application, in order to facilitate the distinction, the network conference requested to be accessed by the conference access request is referred to as the target network conference, and the conference credential of the target network conference is referred to as the target conference credential.

[0129] S305: Obtain the total number of conference accesses by the conference access client.

[0130] The total number of conference accesses is the total number of network conferences accessed by the conference access client (ie, the first conference client) within the most recent set time period.

[0131] The most recently set time period may be set as required, for example, the most recently set time period may be within the last 24 hours before the current time.

[0132] The network conferences accessed by the conference access client within the most recent set time period may be multiple different network conferences. Therefore, the total number of conference accesses is the sum of the number of accesses of the first conference client to each network conference.

[0133] S306: Obtain a list of conference members of the target network conference.

[0134] The conference member list includes information of the conference participants set in the target network conference.

[0135] S307: If the user logged in to the conference access client does not belong to the conference member list, query whether the target network conference belongs to a stored network conference with a sharing mark.

[0136] The above steps S306 and S307 can refer to the above related introduction and will not be repeated here.

[0137] It should be noted that, in practical applications, the order of steps S305, S306 and S307 is not limited to Figure 3 As shown, in actual application, the order of step S305 and step S306 and step S307 can be interchanged, and steps S306 and S307 can also be executed while step S305 is executed.

[0138] S308: If the target network conference is a stored network conference with a sharing mark and the total number of conference accesses by the conference access client does not exceed the set number, respond to the access content requested by the conference access request.

[0139] It is understandable that if the total number of conference accesses of the conference access client (first conference client) exceeds the set number, it means that the conference access client frequently and maliciously accesses different network conferences, and the conference access client can obtain a large number of conference credentials for network conferences in a short period of time, which must be obtained by illegally cracking the conference credentials of different network conferences. Therefore, the conference server can directly reject the conference access request initiated by the conference access client.

[0140] It can be seen that after the conference access client initiates a conference access request, this embodiment will query the total number of conference accesses that the conference access client has accessed to the network conference within the most recent set time period. Since the total number of conference accesses exceeds the set number, it means that the conference access client has used illegally cracked conference credentials to access the network conference. It can be seen that this application will only respond to the conference access request of the conference access client when the target network conference that the conference access client requests to access belongs to a network conference whose network credentials are shared and the total number of conference accesses of the conference access client does not exceed the set number, thereby reducing the situation where the conference access client accesses the network conference by illegally cracking the conference credentials of the network conference, thereby improving the data security of the network conference.

[0141] It is understandable that in any of the above embodiments of the present application, if the conference client obtains the conference credentials of the network conference, it will generally request the conference information of the network conference in a short time. Therefore, if the network conference has ended for a long time, it is unlikely that non-participating members will use the conference credentials shared by the network conference to request the conference information of the network conference. For a conference client that illegally cracks the conference credentials of the network conference, since it may randomly crack a certain network conference, it may be possible to access the network conference to obtain the conference information of the network conference after the network conference has ended for a long time.

[0142] It can be seen from this that in order to further improve the security of conference data of online conferences, when the conference access request initiated by the conference access client (first conference client) is used to request to obtain conference information of the online conference, the present application can also detect whether the target online conference requested to be accessed by the conference access client is a network conference that has ended and the end duration exceeds the set duration threshold.

[0143] Correspondingly, if the logged-in user of the conference access client is not a participant of the target network conference, the conference information requested by the conference access request can only be obtained if the target network conference is a network conference with a credential sharing mark and the target network conference meets the set conditions. The set conditions include: the target network conference has not ended; or the target network conference has ended and the end time does not exceed the set time threshold.

[0144] Of course, if the logged-in user of the conference access client is not a participant of the target network conference, and the network conference requested by the conference access request has ended for a period exceeding the set duration threshold, the conference access request can be directly rejected.

[0145] It is understandable that in a relatively open online conference, the access credential of the online conference is the conference ID of the online conference. In this case, as long as the conference ID of the online conference is cracked, the online conference can be accessed using the conference ID of the online conference, thereby increasing the security risk of the conference data of the online conference.

[0146] The inventor of the present application has discovered through research that after receiving a conference creation request initiated by a conference client, the conference server will generate a conference ID for the network conference requested to be created by the conference client. However, currently conference clients generally use a serial number generator to generate conference IDs. The serial number generator generally generates a new conference ID by incrementing the last generated conference ID in a manner that gradually increases the conference ID. For example, assuming that the most recently generated conference ID is 10010, when there is a need to generate a new conference ID, a new conference ID "10011" is obtained by directly adding one to the conference ID "10010".

[0147] Since the conference IDs currently generated in sequence are incremented one by one, it is very easy to crack the conference ID by traversing the conference ID, which makes the risk of the conference ID being cracked high.

[0148] In order to further reduce the risk of the conference credentials of the network conference being cracked, the present application proposes a new implementation method for constructing the conference identifier of the network conference.

[0149] like Figure 4 As shown, it shows a schematic diagram of an implementation flow of the network identification creation method provided in an embodiment of the present application. The method of this embodiment is applied to a conference server.

[0150] The method of this embodiment may include:

[0151] S401: Obtain a conference creation request initiated by a conference client.

[0152] The conference creation request is used to request the creation of a network conference.

[0153] In an optional manner, the conference creation request may carry conference attribute information of the network conference to be created, such as conference subject, conference host, conference time, and document attachments involved in the conference.

[0154] Of course, the conference creation request may also carry the information of the logged-in user on the conference client side. The information of the logged-in user may also be used as part of the conference attribute information, or may be information other than the conference attribute information, and there is no restriction on this.

[0155] It should be noted that, since different conference clients can initiate conference creation requests simultaneously or at different times as needed, the conference client in this embodiment may be different from the conference initiating client that previously applied for a credential sharing request, or it may be the same client as the previous conference initiating client, that is, after the conference client creates a network conference, the conference client initiates a conference sharing request to the conference server.

[0156] For the same online conference, the conference client that initiates the creation of the online conference and the conference client that applies to access (such as join) the online conference are not the same client. Therefore, in order to facilitate the distinction from the previous first conference client (conference access client), the conference client that requests to create the online conference is also referred to as the second conference client in this application.

[0157] S402, generating a random number having a first set number of digits, and a timestamp sequence having a second set number of digits for representing the current moment.

[0158] For example, the first set number of digits and the second set number of digits can be set as needed, and can be determined in combination with the number of digits of the conference identifier. For example, the first set number of digits can be 28 digits, and the second set number of digits can be 32 digits.

[0159] The random number may be a value randomly generated by any algorithm, and there is no restriction on this.

[0160] The timestamp sequence is a value having a second set number of bits and capable of representing the current moment.

[0161] S403: Generate a conference identifier including a random number and a timestamp sequence.

[0162] For example, the random number and the timestamp sequence may be combined into a conference identifier, and the number of digits of the conference identifier is not less than the sum of the first set number of digits and the second set number of digits.

[0163] In an optional manner, before generating the conference logo, the version number of the logo generation algorithm used to construct the conference logo can also be determined. The version of the logo generation algorithm can be continuously updated, and after each update of the logo generation algorithm, its version number will also change accordingly. The present application can reflect the version number of the logo generation algorithm in the conference logo.

[0164] Accordingly, the identifier generation algorithm can be used to generate a random number with a first set number of digits and a timestamp sequence with a second set number of digits for representing the current moment. Then, the version number, random number and timestamp sequence are combined in sequence to obtain a combined conference identifier.

[0165] For example, see Figure 5 , which shows a schematic diagram of the composition structure of the conference identifier of the network conference in this application.

[0166] exist Figure 5The conference ID of a network conference is a 64-bit binary array as an example. The first four bits of the conference ID are the version number of the ID generation algorithm. If the ID generation algorithm remains unchanged, the first four bits of the conference ID are fixed. The middle 28 bits of the conference ID (5th to 32nd bits) are randomly generated random numbers, and the following 32 bits are a data sequence representing a timestamp.

[0167] It is understandable that since the data sequence indicating the timestamp in the conference ID changes with the time when the conference ID is generated, and the randomly assigned random number is also not fixed, the difficulty of cracking the conference ID is increased and the risk of cracking the conference ID is reduced.

[0168] It is understandable that although the random number in the conference identifier is randomly generated, and the data sequence representing the timestamp is related to the generation time of the conference identifier, the possibility of duplication between the conference identifier and other generated conference identifiers is very small.

[0169] However, in order to avoid duplication of conference identifiers, in an optional manner, after generating the conference identifier, the present application may also detect whether a conference identifier that is duplicated with the currently generated conference identifier is stored in the conference service platform (e.g., the storage server of the conference service platform); if a duplicate conference identifier exists, the conference identifier is discarded, and steps S402 and S403 are re-executed to regenerate a conference identifier; if no duplicate conference identifier exists, the conference identifier is determined as the conference identifier of the network conference requested to be constructed by the conference client, and subsequent step S404 is executed.

[0170] S404: construct a network conference with the conference identifier for the conference client.

[0171] It is understandable that there may be many possible specific implementations of building a network conference based on generating a conference identifier, and the present application does not limit the specific process of building a network conference.

[0172] For example, step S404 may include: storing the conference identifier and conference details information corresponding to the conference identifier, and the conference details information may include conference attribute information carried by the conference establishment request. Of course, after the network conference is created, other conference attribute information sent by the conference client and conference data generated during the network conference may also be stored in the conference details information.

[0173] The step S404 may also include: sending the conference identifier to the conference client.

[0174] In the embodiment of the present application, the conference identifier generated by the conference server for the network conference created by the conference client request not only includes a randomly generated random number, but also includes a timestamp sequence representing the time when the conference identifier is generated, so that the conference identifier is random, reducing the possibility of cracking the conference identifier through successive incremental traversal, thereby improving the security of the conference identifier, and naturally reducing the risk of accessing the network conference using the cracked conference identifier, thereby improving the security of the conference data of the network conference.

[0175] In order to facilitate understanding of the scheme of the present application, the following takes the conference credential of an online conference as the conference identifier of the online conference as an example, and combines an embodiment to introduce the scheme of the present application according to the process of creating a certain online conference, sharing the conference identifier of the online conference, and accessing the online conference.

[0176] like Figure 6 As shown, it shows a process interaction diagram of the conference access control method of the present application.

[0177] exist Figure 6 In the embodiment, a certain network conference is used as an example for explanation. Therefore, the conference client that initiates the creation of the network conference and the conference client that requests to share the network conference are the same conference client, and the conference client is called the conference initiating client of the network conference. The conference client that requests to access the network conference is different from the conference initiating client. For the sake of distinction, the conference client that requests to access the network conference is called the conference accessing client.

[0178] The method of this embodiment may include:

[0179] S601: A conference initiating client sends a conference creation request to a conference server.

[0180] The conference creation request carries the conference attribute information of the network conference requested to be created. The conference attribute information may include the aforementioned conference subject, conference time, conference member list and other information, and may also include the user name of the user logged in to the conference initiating client and other information.

[0181] S602: The conference server determines a version number of an identifier generation algorithm used to construct a conference identifier in response to the conference creation request.

[0182] S603, the conference server uses the identifier generation algorithm to generate a random number with a first set number of digits and a timestamp sequence with a second set number of digits for representing the current moment, and sequentially combines the version number, the random number and the timestamp sequence to obtain a combined conference identifier.

[0183] S604: The conference server detects whether a conference identifier identical to the conference identifier is stored in the storage server.

[0184] S605: If the conference server confirms that there is no conference identifier identical to the conference identifier in the storage server, the conference details information of the network conference corresponding to the conference identifier is stored in the storage server.

[0185] The conference details information includes conference attribute information of the network conference.

[0186] S606: The conference server returns the conference identifier to the conference initiating client.

[0187] S607: The conference initiating client initiates a conference sharing request for the network conference to the conference server.

[0188] The conference sharing request carries the conference identifier of the network conference and the user information of the shared user, wherein the user information of the shared user may be a registered account or user name of the shared user in the conference service platform.

[0189] The conference sharing request is used to request to share the conference identifier of the network conference with the at least one shared user.

[0190] For example, the conference initiating client can display the conference operation interface of the online conference, and at least one sharing icon can be displayed in the conference operation interface. After the conference initiating client detects that the user clicks the sharing icon, the shareer adding page corresponding to the sharing icon can be displayed, so that the conference initiating client obtains the information of the shared user selected or added by the user, and initiates the conference sharing request.

[0191] S608: The conference server generates sharing information including the sharing identifier, and sends the sharing information to conference clients of each shared user according to user information of at least one shared user.

[0192] It should be noted that here the example is taken that the conference server sends the sharing information to the conference client of at least one shared user, but it is understandable that in addition to sending the sharing information to the conference client of the shared user, the conference server can also send the sharing information to the shared user's email or instant messaging client, etc., without any restriction.

[0193] S609: The conference server adds a conference sharing mark to the conference details information of the network conference stored in the storage server according to the conference identifier of the network conference.

[0194] It should be noted that this embodiment is explained by taking the conference sharing request sent by the conference initiating client as an example, indicating at least one shared user to whom the conference identifier needs to be shared in addition to the conference identifier. However, it can be understood that if the conference initiating client only obtains the sharing information for sharing the conference identifier, the conference server can also execute step S609 after returning the sharing information to the conference initiating client.

[0195] S610: The conference access client sends a conference access request to the conference server.

[0196] The conference access request carries the conference identifier of the network conference requested to be accessed and the information of the logged-in user at the conference access client side.

[0197] S611, the conference server obtains the total number of conference accesses by the conference access client within the most recent set time period, and detects whether the total number of conference accesses exceeds the set number. If yes, the conference access request is rejected; if not, step S612 is executed.

[0198] The total number of conference visits is the total number of all network conferences visited by the conference access client within the most recent set time period.

[0199] S612, the conference server obtains the conference member list of the network conference from the conference details information of the network conference stored in the storage server based on the conference identifier of the network conference, and detects whether the logged-in user of the conference access client is a participating member in the conference member list. If yes, respond to the conference access request; if not, execute step S613.

[0200] S613, the conference server queries whether the conference details information of the network conference stored in the storage server has a sharing mark according to the conference identifier of the network conference, and if so, responds to the content requested by the network access request; if not, rejects the network access request.

[0201] It can be understood that in this embodiment, when the network conference requested by the network access request has a sharing mark, the present application can also detect whether the network conference has ended for a period of time exceeding the set duration threshold. If the network conference has ended and the period of time exceeded the set duration threshold, the network access request can be rejected.

[0202] It is understandable that the conference service platform in the present application can be any service platform that can provide network conferences, and the corresponding conference client can also have multiple possibilities. For ease of understanding, the following is an explanation in conjunction with an application scenario.

[0203] For example, the conference service platform is the enterprise WeChat service platform, and the conference client is the enterprise WeChat client.

[0204] like Figure 7 As shown, it shows a schematic diagram of the composition architecture of an application scenario to which the solution of the present application is applicable.

[0205] exist Figure 7 The application scenario includes an enterprise WeChat service platform 710 and multiple enterprise WeChat clients 720. For example, Figure 7 The enterprise WeChat clients include enterprise WeChat client A, enterprise WeChat client B and enterprise WeChat client C.

[0206] The enterprise WeChat service platform includes: at least one enterprise WeChat server 711.

[0207] In an optional embodiment, the enterprise WeChat service platform also includes at least one storage server.

[0208] The enterprise WeChat client and the enterprise WeChat server can achieve communication connection through the network.

[0209] Combination Figure 7 Assume that both enterprise WeChat client A and enterprise WeChat client B need to initiate a network conference through the enterprise WeChat service platform, and enterprise WeChat client C needs to obtain the conference information of the network conference initiated by enterprise WeChat client B.

[0210] like Figure 8 As shown, it shows a schematic diagram of the process interaction of the conference access control method provided by the present application in an application scenario. This embodiment may include:

[0211] S801, the enterprise WeChat client A initiates a first conference creation request to create a network conference A to the enterprise WeChat server.

[0212] The first conference creation request sent by the enterprise WeChat client A may carry conference attribute information such as the conference subject and conference host of the online conference requested to be created by the enterprise WeChat client A.

[0213] S802, the enterprise WeChat server responds to the first conference creation request, generates a conference identifier A for network conference A that includes a version number of the identifier generation algorithm, a first random number and a first timestamp sequence, and stores the conference identifier A and conference details information of network conference A in the storage server.

[0214] S803, the enterprise WeChat server returns the conference identifier A to the enterprise WeChat client A.

[0215] S804, the enterprise WeChat client B initiates a second conference creation request to create network conference B to the enterprise WeChat server.

[0216] The first conference creation request sent by the enterprise WeChat client B may carry conference attribute information such as the conference theme of the online conference that the enterprise WeChat client B requests to create.

[0217] The order of the above steps S801 and S804 is not limited to Figure 8 As shown, it is specifically determined by the moment when the enterprise WeChat client A and the enterprise WeChat client B initiate the meeting creation request.

[0218] S805, the enterprise WeChat server responds to the second conference creation request, generates a conference identifier B for network conference B that includes a version number of the identifier generation algorithm, a second random number, and a second timestamp sequence, and stores the conference identifier B and conference details information of network conference B in the storage server.

[0219] S806, the enterprise WeChat server returns the conference identifier B to the enterprise WeChat client B.

[0220] In the embodiment, an example is taken in which enterprise WeChat client A and enterprise WeChat client B respectively initiate and create a network conference.

[0221] S807, the enterprise WeChat client B sends a conference sharing request for network conference B to the enterprise WeChat server.

[0222] The sharee(s) indicated by the conference sharing request include user C, who is a logged-in user of enterprise WeChat client C. Of course, here, user C is taken as an example as a logged-in user of enterprise WeChat client C. Since enterprise WeChat conferences can send messages to personal WeChat applications, user C can also be a logged-in user of a personal WeChat client.

[0223] It is understandable that if the network conference B initiated by the enterprise WeChat client B is a scheduled conference, the enterprise WeChat client will generally carry the list of conference members of the network conference B in the second conference creation request initiated. If the network conference B initiated by the enterprise WeChat client B is an instant conference (such as clicking "Meet Now" in the enterprise WeChat to initiate an instant conference creation request), the second conference creation request issued by the enterprise WeChat client may not carry the list of conference members. In this case, the user on the enterprise WeChat client B side can use the conference invitation icon on the operation interface of the created network conference to trigger the addition of conference members to invite conference members.

[0224] The conference sharing request mentioned here does not mean inviting the conference participants, but at least needs to share the conference ID and conference link of the online conference with non-participating members.

[0225] exist Figure 8The example in which WeChat client B requests the WeChat server to share a web conference with other WeChat clients is used for explanation. In this case, the user of WeChat client B can click the share icon in the operation interface of web conference B displayed by WeChat client B to enter the contact selection interface, and select the contact to be shared, thereby requesting the WeChat server to share the conference ID of web conference B with the WeChat client of the selected contact.

[0226] Understandably, Figure 8 This is just an example of a possible situation of sharing network conference B. In actual application, in addition to being able to initiate a request to share network conference B with users of other enterprise WeChat clients, enterprise WeChat client B can also initiate a request to share network conference B with contacts in other instant messaging applications (such as WeChat). Moreover, the conference sharing request of enterprise WeChat client B can also be a request to obtain sharing information including the conference ID of network conference B, so that the user of enterprise WeChat client B can manually operate to send the sharing information of network conference B to the terminals of different users to realize the sharing of the conference ID of network conference B.

[0227] S808, the enterprise WeChat server generates sharing information including the conference identifier B, and sends the sharing information to the enterprise WeChat client C.

[0228] For example, the shared information may be one or more of the following information forms: a QR code including the conference identifier B, a conference link pointing to the online conference corresponding to the conference identifier B, and the like.

[0229] S809, the enterprise WeChat server adds a sharing mark to the meeting details information corresponding to the meeting identifier B in the storage server.

[0230] S810, the enterprise WeChat client C sends a conference access request for the network conference B to the enterprise WeChat server.

[0231] The conference access request carries the conference identifier B of the network conference B and the information of user C.

[0232] S811, the enterprise WeChat server obtains the total number of conference visits to the network conferences that the enterprise WeChat client C has visited within the most recent set time period.

[0233] S812, the enterprise WeChat server determines that the total number of visits to the conference does not exceed the set number threshold, and based on the conference identifier B, obtains the conference member list of the network conference B from the storage server.

[0234] S813, the enterprise WeChat server determines based on the conference member list that user C is not a participant of the online conference B, and checks whether the conference details information corresponding to the conference identifier B from the storage server is added with a sharing mark.

[0235] S814, the enterprise WeChat server confirms that a sharing mark corresponding to the conference identifier B is stored in the storage server, and obtains the conference information of the network conference B from the storage server based on the conference access request.

[0236] S815, the enterprise WeChat server returns the meeting information to the enterprise WeChat client C.

[0237] In this embodiment, it is taken as an example that the enterprise WeChat client C obtains the sharing information of the network conference B shared by the enterprise WeChat client B, and requests to obtain the conference information of the network conference B based on the conference identifier B in the sharing information.

[0238] Assume that enterprise WeChat client C obtains the meeting ID of network conference A initiated by enterprise WeChat client A through illegal cracking, and initiates a meeting information request to the enterprise WeChat server to obtain the meeting information of network conference A. Then, since the enterprise WeChat server finds that network conference A does not belong to a network conference with a sharing mark, that is, the meeting ID of network conference A has not been shared, the enterprise WeChat server will reject the meeting access request of enterprise WeChat client C to obtain the meeting information of network conference A.

[0239] On the other hand, corresponding to a conference access control method of the present application, the present application also provides a conference access control device.

[0240] like Fig. 9 As shown, it shows a schematic diagram of a composition structure of a conference access control device of the present application, and the device is applied to a conference server, including:

[0241] The access obtaining unit 901 is used to obtain a conference access request initiated by the first conference client, the conference access request carries the target conference credential and the information of the logged-in user of the first conference client, the target conference credential is used to indicate the target network conference requested to be accessed by the conference access request;

[0242] A list obtaining unit 902 is used to obtain a conference member list of a target network conference, where the conference member list includes information of conference members set in the target network conference;

[0243] A sharing query unit 903 is used to query whether the target network conference belongs to a stored network conference with a credential sharing mark if the logged-in user of the first conference client does not belong to the participating member in the conference member list, wherein the credential sharing mark of the network conference is the mark information generated by the conference server for the network conference after confirming that the conference initiating client of the network conference shares the conference credential of the network conference;

[0244] The access response unit 904 is used to respond to the access content requested by the conference access request if the target network conference is a network conference with a credential sharing mark.

[0245] In a possible implementation, the device further includes:

[0246] The number obtaining unit is used to obtain the total number of conference accesses of the first conference client before the access response unit responds to the access content requested by the conference access request, the total number of conference accesses being the total number of network conferences accessed by the first conference client within a recently set time period;

[0247] The access response unit is specifically used to respond to the access content requested by the conference access request if the target network conference is a network conference with a credential sharing mark and the total number of conference accesses by the first conference client does not exceed a set number.

[0248] In a possible implementation, the device may further include:

[0249] A sharing request obtaining unit, used to obtain a credential sharing request initiated by a conference initiating client of a network conference, wherein the credential sharing request is used to request sharing of conference credentials of the network conference;

[0250] A sharing execution unit, used for executing a sharing operation on the conference credential of the network conference based on the credential sharing request;

[0251] The tag storage unit is used to generate and store the sharing tag corresponding to the network conference after executing the sharing operation.

[0252] In a possible implementation, the sharing execution unit includes one or both of the following first sharing execution unit and second sharing execution unit:

[0253] a first sharing execution unit, configured to generate sharing information including the conference credential of the network conference in response to the credential sharing request, and return the sharing information to the conference initiating client of the network conference, so that the conference initiating client of the network conference sends the sharing information to a terminal of at least one shared user;

[0254] The second sharing execution unit is configured to send sharing information including the conference credential of the network conference to a terminal of at least one shared user indicated in the credential sharing request.

[0255] In yet another possible implementation, in the above apparatus embodiment, the access obtaining unit obtains the target conference credential including: a conference identifier of the target network conference;

[0256] The device also includes:

[0257] A creation request unit, used to obtain a conference creation request initiated by a second conference client before the access obtaining unit obtains the conference access request initiated by the first conference client, wherein the conference creation request is used to request the creation of a target network conference;

[0258] A data generation unit, used to generate a random number having a first set number of digits, and a timestamp sequence having a second set number of digits for representing a current moment;

[0259] An identification generating unit, used to generate a conference identification including a random number and a timestamp sequence;

[0260] The conference construction unit is used to construct a target network conference with a conference identifier for the second conference client.

[0261] In one possible scenario, the device further includes:

[0262] A version determination unit, used to determine a version number of an identifier generation algorithm used to construct a conference identifier before the data generation unit generates a conference identifier including a random number and a timestamp sequence;

[0263] The data generation unit is specifically used to generate a random number having a first set number of digits and a timestamp sequence having a second set number of digits for representing the current moment by using an identification generation algorithm;

[0264] The identifier generation unit is specifically used to sequentially combine the version number, the random number and the timestamp sequence to obtain a combined conference identifier.

[0265] In yet another possible implementation, the conference access request is used to request to obtain conference information of a target network conference;

[0266] Before responding to a conference access request to access the requested content, also include:

[0267] Detect whether the target online conference is a network conference that has ended and whose ending duration exceeds the set duration;

[0268] If the target network conference is a network conference with a credential sharing mark, the access content requested in the response to the conference access request includes:

[0269] If the target network conference is a network conference with a credential sharing mark and the target network conference meets the set conditions, the conference information requested by the conference access request is obtained, and the obtained conference information is returned to the first conference client. The set conditions include: the target network conference has not ended; or the target network conference has ended and the end time does not exceed the set time threshold.

[0270] On the other hand, the present application also provides a server, which may be the conference server in the conference service platform mentioned above in the present application.

[0271] For easier understanding, see Fig.10 , which shows a schematic diagram of the composition structure of a server of the present application.

[0272] exist Fig.10 In the embodiment, the server 1000 may include: a processor 1001 and a memory 1002.

[0273] In a possible implementation, the server may further include: a communication interface 1003 , an input unit 1004 , a display 1005 , and a communication bus 1006 .

[0274] The processor 1001 , the memory 1002 , the communication interface 1003 , the input unit 1004 , and the display 1005 all communicate with each other via the communication bus 1006 .

[0275] In the embodiment of the present application, the processor 1001 may be a central processing unit, a field programmable gate array (FPGA) or other programmable logic devices.

[0276] The processor may call a program stored in the memory 1002 .

[0277] The memory 1002 is used to store one or more programs. The program may include program code, and the program code includes computer operation instructions.

[0278] The memory at least stores a program, and when the program is executed, it is specifically used to implement the conference access control method mentioned in any one of the above embodiments.

[0279] In a possible implementation, the memory 1002 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, the programs mentioned above, etc.; the data storage area may store data created during the use of the server.

[0280] In addition, the memory 1002 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.

[0281] The communication interface 1003 may be an interface of a communication module, such as an interface of a GSM module.

[0282] The present application may further include an input unit 1004, which may include a touch sensing unit for sensing a touch event on the touch display panel, a keyboard, and the like.

[0283] The display 1005 includes a display panel, such as a touch display panel.

[0284] certainly, Fig.10 The server structure shown does not constitute a limitation on the server in the embodiment of the present application. In actual applications, the server may include Fig.10 More or fewer components than shown, or combinations of certain components.

[0285] On the other hand, the present application also provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are loaded and executed by a processor, the conference access control method in any of the above embodiments is implemented.

[0286] It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments can be referred to each other. At the same time, the features recorded in each embodiment in this specification can be replaced or combined with each other, so that professionals in the field can implement or use this application. For device embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0287] As for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0288] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0289] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0290] The above are only preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A conference access control method, characterized in that: Applicable to conference servers, including: Obtaining a conference access request initiated by a first conference client, the conference access request carrying a target conference credential and information about a logged-in user of the first conference client, the target conference credential being used to indicate a target network conference requested to be accessed by the conference access request; Obtaining a conference member list of the target network conference, wherein the conference member list includes information of conference participants set in the target network conference; If the logged-in user of the first conference client does not belong to the participating member in the conference member list, query whether the target network conference belongs to a stored network conference with a credential sharing mark, wherein the credential sharing mark of the network conference is the mark information generated by the conference server for the network conference after confirming that the conference initiating client of the network conference shares the conference credential of the network conference; If the target network conference is a network conference with a credential sharing mark, respond to the access content requested by the conference access request; Before responding to the access content requested by the conference access request, the method further includes: Obtaining a total number of conference accesses by the first conference client, where the total number of conference accesses is a total number of network conferences accessed by the first conference client within a recently set period of time; If the target network conference is a network conference with a credential sharing mark, the access content requested in response to the conference access request includes: If the target network conference is a network conference with a credential sharing mark, and the total number of conference accesses by the first conference client does not exceed a set number, respond to the access content requested by the conference access request.

2. The method according to claim 1, characterized in that The credential sharing mark of the network conference is generated in the following way: Obtaining a credential sharing request initiated by a conference initiating client of a network conference, wherein the credential sharing request is used to request sharing of conference credentials of the network conference; Based on the credential sharing request, executing a sharing operation on the conference credential of the network conference; After the sharing operation is performed, a credential sharing mark corresponding to the network conference is generated and stored.

3. The method according to claim 2, characterized in that The performing of the sharing operation of the conference credential of the network conference based on the credential sharing request includes one or both of the following: In response to the credential sharing request, generating sharing information including the conference credential of the network conference, and returning the sharing information to the conference initiating client of the network conference, so that the conference initiating client of the network conference sends the sharing information to a terminal of at least one shared user; Based on at least one shared user indicated in the credential sharing request, sharing information including the conference credential of the network conference is sent to a terminal of the at least one shared user.

4. The method according to any one of claims 1 to 3, characterized in that: The target conference credential includes: a conference identifier of the target network conference; Before obtaining the conference access request initiated by the first conference client, the method further includes: Obtaining a conference creation request initiated by a second conference client, wherein the conference creation request is used to request creation of the target network conference; Generate a random number with a first set number of digits, and a timestamp sequence with a second set number of digits for representing the current moment; Generate a conference identifier including the random number and a timestamp sequence; A target network conference with the conference identifier is constructed for the second conference client.

5. The method according to claim 4, characterized in that Before generating the conference identifier including the random number and the timestamp sequence, the method further includes: Determine a version number of an identifier generation algorithm used to construct a conference identifier; The generating of a random number having a first set number of digits and a timestamp sequence having a second set number of digits for representing the current moment comprises: Using the identification generation algorithm, a random number having a first set number of digits and a timestamp sequence having a second set number of digits for representing the current moment are generated; The generating of the conference identifier including the random number and the timestamp sequence comprises: The version number, random number and timestamp sequence are combined in sequence to obtain a combined conference identifier.

6. The method according to claim 1, characterized in that The conference access request is used to request to obtain conference information of the target network conference; Before responding to the access content requested by the conference access request, the method further includes: Detecting whether the target network conference is a network conference that has ended and whose ending duration exceeds a set duration; If the target network conference is a network conference with a credential sharing mark, the access content requested in response to the conference access request includes: If the target network conference is a network conference with a credential sharing mark and the target network conference meets the set conditions, the conference information requested by the conference access request is obtained, and the obtained conference information is returned to the first conference client, and the set conditions include: the target network conference has not ended; or the target network conference has ended and the end time does not exceed the set time threshold.

7. A conference access control device, characterized in that: Applicable to conference servers, including: An access obtaining unit, configured to obtain a conference access request initiated by a first conference client, wherein the conference access request carries a target conference credential and information about a logged-in user of the first conference client, wherein the target conference credential is used to indicate a target network conference requested to be accessed by the conference access request; A list obtaining unit, configured to obtain a conference member list of the target network conference, wherein the conference member list includes information of conference participants set in the target network conference; A sharing query unit, for querying whether the target network conference belongs to a stored network conference with a credential sharing mark if the logged-in user of the first conference client does not belong to the participating member in the conference member list, wherein the credential sharing mark of the network conference is the mark information generated by the conference server for the network conference after confirming that the conference initiating client of the network conference shares the conference credential of the network conference; An access response unit, configured to respond to the access content requested by the conference access request if the target network conference belongs to a stored network conference with a credential sharing mark; The number obtaining unit is used to obtain the total number of conference accesses of the first conference client before the access response unit responds to the access content requested by the conference access request, where the total number of conference accesses is the total number of network conferences accessed by the first conference client within a recently set time period; The access response unit is specifically used to respond to the access content requested by the conference access request if the target network conference is a network conference with a credential sharing mark and the total number of conference accesses by the first conference client does not exceed a set number.

8. The device according to claim 7, characterized in that The device also includes: A sharing request obtaining unit, used to obtain a credential sharing request initiated by a conference initiating client of a network conference, wherein the credential sharing request is used to request sharing of conference credentials of the network conference; A sharing execution unit, configured to execute a sharing operation on the conference credential of the network conference based on the credential sharing request; The tag storage unit is used to generate and store the credential sharing tag corresponding to the network conference after executing the sharing operation.

9. The device according to claim 8, characterized in that The sharing execution unit includes one or both of the following first sharing execution unit and second sharing execution unit: a first sharing execution unit, configured to generate sharing information including the conference credential of the network conference in response to the credential sharing request, and return the sharing information to the conference initiating client of the network conference, so that the conference initiating client of the network conference sends the sharing information to a terminal of at least one shared user; The second sharing execution unit is configured to send sharing information including the conference credential of the network conference to a terminal of at least one shared user indicated in the credential sharing request.

10. The device according to any one of claims 7 to 9, characterized in that The target conference credential obtained by the access obtaining unit includes: a conference identifier of the target network conference; The device also includes: A creation request unit, configured to obtain a conference creation request initiated by a second conference client before the access obtaining unit obtains the conference access request initiated by the first conference client, wherein the conference creation request is used to request the creation of the target network conference; A data generation unit, used to generate a random number having a first set number of digits, and a timestamp sequence having a second set number of digits for representing a current moment; An identification generating unit, used to generate a conference identification including the random number and a timestamp sequence; The conference construction unit is used to construct a target network conference with the conference identifier for the second conference client.

11. The device according to claim 10, characterized in that The device also includes: A version determination unit, used to determine a version number of an identifier generation algorithm used to construct a conference identifier before generating the conference identifier including the random number and the timestamp sequence; A data generation unit, specifically used to generate a random number with a first set number of digits and a timestamp sequence with a second set number of digits for representing the current moment by using the identification generation algorithm; The identifier generating unit is specifically used to sequentially combine the version number, the random number and the timestamp sequence to obtain a combined conference identifier.

12. The device according to claim 7, characterized in that The conference access request is used to request to obtain conference information of the target network conference; Before responding to the access content requested by the conference access request, the method further includes: Detecting whether the target network conference is a network conference that has ended and whose ending duration exceeds a set duration; If the target network conference is a network conference with a credential sharing mark, the access content requested in response to the conference access request includes: If the target network conference is a network conference with a credential sharing mark and the target network conference meets the set conditions, the conference information requested by the conference access request is obtained, and the obtained conference information is returned to the first conference client, and the set conditions include: the target network conference has not ended; or the target network conference has ended and the end time does not exceed the set time threshold.

13. A server, characterized in that: including memory and processor; Wherein, the memory is used to store programs; The processor is used to execute the program, and when the program is executed, it is specifically used to implement the conference access control method according to any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are loaded and executed by the processor, the conference access control method as described in any one of claims 1 to 6 is implemented.

Images