Information sending method, apparatus, device, medium and program product
Patent Information
- Application Number
- CN202510571780.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-30
- Publication Date
- 2026-10-30
AI Technical Summary
[0004]参会人数据一般数据量比较大,在参会人数据请求量大的时候,存在查询性能隐患,导致查询效率低下
[0023]本公开的上述各个实施例具有如下有益效果:通过本公开的一些实施例的信息发送方法,可以在会议信息保密的情况下,快捷、高效地实现会议操作用户的身份确认,避免会议出现安全隐患。具体来说,造成相关的身份确认不够高效且存在安全隐患的原因在于:参会人数据一般数据量比较大,在参会人数据请求量大的时候,存在查询性能隐患,导致查询效率低下。除此之外,直接通过查库的方式,可能存在关键会议信息泄露的安全隐患。基于此,本公开的一些实施例的信息发送方法,首先,获取业务操作信息,其中,上述业务操作信息是目标用户在第一会议客户端对目标会议执行目标业务操作的操作信息,上述业务操作信息包括:目标参会人对应的凭证编码入参和会议操作入参,上述目标参会人为上述目标会议的参会人。在这里,在确定目标用户在第一会议客户端对目标会议执行目标业务操作时,通过获取业务操作信息来确定目标用户是否为参会人的身份验证信息。在这里,通过业务操作包括的凭证编码入参和会议操作入参,以后续确定存在会议凭证和进行内容匹配。然后,根据上述凭证编码入参,确定目标缓存中是否存在对应的会议凭证。在这里,通过凭证编码入参和会议凭证包括的凭证编码的匹配来确定目标缓存中是否存在对应的会议凭证,可以保障在查询过程中的隐私会议信息的安全,避免出现关键安全信息的泄露。最后,响应于确定存在上述会议凭证且上述会议凭证中的凭证内容与上述会议操作入参匹配,生成表征上述目标用户为上述目标参会人的身份确认信息和支持信息,上述支持信息表征上述目标用户存在权限在第一会议客户端对目标会议执行目标业务操作。在这里,通过生成身份确认信息和支持信息,以表征上述目标用户存在操作权限对上述目标会议执行上述目标业务操作且目标用户为参会人员。在这里,通过内容匹配的形式,可以保障会议基础信息(即会议凭证中的凭证内容)和会议操作过程中的相关信息(会议操作入参)的内容匹配,以进一步确认会议操作相关信息是否一致。最后,将上述身份确认信息和上述支持信息发送至上述第一会议客户端,以对目标会议执行目标业务操作。综上,通过凭证编码匹配的方式,可以在保障会议信息安全的基础上确定目标缓存中是否存在凭证编码入参相对应的会议凭证。在此基础上,通过内容匹配的方式可以进一步确定会议操作相关的信息的是否一致,可以快捷、高效地实现会议操作用户的身份确认,避免会议出现安全隐患。
Smart Images

