Conference access method, apparatus and system

Abstract

The present application relates to the technical field of cloud computing, and provides a conference access method, apparatus and system. The method comprises: receiving a conference request from a user side, the conference request being used for instructing to add the user side to a target conference in a hardware video conference system other than a cloud conference system; querying, in a created cloud conference, whether a first cloud conference associated with the target conference exists; and if the first cloud conference associated with the target conference exists, adding the user side to the target conference by means of the first cloud conference. In this way, a user can simply and conveniently join a conference in a hardware video conference system by means of a cloud conference system.

Description

Conference access method, device and system

[0001] The present application claims priority from the Chinese patent application No. 202411303005.1 filed on September 18, 2024, and entitled "Conference access method, device and system", the whole content of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of cloud computing technology, in particular to a conference access method, device and system. BACKGROUND

[0003] A cloud conference system creates and runs a cloud conference by a server, and users can participate in the cloud conference by network communication with the server of the cloud conference system at any location through various types of user terminals, such as computers, mobile phones, etc. Some other conference systems, such as hardware video conference systems, need to deploy conference hardware devices at user locations, such as enterprise office sites, to create and run conferences by the conference hardware devices, and users need to participate in the conference at the places where the conference hardware devices are deployed, such as enterprise conference rooms.

[0004] Users can join the conference of a hardware video conference system through the cloud conference system, so that users of different conference systems can jointly conduct a conference, but the operation is relatively complex. SUMMARY

[0005] The present application provides a conference access method, device and system, which can easily add users of a cloud conference system to a conference of another conference system.

[0006] In a first aspect, a conference access method is provided, which can be implemented by a cloud conference system. The method includes receiving a conference request from a user terminal, the conference request being used to indicate that the user terminal is to be added to a target conference, the target conference being a conference in a hardware video conference system other than the cloud conference system. The method also includes querying whether there is a first cloud conference associated with the target conference in an established cloud conference, and adding the user terminal to the target conference through the first cloud conference in the case where there is a first cloud conference associated with the target conference.

[0007] By the conference access method provided in the embodiments of the present application, the user terminal sends a request for joining the target conference to the cloud conference system, and the cloud conference system can successfully join the user terminal to the target conference in the other conference system through the cloud conference. In this way, the user can more simply and conveniently join the target conference in the other conference system through the cloud conference system. In addition, in the case where the first cloud conference associated with the target conference exists in the created cloud conference, the cloud conference system directly joins the user terminal to the target conference through the created first cloud conference. In this way, multiple users can conveniently join the target conference through the created first cloud conference, and resource waste caused by creating more cloud conferences is avoided.

[0008] In some possible implementation manners, the conference request includes a conference identifier and a conference password of the target conference, and the joining the user terminal to the target conference through the first cloud conference includes: in the case where the conference password and the conference identifier of the target conference are verified, joining the user terminal to the first cloud conference.

[0009] In this way, the user can directly send the conference password and the conference identifier of the target conference to the cloud conference system to join the target conference in the case where the user knows the conference password and the conference identifier of the target conference, and the user operation is more simple and convenient.

[0010] In other possible implementation manners, the querying whether the first cloud conference associated with the target conference exists in the established cloud conference includes: querying whether the first cloud conference associated with the target conference exists in the established cloud conference according to the conference identifier of the target conference.

[0011] The cloud conference system can record the conference identifier of the conference associated with the established cloud conference. Based on this, the first cloud conference associated with the target conference can be accurately found in the established cloud conference according to the conference identifier of the target conference.

[0012] In other possible implementation manners, the method further includes, in the case where the first cloud conference associated with the target conference does not exist, creating the first cloud conference according to the conference request, and sending a conference association request to the hardware video conference system to establish an association relationship between the target conference and the first cloud conference.

[0013] By the conference access method provided in the embodiments of the present application, when the user joins the target conference through the cloud conference system, if the established cloud conference associated with the target conference does not exist in the cloud conference system, the user can also join the target conference by creating the first cloud conference associated with the target conference. It is ensured that the user can successfully join the target conference through the cloud conference system in multiple cases.

[0014] In some possible implementation manners, the method further includes: obtaining a conference name of the target conference, and generating the conference name of the first cloud conference according to the conference name of the target conference after the first cloud conference is created according to the conference request.

[0015] In this way, the conference name of the first cloud conference is consistent with the conference name of the target conference. The same conference name can be seen by the cloud conference system users and the hardware video conference system users who join the target conference, and the conference experience of the users is better.

[0016] In some possible implementation manners, the user end includes a first user end and a second user end, and the joining of the user end into the target conference through the first cloud conference includes: joining the first user end and the second user end into the target conference through the first cloud conference.

[0017] According to the conference access method provided in the embodiments of the present application, multiple users can conveniently join a target conference through one first cloud conference that has been created, and it is not necessary to create multiple cloud conferences, thereby reducing resource consumption for creating cloud conferences.

[0018] In some possible implementation manners, after the first user end and the second user end are joined into the target conference through the first cloud conference, the method further includes: receiving target conference data from the first user end; and sending the target conference data of the first user end to the second user end.

[0019] According to the conference access method provided in the embodiments of the present application, after multiple cloud conference system users join a target conference through one first cloud conference that has been created, the multiple cloud conference system users can also communicate in the conference, and the conference experience of the users is better.

[0020] In a second aspect, a conference access apparatus is provided, and the apparatus includes a communication module and a processing module. The communication module is configured to receive a conference request from a user end, the conference request being used to indicate that the user end is to be joined into a target conference, the target conference being a conference in a hardware video conference system other than a cloud conference system, and the cloud conference system being used to create a cloud conference. The processing module is configured to query whether a first cloud conference associated with the target conference exists in an established cloud conference, and in the case that the first cloud conference associated with the target conference exists, join the user end into the target conference through the first cloud conference.

[0021] In some possible implementation manners, the conference request includes a conference identifier and a conference password of the target conference, and the processing module is further configured to: in the case that the conference password and the conference identifier of the target conference are verified, join the user end into the first cloud conference.

[0022] In some possible implementation manners, the processing module is further configured to: query the first cloud conference associated with the target conference in the established cloud conference according to the conference identifier of the target conference.

[0023] In some possible implementation ways, the processing module is further configured to: create the first cloud conference according to the conference request in the absence of the first cloud conference associated with the target conference, and send a conference association request to the hardware video conference system to establish an association relationship between the target conference and the first cloud conference.

