Access method, device and equipment of audio and video online conference and medium

Abstract

The application discloses an access method and device of an audio and video online conference, equipment and medium, and belongs to the network application field. The application is applied to a unified conference client, and comprises the following steps: sending user registration information and a feedback token request to a unified conference server, and receiving a target token fed back by the unified conference server based on the user registration information and the feedback token request; determining a third-party conference server, and sending the target token to the third-party conference server for verification; and if the verification result fed back by the third-party conference server is verification pass, establishing an audio and video online conference with the third-party conference server. Once the unified conference client is registered, various audio and video online conferences can be selected and accessed, and the efficiency of accessing the audio and video online conference and office is greatly improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of network applications, and in particular to an access method, device and equipment for online audio-video conference and a storage medium. BACKGROUND

[0002] At present, with the acceleration of the digital transformation of the economic society, remote office is accelerating popularization. Meanwhile, driven by the epidemic, the scale of remote office users gradually expands and the use habits gradually develop, and audio-video conference, as a high-frequency application of remote office, develops rapidly.

[0003] The existing audio-video conference scheme usually takes a mobile phone, a PC and the like as a client carrier, needs to install a dedicated conference client, and the conference initiator and the conference participant need to install the same conference client to realize interconnection and intercommunication of both parties of the conference. For example, Figure 2 As shown, when user A needs to join the conference initiated by user B for audio-video conference communication, if user B uses XX conference, user A needs to install the XX conference client to join the XX conference initiated by user B; if the next time needs to have audio-video conference with user C, and user C uses YY conference, user A needs to additionally install the YY conference client to join the YY conference initiated by user C.

[0004] The mainstream clients in the current market are various, and usually need to register and install various types of audio-video conference software clients to join or initiate various audio-video conferences at any time. SUMMARY

[0005] The main purpose of the present application is to provide an access method, device and storage medium for online audio-video conference, aiming at solving the technical problem of complicated steps in participating in different types of online conference on the audio-video conference device in the prior art.

[0006] To achieve the above-mentioned purpose, the present application provides an access method for online audio-video conference, which is applied to a unified conference client and includes the following steps.

[0007] Sending user registration information and a feedback token request to a unified conference server, and receiving a target token fed back by the unified conference server based on the user registration information and the feedback token request;

[0008] Determining a third-party conference server, and sending the target token to the third-party conference server for verification;

[0009] If the verification result fed back by the third-party conference server is verification passed, an online audio-video conference with the third-party conference server is established.

[0010] Optionally, the step of receiving the feedback token requested by the unified conference server based on the user registration information and the feedback token request comprises:

[0011] If the feedback token request is an SDK token request, receiving an SDK token fed back by the unified conference server based on the user registration information and the SDK token request; and / or,

[0012] If the feedback token request is an identity token request, receiving an identity token fed back by the unified conference server based on the user registration information and the identity token request.

[0013] To achieve the above object, the present application provides an access method of an audio and video online conference, which is applied to a unified conference server and comprises the following steps:

[0014] If the user registration information and the feedback token request sent by the unified conference client are received, responding to the feedback token request, generating a first target key corresponding to the type of the feedback token request according to the user registration information;

[0015] Generating a target token according to the first target key and feeding back the target token to the unified conference client.

[0016] Optionally, the access method of the audio and video online conference further comprises the following steps:

[0017] If the feedback token request is an SDK token request, generating a first SDK key according to the user registration information, generating an SDK token according to the first SDK key, and feeding back the SDK token to the unified conference client; and / or,

[0018] If the feedback token request is an identity token request, generating a first identity key according to the user registration information, generating an identity token according to the first identity key, and feeding back the identity token to the unified conference client.

[0019] Optionally, after the step of receiving the user registration information sent by the unified conference client, the method further comprises the following steps:

[0020] Sending the user registration information to a third-party conference service.

[0021] To achieve the above object, the present application provides an access method of an audio and video online conference, which is applied to a third-party conference server and comprises the following steps:

[0022] If the target token sent by the unified conference client is received, the target token is checked according to the second target key to obtain a checking result, and the checking result is fed back to the unified conference client.

[0023] Optionally, the step of checking the target token according to the second target key to obtain a checking result comprises:

[0024] Receiving user registration information sent by the unified conference server, and generating a second target key corresponding to the type of the target token according to the user registration information;

[0025] If the target token is an SDK token, a second SDK key is generated according to the user registration information, and the SDK token is checked according to the second SDK key to obtain a checking result; and / or,