Figure CN123020527A_ABST
Abstract
Description
Technical Field
[0001] The embodiments disclosed herein relate to the field of conference security, specifically to information transmission methods, apparatus, devices, media, and program products. Background Technology
[0002] Currently, ensuring meeting security is one of the important development directions in the security field. Verifying the identity of meeting operators is crucial for meeting security. The common method for verifying the identity of meeting operators is through database lookup to confirm whether the operator is a participant in the meeting.
[0003] However, the inventors discovered that when using the above method to verify the identity of users operating in a meeting, the following technical problems often arise:
[0004] Attendee data is typically quite large, and when there are many requests for this data, query performance may suffer, leading to low query efficiency. Furthermore, directly querying the database may pose a security risk of leaking critical meeting information.
[0005] The information disclosed in this background section is only intended to enhance the understanding of the background of the inventive concept, and therefore may contain information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0006] The summary portion of this disclosure is intended to provide a brief overview of the concepts, which will be described in detail in the detailed description portion. This summary portion is not intended to identify key or essential features of the claimed technical solutions, nor is it intended to limit the scope of the claimed technical solutions.
[0007] Some embodiments of this disclosure provide information transmission methods, apparatuses, devices, media, and program products to address the technical problems mentioned in the background section above.
[0008] In a first aspect, some embodiments of this disclosure provide an information sending method, including: acquiring business operation information, wherein the business operation information is operation information of a target user performing a target business operation on a target meeting in a first meeting client, the business operation information including: a credential code input parameter corresponding to a target participant and a meeting operation input parameter, the target participant being a participant in the target meeting; determining whether a corresponding meeting credential exists in a target cache based on the credential code input parameter; in response to determining that the meeting credential exists and that the credential content in the meeting credential matches the meeting operation input parameter, generating identity confirmation information and support information indicating that the target user is the target participant, the support information indicating that the target user has the authority to perform the target business operation on the target meeting in the first meeting client; and sending the identity confirmation information and the support information to the first meeting client to perform the target business operation on the target meeting.
[0009] Optionally, the above-mentioned meeting operation input parameters include: meeting information input parameters; and the above-mentioned determination of whether there is a corresponding meeting credential in the target cache based on the above-mentioned credential code input parameters includes: determining from the above-mentioned target cache whether there is a meeting credential corresponding to the above-mentioned credential code input parameters and the above-mentioned meeting information input parameters based on the credential code and meeting information included in the meeting credential.
[0010] Optionally, the above method further includes: in response to determining that the above meeting credentials exist and that the credentials content in the above meeting credentials does not match the above meeting operation input parameters, sending identity confirmation information indicating that the above target user is not the above target participant to the above first meeting client, so as to prompt the above target user that they do not have the operation permission to perform the above target business operation on the above target meeting.
[0011] Optionally, the above-mentioned meeting operation input parameters further include: user information input parameters; and before generating identity verification information and support information indicating that the target user is the target participant in response to determining that the above-mentioned meeting credentials exist and that the credential content in the above-mentioned meeting credentials matches the above-mentioned meeting operation input parameters, the above-mentioned method further includes: for the above-mentioned credential content, performing the following matching steps: determining whether the user information in the above-mentioned credential content matches the above-mentioned user information input parameters to generate user matching information; determining whether the meeting time in the above-mentioned credential content matches the meeting time input parameter in the above-mentioned meeting information input parameters to generate time matching information; in response to determining that the above-mentioned user matching information indicates a match and the above-mentioned time matching information indicates a match, determining that the credential content in the above-mentioned meeting credentials matches the above-mentioned meeting operation input parameters.
[0012] Optionally, the above method further includes: in response to determining that the group members corresponding to the target meeting perform a change operation for the target meeting on the second meeting client, notifying each online meeting client in the online meeting client set to update the meeting list, so as to change the meeting credentials related to the target meeting for each participant in the target cache, wherein the change operation is one of the following: meeting deletion operation, meeting cancellation operation, meeting time change operation.
[0013] Optionally, the above method further includes: in response to the target number of times the target business operation is executed and a prompt is made each time that the target user is not the target participant, sending the business operation information set corresponding to the target user to the meeting abnormal operation processing terminal; in response to receiving the abnormal operation processing information sent by the meeting abnormal operation processing terminal, generating an alarm prompt word corresponding to the abnormal operation processing information; and displaying the alarm prompt word on the first meeting client.
[0014] Secondly, some embodiments of this disclosure provide an information sending apparatus, including: an acquisition unit configured to acquire business operation information, wherein the business operation information is operation information of a target user performing a target business operation on a target meeting in a first meeting client, the business operation information including: a credential code input parameter corresponding to a target participant and a meeting operation input parameter, the target participant being a participant in the target meeting; a determination unit configured to determine whether a corresponding meeting credential exists in a target cache based on the credential code input parameter; a generation unit configured to, in response to determining that the meeting credential exists and that the credential content in the meeting credential matches the meeting operation input parameter, generate identity confirmation information and support information indicating that the target user is the target participant, the support information indicating that the target user has the authority to perform the target business operation on the target meeting in the first meeting client; and a sending unit configured to send the identity confirmation information and the support information to the first meeting client to perform the target business operation on the target meeting.
[0015] Optionally, the above-mentioned meeting operation input parameters include: meeting information input parameters; and the determining unit can be configured to: determine from the above-mentioned target cache whether there is a meeting credential corresponding to the above-mentioned credential code input parameter and the above-mentioned meeting information input parameter, based on the credential code and meeting information included in the meeting credential.
[0016] Optionally, the device further includes: in response to determining that the meeting credentials exist and that the content of the meeting credentials does not match the meeting operation input parameters, sending identity confirmation information indicating that the target user is not the target participant to the first meeting client, so as to prompt the target user that they do not have the operation permission to perform the target business operation on the target meeting.
[0017] Optionally, the above-mentioned meeting operation input parameters further include: user information input parameters; and the device further includes: for the above-mentioned credential content, performing the following matching steps: determining whether the user information in the above-mentioned credential content matches the above-mentioned user information input parameters, so as to generate user matching information; determining whether the meeting time in the above-mentioned credential content matches the meeting time input parameters in the above-mentioned meeting information input parameters, so as to generate time matching information; in response to determining that the above-mentioned user matching information indicates a match and the above-mentioned time matching information indicates a match, determining that the credential content in the above-mentioned meeting credential matches the above-mentioned meeting operation input parameters.
[0018] Optionally, the apparatus further includes: in response to determining that the group members corresponding to the target meeting perform a change operation for the target meeting on the second meeting client, notifying each online meeting client in the online meeting client set to update the meeting list, so as to change the meeting credentials related to the target meeting for each participant in the target cache, wherein the change operation is one of the following: meeting deletion operation, meeting cancellation operation, meeting time change operation.
[0019] Optionally, the device further includes: in response to the target number of times the target business operation is performed and a prompt is made each time that the target user is not the target participant, sending the business operation information set corresponding to the target user to the meeting abnormal operation processing terminal; in response to receiving the abnormal operation processing information sent by the meeting abnormal operation processing terminal, generating an alarm prompt word corresponding to the abnormal operation processing information; and displaying the alarm prompt word on the first meeting client.
[0020] Thirdly, some embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device having one or more programs stored thereon, such that when the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any implementation of the first aspect.
[0021] Fourthly, some embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method as described in any implementation of the first aspect.
[0022] Fifthly, some embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the method described in any of the implementations of the first aspect above.
[0023] The above-described embodiments of this disclosure have the following beneficial effects: Through the information sending methods of some embodiments of this disclosure, the identity verification of meeting operation users can be achieved quickly and efficiently while maintaining the confidentiality of meeting information, thus avoiding security risks in the meeting. Specifically, the reason for the inefficient identity verification and security risks is that the participant data is generally large in volume, and when the number of participant data requests is large, there are query performance risks, leading to low query efficiency. In addition, directly querying the database may pose a security risk of leaking critical meeting information. Based on this, the information sending method of some embodiments of this disclosure first obtains business operation information, wherein the aforementioned business operation information is the operation information of the target user performing a target business operation on the target meeting in the first meeting client. The aforementioned business operation information includes: the credential code input parameter corresponding to the target participant and the meeting operation input parameter, and the aforementioned target participant is the participant of the aforementioned target meeting. Here, when determining that the target user is performing a target business operation on the target meeting in the first meeting client, the identity verification information of the target user as a participant is determined by obtaining the business operation information. Here, the credential code input parameter and the meeting operation input parameter included in the business operation are used to subsequently determine the existence of meeting credentials and perform content matching. Then, based on the aforementioned credential code input parameter, it is determined whether a corresponding meeting credential exists in the target cache. Here, determining the existence of a corresponding meeting credential in the target cache by matching the credential code input parameter with the credential codes included in the meeting credential ensures the security of private meeting information during the query process and prevents the leakage of critical security information. Finally, in response to the determination that the aforementioned meeting credential exists and that the credential content in the aforementioned meeting credential matches the aforementioned meeting operation input parameter, identity verification information and support information are generated, indicating that the aforementioned target user is the aforementioned target participant. The support information indicates that the aforementioned target user has the authority to perform the target business operation on the target meeting in the first meeting client. Here, by generating identity verification information and support information, it is confirmed that the aforementioned target user has the operation authority to perform the aforementioned target business operation on the aforementioned target meeting and that the target user is a participant. Here, through content matching, it is ensured that the basic meeting information (i.e., the credential content in the meeting credential) and the relevant information during the meeting operation process (meeting operation input parameter) match, further confirming whether the relevant information of the meeting operation is consistent. Finally, the aforementioned identity verification information and the aforementioned support information are sent to the aforementioned first meeting client to perform the target business operation on the target meeting. In summary, by matching credential codes, we can determine whether a meeting credential corresponding to the credential code input parameter exists in the target cache while ensuring the security of meeting information. Furthermore, content matching can further verify the consistency of meeting operation-related information, enabling quick and efficient user identity verification and preventing security risks during meetings. Attached Figure Description
[0024] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and elements are not necessarily drawn to scale.
[0025] Figure 1 This is a schematic diagram illustrating an application scenario of an information sending method according to some embodiments of the present disclosure;
[0026] Figure 2 This is a flowchart of some embodiments of the information transmission method according to this disclosure;
[0027] Figure 3 These are flowcharts of other embodiments of the information transmission method according to this disclosure;
[0028] Figure 4 This is a schematic diagram illustrating adaptive adjustments to authentication and conference credentials in some embodiments of the information transmission method according to this disclosure;
[0029] Figure 5 These are schematic diagrams illustrating the structure of some embodiments of the information transmission apparatus according to this disclosure;
[0030] Figure 6 This is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. Detailed Implementation
[0031] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.
[0032] It should also be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings. Unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other.
[0033] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.
[0034] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".
[0035] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.
[0036] Before performing any of the operations involving the collection, storage, or use of user personal information (such as business operation information) disclosed in this disclosure, the relevant organizations or individuals shall fulfill their obligations, including conducting personal information security impact assessments, informing personal information subjects, and obtaining prior authorization and consent from personal information subjects.
[0037] This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.
[0038] Figure 1 This is a schematic diagram of an application scenario of an information sending method according to some embodiments of the present disclosure.
[0039] exist Figure 1In this application scenario, firstly, electronic device 101 can obtain business operation information 102. This business operation information 102 is the operation information of target user 104 performing a target business operation on the target meeting through the first meeting client 103. The business operation information 102 includes: the credential code input parameter corresponding to the target participant and the meeting operation input parameter. The target participant is the participant in the target meeting. In this application scenario, business operation information 102 can be the operation information of target user 104 performing the operation of viewing meeting details on meeting A through the first meeting client 103. The target participant can be participant A. The credential code input parameter can be "213saa". The meeting operation input parameter can be "user contact information, meeting ID". Then, electronic device 101 can determine whether a corresponding meeting credential 106 exists in the target cache 105 based on the credential code input parameter. In this application scenario, the target cache 105 includes: meeting credential A, meeting credential B, meeting credential C, and meeting credential D. Meeting credential A can be "(credential code input parameter: 213saa), credential content A". Meeting credential B can be "(credential code input parameter: 123rda), credential content B". Meeting credential C can be "(credential code input parameter: 358Sza), credential content C". Meeting credential D can be "(credential code input parameter: 1983da), credential content D". Meeting credential 106 can be meeting credential A. Furthermore, in response to determining the existence of the aforementioned meeting credential 106 and that the credential content in the aforementioned meeting credential 106 matches the aforementioned meeting operation input parameter, electronic device 101 can generate identity verification information 107 and supporting information 108 indicating that the aforementioned target user 104 is the aforementioned target participant. The supporting information 108 indicates that the aforementioned target user 104 has the authority to perform the target business operation on the target meeting in the first meeting client 103. Finally, electronic device 101 can send the aforementioned identity verification information 107 and the aforementioned supporting information 108 to the aforementioned first meeting client 103 to perform the target business operation on the target meeting.
[0040] It should be noted that the aforementioned electronic device 101 can be either hardware or software. When the electronic device is hardware, it can be implemented as a distributed cluster consisting of multiple servers or terminal devices, or as a single server or a single terminal device. When the electronic device is software, it can be installed in the hardware devices listed above. It can be implemented as, for example, multiple software programs or software modules used to provide distributed services, or as a single software program or software module. No specific limitations are made here.
[0041] It should be understood that Figure 1 The number of electronic devices shown is merely illustrative. Any number of electronic devices can be used depending on the implementation requirements.
[0042] Continue to refer to Figure 2 The flowchart 200 illustrates some embodiments of an information transmission method according to the present disclosure. The information transmission method includes the following steps:
[0043] Step 201: Obtain business operation information.
[0044] In some embodiments, the entity executing the above information sending method (e.g.) Figure 1 The electronic device 101 shown can acquire business operation information via wired or wireless connection. This business operation information refers to the operation information of the target user performing target business operations on the target meeting through the first meeting client. The target user can be a user whose identity needs to be verified and who is performing the target business operation on the target meeting. Identity verification can determine whether the target user is a target participant. The first meeting client can be the client operated by the target user. In practice, the first meeting client can be a client displaying the meeting schedule corresponding to the target participant. For example, the first meeting client can be the meeting client on the terminal used by the target participant. The target meeting can be the object of the business operation performed by the target user. The target business operation can be the business operation selected by the target user to perform on the target meeting. In practice, the target business operation can be, but is not limited to, one of the following: video conference entry operation, viewing meeting details operation, binding / unbinding document operation, creating meeting minutes operation, creating group chat operation, binding / unbinding meeting room operation. The target participant can be the target of the meeting schedule displayed by the first meeting client. That is, the meeting schedule displayed by the first meeting client is created for the target participant. It should be noted that the target user is the object of operation for the target meeting in the first meeting client, while the target participant is the actual participant in the target meeting. That is, the target user is not necessarily the target participant, and further identity verification is required. The credential encoding parameter can be a credential encoding parameter set corresponding to the target participant. In practice, business operation information can be information related to the business operation process that is parsed and processed in the confirmation request sent by the first meeting client. The credential encoding parameter and the meeting operation parameter can be request parameters in the confirmation request. The credential encoding parameter can be a parameter of the encrypted credential. In practice, the corresponding encryption algorithm can be preset. The content of the credential encoding parameter is relatively small, which is convenient for the target cache to store and query without requiring a large target cache device configuration. In addition, the method of encrypting the credential can effectively achieve the security and confidentiality of meeting information during the query process. For example, the size of the credential encoding parameter in bytes or the string size is less than a preset value. The meeting operation parameter can be parameter content related to the meeting operation process. In practice, the meeting operation parameter can include, but is not limited to, one of the following: information related to the meeting operation user, information related to the target meeting, business operation type, and business operation duration.
[0045] In specific business scenarios, the target attendee can be a real participant in the target meeting. The various meetings corresponding to the target attendee are displayed in the first meeting client. For example, the meetings include: Meeting 1, Meeting 2, Meeting 3, and Meeting 4. When a target user selects to query the meeting details for Meeting 2 in the first meeting client, business operation information is generated during the query process. This information is used to subsequently determine whether the target user is indeed the target attendee.
[0046] Step 202: Based on the above credential code input parameter, determine whether the corresponding meeting credential exists in the target cache.
[0047] In some embodiments, the aforementioned execution entity can determine whether a corresponding meeting credential exists in the target cache based on the aforementioned credential code input parameter. The target cache stores the meeting credentials of the target participant for various time periods. For example, if the target participant has four meetings on November 10th, then the target cache will store four meeting credentials corresponding to the target participant on November 10th. The meeting credential can represent relevant proof of the meeting. The meeting credential may include, but is not limited to: the credential content and credential code corresponding to the meeting. The credential content can be relevant identity verification content for the meeting. In practice, the credential content may include, but is not limited to, one of the following: participant ID, tenant ID, meeting start and end time, and meeting ID.
[0048] As an example, the aforementioned execution entity can perform a consistency check between the credential code in each meeting credential in the target cache and the credential code input parameter to determine whether the corresponding meeting credential exists in the target cache. That is, if the credential code input parameter is found to be the same as the corresponding credential code, it indicates that the corresponding meeting credential exists in the target cache.
[0049] In some optional implementations of certain embodiments, the above-mentioned meeting operation input parameters include: meeting information input parameters. The meeting information input parameters can be meeting introduction information related to the target meeting. For example, the meeting information input parameter can be a meeting ID.
[0050] Optionally, based on the credential code and meeting information included in the meeting credential, the aforementioned executing entity can determine from the aforementioned target cache whether there is a meeting credential corresponding to the aforementioned credential code input parameter and the aforementioned meeting information input parameter.
[0051] As an example, the aforementioned execution entity can query the target cache to see if there is a meeting credential with the corresponding credential code matching the credential code input parameter and the corresponding meeting information matching the meeting information input parameter.
[0052] In practical scenarios, for each meeting on the meeting schedule, the first step is to encrypt and combine meeting-related information to generate a meeting-specific credential code. For example, the meeting time, meeting ID, and participant information can be combined (e.g., information concatenation followed by encoding) to obtain the credential code. Then, the credential code is combined again with other meeting-related information to generate the corresponding meeting credential. For instance, the credential code, meeting time, meeting ID, and participant information can be concatenated to obtain the meeting credential.
[0053] For example, the meeting time, meeting ID, and participant information can be directly combined and encoded to obtain meeting credentials.
[0054] Step 203: In response to determining that the above-mentioned meeting credentials exist and that the content of the above-mentioned meeting credentials matches the above-mentioned meeting operation input parameters, generate identity verification information and support information that characterize the above-mentioned target user as the above-mentioned target participant.
[0055] In some embodiments, in response to determining that the aforementioned meeting credentials exist and that the credential content in the meeting credentials matches the aforementioned meeting operation input parameters, the executing entity can generate identity verification information and support information indicating that the aforementioned target user is the aforementioned target participant. The identity verification information can be confirmation information confirming whether the target user is the target participant. In practice, the identity verification information can be one of the following: information indicating that the aforementioned target user is not the aforementioned target participant, or information indicating that the aforementioned target user is the aforementioned target participant. The support information indicates that the aforementioned target user has the authority to perform the target business operation on the target meeting in the first meeting client.
[0056] Step 204: Send the aforementioned identity verification information and supporting information to the aforementioned first conference client to perform the target business operation on the target conference.
[0057] In some embodiments, the aforementioned executing entity may send the aforementioned identity verification information and the aforementioned support information to the aforementioned first conference client in order to perform target business operations on the target conference.
[0058] In some optional implementations of certain embodiments, after step 204, the steps further include:
[0059] In response to the determination that the aforementioned meeting credentials exist and that the content of the meeting credentials does not match the aforementioned meeting operation input parameters, the executing entity may send identity confirmation information indicating that the aforementioned target user is not the aforementioned target participant to the aforementioned first meeting client, thereby prompting the aforementioned target user that they do not have the operation permission to perform the aforementioned target business operation on the aforementioned target meeting. In a specific scenario, this can be achieved through a pop-up message indicating that the aforementioned target user does not have the operation permission to perform the aforementioned target business operation on the aforementioned target meeting.
[0060] In some optional implementations of certain embodiments, the above-mentioned conference operation input parameters further include: user information input parameters. Here, user information input parameters can be user information parameters related to the target user. In practice, user information input parameters can be parameter information related to the target user extracted from the request information sent by the first conference client. In practice, user information input parameters can include, but are not limited to, at least one of the following: user ID, user contact information, user login IP, user name, and user login device information.
[0061] Optionally, prior to step 203, the above method further includes the following steps:
[0062] The first step is to perform the following matching steps for the above voucher content:
[0063] Sub-step 1 determines whether the user information in the aforementioned voucher content matches the aforementioned user information input parameters, thereby generating user matching information. The user information in the voucher content can be participant information related to the target participant. In practice, user information can include, but is not limited to, one of the following: participant identifier, participant tenant identifier, participant name, participant contact information. User matching information can be one of the following: matching information indicating a mismatch between the user information and the user information input parameters, or matching information indicating a match between the user information and the user information input parameters.
[0064] Sub-step 2 involves determining whether the meeting time in the aforementioned voucher content matches the meeting time input parameter in the aforementioned meeting information, in order to generate time matching information. The meeting time can be the meeting start time or the meeting end time. The time matching information can be one of the following: information indicating a time mismatch, or information indicating a time match.
[0065] The second step is to determine, in response to the determination of the above user matching information representation matching and the above time matching information representation matching, to determine that the above meeting credentials exist and that the content of the above meeting credentials matches the above meeting operation input parameters.
[0066] In some optional implementations of certain embodiments, after determining that the user matching information representation matches and the time matching information representation matches, and determining that the meeting credential exists and that the credential content in the meeting credential matches the meeting operation input parameters, the steps further include:
[0067] In response to determining that the above user matching information representation does not match and / or the above time matching information representation does not match, it is determined that the above meeting credentials exist and that the content of the above meeting credentials does not match the above meeting operation input parameters.
[0068] In some optional implementations of certain embodiments, after step 204, the steps further include:
[0069] The first step, in response to the target number of times the target business operation is executed reaching the target number, and each time a notification is sent indicating that the target user is not the target participant, sends the business operation information set corresponding to the target user to the meeting anomaly handling terminal. The number of times the target business operation is executed can be the total number of operations performed on the target meeting within a certain time period. For example, within 10 minutes, the target user performs a total of 3 operations on the target meeting. The target number can be a pre-set anomaly alarm count value. For example, the target number could be "5 times". The business operation information set can be the individual business operation information obtained after each execution of the target business operation. The anomaly handling terminal can be a processing terminal that detects whether there are any abnormal operations on the target meeting. Specific anomaly detection can be determined through preset algorithm logic. For example, anomaly detection can be based on operation frequency.
[0070] The second step involves generating an alarm message corresponding to the received abnormal operation handling information from the aforementioned meeting abnormal operation handling terminal. The abnormal operation handling information can be the result of handling whether an abnormal operation occurred after the target user performed multiple operations. That is, the abnormal operation handling information can be one of the following: handling information indicating an abnormal operation occurred, or handling information indicating no abnormal operation occurred. The alarm message can be a message used to alert the target user whether their corresponding operation behavior is abnormal and to indicate how to handle it. For example, for abnormal operation handling information indicating an abnormal operation occurred, the corresponding alarm message could be "You are not a participant; please do not perform any further operations on the target meeting." As another example, for abnormal operation handling information indicating no abnormal operation occurred, the corresponding alarm message could be "You are not a participant; please follow *** for further verification to see if you have permission to operate on the target meeting."
[0071] The third step is to display the aforementioned alarm message in the first meeting client.
[0072] The above-described embodiments of this disclosure have the following beneficial effects: Through the information sending methods of some embodiments of this disclosure, the identity verification of meeting operation users can be achieved quickly and efficiently while maintaining the confidentiality of meeting information, thus avoiding security risks in the meeting. Specifically, the reason for the inefficient identity verification and security risks is that the participant data is generally large in volume, and when the number of participant data requests is large, there are query performance risks, leading to low query efficiency. In addition, directly querying the database may pose a security risk of leaking critical meeting information. Based on this, the information sending method of some embodiments of this disclosure first obtains business operation information, wherein the aforementioned business operation information is the operation information of the target user performing a target business operation on the target meeting in the first meeting client. The aforementioned business operation information includes: the credential code input parameter corresponding to the target participant and the meeting operation input parameter, and the aforementioned target participant is the participant of the aforementioned target meeting. Here, when determining that the target user is performing a target business operation on the target meeting in the first meeting client, the identity verification information of the target user as a participant is determined by obtaining the business operation information. Here, the credential code input parameter and the meeting operation input parameter included in the business operation are used to subsequently determine the existence of meeting credentials and perform content matching. Then, based on the aforementioned credential code input parameter, it is determined whether a corresponding meeting credential exists in the target cache. Here, determining the existence of a corresponding meeting credential in the target cache by matching the credential code input parameter with the credential codes included in the meeting credential ensures the security of private meeting information during the query process and prevents the leakage of critical security information. Finally, in response to the determination that the aforementioned meeting credential exists and that the credential content in the aforementioned meeting credential matches the aforementioned meeting operation input parameter, identity verification information and support information are generated, indicating that the aforementioned target user is the aforementioned target participant. The support information indicates that the aforementioned target user has the authority to perform the target business operation on the target meeting in the first meeting client. Here, by generating identity verification information and support information, it is confirmed that the aforementioned target user has the operation authority to perform the aforementioned target business operation on the aforementioned target meeting and that the target user is a participant. Here, through content matching, it is ensured that the basic meeting information (i.e., the credential content in the meeting credential) and the relevant information during the meeting operation process (meeting operation input parameter) match, further confirming whether the relevant information of the meeting operation is consistent. Finally, the aforementioned identity verification information and the aforementioned support information are sent to the aforementioned first meeting client to perform the target business operation on the target meeting. In summary, by matching credential codes, we can determine whether a meeting credential corresponding to the credential code input parameter exists in the target cache while ensuring the security of meeting information. Furthermore, content matching can further verify the consistency of meeting operation-related information, enabling quick and efficient user identity verification and preventing security risks during meetings.
[0073] Further reference Figure 3 The flowchart 300 illustrates another embodiment of the information transmission method according to this disclosure. The information transmission method includes the following steps:
[0074] Step 301: Obtain business operation information.
[0075] Step 302: Based on the above credential code input parameter, determine whether the corresponding meeting credential exists in the target cache.
[0076] Step 303: In response to determining that the above-mentioned meeting credentials exist and that the content of the above-mentioned meeting credentials matches the above-mentioned meeting operation input parameters, generate identity verification information and support information that characterize the above-mentioned target user as the above-mentioned target participant.
[0077] Step 304: Send the aforementioned identity verification information and supporting information to the aforementioned first conference client to perform the target business operation on the target conference.
[0078] In some embodiments, the specific implementation of steps 301-304 and the resulting technical effects can be found in [reference needed]. Figure 2 Steps 201-204 in the corresponding embodiments will not be repeated here.
[0079] Step 305: In response to determining that the group members corresponding to the target meeting will perform a change operation for the target meeting in the second meeting client, notify each online meeting client in the online meeting client set to update the meeting list so as to change the meeting credentials related to the target meeting for each participant in the target cache.
[0080] In some embodiments, in response to determining that the group members corresponding to the target meeting perform a change operation for the target meeting on the second meeting client, the executing entity (e.g., Figure 1The electronic device 101 shown can notify each online meeting client in the online meeting client set to update the meeting list, thereby changing the meeting credentials associated with the target meeting for each participant in the target cache. The change operation can be one of the following: participant deletion, meeting cancellation, or meeting time change. The group leader can be the object that organizes the target meeting; that is, the group leader is the object that creates the target meeting. The second meeting client can be the meeting client used by the group leader. The meeting cancellation operation can be an operation to cancel the meeting schedule for the target meeting. The participant deletion operation can be an operation to delete each participant in the target meeting. The meeting time change operation can be an operation to change the meeting time; that is, an operation to change the start time of the target meeting. The online meeting client can be a meeting client with user access and login. The meeting list can be the meeting list of the user corresponding to the online meeting client. For the participant deletion operation, the meeting credentials of the corresponding participant in the target cache can be deleted according to the meeting ID and meeting time. For the meeting cancellation operation, each meeting credential corresponding to the target meeting in the target cache can be deleted according to the meeting ID and meeting time. For changes to meeting times, the meeting times of each meeting credential in the target cache corresponding to the target meeting can be adjusted based on the meeting ID and the meeting time.
[0081] like Figure 4 The diagram illustrates the adaptive adjustments to authentication and meeting credentials.
[0082] First, when a participant accesses the meeting client, the client is triggered to call the meeting list interface to query the meeting list, which is then returned to the client for displaying the participant's assigned meeting. In addition, the meeting list is iterated, and for each meeting, a participant credential code field (i.e., meeting credential) is generated using a participant credential calculation method. Here, the unique key for the meeting is the meeting ID and the meeting start and end times. A credential code is generated by MD6 encryption of the meeting ID, start and end times, user ID, tenant ID, and key. The credential content is generated using the meeting ID, start and end times, user ID, and tenant ID. The meeting credential is generated using a structure <unique key, credential code, credential content>, with a corresponding expiration time set. When a target user is determined to perform a business operation on a target meeting, the participant credential check result determines whether the target user is a participant. If the target user is not a participant, they are prompted that they do not have participant privileges. If the target user is a participant, the next business processing operation is executed. Here, the execution logic of the participant credential check interface is as follows: First, the target cache is queried using the unique key and credential code to determine if a corresponding meeting credential exists. Then, the current user information corresponding to the target user is queried using the user token. Next, the user ID in the meeting credential and the user ID in the current user information are checked to verify user consistency. Finally, the meeting ID and meeting start and end time in the meeting credential are compared with the meeting time and meeting ID input parameters to verify meeting consistency. In addition, when a group allows a meeting change operation to be performed through the meeting client, all online clients will be notified to update the meeting list and adjust the corresponding meeting credentials for the change operation. For example, for a meeting change operation to modify the meeting start and end time, the meeting start and end time can be changed according to the meeting ID to adjust the meeting credential. For a meeting change operation to delete a participant, the corresponding credential code can be deleted according to the unique key. For a meeting change operation to cancel the meeting, each meeting credential in the target cache corresponding to the target meeting is cached and deleted according to the unique key.
[0083] from Figure 3 It can be seen from this that, with Figure 2 Compared to the description of some corresponding embodiments, Figure 3 In some corresponding embodiments, the information sending method process 300 can adaptively adjust each meeting credential in the target cache according to the change operation of the group members, so as to facilitate user authentication of subsequent users, improve authentication efficiency, and avoid wasting a lot of query resources.
[0084] Further reference Figure 5As an implementation of the methods shown in the above figures, this disclosure provides some embodiments of an information transmission device, which are similar to... Figure 2 Corresponding to the method embodiments shown, this information transmission device can be specifically applied to various electronic devices.
[0085] like Figure 5 As shown, an information sending device 500 includes: an acquisition unit 501, a determination unit 502, a generation unit 503, and a sending unit 504. The acquisition unit 501 is configured to acquire business operation information, wherein the business operation information is the operation information of a target user performing a target business operation on a target meeting in a first meeting client. The business operation information includes: a credential code input parameter corresponding to the target participant and meeting operation input parameters, wherein the target participant is a participant in the target meeting. The determination unit 502 is configured to determine whether a corresponding meeting credential exists in the target cache based on the credential code input parameter. The sending unit generation unit 503 is configured to, in response to the determination that the meeting credential exists and that the credential content in the meeting credential matches the meeting operation input parameters, generate identity confirmation information and support information indicating that the target user is the target participant. The support information indicates that the target user has the authority to perform the target business operation on the target meeting in the first meeting client. The sending unit 504 is configured to send the identity confirmation information and the support information to the first meeting client to perform the target business operation on the target meeting.
[0086] In some optional implementations of some embodiments, the above-mentioned meeting operation input parameters include: meeting information input parameters; and the determining unit 502 may be further configured to: determine from the above-mentioned target cache whether there is a meeting credential corresponding to the above-mentioned credential code input parameter and the above-mentioned meeting information input parameter, based on the credential code and meeting information included in the meeting credential.
[0087] In some optional implementations of some embodiments, the information sending device 500 may also be configured to: in response to determining that the above-mentioned meeting credentials exist and that the credential content in the above-mentioned meeting credentials does not match the above-mentioned meeting operation input parameters, send identity confirmation information indicating that the above-mentioned target user is not the above-mentioned target participant to the above-mentioned first meeting client, so as to prompt the above-mentioned target user that there is no operation permission to perform the above-mentioned target business operation on the above-mentioned target meeting.
[0088] In some optional implementations of certain embodiments, the above-mentioned meeting operation input parameters further include: user information input parameters; and the information sending device 500 can also be configured to: for the above-mentioned credential content, perform the following matching steps: determine whether the user information in the above-mentioned credential content matches the above-mentioned user information input parameters, so as to generate user matching information; determine whether the meeting time in the above-mentioned credential content matches the meeting time input parameters in the above-mentioned meeting information input parameters, so as to generate time matching information; in response to determining that the above-mentioned user matching information represents a match and the above-mentioned time matching information represents a match, determine that the credential content in the above-mentioned meeting credential matches the above-mentioned meeting operation input parameters. In some optional implementations of certain embodiments, the above-mentioned device 500 further includes: a notification unit (not shown in the figure). The above-mentioned notification unit can be configured to: in response to determining that the group members corresponding to the above-mentioned target meeting perform a change operation for the above-mentioned target meeting on the second meeting client, notify each online meeting client in the online meeting client set to update the meeting list, so as to change the credentials of each participant in the above-mentioned target cache related to the above-mentioned target meeting, wherein the above-mentioned change operation is one of the following: meeting deletion operation, meeting cancellation operation, meeting time change operation.
[0089] In some optional implementations of certain embodiments, the apparatus 500 further includes: an information sending unit, a prompt word generation unit, and a display unit (not shown in the figure). The information sending unit can be configured to: in response to the target number of times the target business operation is performed reaching a target number, and each time a prompt is given indicating that the target user is not the target participant, send the business operation information set corresponding to the target user to the meeting abnormal operation handling terminal. The prompt word generation unit can be configured to: in response to receiving abnormal operation handling information sent by the meeting abnormal operation handling terminal, generate an alarm prompt word corresponding to the abnormal operation handling information. The display unit can be configured to: display the alarm prompt word on the first meeting client.
[0090] It is understandable that the units described in the information transmitting device 500 are related to the reference. Figure 2 The steps in the described method correspond to each other. Therefore, the operations, features, and beneficial effects described above for the method also apply to the information transmitting device 500 and the units contained therein, and will not be repeated here.
[0091] The following is for reference. Figure 6 It illustrates electronic devices suitable for implementing some embodiments of this disclosure (e.g., Figure 1 A schematic diagram of the structure of electronic device 101)600 in the middle. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of this disclosure.
[0092] like Figure 6 As shown, the electronic device 600 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory 602 or a program loaded from a storage device 608 into a random access memory 603. The random access memory 603 also stores various programs and data required for the operation of the electronic device 600. The processing unit 601, the read-only memory 602, and the random access memory 603 are interconnected via a bus 604. An input / output interface 605 is also connected to the bus 604.
[0093] Typically, the following devices can be connected to the input / output interface 605: input devices 606 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 608 including, for example, magnetic tape, hard disk, etc.; and communication devices 609. Communication device 609 allows electronic device 600 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 6 An electronic device 600 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively. Figure 6 Each box shown can represent a device or multiple devices as needed.
[0094] In particular, according to some embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, some embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 609, or installed from a storage device 608, or installed from a read-only memory 602. When the computer program is executed by the processing device 601, it performs the functions defined above in the methods of some embodiments of this disclosure.
[0095] It should be noted that, in some embodiments of this disclosure, the computer-readable medium described above may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In some embodiments of this disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In some embodiments of this disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.
[0096] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.
[0097] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently without being assembled into the electronic device. The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: acquire business operation information, wherein the aforementioned business operation information is operation information of a target user performing a target business operation on a target meeting in a first meeting client, the aforementioned business operation information including: a credential code input parameter corresponding to the target participant and meeting operation input parameters, the aforementioned target participant being a participant in the aforementioned target meeting; determine whether a corresponding meeting credential exists in the target cache based on the aforementioned credential code input parameter; in response to determining that the aforementioned meeting credential exists and that the credential content in the aforementioned meeting credential matches the aforementioned meeting operation input parameters, generate identity verification information and support information indicating that the aforementioned target user is the aforementioned target participant, the aforementioned support information indicating that the aforementioned target user has the authority to perform the target business operation on the target meeting in the first meeting client; and send the aforementioned identity verification information and the aforementioned support information to the aforementioned first meeting client to perform the target business operation on the target meeting.
[0098] Computer program code for performing operations of some embodiments of this disclosure can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, and conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0099] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0100] The units described in some embodiments of this disclosure can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including an acquisition unit, a determination unit, a generation unit, and a transmission unit. The names of these units do not necessarily limit the specific unit; for example, an acquisition unit can also be described as a "unit for acquiring business operation information."
[0101] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.
[0102] Some embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements any of the above-described information transmission methods.
[0103] The above description is merely a selection of preferred embodiments of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the embodiments of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in the embodiments of this disclosure.
Claims
1. A method for sending information, comprising: Obtain business operation information, wherein the business operation information is the operation information of the target user performing the target business operation on the target meeting in the first meeting client, and the business operation information includes: the credential code input parameter corresponding to the target participant and the meeting operation input parameter, wherein the target participant is the participant of the target meeting; Based on the credential code input parameter, determine whether the corresponding meeting credential exists in the target cache; In response to determining that the meeting credentials exist and that the content of the meeting credentials matches the meeting operation input parameters, identity verification information and support information are generated to indicate that the target user is the target participant. The support information indicates that the target user has the authority to perform target business operations on the target meeting in the first meeting client. The identity verification information and the support information are sent to the first conference client to perform the target business operation on the target conference.
2. The method according to claim 1, wherein, The meeting operation input parameters include: meeting information input parameters; and The step of determining whether a corresponding meeting credential exists in the target cache based on the credential encoding input parameter includes: Based on the credential code and meeting information included in the meeting credential, determine from the target cache whether a meeting credential corresponding to the credential code input parameter and the meeting information input parameter exists.
3. The method according to claim 1, wherein, The method further includes: In response to determining that the meeting credentials exist and that the content of the meeting credentials does not match the meeting operation input parameters, an identity verification message indicating that the target user is not the target participant is sent to the first meeting client to prompt the target user that they do not have the operation permission to perform the target business operation on the target meeting.
4. The method according to claim 1, wherein, The meeting operation input parameters also include: user information input parameters; and Before generating identity verification information and support information indicating that the target user is the target participant in response to determining that the meeting credential exists and that the credential content in the meeting credential matches the meeting operation input parameters, the method further includes: For the content of the voucher, perform the following matching steps: Determine whether the user information in the voucher content matches the user information input parameters, so as to generate user matching information; Determine whether the meeting time in the voucher content matches the meeting time input parameter in the meeting information input parameter, so as to generate time matching information; In response to determining that the user matching information indicates a match and the time matching information indicates a match, the content of the credential in the meeting credential is determined to match the meeting operation input parameters.
5. The method according to claim 1, wherein, The method further includes: In response to determining that the group members corresponding to the target meeting perform a change operation for the target meeting on the second meeting client, the online meeting client set is notified to update the meeting list so as to change the meeting credentials related to the target meeting for each participant in the target cache. The change operation is one of the following: meeting deletion operation, meeting cancellation operation, and meeting time change operation.
6. The method according to claim 1, wherein, The method further includes: In response to the target number of times the target business operation is executed and a prompt is made each time that the target user is not the target participant, the business operation information set corresponding to the target user is sent to the meeting abnormal operation processing terminal. In response to receiving abnormal operation processing information sent by the conference abnormal operation processing terminal, an alarm prompt word corresponding to the abnormal operation processing information is generated; The alarm message will be displayed in the first conference client.
7. An information transmitting device, comprising: The acquisition unit is configured to acquire business operation information, wherein the business operation information is the operation information of the target user performing target business operations on the target meeting in the first meeting client, and the business operation information includes: the credential code input parameter corresponding to the target participant and the meeting operation input parameter, wherein the target participant is the participant of the target meeting; The determining unit is configured to determine whether a corresponding meeting credential exists in the target cache based on the credential encoding input parameter; The generation unit is configured to generate identity verification information and support information that characterize the target user as the target participant in response to determining that the meeting credential exists and that the credential content in the meeting credential matches the meeting operation input parameters. The support information characterizes that the target user has the authority to perform target business operations on the target meeting in the first meeting client. The sending unit is configured to send the identity verification information and the support information to the first conference client in order to perform target business operations on the target conference.
8. An electronic device, comprising: One or more processors; Storage device, on which one or more programs are stored, When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6.
9. A computer-readable medium having a computer program stored thereon, wherein, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-6.
10. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-6.