[0024] In some possible implementation ways, the processing module is further configured to: obtain a conference name of the target conference, and further include generating a conference name of the first cloud conference according to the conference name of the target conference after creating the first cloud conference according to the conference request.

[0025] In some possible implementation ways, the user end includes a first user end and a second user end, and the processing module is further configured to add the first user end and the second user end to the target conference through the first cloud conference.

[0026] In some possible implementation ways, the processing module is further configured to: receive target conference data from the first user end, and send the target conference data of the first user end to the second user end.

[0027] In a third aspect, a cloud conference system is provided, and the cloud conference system includes a server configured to perform the conference access method according to the first aspect.

[0028] In a fourth aspect, a computing device cluster is provided, and the computing device cluster includes at least one computing device, wherein each computing device includes a processor and a memory; and the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster performs the conference access method according to the first aspect.

[0029] In a fifth aspect, a computer program product including instructions is provided, which, when executed by at least one computing device, causes the at least one computing device to perform the conference access method according to the first aspect.

[0030] In a sixth aspect, a computer-readable storage medium is provided, which includes computer program instructions, and when the computer program instructions are executed by at least one computing device, the at least one computing device performs the conference access method according to the first aspect.

[0031] On the basis of the implementation manners of the aspects provided in the above, further combinations can be made to provide more implementation manners.

[0032] In the following description, more specific contents of the implementation manners provided in the above aspects are included. BRIEF DESCRIPTION OF DRAWINGS

[0033] FIG. 1 is a schematic architecture diagram of a conference access system provided by an embodiment of the present application.

[0034] FIG. 2 is a flow diagram of a conference access method according to an embodiment of the present application;

[0035] FIG. 3 is a flow diagram of a conference access method according to another embodiment of the present application;

[0036] FIG. 4 is a structural diagram of a conference access apparatus according to an embodiment of the present application;

[0037] FIG. 5 is a structural diagram of a computing device according to an embodiment of the present application;

[0038] FIG. 6 is a structural diagram of a computing device cluster according to an embodiment of the present application;

[0039] FIG. 7 is a structural diagram of a computing device cluster according to another embodiment of the present application. DETAILED DESCRIPTION

[0040] A media conference refers to a conference in which users exchange information through transmission of media data. Media refers to materials and tools that carry information or transmit and control information, such as text, images, sound, etc. A media conference can include a multimedia conference, which refers to a conference in which users exchange information through transmission of multiple types of media data. The conference referred to in the embodiments of the present application can refer to a media conference.

[0041] A cloud conference system creates and runs a cloud conference through a server (e.g., a server of a cloud, a private cloud, etc.) and provides conference services to users through a network. Users can use the cloud conference system through various types of user terminals at any location. For example, a user uses a user terminal to perform network communication with a server of the cloud conference system to create and join a cloud conference.

[0042] Here, a user terminal refers to a terminal used by a user, which can be a computer, a mobile phone, a smart television, a smart watch, etc.

[0043] As an example, enterprise A rents a cloud conference system, employee 1 of enterprise A can use user terminal 1 in an office to send a request to create a cloud conference a to a cloud, and the cloud creates cloud conference a. Employee 2 of enterprise A can use user terminal 2 at home to send a request to join cloud conference a to the cloud, and the cloud can add user terminal 2 of employee 2 to cloud conference a. Employee 3 can use user terminal 3 at a restaurant to send a request to join cloud conference a to the cloud, and the cloud can add user terminal 3 of employee 3 to cloud conference a.

[0044] Here, when a user uses a user terminal to join a cloud conference, the user terminal sends a conference identifier and a conference password of the cloud conference to a server of the cloud conference system, and the server of the cloud conference system can verify the conference password corresponding to the conference identifier. If the verification is passed, the user terminal of the user can be added to the cloud conference.

[0045] After multiple users join the cloud conference by using multiple user terminals respectively, the server of the cloud conference system can obtain conference data of each user terminal, process the conference data of the user terminal, and forward the conference data of the user terminal to other user terminals.

[0046] The conference data of the terminal can include text (such as user input text), image (such as user video image), sound (such as user voice), and other media data obtained by the terminal.

[0047] Some other conference systems such as a hardware video conference system need to deploy conference hardware devices at a user location such as an enterprise office, and create and run a conference by using the conference hardware devices. The user needs to participate in the conference at a place where the conference hardware devices are deployed, such as an enterprise conference room. The conference hardware devices can include a controller, a conference terminal, and the like.

[0048] The conference terminal is configured to collect media data and send the media data to the controller. The conference terminal can include a camera, a sound receiving device, a display device, a processor, and the like.

[0049] The controller is configured to obtain conference data of each conference terminal, and process and forward the conference data of the conference terminal. The controller can include a multipoint control unit (MCU). The MCU can further include a multipoint controller (MC) and a multipoint processor (MP). The MC is configured to coordinate and control a multipoint conference, and the MP is configured to receive and process conference data.

[0050] As an example, an enterprise B uses a hardware video conference system (the hardware video conference system can also be referred to as a resident conference system), and purchases conference hardware devices of the hardware video conference system such as a controller, multiple conference terminals, and the like. The controller is installed in a machine room of the enterprise office, and the multiple conference terminals (for example, a conference terminal 1 and a conference terminal 2) are installed in multiple conference rooms (for example, a conference room 1 and a conference room 2) of the enterprise office respectively.

[0051] An employee 1 of the enterprise B can create a conference b by using the controller. An employee 2 can send a request for joining the conference b to the controller by using the conference terminal 1 of the conference room 1, and the controller can add the conference terminal 1 to the conference b. An employee 3 can send a request for joining the conference b to the controller by using the conference terminal 2 of the conference room 2, and the controller can add the conference terminal 2 to the conference b.

[0052] Wherein, when the employee joins the conference by using the conference terminal, the conference terminal sends the conference identifier and the conference password of the conference to the controller, the controller can verify the conference identifier and the corresponding conference password, and if the verification is passed, the conference terminal can be added to the conference.

[0053] After multiple users join the conference by using multiple conference terminals respectively, the controller can obtain the conference data of each conference terminal, process the conference data of the conference terminal, and forward the conference data of the conference terminal to other conference terminals.