[0026] If the target token is an identity token, a second identity key is generated according to the user registration information, and the identity token is checked according to the second identity key to obtain a checking result.

[0027] In addition, to achieve the above-mentioned purpose, the application also provides an access device of an audio and video online conference, the access device of the audio and video online conference comprises:

[0028] A unified conference client is configured to send user registration information and a feedback token request to a unified conference server, and receive a target token fed back by the unified conference server based on the user registration information and the feedback token request;

[0029] A third-party conference server is determined, and the target token is sent to the third-party conference server for checking;

[0030] If the checking result fed back by the third-party conference server is checking pass, an audio and video online conference with the third-party conference server is established;

[0031] A unified conference server is configured to, if user registration information and a feedback token request sent by a unified conference client are received, generate a first target key corresponding to the type of the feedback token request according to the user registration information in response to the feedback token request;

[0032] A target token is generated according to the first target key, and the target token is fed back to the unified conference client;

[0033] A third-party conference server is configured to, if a target token sent by a unified conference client is received, check the target token according to a second target key to obtain a checking result, and feed back the checking result to the unified conference client.

[0034] Furthermore, to achieve the above objectives, the present invention also provides an access device for online audio and video conferencing, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the above-described access method for online audio and video conferencing.

[0035] In addition, to achieve the above objectives, the present invention also provides a storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described online audio and video conferencing access method.

[0036] In the online audio and video conferencing access method of the present invention, applied to a unified conferencing client, the method includes: sending user registration information and a feedback token request to a unified conferencing server, and receiving a target token fed back by the unified conferencing server based on the user registration information and the feedback token request; determining a third-party conferencing server, and sending the target token to the third-party conferencing server for verification; if the verification result received from the third-party conferencing server is that the verification is successful, then establishing an online audio and video conferencing session with the third-party conferencing server.

[0037] Applied to a unified conferencing server, the method includes: if a user registration information and a feedback token request are received from a unified conferencing client, responding to the feedback token request, generating a first target key corresponding to the type of the feedback token request based on the user registration information; generating a target token based on the first target key, and sending the target token back to the unified conferencing client.

[0038] Applied to third-party conferencing servers, the method includes: if a target token is received from a unified conferencing client, the target token is verified according to a second target key to obtain a verification result, and the verification result is fed back to the unified conferencing client.

[0039] By integrating various third-party meeting SDKs into a local unified meeting client, users can access a wide range of online audio and video conferences with just one installation and registration. A single unified meeting client account enables seamless interoperability between different online audio and video conferences, significantly improving user efficiency in accessing online audio and video conferencing and for work. Furthermore, the unified meeting client aggregates scheduled tasks and historical meeting information, eliminating the need for users to switch between different audio and video conferencing clients to view these information.

[0040] Users no longer need to download and install multiple online audio and video conferencing clients, saving storage space on their audio and video conferencing devices. Furthermore, users don't need to register and log in separately for each client; they only need to register and log in once through a unified client to easily join different designated online audio and video conferences. This lowers the barrier to entry for users and improves their work efficiency. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram of the hardware operating environment involved in the embodiments of the present invention;

[0043] Figure 2 This is a schematic diagram of the current network connection status of an embodiment of the online audio and video conferencing access method of the present invention;

[0044] Figure 3 This is a schematic diagram illustrating an improved network connection in an embodiment of the online audio / video conferencing access method of the present invention;

[0045] Figure 4 This is a schematic diagram illustrating the synchronization of user registration information in an embodiment of the online audio and video conferencing access method of the present invention;

[0046] Figure 5 This is an SDK verification timing diagram of an embodiment of the online audio and video conferencing access method of the present invention;

[0047] Figure 6 This is a timing diagram of identity verification in an embodiment of the online audio / video conferencing access method of the present invention.

[0048] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0049] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0050] like Figure 1 As shown, Figure 1Figure 1 is a schematic diagram of a device structure of a hardware running environment involved in an embodiment of the present application. The device of the hardware running environment in the embodiment of the present application can include a processor 1001, for example, a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to realize the connection and communication among the components. The user interface 1003 can include a display screen (Display) and an input unit such as a keyboard (Keyboard). Optionally, the user interface 1003 can further include a standard wired interface and a wireless interface. The network interface 1004 can optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory) such as a magnetic disk memory. The memory 1005 can be optionally a storage device independent of the aforementioned processor 1001.