[0054] In the embodiments of the present application, some other conference systems such as the hardware video conference system in addition to the cloud conference system can be referred to as third-party conference systems, and the conference created by the third-party conference system can be referred to as a third-party conference.

[0055] In some scenarios, part of the users use the cloud conference system (which can be referred to as users of the cloud conference system), and another part of the users use the third-party conference system (which can be referred to as users of the third-party conference system), and the two parts of the users need to jointly conduct a conference.

[0056] In some implementations, the users of the cloud conference system and the users of the third-party conference system can jointly conduct a conference by the following method:

[0057] The administrator creates a cloud conference by using the cloud conference system, and also creates a third-party conference by using the third-party conference system. The administrator informs the users of the cloud conference system of the conference information of the created cloud conference, and also informs the users of the third-party conference system of the conference information of the third-party conference.

[0058] In addition, the cloud conference system and the third-party conference system communicate with each other to establish an association relationship (which can also be referred to as cascading) between the cloud conference and the third-party conference.

[0059] After the cloud conference and the third-party conference are associated, the cloud conference system can transmit the conference data of the participants of the cloud conference to the third-party conference system, and the third-party conference system can transmit the conference data of the participants of the third-party conference to the cloud conference system.

[0060] One or more users of the third-party conference system join the third-party conference by using the conference terminal of the third-party conference system according to the conference information (such as the conference identifier and the conference password) of the third-party conference.

[0061] One or more users of the cloud conference system join the cloud conference by using the user terminal according to the conference information (such as the conference identifier and the conference password) of the cloud conference.

[0062] Thus, the user of the cloud conference system joins the third-party conference through the cloud conference created in advance, and the user of the cloud conference system and the user of the third-party conference system can jointly conduct the conference.

[0063] In this method, the cloud conference needs to be created in advance, the association between the cloud conference and the third-party conference needs to be established, and the conference information of the cloud conference needs to be informed to the user of the cloud conference system, so that the user of the cloud conference system can join the third-party conference through the cloud conference created in advance. This method is relatively complex to operate, and if the user of the cloud conference system does not know the conference information of the cloud conference, the user cannot join the third-party conference.

[0064] In addition, it is difficult for the administrator to know whether there is a user participating in the third-party conference through the cloud conference, and when the user participates in the third-party conference through the cloud conference. Thus, there can be no user or no user for a long time to join the cloud conference. In the time when there is no user to join the cloud conference, the cloud conference created in advance will still consume computing resources and network resources, causing waste of resources.

[0065] In some implementations, in a case where the third-party conference has been created and the user of the cloud conference system knows the conference information of the third-party conference, each user of one or more users of the cloud conference system can join the third-party conference in the following manner:

[0066] The user creates a cloud conference using the cloud conference system, the user terminal used by the user joins the cloud conference, and the cloud conference system and the third-party conference system communicate to establish the association between the cloud conference and the third-party conference. Thus, each user joins the third-party conference through the cloud conference created by the user, and can jointly conduct the conference with the user of the third-party conference system.

[0067] In this method, when multiple users join the third-party conference through the cloud conference system, multiple cloud conferences need to be created, and the multiple cloud conferences are all associated with the third-party conference. Thus, the multiple cloud conferences consume relatively more computing resources and network resources.

[0068] In addition, in the method, each user of the cloud conference system joins a cloud conference individually, and there is no association between the multiple cloud conferences created by the multiple users. Thus, the conference data of the participants of the cloud conference is not sent to the participants of other cloud conferences, and the multiple users of the cloud conference system cannot communicate with each other.

[0069] Embodiments of the present application provide a conference access method, which can achieve joining the user of the cloud conference system to the third-party conference in a case where the third-party conference has been created and the user of the cloud conference system can know the conference information of the third-party conference.

[0070] The conference access method provided by the embodiments of the present application can be implemented by a cloud conference system, and the method comprises receiving a conference request from a user terminal, the conference request being used to indicate that the user terminal is to join a target conference, the target conference being a conference in a target conference system other than the cloud conference system; and querying a first cloud conference associated with the target conference in an established cloud conference, and in the case that the first cloud conference associated with the target conference exists, joining the user terminal to the target conference through the first cloud conference.

[0071] The third-party conference that the user needs to join is referred to as a target conference. The third-party conference system to which the target conference belongs can be referred to as a target conference system. For example, the user needs to join a conference b of a hardware video conference system of enterprise B, and the hardware video conference system of enterprise B is used as the target conference system.

[0072] Through the conference access method provided by the embodiments of the present application, the user terminal sends a request indicating joining a target conference (i.e. a third-party conference) to the cloud conference system, and the cloud conference system can successfully join the user terminal to the target conference in the other conference system through the cloud conference. In this way, the user can more simply and conveniently join the target conference through the cloud conference system. In the case that the first cloud conference associated with the target conference exists in the established cloud conference, the cloud conference system directly joins the user terminal to the target conference through the established first cloud conference. In this way, multiple users can conveniently join the target conference through the established first cloud conference, and resource waste caused by creating more cloud conferences is avoided.

[0073] The system architecture provided by the embodiments of the present application is introduced below.

[0074] FIG. 1 is a schematic diagram of the architecture of a conference access system provided by the embodiments of the present application. The conference access system 100 can be used to implement the conference access method proposed by the embodiments of the present application. As shown in FIG. 1, the conference access system 100 comprises a user terminal 110, a cloud conference system device 120, and a third-party conference system device 130.

[0075] The third-party conference system device 130 is used to create and run a conference of a third-party conference system, and can be various devices that can implement the function thereof. In some embodiments, the third-party conference system device 130 can comprise a controller 131 and a conference terminal 132.

[0076] The cloud conference system device 120 is used to create and run a cloud conference of a cloud conference system. The cloud conference system device 120 can comprise a server 121 (also referred to as a cloud platform). The server 121 can comprise at least one computing device.

[0077] The cloud conference system device 120 can also be used to communicate with the third-party conference system device 130, so as to implement communication between the cloud conference system and the third-party conference system, and establish an association relationship between the cloud conference and the third-party conference.

[0078] In some embodiments, the cloud conference system device 120 can further include a cloud conference connector 122. The cloud conference connector 122 can be communicatively connected with the server 121, and can also be referred to as a meeting virtual connector (MVC). The cloud conference connector 122 is configured to communicate with a controller 131 of the third-party conference system device 130, so as to enable the cloud conference system and the third-party conference system to communicate.

[0079] The cloud conference connector 122 can be various devices that can implement its functions, such as a computing device, a gateway, etc. The controller 131 has a communication function, for example, the controller 131 itself integrates a communication function, or the controller 131 includes a control device and a gateway component for implementing a communication function.

[0080] In some embodiments, the cloud conference connector 122 and the controller 131 can transmit signaling based on a communication protocol to communicate with each other, so as to enable the communication between the two. The communication protocol can be a Session Initiation Protocol (SIP), an H.323 protocol, etc. In some embodiments, the cloud conference connector 122 and the controller 131 can also transmit information based on a dual-tone multifrequency (DTMF) mode to communicate with each other.

[0081] The user terminal 110 can include various terminals such as a computer, a mobile phone, a smart television, a smart watch, etc. The user terminal 110 can include one or more user terminals 110-1, 110-2, etc. One or more users can use one or more user terminals 110-1, 110-2, etc. to interact with the cloud conference system device 120, respectively.

[0082] The cloud conference system device 120 can be configured to execute the conference access method provided by the embodiments of the present application, so as to enable the user terminal 110 (for example, one or more user terminals 110-1, 110-2, etc.) used by a user to join a conference of the third-party conference system device 130 through a cloud conference, so that the user of the cloud conference system can jointly conduct a conference with the user of the third-party conference system.

[0083] For example, the third-party conference system device 130 has created and run a target conference 133, and a user can send a conference request to the server 121 of the cloud conference system device 120 through the user terminal 110. The conference request can indicate that the user terminal 110 is to join the target conference 133.

[0084] After the server 121 of the cloud conference system device 120 receives the conference request of the user terminal 110, the server 121 can execute the conference access method provided by the embodiments of the present application. The method can include:

[0085] In the established cloud conference, the cloud conference associated with the target conference 133 (may be referred to as the first cloud conference 123) is queried.

[0086] When the first cloud conference 123 associated with the target conference 133 exists, the server 121 can perform joining the user terminal 110 into the target conference 133 through the first cloud conference.

[0087] When the first cloud conference 123 associated with the target conference 133 does not exist, the server 121 can perform creating a cloud conference (the cloud conference can also be referred to as the first cloud conference 123) according to the conference request of the user terminal 110, and joining the user terminal 110 into the created first cloud conference 123.

[0088] In addition, the cloud conference system device 120 and the third-party conference system device 130 also communicate to establish an association relationship between the created first cloud conference 123 and the target conference 133. For example, the server 121 of the cloud conference system device 120 instructs the cloud conference connector 122 and the controller 131 of the third-party conference system device 130 to communicate to establish an association relationship between the created first cloud conference 123 and the target conference 133. In this way, the user terminal 110 joins the target conference 133 through the first cloud conference 123.

[0089] After the above operation, the cloud conference system device 120 can send conference data of the user terminal joining the target conference through the first cloud conference (may be referred to as target conference data of the user terminal) to the third-party conference system device 130, and the third-party conference system device 130 can send conference data of the conference terminal joining the target conference (may be referred to as target conference data of the conference terminal) to the cloud conference system device 120.

[0090] In addition, the target conference system device 130 can also forward the received target conference data of the user terminal to the conference terminal 132 joining the target conference, and the cloud conference system device 120 can also forward the received target conference data of the conference terminal to the user terminal 110 joining the target conference through the first cloud conference.

[0091] Therefore, the user terminal 110 of the cloud conference system can transmit information with the conference terminal 132 using the third-party conference system, that is, the user of the cloud conference system and the user of the target conference system can jointly conduct a conference.

[0092] For example, the server 121 of the cloud conference system device 120 can obtain the target conference data of the user terminal 110 and send it to the cloud conference connector 122, the cloud conference connector 122 sends the target conference data of the user terminal 110 to the controller 131 of the third-party conference system device 130, and the controller 131 forwards the target conference data of the user terminal 110 to the conference terminal 132.

[0093] And the controller 131 of the third-party conference system 130 can acquire the target conference data of the conference terminal 132 and send it to the cloud conference connector 122, which forwards the target conference data of the conference terminal 132 to the user terminal 110.

[0094] When multiple user terminals, such as the user terminals 110-1 and 110-2, join the target conference through the first cloud conference, the server 121 of the cloud conference system device 120 also sends the acquired target conference data of each user terminal to other user terminals. For example, the server 121 sends the acquired target conference data of the user terminal 110-1 to the user terminal 110-2 and other user terminals, and sends the acquired target conference data of the user terminal 110-2 to the user terminal 110-1 and other user terminals.

[0095] In this way, information transmission can also be performed between multiple user terminals that join the target conference, that is, communication can also be performed between multiple cloud conference system users that join the target conference.

[0096] For more specific content of the conference access method provided in the embodiments of the present application, please refer to FIG. 2, FIG. 3 and the related descriptions thereof.

[0097] FIG. 1 is only a schematic diagram of the architecture of a conference access system provided in the embodiments of the present application, and the positional relationship between the devices, components, modules and the like shown in the diagram does not constitute any limitation.

[0098] For example, in FIG. 1, the server 121 and the cloud conference connector 122 are different devices, and in other cases, the cloud conference connector 122 can also be arranged in the server 121.

[0099] For another example, in FIG. 1, the controller 131 and the conference terminal 132 are different devices, and in other cases, the controller 131 and the conference terminal 132 can also be arranged in the same device.

[0100] The conference access method provided in the embodiments of the present application will be described in detail below. The conference access method provided in the embodiments of the present application can be implemented on the conference access system 100 shown in FIG. 1.

[0101] FIG. 2 is a flowchart of a conference access method provided in the embodiments of the present application. The conference access method shown in FIG. 2 can be executed by a computing device. For example, it can be executed by the cloud conference system device 120 in the conference access system 100. In some embodiments, it can be specifically executed by the server 121 (for example, one or more computing devices of the server 121) in the cloud conference system device 120.

[0102] For any user who needs to join a target conference through the cloud conference system, the cloud conference system device can add the user's user terminal to the target conference in the third-party conference system (such as a hardware video conference system) through the method in FIG. 2.

[0103] As shown in FIG. 2, the method includes the following steps.

[0104] Step 210, receiving a conference request from the user terminal.

[0105] In some embodiments, the user can use the user terminal to send a conference request to the cloud conference system device. Alternatively, the user terminal can also send a conference request to the cloud conference system device according to user settings or instructions of other devices, etc.