[0051] Optionally, the device of the hardware running environment can further include a camera, an RF (Radio Frequency, radio frequency) circuit, a sensor, an audio circuit, a WiFi module, and the like. The sensor can be, for example, a light sensor, a motion sensor, and other sensors. The ambient light sensor can adjust the brightness of the display screen according to the brightness of the ambient light. The proximity sensor can turn off the display screen and / or backlight when the hardware device is moved to the ear. As a kind of motion sensor, the gravity acceleration sensor can detect the size of acceleration in each direction (generally three axes). When at rest, the gravity acceleration sensor can detect the size and direction of gravity, and can be used for identifying the posture of the hardware device (such as landscape / portrait screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), and the like. Of course, the hardware device can also be configured with a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and other sensors, which will not be described here.

[0052] Those skilled in the art can understand that Figure 1 The device structure shown in the above figure does not constitute a limitation on the device, and can include more or fewer components than the figure, or combine certain components, or different component arrangements.

[0053] As Figure 1 shown, the memory 1005 as a kind of computer storage medium can include an operating system, a network communication module, a user interface module, and a computer program.

[0054] In Figure 1In the illustrated device, the network interface 1004 is mainly used for connecting a background server and communicating data with the background server; the user interface 1003 is mainly used for connecting a client (user end) and communicating data with the client; and the processor 1001 can be used for calling a computer program stored in the memory 1005 and performing the following operations:

[0055] The application is applied to a unified conference client, and comprises:

[0056] sending user registration information and a feedback token request to a unified conference server, and receiving a target token fed back by the unified conference server based on the user registration information and the feedback token request;

[0057] determining a third-party conference server, and sending the target token to the third-party conference server for verification;

[0058] if a verification result fed back by the third-party conference server is verification passed, establishing an audio and video online conference with the third-party conference server.

[0059] Further, the processor 1001 can call a computer program stored in the memory 1005 and further perform the following operations:

[0060] The step of receiving the target token fed back by the unified conference server based on the user registration information and the feedback token request comprises:

[0061] if the feedback token request is an SDK token request, receiving an SDK token fed back by the unified conference server based on the user registration information and the SDK token request; and / or,

[0062] if the feedback token request is an identity token request, receiving an identity token fed back by the unified conference server based on the user registration information and the identity token request.

[0063] Further, the processor 1001 can call a computer program stored in the memory 1005 and further perform the following operations:

[0064] The application is applied to a unified conference server, and comprises:

[0065] if user registration information and a feedback token request sent by a unified conference client are received, responding to the feedback token request, generating a first target key corresponding to a type of the feedback token request according to the user registration information;

[0066] generating a target token according to the first target key, and feeding back the target token to the unified conference client.

[0067] Further, the processor 1001 can invoke the computer program stored in the memory 1005, and further perform the following operations:

[0068] The access method of the online audio and video conference further includes:

[0069] If the feedback token request is an SDK token request, a first SDK key is generated according to the user registration information, an SDK token is generated according to the first SDK key, and the SDK token is fed back to the unified conference client; and / or,

[0070] If the feedback token request is an identity token request, a first identity key is generated according to the user registration information, an identity token is generated according to the first identity key, and the identity token is fed back to the unified conference client.

[0071] Further, the processor 1001 can invoke the computer program stored in the memory 1005, and further perform the following operations:

[0072] After the step of receiving the user registration information sent by the unified conference client, the method further includes:

[0073] The user registration information is sent to a third-party conference service.

[0074] Further, the processor 1001 can invoke the computer program stored in the memory 1005, and further perform the following operations:

[0075] Applied to a third-party conference server, the method includes:

[0076] If a target token sent by the unified conference client is received, a verification result is obtained by verifying the target token according to a second target key, and the verification result is fed back to the unified conference client.

[0077] Further, the processor 1001 can invoke the computer program stored in the memory 1005, and further perform the following operations:

[0078] The step of verifying the target token according to the second target key to obtain a verification result includes:

[0079] Receiving user registration information sent by a unified conference server, a second target key corresponding to the type of a target token is generated according to the user registration information;

[0080] If the target token is an SDK token, a second SDK key is generated according to the user registration information, and a verification result is obtained by verifying the SDK token according to the second SDK key; and / or,

[0081] If the target token is an identity token, a second identity key is generated according to the user registration information, and the identity token is verified according to the second identity key to obtain a verification result.

[0082] In an embodiment of the access method of the online audio-video conference, the access method of the online audio-video conference is applied to a unified conference client, and the access method comprises:

[0083] The user registration information and a feedback token request are sent to a unified conference server, and a target token fed back by the unified conference server based on the user registration information and the feedback token request is received;

[0084] A third-party conference server is determined, and the target token is sent to the third-party conference server for verification;

[0085] If a verification result fed back by the third-party conference server is verification passed, an online audio-video conference with the third-party conference server is established.

[0086] As a high-frequency application of remote office, the audio-video conference has developed rapidly, and while improving the communication efficiency of users, there are many inconveniences and needs for optimization and improvement. First, users need to download multiple audio-video conference clients on audio-video conference devices such as mobile phones and computers: current audio-video conference clients and audio-video conference solutions are various, users need to download and use various audio-video conference client software to initiate or join audio-video conferences, which further occupies the storage space of the audio-video conference device running the audio-video conference client. Second, multiple application accounts of the audio-video conference client need to be registered, and the application accounts are not interconnected: users need to register various audio-video conference clients, but the accounts are not interconnected, resulting in that multiple audio-video conferences cannot be transferred and connected. Moreover, the reservation to-be-done information and the historical conference information of the audio-video conference are not interconnected: users need to switch between various audio-video conference clients to check the reservation to-be-done information and the historical conference information, causing the fragmentation of office information.

[0087] In the embodiment, a unified conference client is installed on a local audio and video conference device of a user, and a third-party conference SDK (Software Development Kit) is pre-integrated in the unified conference client. The third-party conference SDK is packaged with APIs (Application Programming Interface) that directly work and implement various functions of the third-party conference. The APIs can be downloaded to the local audio and video conference device for installation and use after being applied to the third-party conference developer and being approved. In addition, the third-party conference SDK can be added and the existing third-party conference SDK can be updated to adapt to different types and more and more third-party audio and video conferences.

[0088] With reference to Figure 3 The unified conference client sends user registration information and a feedback token request to the unified conference server. The unified conference server responds to the feedback token request and generates and returns a target token to the unified conference client according to the user registration information and the feedback token request. After receiving the target token generated and returned by the unified conference server, the unified conference client determines a third-party conference server with which an audio and video online conference is to be performed, and sends the target token to the third-party conference server for verification of whether the target token is tampered with. The verification result fed back by the third-party conference server is received. If the verification result is that the verification is passed, an audio and video online conference with the third-party conference server is established, and an audio and video online conference with a remote is performed.

[0089] Optionally, the step of receiving the target token fed back by the unified conference server based on the user registration information and the feedback token request comprises:

[0090] If the feedback token request is an SDK token request, an SDK token fed back by the unified conference server based on the user registration information and the SDK token request is received; and / or,

[0091] If the feedback token request is an identity token request, an identity token fed back by the unified conference server based on the user registration information and the identity token request is received.

[0092] When the unified conference client is started, all third-party conference SDKs integrated in the unified conference client are subjected to legality verification in the process of loading the unified conference client. Specifically, the third-party conference SDKs are subjected to SDK security verification by the third-party conference server in a JWT (JSON web token) manner.

[0093] After passing the SDK security check of all third-party conference SDKs, the target SDK is determined by receiving the selection of the target SDK by the user in all third-party conference SDKs pre-integrated in the unified conference client. For example, after starting and loading the unified conference client, and after the legitimacy check of all third-party conference SDKs integrated in the unified conference client is passed, the unified conference client displays all third-party conference SDKs for the user to select, and at this time, the target SDK is determined by receiving the selection of the target SDK by the user in all third-party conference SDKs in the unified conference client. After the target SDK is determined, the target conference server corresponding to the online conference to be participated by the user can be determined according to the target SDK.

[0094] After passing the SDK security check of all third-party conference SDKs, the user can input the current user information such as an account and a password in the login interface of the unified conference client for login. After the preliminary check of the current user information of the user is passed in the unified conference client (or the unified conference server) and the login is successful, the target conference server further checks the user identity of the currently logged-in user. Since the check of the current user information and the user registration information in the unified conference client is not enough to ensure the security of the audio / video online conference, specifically, the target conference server needs to further check the user identity of the currently logged-in user in the JWT manner to further ensure the security of the audio / video online conference. Among them, after passing the SDK security check of all third-party conference SDKs, the target SDK can be selected after being displayed, and then the login can be performed in the unified conference client, or the target SDK can be displayed and selected after the login, and the order of the two steps of login and selection of the target SDK is not limited. Of course, in the safest case, the SDK security check should be performed before the user identity check, but the embodiment also provides a method of completing the conference security check according to only one kind of check.