[0106] The conference request is used to indicate that the user terminal is added to the target conference, and the target conference is a conference in a target conference system other than the cloud conference system (i.e., a third-party conference created by a third-party conference system, such as a conference created in a hardware video conference system).

[0107] For example, the conference request can include conference information of the target conference, and the conference information can include a conference identifier, a conference password, etc.

[0108] The conference identifier can include a conference number (also known as a conference identity document (ID)) and other information that can be used to represent the conference identifier. The conference password can include numbers, letters, symbols, and other information that can be used to represent the conference password.

[0109] The user terminal can determine the target conference and obtain the conference information of the target conference through various feasible methods. Some examples are described below.

[0110] As an example, an administrator of the target conference can inform the users of the cloud conference system of the conference information of the target conference, and the users input the conference information of the target conference to the user terminal and initiate a conference request.

[0111] As another example, the third-party conference system device or administrator can send or input the conference information of one or more third-party conferences created to the cloud conference system device, and the user terminal can obtain the conference information of the one or more third-party conferences created from the cloud conference system device. The user can select a target conference to join from the one or more third-party conferences created through the user terminal. The user terminal can determine the target conference and its conference information according to the user selection and initiate a conference request.

[0112] As an example, FIG. 2 also shows a user terminal interface diagram. Taking an example in which the user inputs the conference information of the target conference to the user terminal and initiates a conference request:

[0113] The user terminal interface can include input boxes for conference information of the target conference, such as an input box 2212 for a conference identifier of the target conference and an input box 2214 for a conference password of the target conference. The user can input conference information of the target conference, such as the conference identifier, the conference password, and the like, in the input boxes.

[0114] The user terminal interface can also include an icon (not shown in the figure) for initiating a conference request. After the user inputs conference information of the target conference, such as the conference identifier, the conference password, and the like, the user can click the icon for initiating a conference request, and the user terminal sends a conference request to the cloud conference system device.

[0115] Step 220: Query a first cloud conference associated with the target conference.

[0116] In the case where there is no established cloud conference in the cloud conference system, the query result in step 220 is that there is no first cloud conference associated with the target conference.

[0117] In the case where there is an established cloud conference in the cloud conference system, the cloud conference system device can query a cloud conference associated with the target conference (referred to as a first cloud conference) in the established cloud conference. In step 220, the established cloud conference can refer to an established and running cloud conference.

[0118] In some embodiments, the established cloud conference in the cloud conference system includes a cloud conference associated with the target conference, and the query result is that there is a first cloud conference associated with the target conference. For example, before the current time, a user has already joined the target conference using the cloud conference system, the cloud conference system has created a first cloud conference, and the first cloud conference and the target conference have been associated.

[0119] In some embodiments, the established cloud conference in the cloud conference system does not include a cloud conference associated with the target conference, and the query result is that there is no first cloud conference associated with the target conference. For example, before the current time, no user has joined the target conference using the cloud conference system, and the current user terminal is the first user terminal to join the target conference using the cloud conference system.

[0120] The cloud conference system device can query a cloud conference associated with the target conference in the established cloud conference by various feasible methods. Some examples are described below.

[0121] The cloud conference system can include conference information, such as a conference identifier, of an associated conference of the established cloud conference. In addition, a first cloud conference associated with the target conference can be queried in the established cloud conference according to conference information, such as a conference identifier, of the target conference.

[0122] As an example, the cloud conference system includes an established cloud conference a and a cloud conference b. The cloud conference a is associated with a third-party conference 1, and the cloud conference system records a conference identifier of the third-party conference 1 associated with the cloud conference a as s1. The cloud conference b is associated with a third-party conference 2, and the cloud conference system records a conference identifier of the third-party conference 2 associated with the cloud conference b as s2.

[0123] The target conference to which the user needs to join is the third-party conference 2, and the conference identifier thereof is s2. According to the conference identifier s2, the cloud conference system can query the cloud conference whose associated conference has the same conference identifier as s2.

[0124] When the cloud conference (for example, the cloud conference b) whose associated conference has the same conference identifier as s2 exists, the cloud conference is determined as the first cloud conference. The cloud conference (for example, the cloud conference a) other than the first cloud conference in the cloud conference system can be referred to as the second cloud conference.

[0125] When the conference identifier of the associated conference of all the established cloud conferences is not the same as s2, it can be determined that there is no first cloud conference associated with the target conference.

[0126] Step 230: joining the user terminal to the target conference through the first cloud conference.

[0127] In some implementations, when the query result in step 220 is that there is no first cloud conference associated with the target conference, the following method steps can be performed:

[0128] Creating a new cloud conference (which can be referred to as the first cloud conference), and sending a conference association request to the target conference system by the cloud conference system to establish an association relationship between the target conference and the created first cloud conference.

[0129] In some embodiments, the first cloud conference can be created according to the received conference request, so that any user terminal can join the first cloud conference using the conference information of the target conference.

[0130] As an example, creating the first cloud conference according to the conference request can include: when the first cloud conference is created, generating the entry verification information of the first cloud conference according to the conference information of the target conference.

[0131] In this way, the subsequent operation of joining the user terminal to the created first cloud conference can include: verifying the conference information sent by the user terminal. When the verification is passed (for example, the conference information sent by the user terminal is consistent with the entry verification information of the first cloud conference), the user terminal is joined to the first cloud conference. When the verification fails (for example, the conference information sent by the user terminal is inconsistent with the entry verification information of the first cloud conference), the user terminal is not joined to the first cloud conference, that is, the user terminal fails to join the first cloud conference.

[0132] In some embodiments, the conference information of the target conference includes a conference identifier of the target conference, a conference password of the target conference. The entry check information of the first cloud conference can be generated according to at least one of the conference identifier of the target conference and the conference password of the target conference. For example, the conference identifier of the target conference and the conference password of the target conference are taken together as the entry check information of the first cloud conference. For another example, the conference password of the target conference is taken as the conference password of the first cloud conference.

[0133] As an example, the cloud conference system sends a conference association request to the target conference system (for example, a hardware video conference system device) to establish an association relationship between the target conference and the created first cloud conference, which can be implemented in the following manner:

[0134] As described above, the cloud conference system device includes a server and a cloud conference connector, and the hardware video conference system device includes a controller and a conference terminal. The server of the cloud conference system instructs the cloud conference connector to send a conference association request to the controller of the hardware video conference system according to the conference identifier and the conference password of the target conference, and the conference association request is used to request to establish an association relationship between the first cloud conference and the target conference. After the controller receives the conference association request, the cloud conference connector establishes the association relationship between the first cloud conference and the target conference.

[0135] This process can also be regarded as that the cloud conference connector calls the conference information of the target conference as a terminal number of a participating terminal, and the controller establishes the association relationship between the first cloud conference and the target conference after receiving the call of the cloud conference connector.

[0136] In this process, the cloud conference connector can send the conference password of the target conference to the controller, and the controller can check the received conference password of the target conference. After the check is passed, the controller establishes the association relationship between the first cloud conference and the target conference. The check passing can mean that the received conference password of the target conference is the same as the real conference password of the target conference.

[0137] In some embodiments, the cloud conference system device can also obtain a conference name of the target conference, and generate a conference name of the first cloud conference according to the conference name of the target conference. For example, the conference name of the target conference is taken as the conference name of the first cloud conference.

[0138] In this process, the cloud conference system device can obtain the conference name of the target conference by various feasible methods. For example, an application program interface (API) of the target conference system is installed on the cloud conference system device, and the cloud conference system device can run the API of the target conference system to query the conference name of the target conference of the target conference system. For another example, the cloud conference system device can communicate with the hardware video conference system device to obtain the conference name of the target conference.

[0139] After the first cloud conference is created according to the method, the user terminal can be added to the target conference through the newly created first cloud conference.

[0140] In the embodiments of the present application, adding the user terminal to the target conference through the first cloud conference can mean adding the user terminal to the first cloud conference associated with the target conference.

[0141] In some embodiments, the current user terminal can be directly added to the newly created first cloud conference, that is, it is not necessary to verify the conference information sent by the current user terminal. The current user terminal can be regarded as the creator of the first cloud conference, so that the current user terminal can be directly added to the first cloud conference without verification, which can further simplify the process of the conference access method.

[0142] In some implementations, in the case where the query result in step 220 is that there is a first cloud conference associated with the target conference, the user terminal can be added to the target conference through the queried first cloud conference.

[0143] For example, a user has used the cloud conference system to join the target conference before the current time, and the cloud conference system has created a first cloud conference, and the first cloud conference is associated with the target conference. The creation method of the first cloud conference can be similar to the method of creating the first cloud conference in the case where the query result is that there is no first cloud conference associated with the target conference.

[0144] The operation of adding the user terminal to the created first cloud conference can be similar to the operation of adding the user terminal to the newly created first cloud conference, which can include verifying the conference information (such as the conference identifier and the conference password of the target conference) sent by the user terminal, adding the user terminal to the first cloud conference when the verification is passed, and not adding the user terminal to the first cloud conference when the verification fails, that is, the user terminal fails to join the first cloud conference. For specific method content of verifying the conference information sent by the user terminal, please refer to the related description of adding the user terminal to the newly created first cloud conference.

[0145] As described in FIG. 1, after the user terminal joins the target conference through the first cloud conference, the cloud conference system device can send the target conference data of the user terminal to the target conference system, and the conference terminal in the target conference system that joins the target conference can receive the target conference data of the user terminal.

[0146] In addition, the target conference system device can send the target conference data of the conference terminal that joins the target conference to the cloud conference system, and the user terminal in the cloud conference system that joins the target conference through the first cloud conference can receive the target conference data of the conference terminal.

[0147] FIG. 3 is a flow diagram of a conference access method according to an embodiment of the present application. The conference access method shown in FIG. 3 can be performed by a processing device. For example, the conference access method shown in FIG. 3 can be performed by the cloud conference system device 120 in the conference access system 100. In some embodiments, the conference access method shown in FIG. 3 can be performed by the server 121 (e.g., one or more computing devices of the server 121) in the cloud conference system device 120.

[0148] The method flow of the conference access method when multiple users join a target conference of a third-party conference system via a cloud conference system is shown in FIG. 3. The multiple users use multiple user terminals respectively.

[0149] As an example, the user 1 and the user 2 join a target conference of a third-party conference system (e.g., a hardware video conference system) via a cloud conference system in sequence, the user 1 uses a first user terminal, and the user 2 uses a second user terminal.

[0150] In step 310, a conference request from the first user terminal is received.

[0151] In step 320, a first cloud conference associated with the target conference is queried. At this time, the query result is that there is no first cloud conference associated with the target conference.

[0152] In step 330, a first cloud conference is created according to the conference request, a conference association request is sent to the target conference system (e.g., the conference association request is sent to the hardware video conference system device in FIG. 3), and an association relationship between the target conference and the created first cloud conference is established.

[0153] In step 340, the first user terminal is joined to the target conference via the first cloud conference.

[0154] In step 350, a conference request from the second user terminal is received.

[0155] In step 360, a first cloud conference associated with the target conference is queried. At this time, the query result is that there is a first cloud conference associated with the target conference.

[0156] In step 370, the second user terminal is joined to the target conference via the first cloud conference.

[0157] The specific operation contents of the steps 310 and 350 are similar to those of the step 210, and the related descriptions of the step 210 can be referred to. The specific operation contents of the step 320 can be referred to the related descriptions of the step 220. The specific operation contents of the steps 330 and 340 can be referred to the related descriptions of the step 230, and the specific operation contents of the step 370 can also be referred to the related descriptions of the step 230.

[0158] Through the method in FIG. 3, the plurality of user terminals (for example, the first user terminal of user 1 and the second user terminal of user 2) join the same first cloud conference, and the first cloud conference is associated with the target conference. That is, the plurality of user terminals (for example, the first user terminal of user 1 and the second user terminal of user 2) join the target conference through the same first cloud conference.

[0159] The conference access method provided by the embodiments of the present application is described in detail above in combination with FIGS. 2 to 3. The apparatus provided by the embodiments of the present application will be described below in combination with FIG. 4. The apparatuses can be used to realize the functions of the processors in the method embodiments described above, and thus can also realize the beneficial effects possessed by the method embodiments described above.

[0160] FIG. 4 is a structural schematic diagram of a conference access apparatus provided by an embodiment of the present application. As shown in FIG. 4, the conference access apparatus 400 includes a communication module 410 and a processing module 420.