[0095] After passing the user identity check, the currently logged-in user can use the target SDK to perform the online conference with the remote through the target conference server in the unified conference client, so as to ensure the security of the online conference and start the conference.

[0096] Further, in an embodiment of the access method of the audio / video online conference, the access method of the audio / video online conference is applied to a unified conference server, and the access method comprises the following steps of:

[0097] If the user registration information and the feedback token request sent by the unified conference client are received, a first target key corresponding to the type of the feedback token request is generated according to the user registration information in response to the feedback token request;

[0098] According to the first target key, a target token is generated, and the target token is fed back to the unified conference client.

[0099] Referring to Figure 3 , the unified conference client sends user registration information and a feedback token request to the unified conference server, the unified conference server responds to the feedback token request, generates a first target key corresponding to a type of the feedback token request according to the user registration information, generates a target token according to the first target key, and feeds back the target token to the unified conference client.

[0100] Optionally, the access method of the audio and video online conference further includes:

[0101] If the feedback token request is an SDK token request, a first SDK key is generated according to the user registration information, an SDK token is generated according to the first SDK key, and the SDK token is fed back to the unified conference client; and / or,

[0102] If the feedback token request is an identity token request, a first identity key is generated according to the user registration information, an identity token is generated according to the first identity key, and the identity token is fed back to the unified conference client.

[0103] Optionally, after the step of receiving the user registration information sent by the unified conference client, the method further includes:

[0104] The user registration information is sent to a third-party conference service.

[0105] In this embodiment, before the third-party conference server performs SDK security verification on the third-party conference SDK, user registration and synchronization of registration information are required. As shown in Figure 4 , the unified conference client uploads user registration information to the unified conference server, and the unified conference server receives and forwards the user registration information to the third-party conference server corresponding to the third-party conference SDK for synchronization.

[0106] After the user registration and the synchronization of the registration information are completed, the unified conference server and the third-party conference server can generate and save the same SDK key and the same identity key according to the same user registration information, that is, the first target key for encryption on the unified conference server and the second target key for decryption on the third-party conference server are the same. The unified conference server generates an SDK token by encryption through the SDK key and generates an identity token by encryption through the identity key, and the third-party conference server decrypts the SDK token by using the same SDK key as that used for generating the SDK token and decrypts the identity token by using the same identity key as that used for generating the identity token. Alternatively, the third-party conference server can generate and save the SDK key and the identity key according to the user registration information, and then issue (return) them to the unified conference server, so that the keys of the two servers are the same.

[0107] The SDK key and the identity key are different between different third-party conference servers, for example, the unified conference server and the XX conference server save the same first SDK key, the unified conference server and the YY conference server save the same second SDK key, and the first SDK key and the second SDK key are different; the unified conference server and the XX conference server save the same third identity key, the unified conference server and the YY conference server save the same fourth identity key, and the third identity key and the fourth identity key are different.

[0108] Of course, the SDK key and the identity key can be the same between different third-party conference servers, but for security purposes, to prevent the failure of SDK verification or identity verification due to the loss of a certain SDK key or identity key, and to prevent security vulnerabilities of the audio and video online conference, in this embodiment, the SDK key and the identity key are set to be different.

[0109] Further, in an embodiment of the access method of the audio and video online conference, the access method of the audio and video online conference is applied to a third-party conference server, and the access method comprises the following steps:

[0110] If the target token sent by the unified conference client is received, the target token is verified according to the second target key to obtain a verification result, and the verification result is fed back to the unified conference client.

[0111] Referring to Figure 3 The unified conference client sends a target token to the third-party conference server, the third-party conference server verifies the target token according to the second target key, and obtains and feeds back a verification result to the unified conference client.

[0112] Optionally, the step of verifying the target token according to the second target key to obtain a verification result comprises:

[0113] receive the user registration information sent by the unified conference server, and generate a second target key corresponding to a type of the target token according to the user registration information;

[0114] If the target token is an SDK token, a second SDK key is generated according to the user registration information, and the SDK token is verified according to the second SDK key to obtain a verification result; and / or,

[0115] If the target token is an identity token, a second identity key is generated according to the user registration information, and the identity token is verified according to the second identity key to obtain a verification result.

[0116] In this embodiment, the SDK security verification is performed first, and then the user identity verification is performed. Before the third-party conference server performs the SDK security verification on the third-party conference SDK, the encrypted SDK token uploaded by the unified conference client needs to be received first. As shown in FIG. 8, when the unified conference client is started and the initialization is completed, the legality and security verification of all integrated third-party conference SDKs calling the unified conference client is completed. Figure 5

[0117] First, when the unified conference client is started, the unified conference server is requested to send an SDK id (identifier) and an SDK token (SDK token). The SDK id is used to indicate a target server in the third-party conference server. For example, after the user registration and the synchronization of the registration information are completed, the unified conference server and the XX conference server save the same first SDK key, the unified conference server and the YY conference server save the same second SDK key, and the first SDK key and the second SDK key are different. At this time, the unified conference server generates and saves SDK id1 for indicating the XX conference server, and generates and saves SDK id2 for indicating the YY conference server.

[0118] ​Then, the unified conference server generates an SDK token according to the SDK key corresponding to the SDK id in a JWT manner, and returns the SDK Token to the unified conference client in an HMACSHA256 digital signature manner. For example, after the unified conference server receives the request of replying the SDK id and the SDK token, the unified conference server determines the SDK id1 and the SDK id2 according to the order of receiving the request, then generates the SDK token1 according to the first SDK key corresponding to the SDK id1 in a JWT manner, and replies the SDK id1 and the SDK token1 to the unified conference client; similarly, the unified conference server generates the SDK token2 according to the second SDK key corresponding to the SDK id2 in a JWT manner, and replies the SDK id2 and the SDK token2 to the unified conference client. In this way, the unified conference client's request of SDK id and SDK Token is responded.

[0119] Then, after the unified conference client receives the SDK id and the SDK Token replied by the unified conference server, the unified conference client applies for SDK security check to the third-party conference server indicated by the SDK id with the SDK Token. For example, the unified conference client receives the SDK id1 and the SDK token1, the SDK id2 and the SDK token2 replied by the unified conference server, and then applies for SDK security check to the XX conference server and the YY conference server respectively through the initSDK(SDK id, SDK token) method.

[0120] Finally, after the third-party conference server receives the application of the unified conference server for SDK security check and the SDK Token, the third-party conference server decrypts and checks the SDK Token according to the SDK key. The SDK key used for decryption in the third-party conference server is the same as the SDK key used for encryption in the unified conference server, and the two SDK keys are the same in the user registration and registration information synchronization stage. For example, after the XX conference server receives the SDK token1, the XX conference server decrypts and checks the SDK token1 using the same first SDK key as the unified conference server; after the YY conference server receives the SDK token2, the YY conference server decrypts and checks the SDK token2 using the same second SDK key as the unified conference server, so as to determine whether the payload content in the JWT token (the SDK token1 and the SDK token2) is tampered.

[0121] After the decryption verification of the JWT token, the third-party conference server can determine to open the server-side API interface to the third-party conference SDK integrated in the local unified conference client, so that the unified conference client calls the local API interface packaged in advance in the third-party conference SDK to dock with the server-side API interface, thereby opening the data channel and enabling the data of the audio and video online conference to flow, thereby completing the construction of the audio and video online conference room and enabling the user to participate in the audio and video online conference.

[0122] After the SDK security verification, before the unified conference client calls the local API interface packaged in advance in the third-party conference SDK to dock with the server-side API interface and establish the data channel of the audio and video online conference, the target conference server also needs to perform user identity verification on the currently logged-in user to further ensure the security of the audio and video online conference.

[0123] The user logs in by inputting the current user information such as an account and a password which are the same as the user registration information pre-registered and passed to the unified conference server, and the unified conference client uploads the current user information to the unified conference server to request an identity token encrypted according to the current user information and an identity key corresponding to the target conference server. After obtaining the identity token, it is uploaded to the target conference server to apply for user identity verification.

[0124] As shown in Figure 6 After determining the target conference server and passing the SDK security verification, the unified conference client uploads the current user information and the identity token to the unified conference server, the unified conference server uses the JWT method to write the current user information into the payload content of the identity token, and uses the identity key to encrypt and generate and return the identity token to the unified conference client.

[0125] The unified conference client uploads the identity token to the target conference server, the target conference server uses the same identity key as the unified conference server to encrypt the identity token to decrypt and verify the identity token received from the unified conference client, and returns the verification result to the unified conference client. During the user registration and registration information synchronization stage, the identity keys of the unified conference server and the target conference server are made the same.