[0161] The communication module 410 is configured to receive a conference request from a user terminal, the conference request being used to indicate that the user terminal is to join a target conference, the target conference being a conference in a hardware video conference system other than a cloud conference system, and the cloud conference system being used to create a cloud conference.

[0162] The processing module 420 is configured to query whether there is a first cloud conference associated with the target conference in the established cloud conference, and in the case where there is a first cloud conference associated with the target conference, join the user terminal to the target conference through the first cloud conference.

[0163] In some implementations, the conference request includes a conference identifier and a conference password of the target conference, and the processing module 420 is further configured to: in the case where the conference password and the conference identifier of the target conference are verified, join the user terminal to the first cloud conference.

[0164] In some implementations, the processing module 420 is further configured to: query the first cloud conference associated with the target conference in the established cloud conference according to the conference identifier of the target conference.

[0165] In some implementations, the processing module 420 is further configured to: in the case where there is no first cloud conference associated with the target conference, create the first cloud conference according to the conference request, and send a conference association request to the target conference system to establish an association relationship between the target conference and the first cloud conference.

[0166] In some implementations, the processing module 420 is further configured to: obtain a conference name of the target conference, and after creating the first cloud conference according to the conference request, further include generating a conference name of the first cloud conference according to the conference name of the target conference.

[0167] In some embodiments, the user terminals include a first user terminal and a second user terminal, and the processing module 420 is further configured to add the first user terminal and the second user terminal to the target conference through the first cloud conference.

[0168] In some embodiments, the processing module 420 is further configured to receive target conference data from the first user terminal, and send the target conference data of the first user terminal to the second user terminal.

[0169] More details about the functions of the aforementioned communication module 410 and processing module 420 can be found in the description of the conference access method provided by the embodiments of the present application in FIG. 2-FIG. 3.

[0170] Optionally, the communication module 410 and the processing module 420 can each include a plurality of sub-modules, which can be respectively deployed to respectively implement part of the functions of the corresponding modules, for example, to implement one or more steps of the conference access method provided in the aforementioned FIG. 2-FIG. 3.

[0171] The communication module 410 and the processing module 420 can each be implemented by software or by hardware. For example, the implementation of the processing module 420 is described below. Similarly, the implementation of the communication module 410 can refer to the implementation of the processing module 420.

[0172] As an example of a software functional unit, the processing module 420 can include code running on a computing instance. The computing instance can include at least one of a physical host (computing device), a virtual machine, and a container. Further, the computing instance can be one or more. For example, the A module can include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code can be distributed in the same region (region), or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code can be distributed in the same availability zone (AZ), or in different AZs, each AZ including a data center or multiple data centers with similar geographical locations. Generally, one region can include multiple AZs.

[0173] Likewise, the plurality of hosts / virtual machines / containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Among them, usually one VPC is set in one region, and communication between two VPCs in the same region and between VPCs in different regions needs to set a communication gateway in each VPC to realize the interconnection between VPCs through the communication gateway.

[0174] As an example of a hardware functional unit, the processing module 420 can include at least one computing device, such as a server, etc. Alternatively, the processing module 420 can also be a device implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), etc. Among them, the above-mentioned PLD can be implemented by a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0175] The plurality of computing devices included in the processing module 420 can be distributed in the same region or in different regions. The plurality of computing devices included in the processing module 420 can be distributed in the same AZ or in different AZs. Likewise, the plurality of computing devices included in the processing module 420 can be distributed in the same VPC or in multiple VPCs. Among them, the plurality of computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0176] It should be noted that in other embodiments, the processing module 420 can be used to perform any step of the conference access method provided in FIGS. 2-3 of the embodiments of the present application, the communication module 410 can be used to perform any step of the conference access method provided in FIGS. 2-3 of the embodiments of the present application, and the steps responsible for the communication module 410 and the processing module 420 can be specified as needed. By implementing different steps in the conference access method provided in FIGS. 2-3 of the embodiments of the present application through the communication module 410 and the processing module 420 respectively, the entire function of the conference access device 400 can be realized.

[0177] The application also provides a computing device 500. As shown in FIG. 5, the computing device 500 includes a bus 502, a processor 504, a memory 506, and a communication interface 508. The processor 504, the memory 506, and the communication interface 508 communicate with each other through the bus 502. The computing device 500 can be a server or a terminal device. It should be understood that the number of processors and memories in the computing device 500 is not limited. Optionally, the processor 504 of the computing device 500 can be connected to a display and an input device (not shown in FIG. 5) through the communication interface 508.

[0178] The bus 502 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one line is shown in FIG. 5, but it does not mean that there is only one bus or only one type of bus. The bus 502 can include a path for transmitting information between various components (for example, the memory 506, the processor 504, and the communication interface 508) of the computing device 500.

[0179] The processor 504 can include any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP), etc. In the embodiments of the application, the processor 504 is configured to perform the steps or operations of the conference access method provided in FIGS. 2-3.

[0180] The memory 506 can include a volatile memory such as a random access memory (RAM). The processor 504 can also include a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0181] The executable program code stored in the memory 506 is executed by the processor 504 to implement the functions of the aforementioned communication module 410 and processing module 420 respectively, thereby implementing the conference access method provided in FIG. 2-3 of the embodiments of the present application. That is, the memory 506 stores instructions for executing the conference access method provided in FIG. 2-3 of the embodiments of the present application.

[0182] The communication interface 508 uses a transceiving module such as but not limited to a network interface card and a transceiver to implement the communication between the computing device 500 and other devices or communication networks.

[0183] The display can include various display devices such as a plasma display and a liquid crystal display that can implement display functions. The computing device 500 can implement the display functions related to the conference access method provided in FIG. 2-3 of the embodiments of the present application through the display.

[0184] The input device can include various input devices such as a keyboard, a mouse, and a touch screen that can implement information / signal input.

[0185] The present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a notebook computer, or a smart phone.

[0186] As shown in FIG. 6, the computing device cluster 600 includes at least one computing device 500. The memory 506 in one or more computing devices 500 in the computing device cluster can store the same instructions for executing the conference access method provided in FIG. 2-3 of the embodiments of the present application.

[0187] In some possible implementations, the memory 506 of one or more computing devices 500 in the computing device cluster can also respectively store partial instructions for executing the conference access method provided in FIG. 2-3 of the embodiments of the present application. In other words, the combination of one or more computing devices 500 can collectively execute the instructions for executing the conference access method provided in FIG. 2-3 of the embodiments of the present application.