[0126] In summary, the overall steps of the scheme of the present application are as follows: integrating a third-party conference SDK in a unified conference client, uploading user registration information to a unified conference server and synchronizing to a third-party conference server, and the two servers generate and save the same SDK key and identity key. Starting the unified conference client, loading the third-party conference SDK during initialization, and performing SDK security verification using the same SDK key. After the SDK security verification passes, the current user information is checked with the user registration information. After the check passes, the target SDK and the target conference server are determined, the user identity is verified using the same identity key, and after the user identity verification passes, the audio and video online conference is performed.

[0127] In addition, the embodiment of the present application also provides an access device for an audio and video online conference, the access device for the audio and video online conference comprising:

[0128] a unified conference client, configured to send user registration information and a feedback token request to a unified conference server, and receive a target token fed back by the unified conference server based on the user registration information and the feedback token request;

[0129] determine a third-party conference server, and send the target token to the third-party conference server for verification;

[0130] if the verification result fed back by the third-party conference server is verification pass, establish an audio and video online conference with the third-party conference server;

[0131] Optionally, the unified conference client is further configured to, if the feedback token request is an SDK token request, receive an SDK token fed back by the unified conference server based on the user registration information and the SDK token request; and / or,

[0132] if the feedback token request is an identity token request, receive an identity token fed back by the unified conference server based on the user registration information and the identity token request;

[0133] a unified conference server, configured to, if receiving user registration information and a feedback token request sent by a unified conference client, respond to the feedback token request, and generate a first target key corresponding to the type of the feedback token request according to the user registration information;

[0134] generate a target token according to the first target key, and feed back the target token to the unified conference client;

[0135] Optionally, the unified conference server is further configured to, if the feedback token request is an SDK token request, generate a first SDK key according to the user registration information, generate an SDK token according to the first SDK key, and feed back the SDK token to the unified conference client; and / or,

[0136] if the feedback token request is an identity token request, generate a first identity key according to the user registration information, generate an identity token according to the first identity key, and feed back the identity token to the unified conference client;

[0137] Optionally, the unified conference server is further configured to, after the step of receiving the user registration information sent by the unified conference client, further comprising:

[0138] sending the user registration information to a third-party conference service;

[0139] The third-party conference server is configured to, if a target token sent by the unified conference client is received, check the target token according to a second target key to obtain a check result, and feed back the check result to the unified conference client.

[0140] Optionally, the third-party conference server is further configured to receive user registration information sent by the unified conference server, and generate a second target key corresponding to the type of the target token according to the user registration information.

[0141] if the target token is an SDK token, generate a second SDK key according to the user registration information, and check the SDK token according to the second SDK key to obtain a check result; and / or,

[0142] if the target token is an identity token, generate a second identity key according to the user registration information, and check the identity token according to the second identity key to obtain a check result.

[0143] The access device for the online audio / video conference provided by the application has the beneficial effects of the access method for the online audio / video conference provided by the above-mentioned embodiments, and other technical features in the access device for the online audio / video conference are the same as the features disclosed in the above-mentioned method, which will not be repeated here.

[0144] In addition, the embodiment of the present application further provides an access device of an audio and video online conference, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the computer program implements the steps of each embodiment of the method for responding to the operation of the access device of the audio and video online conference when executed by the processor.

[0145] In addition, the embodiment of the present application further provides a readable storage medium, which stores a computer program, and the computer program implements the steps of each embodiment of the method for responding to the operation of the access device of the audio and video online conference when executed by a processor.

[0146] The detailed description of the access device of the audio and video online conference and the readable storage medium of the present application is basically the same as the above-mentioned method for responding to the operation of the access device of the audio and video online conference, and is not repeated here.

[0147] It should be noted that in this paper, the terms "including", "containing" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or system including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or system. Without more limitations, the element defined by the statement "including a" does not exclude the presence of another identical element in the process, method, article or system including the element.

[0148] The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0149] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a plurality of instructions for making a device (which can be a mobile phone, computer, server, air conditioner or network device, etc.) execute the method described in each embodiment of the present application.

[0150] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied to other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. An access method of an audio-video online conference, characterized in that, The access method of the audio and video online conference is applied to a unified conference client, and includes the following steps: sending user registration information and a feedback token request to a unified conference server, and receiving a target token fed back by the unified conference server based on the user registration information and the feedback token request, wherein the unified conference server sends the user registration information to a third-party conference server, and a third-party conference SDK is integrated in the unified conference client; determining the third-party conference server, and sending the target token to the third-party conference server for verification, wherein the third-party conference server verifies the target token based on the user registration information; if a verification result fed back by the third-party conference server is verification passed, establishing an audio and video online conference with the third-party conference server; the step of receiving the target token fed back by the unified conference server based on the user registration information and the feedback token request includes the following steps: if the feedback token request is an SDK token request, receiving an SDK token fed back by the unified conference server based on the user registration information and the SDK token request.

2. The access method of an audio / video online conference according to claim 1, wherein, the step of receiving the target token fed back by the unified conference server based on the user registration information and the feedback token request further includes the following steps: if the feedback token request is an identity token request, receiving an identity token fed back by the unified conference server based on the user registration information and the identity token request.

3. An access method of an audio-video online conference, characterized in that, The access method of the audio and video online conference is applied to a unified conference server, and includes the following steps: if user registration information and a feedback token request sent by a unified conference client are received, responding to the feedback token request, generating a first target key corresponding to the type of the feedback token request according to the user registration information; sending the user registration information to a third-party conference server; wherein a third-party conference SDK is integrated in the unified conference client; generating a target token according to the first target key, and feeding back the target token to the unified conference client; if the feedback token request is an SDK token request, generating a first SDK key according to the user registration information, generating an SDK token according to the first SDK key, and feeding back the SDK token to the unified conference client.

4. The access method of online audio-video conference according to claim 3, wherein, The access method of the audio and video online conference further includes the following steps: if the feedback token request is an identity token request, generating a first identity key according to the user registration information, generating an identity token according to the first identity key, and feeding back the identity token to the unified conference client.

5. An access method of an audio-video online conference, characterized in that, The access method of the audio and video online conference is applied to a third-party conference server, and includes the following steps: if a target token sent by a unified conference client is received, receiving user registration information sent by a unified conference server, generating a second target key corresponding to the type of the target token according to the user registration information; verifying the target token according to the second target key to obtain a verification result, and feeding back the verification result to the unified conference client; wherein a third-party conference SDK is integrated in the unified conference client; The step of verifying the target token according to the second target key comprises: If the target token is an SDK token, a second SDK key is generated according to the user registration information, and the SDK token is verified according to the second SDK key to obtain a verification result.

6. The access method of online audio-video conference according to claim 5, wherein, The step of verifying the target token according to the second target key further comprises: If the target token is an identity token, a second identity key is generated according to the user registration information, and the identity token is verified according to the second identity key to obtain a verification result.

7. An access device for an audio-video online conference, characterized in that, The access device of the online audio and video conference comprises: The unified conference client is configured to send user registration information and a feedback token request to the unified conference server, and receive a target token fed back by the unified conference server based on the user registration information and the feedback token request, wherein the unified conference server sends the user registration information to a third-party conference server, and integrates a third-party conference SDK in the unified conference client; The third-party conference server is determined, and the target token is sent to the third-party conference server for verification, wherein the third-party conference server verifies the target token based on the user registration information; If a verification result fed back by the third-party conference server is a verification pass, an online audio and video conference with the third-party conference server is established; The step of receiving the target token fed back by the unified conference server based on the user registration information and the feedback token request comprises: If the feedback token request is an SDK token request, an SDK token fed back by the unified conference server based on the user registration information and the SDK token request is received; The unified conference server is configured to, if the user registration information and the feedback token request sent by the unified conference client are received, respond to the feedback token request, generate a first target key corresponding to a type of the feedback token request according to the user registration information, and send the user registration information to the third-party conference server; A target token is generated according to the first target key, and the target token is fed back to the unified conference client; If the feedback token request is an SDK token request, a first SDK key is generated according to the user registration information, an SDK token is generated according to the first SDK key, and the SDK token is fed back to the unified conference client; The third-party conference server is configured to, if the target token sent by the unified conference client is received, receive the user registration information sent by the unified conference server, generate a second target key corresponding to a type of the target token according to the user registration information, verify the target token according to the second target key to obtain a verification result, and feed back the verification result to the unified conference client; The step of verifying the target token according to the second target key comprises: If the target token is an SDK token, a second SDK key is generated according to the user registration information, and the SDK token is verified according to the second SDK key to obtain a verification result.

8. An access device for an audio-video online conference, characterized in that, The device comprises a memory, a processor, and a computer program stored on the memory and executable on the processor, and the computer program is configured to implement the steps of the access method of the audio and video online conference according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the steps of the access method of the audio and video online conference according to any one of claims 1 to 6.

Images