[0188] It should be noted that the memory 506 in different computing devices 500 in the computing device cluster can store different instructions for respectively implementing part of the functions of the conference access apparatus 400. That is, the instructions stored in the memory 506 in different computing devices 500 can implement the functions of one or more of the aforementioned communication module 410 and processing module 420.

[0189] In some possible implementation manners, one or more of the computing devices in the computing device cluster can be connected through a network. The network can be a wide area network, a local area network, or the like.

[0190] FIG. 7 shows one possible implementation manner. As shown in FIG. 7, the computing device 500A and the computing device 500B are connected through a network. Specifically, the computing devices are connected to the network through the communication interfaces in the computing devices. In this type of possible implementation manner, the memory 506 in the computing device 500A stores instructions for performing the functions of the communication module 410. Meanwhile, the memory 506 in the computing device 500B stores instructions for performing the functions of the processing module 420.

[0191] The connection manner between the computing device cluster shown in FIG. 7 can be that, considering that the conference access method provided in the present application needs to process a large amount of conference data, and the like, the functions implemented by the processing module 420 are executed by the computing device 500B.

[0192] It should be understood that the functions of the computing device 500A shown in FIG. 7 can also be completed by multiple computing devices 500. Similarly, the functions of the computing device 500B can also be completed by multiple computing devices 500.

[0193] The embodiments of the present application further provide another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to the connection manners of the computing device clusters described with reference to FIG. 6 and FIG. 7. The difference is that the memory 506 in one or more of the computing devices 500 in the computing device cluster can store the same instructions for performing the conference access methods provided in FIG. 2-FIG. 3 of the embodiments of the present application.

[0194] In some possible implementation manners, the memory 506 of one or more of the computing devices 500 in the computing device cluster can also respectively store part of the instructions for performing the conference access methods provided in FIG. 2-FIG. 3 of the embodiments of the present application. In other words, the combination of one or more of the computing devices 500 can collectively execute the instructions for performing the conference access methods provided in FIG. 2-FIG. 3 of the embodiments of the present application.

[0195] The embodiments of the present application further provide a computer program product containing instructions. The computer program product can be a software or program product containing instructions, which can be run on a computing device or stored in any available medium. The instructions contained in the computer program product can include instructions for performing the conference access methods provided in FIG. 2-FIG. 3 of the embodiments of the present application. When the computer program product is run on at least one computing device, the at least one computing device is caused to perform the steps or operations of the conference access methods provided in FIG. 2-FIG. 3 of the embodiments of the present application.

[0196] The computer readable storage medium can be any available media or data storage device that can be accessed by the computing device and includes one or more of a magnetic media, (e.g., a floppy disk, a hard disk drive, a magnetic tape), an optical media, (e.g., a compact disk, a DVD), or a semiconductor media (e.g., a solid state hard drive), etc. The computer readable storage medium includes instructions that instruct the computing device to perform the steps or operations of the conference access method provided in FIG. 2-3.

[0197] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the protection scope of the technical solutions of the embodiments of the present application.

[0198] The terms "first", "second", "third", and "fourth" and the like in the specification and claims of the present application and the above-described drawings are used to distinguish different objects, and are not intended to define a particular order.

[0199] In the embodiments of the present application, the words "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design presented as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or advantageous than other embodiments or design solutions. Rather, the use of the words "exemplary" or "for example" is intended to present concepts in a particular manner.

Claims

1. A conference access method, characterized by, The method comprises: receiving a conference request from a user terminal, the conference request being used to indicate that the user terminal is to join a target conference, the target conference being a conference in a hardware video conference system outside a cloud conference system, the cloud conference system being used to create a cloud conference; querying whether a first cloud conference associated with the target conference exists in an established cloud conference; in a case where the first cloud conference associated with the target conference exists, joining the user terminal to the target conference through the first cloud conference.

2. The method of claim 1, wherein, The conference request comprises a conference identifier and a conference password of the target conference, and the joining of the user terminal to the target conference through the first cloud conference comprises: in a case where the conference password and the conference identifier of the target conference are verified, joining the user terminal to the first cloud conference.

3. The method according to claim 1 or 2, characterized in that, The querying whether the first cloud conference associated with the target conference exists in the established cloud conference comprises: querying whether the first cloud conference associated with the target conference exists in the established cloud conference according to the conference identifier of the target conference.

4. The method according to any one of claims 1-3, characterized in that, The method further comprises: in a case where the first cloud conference associated with the target conference does not exist, creating the first cloud conference according to the conference request; sending a conference association request to the hardware video conference system to establish an association relationship between the target conference and the first cloud conference.

5. The method of claim 4, wherein, The method further comprises: obtaining a conference name of the target conference; after the first cloud conference is created according to the conference request, the method further comprises: generating a conference name of the first cloud conference according to the conference name of the target conference.

6. The method according to any one of claims 1-5, characterized in that, The user terminal comprises a first user terminal and a second user terminal, and the joining of the user terminal to the target conference through the first cloud conference comprises: joining the first user terminal and the second user terminal to the target conference through the first cloud conference.

7. The method of claim 6, wherein, After the first user terminal and the second user terminal are joined to the target conference through the first cloud conference, the method further comprises: receiving target conference data from the first user terminal; sending the target conference data of the first user terminal to the second user terminal.

8. A conference access device, characterized by The apparatus comprises: a communication module configured to receive a conference request from a user terminal, the conference request being used to indicate that the user terminal is to join a target conference, the target conference being a conference in a hardware video conference system outside a cloud conference system, the cloud conference system being used to create a cloud conference; a processing module configured to query whether a first cloud conference associated with the target conference exists in an established cloud conference, and in a case where the first cloud conference associated with the target conference exists, join the user terminal to the target conference through the first cloud conference.

9. A cloud conferencing system, characterized by The cloud conference system comprises a server configured to perform the method according to any one of claims 1-7.

10. A cluster of computing devices, characterized in that, The cluster of computing devices comprises at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the method according to any one of claims 1-7.

11. A computer program product comprising instructions, characterized in that, When the instructions are executed by at least one computing device, the at least one computing device is caused to perform the method of any of claims 1-7.

12. A computer-readable storage medium, characterized in that, comprising computer program instructions, when executed by at least one computing device, cause the at least one computing device to perform the method of any of claims 1-7.

Images