WO2024007608A1

WO2024007608A1 - Conference control method and apparatus, and communication system

Info

Publication number: WO2024007608A1
Application number: PCT/CN2023/080085
Authority: WO
Inventors: 童春荣
Original assignee: 华为云计算技术有限公司
Priority date: 2022-07-07
Filing date: 2023-03-07
Publication date: 2024-01-11
Also published as: CN117411861A

Abstract

The present application relates to the technical field of communications, and discloses a conference control method and apparatus, and a communication system. The method comprises: once a conference management device determines that a first conference meets a switching condition, the conference management device sends switching instruction information to a first conference terminal which accesses the first conference so as to instruct the first conference terminal to switch from the first conference to a second conference. Since the conference management device controls the first conference terminal to perform conference switching once the first conference meets the switching condition, manual participation is not needed in the conference switching process, the switching process is simple and not prone to errors, the switching speed is fast, and the switching efficiency is high.

Description

Conference control method, device and communication system

This application claims priority to the Chinese patent application with the filing date of July 7, 2022, the application number 202210803404.9, and the name "Conference Control Method, Device and Communication System", the entire content of which is incorporated into this application by reference.

Technical field

The present application relates to the field of communication technology, and in particular to a conference control method, device and communication system.

Background technique

Multimedia conference refers to a virtual conference realized through communication technology, which allows geographically dispersed individuals or groups to gather together and exchange information through graphics, sound and other methods. With the popularization of telecommuting, online education, online communication and other services, multimedia conferencing has become a necessity in all walks of life, and the reliability requirements of multimedia conferencing are getting higher and higher.

Currently, in order to ensure the reliability of multimedia conferences, multimedia conferences are usually held in at least two conference rooms. For example, the at least two conference rooms include conference room 1 and conference room 2. Conference room 1 is usually used to hold multimedia conferences. After conference room 1 fails, participants manually switch to conference room 2 to continue the multimedia conference. The conference room is also called a conference, a multimedia conference room, etc. For example, conference room 1 can be called conference 1, and conference room 2 can be called conference 2.

However, the above solution requires participants to manually switch conferences, which is complex and has low switching efficiency.

Contents of the invention

This application provides a conference control method, device and communication system, which helps to simplify the conference switching process and improve conference switching efficiency. The technical solution of this application is as follows:

In a first aspect, a conference control method is provided, which method includes: the conference management device determines that the first conference satisfies the switching condition; the conference management device sends switching instruction information to the first conference terminal that accesses the first conference, and the switching instruction information Used to instruct the first conference terminal to switch from the first conference to the second conference.

In some implementation scenarios, the first conference may be called the first conference room, and the second conference may be called the second conference room. That is, when a conference terminal accesses a certain conference, it means that the conference terminal accesses the certain conference. meeting room.

In the technical solution provided by this application, after the conference management device determines that the first conference meets the switching conditions, the conference management device controls the first conference terminal to switch from the first conference to the second conference. Therefore, the first conference terminal switches from the first conference to the second conference. The process of the second meeting does not require manual participation, the switching process is simple and not error-prone, the switching speed is fast, and the switching efficiency is high.

Optionally, the first conference and the second conference belong to different conference systems. For example, the first conference belongs to the first conference system, and the first conference belongs to the second conference system. Among them, the first conference system and the second conference system are conference systems of different manufacturers, or they may be conference systems of the same manufacturer.

In the technical solution provided by this application, since the first conference and the second conference belong to different conference systems, the first conference terminal switches from the first conference to the second conference, that is, the first conference terminal switches between different conference systems. Therefore, this application can use the conference management equipment to control the conference terminal to switch between different conference systems. The switching process of the conference system does not require manual participation. The switching process is simple and not prone to errors. The switching speed is fast and the switching efficiency is high.

Optionally, the first conference and the second conference belong to the same conference system. For example, the first conference and the second conference both belong to the first conference system, or the first conference and the second conference both belong to the second conference system.

In the technical solution provided by this application, since the first conference and the second conference belong to the same conference system, this application can use the conference management device to control the conference terminal to switch between different conferences (that is, different conference rooms) in the same conference system. , the conference switching process does not require manual participation, the switching process is simple and not error-prone, the switching speed is fast, and the switching efficiency is high.

Optionally, the switching conditions include one or more of the following: failure of the first conference, failure of the conference system to which the first conference belongs. The failure of the first conference may include but is not limited to: the number of conference terminals that are disconnected among the multiple conference terminals that access the first conference (that is, the conference terminals that are disconnected from the first conference) is greater than the preset number, The proportion of disconnected conference terminals among the plurality of conference terminals connected to the first conference is greater than the preset proportion, and the number of disconnections of at least one conference terminal connected to the first conference is greater than the preset ratio. times, the conference resources (such as conference number, conference room) of the first conference are invalid or unavailable, the conference instance corresponding to the first conference in the conference system to which the first conference belongs fails, etc. For the convenience of description, assume that the conference system to which the first conference belongs is the first conference system. For illustration, a failure of the conference system to which the first conference belongs may include but is not limited to: a conference that fails in multiple conferences being carried out simultaneously by the first conference system. The number of meetings is greater than the target number. The proportion of failed meetings in multiple meetings held simultaneously by the first conference system is greater than the target proportion. If a network failure occurs in the first meeting system (for example, the network is disconnected), the first meeting Abnormal heartbeat occurs in the system.

According to the technical solution provided by this application, when the first conference fails and/or the conference system to which the first conference belongs fails, the conference management device determines that the first conference meets the switching conditions and instructs the first conference terminal to access the first conference. Switch from the first conference to the second conference. Therefore, this application can perform conference system switching for conference system-level failures, and can also perform conference switching for conference-level failures. The technical solution of this application has high flexibility, usability, and Strong popularity.

Optionally, before the conference management device sends the switching instruction information to the first conference terminal, the method also includes: the conference management device determines the conference identification of the second conference according to the target association relationship and the conference identification of the first conference, and the switching The instruction information includes the conference identifier of the second conference, and the target association includes an association between the conference identifier of the first conference and the conference identifier of the second conference. The switching instruction information may also include an identification of the conference system to which the second conference belongs.

In the technical solution provided by this application, the conference management device determines the conference identifier of the second conference based on the target association relationship and the conference identifier of the first conference, and includes the conference identifier of the second conference in the switching instruction information sent to the first conference terminal. As a result, the switching instruction information can instruct the first conference terminal to switch from the first conference to the second conference.

Optionally, before the first conference terminal accesses the first conference, the method further includes: the conference management device sends first access instruction information to the first conference terminal, and the first access instruction information is used to instruct the first conference terminal. Access the first meeting. The conference management device may actively send the first access instruction information to the first conference terminal, or may send the first access instruction information to the first conference terminal at the request of the first conference terminal. The conference management device sends the first access instruction information to the first conference terminal, which can facilitate the first conference terminal to access the first conference according to the first access instruction information.

Optionally, before the conference management device sends the first access indication information to the first conference terminal, the method further includes:

The conference management equipment receives the first conference joining request sent by the first conference terminal. The first conference joining request carries the target conference identification. The target conference identification is used for the conference terminal to access the first conference or the second conference; the conference management equipment determines the target association relationship and the second conference. The target conference identifier carried in a conference joining request determines the conference identifier of the first conference, the first access instruction information includes the conference identifier of the first conference, and the target association relationship includes the association relationship between the target conference identifier and the conference identifier of the first conference.

In the technical solution provided by this application, after receiving the first joining request sent by the first conference terminal, the conference management device determines the conference identification of the first conference based on the target association relationship and the target conference identification carried in the first joining request, and sends the conference identification to the first meeting. The conference terminal sends the first access instruction information including the conference identifier of the first conference, so that the first access instruction information can instruct the first conference terminal to access the first conference, and the first conference terminal can access the first conference according to the first access instruction information. Enter the first meeting. In addition, since the target conference ID is used by the conference terminal to access the first conference or the second conference, the conference terminal can access either of the first conference and the second conference based only on the target conference ID. , participants only need to perceive the target conference identity, but do not need to perceive the conference identity of the first conference and the conference identity of the second conference. When the first conference and the second conference belong to two conference systems (for example, the first conference belongs to the first conference system and the second conference belongs to the second conference system), the two conference systems can correspond to the same conference client, and the participants There is no need to perceive the existence of the two conference systems, the requirements for participants are lower, the actual operation is simpler, less error-prone, and the implementation cost is lower.

Optionally, after the first conference terminal switches to the second conference, the method further includes: the conference management device sends second access instruction information to the second conference terminal based on the switching instruction information, and the second access instruction information is used to Instruct the second conference terminal to access the second conference. The conference management device may actively send the second access instruction information to the second conference terminal, or may send the second access instruction information to the second conference terminal at the request of the second conference terminal.

In the technical solution provided by this application, after the first conference terminal switches to the second conference, the conference management device sends second access instruction information to the second conference terminal based on the switching instruction information to control the second conference terminal to access the second conference. , this can prevent the second conference terminal from accessing the first conference due to failure and affecting the convening of the multimedia conference.

Optionally, before the conference management device sends the second access indication information to the second conference terminal, the method further includes:

The conference management equipment receives the second conference joining request sent by the second conference terminal. The second conference joining request carries the target conference identification. The target conference identification is used for the conference terminal to access the first conference or the second conference; the conference management equipment determines the target association relationship and the second conference. The target conference identifier carried in the second conference joining request determines the conference identifier of the second conference, the second access instruction information includes the conference identifier of the second conference, and the target association relationship includes the association relationship between the target conference identifier and the conference identifier of the second conference.

In the technical solution provided by this application, after receiving the second joining request sent by the second conference terminal, the conference management device determines the conference identification of the second conference based on the target association relationship and the target conference identification carried in the second joining request, and sends the conference identification to the second meeting. The conference terminal sends the second access instruction information including the conference identifier of the second conference, so that the second access instruction information can instruct the second conference terminal to access the second conference, and the second conference terminal can access the second conference according to the second access instruction information. Enter the second meeting. In addition, since the target conference ID is used by the conference terminal to access the first conference or the second conference, the conference terminal can access either of the first conference and the second conference based only on the target conference ID. , participants only need to perceive the target conference identity, but do not need to perceive the conference identity of the first conference and the conference identity of the second conference. When the first conference and the second conference belong to two conference systems (for example, the first conference belongs to the first conference system and the second conference belongs to the second conference system), the two conference systems can correspond to the same conference client, and the participants There is no need to perceive the existence of the two conference systems, the requirements for participants are lower, the actual operation is simpler, less error-prone, and the implementation cost is lower.

Optionally, the method also includes: the conference management device receives a conference reservation request sent by the conference reservation terminal; the conference management device generates a target conference identification according to the conference reservation request, and the target conference identification is the same as the conference identification of the first conference and the conference identification of the second conference. The conference identifiers are all associated; the conference management device sends a conference reservation response to the conference reservation terminal, and the conference reservation response carries the target conference identifier, and the target conference identifier is used for the conference terminal to access the first conference or the second conference.

In the technical solution provided by this application, after the conference management device receives the conference reservation request sent by the conference reservation terminal, the conference management device generates a target conference identifier, and makes the target conference identifier consistent with the conference identifier of the first conference and the conference identifier of the second conference. After the association, the conference management device feeds back the target conference identification to the conference reservation terminal, and the conference reservation terminal can send the target conference identification to each conference terminal. The conference terminal that obtains the target conference ID is only based on the target conference. By identifying this conference ID, you can access either of the first conference and the second conference. Participants only need to perceive the conference ID of the target conference ID, and do not need to perceive the conference ID of the first conference and the conference ID of the second conference. Conference logo. When the first conference and the second conference belong to two conference systems (for example, the first conference belongs to the first conference system and the second conference belongs to the second conference system), the two conference systems can correspond to the same conference client, and the participants There is no need to perceive the existence of the two conference systems, the requirements for participants are lower, the actual operation is simpler, less error-prone, and the implementation cost is lower.

Optionally, the method further includes: the conference management device generates a target association relationship, where the target association relationship is an association relationship between the target conference ID and the conference ID of the first conference and the conference ID of the second conference.

In the technical solution provided by this application, the conference management device generates a target association relationship, which can facilitate the conference management device to determine the conference identifier of the first conference or the third conference according to the target association relationship and the target conference identifier carried in the conference join request when the conference management device receives the request. The conference ID of the second conference, and when the conference management device determines that the first conference meets the switching condition, determines the conference ID of the second conference that can be switched based on the target association relationship and the conference ID of the failed first conference.

Optionally, the first conference belongs to the first conference system, and the second conference belongs to the second conference system. The method also includes: the conference management device sends a conference creation request to the first conference system and the second conference system respectively according to the conference reservation request. ; The conference management device receives the conference creation response sent by the first conference system and the second conference system respectively. The conference creation response sent by the first conference system carries the conference ID of the first conference, and the conference creation response sent by the second conference system carries the second conference ID. The conference ID of the conference.

In the technical solution provided by this application, after the conference management device receives the conference reservation request sent by the conference reservation terminal, it reserves meetings with the first conference system and the second conference system respectively according to the conference reservation request. During the process of booking a conference, the first conference system can create the first conference, generate the conference ID of the first conference, and send the conference ID of the first conference to the conference management device. During the process of booking the conference from the conference management device to the second conference system , the second conference system can create the second conference, generate the conference ID of the second conference, and send the conference ID of the second conference to the conference management device. In this way, the conference management device can obtain the conference ID and the conference ID of the first conference. The conference identifier of the second conference, and associates the target conference identifier with both the conference identifier of the first conference and the conference identifier of the second conference.

Optionally, both the first conference and the second conference belong to the first conference system. The method also includes: the conference management device sends a conference creation request to the first conference system according to the conference reservation request; the conference management device receives the conference request sent by the first conference system. The conference creation response carries the conference ID of the first conference and the conference ID of the second conference.

In the technical solution provided by this application, after the conference management device receives the conference reservation request sent by the conference reservation terminal, the conference management device reserves the first conference and the second conference with the first conference system according to the conference reservation request. The first conference system can create The first meeting and the second meeting generate the meeting ID of the first meeting and the meeting ID of the second meeting, and send the meeting ID of the first meeting and the meeting ID of the meeting to the meeting management device, so that the meeting management device can obtain to the conference ID of the first conference and the conference ID of the second conference, and associate the target conference ID with both the conference ID of the first conference and the conference ID of the second conference.

Optionally, the conference reservation terminal is the first conference terminal or the second conference terminal. The conference reservation terminal may also be a conference terminal other than the first conference terminal and the second conference terminal, or the conference reservation terminal may be a terminal dedicated to conference reservation.

In a second aspect, a conference control method is provided. The method includes: a first conference terminal receiving switching instruction information sent by a conference management device, where the switching instruction information is a first conference to which the conference management device determines that the first conference terminal is accessed. Sent after the switching condition is met; the first conference terminal switches from the first conference to the second conference according to the switching instruction information.

In the technical solution provided by this application, after the conference management equipment determines that the first conference meets the switching conditions, the conference management The device controls the first conference terminal to switch from the first conference to the second conference. Therefore, the process of switching the first conference terminal from the first conference to the second conference does not require manual participation. The switching process is simple and not error-prone, and the switching speed is fast. Higher efficiency.

Optionally, the first conference and the second conference belong to different conference systems.

Optionally, the first conference and the second conference belong to the same conference system.

Optionally, the switching conditions include one or more of the following: failure of the first conference, failure of the conference system to which the first conference belongs.

Optionally, the first conference belongs to the first conference system, the second conference belongs to the second conference system, and a conference client is installed in the first conference terminal. The conference client includes a first conference interface corresponding to the first conference system and Corresponding to the second conference interface of the second conference system, the first conference terminal switches from the first conference to the second conference according to the switching instruction information, including: the first conference terminal calls the second conference interface to access the second conference according to the switching instruction information. Two meetings.

In the technical solution provided by this application, since the conference client installed in the first conference terminal includes a first conference interface corresponding to the first conference system and a second conference interface corresponding to the second conference system, one conference client corresponds to There are two conference systems, the first conference system and the second conference system. The first conference terminal can access the conference created by any one of the first conference system and the second conference system through the conference client, and the participants do not need to be aware of it. The existence of the first conference system and the second conference system has lower requirements for participants, is relatively simple to operate in practice, and is less prone to errors.

Optionally, before the first conference terminal receives the switching instruction information sent by the conference management device, the method further includes: the first conference terminal receives the first access instruction information sent by the conference management device; Enter the instruction information to access the first conference. The conference management device may actively send the first access instruction information to the first conference terminal, or may send the first access instruction information to the first conference terminal at the request of the first conference terminal.

Optionally, before the first conference terminal receives the first access instruction information sent by the conference management device, the method further includes: the first conference terminal sends a first conference joining request to the conference management device, and the first conference joining request carries the target conference identifier. , the target conference identification is used for the conference terminal to access the first conference or the second conference. After the first conference terminal sends the first conference joining request to the conference management device, the conference management device sends first access instruction information to the first conference terminal. That is, the conference management device sends the first access indication information to the first conference terminal at the request of the first conference terminal.

In the technical solution provided by this application, the first conference terminal sends a first joining request to the conference management device, which can facilitate the conference management device to determine the conference ID of the first conference based on the target association relationship and the target conference ID carried in the first joining request, and send the conference ID to the conference management device. The first conference terminal sends first access instruction information including the conference identifier of the first conference to indicate to the first conference terminal Access the first meeting. In addition, the target conference ID is used for the conference terminal to access the first conference or the second conference. Therefore, the conference terminal can access either of the first conference and the second conference based only on the target conference ID. Participants only need to perceive the target conference identifier, but do not need to perceive the conference identifier of the first conference and the conference identifier of the second conference. When the first conference and the second conference belong to two conference systems, the two conference systems can correspond to the same conference client, and participants can control the conference terminal to access the two conference terminals through the conference client and the target conference identification. For meetings created by any one of the two conference systems, participants do not need to be aware of the existence of the two conference systems. The requirements for participants are lower, the actual operation is simpler, less error-prone, and the implementation cost is low.

Optionally, the first conference belongs to the first conference system, the second conference belongs to the second conference system, and a conference client is installed in the first conference terminal. The conference client includes a first conference interface corresponding to the first conference system and Corresponding to the second conference interface of the second conference system, the first conference terminal accesses the first conference according to the first access instruction information, including: the first conference terminal calls the first conference interface to access according to the first access instruction information. First meeting.

In a third aspect, a conference control device is provided, including various modules for executing the method provided in the above-mentioned first aspect or any optional manner of the first aspect. The modules can be implemented based on software, hardware, or a combination of software and hardware, and the modules can be arbitrarily combined or divided based on specific implementations.

A fourth aspect provides a conference control device, including various modules for executing the method provided in the above-mentioned second aspect or any optional manner of the second aspect. The modules can be implemented based on software, hardware, or a combination of software and hardware, and the modules can be arbitrarily combined or divided based on specific implementations.

In a fifth aspect, a conference control device is provided, including a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory so that the conference control device performs the above-mentioned first aspect or the first The conference control method provided by any of the optional methods.

A sixth aspect provides a conference control device, including a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory so that the conference control device performs the above-mentioned second aspect or the second aspect. The conference control method provided by any of the optional methods.

In a seventh aspect, a communication system is provided. The communication system includes a conference management device and a first conference terminal. The conference management device and the first conference terminal are communicatively connected. The conference management device includes a device as provided in the third or fifth aspect. A conference control device, the first conference terminal includes a conference control device as provided in the fourth aspect or the sixth aspect.

In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes computer program instructions. When the computer program instructions are executed by a conference management device, the conference management device performs the above-mentioned first aspect or the third aspect. On the one hand, any of the optional methods provided by the conference control method.

In a ninth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes computer program instructions. When the computer program instructions are executed by a conference terminal, the conference terminal causes the conference terminal to execute the above second aspect or the second aspect. Conference control method provided by any of the optional methods.

In a tenth aspect, a computer program product containing instructions is provided. When the instructions are executed by a conference management device, The conference management device is caused to execute the conference control method provided by the above-mentioned first aspect or any optional method of the first aspect.

An eleventh aspect provides a computer program product containing instructions. When the instructions are executed by a conference terminal, the conference terminal causes the conference terminal to perform conference control as provided in the above-mentioned second aspect or any optional method of the second aspect. method.

In a twelfth aspect, a chip is provided. The chip includes programmable logic circuits and/or program instructions. When the chip is run, it is used to implement the method provided by the above-mentioned first aspect or any alternative method of the first aspect. , or implement the conference control method as provided in the above second aspect or any optional manner of the second aspect.

The technical effects in the third to twelfth aspects can be referred to the technical effects in the first to second aspects, so they will not be described again.

Description of the drawings

Figure 1 is a schematic diagram of an application scenario provided by an embodiment of the present application;

Figure 2 is a flow chart of a conference control method provided by an embodiment of the present application;

Figure 3 is a flow chart of another conference control method provided by an embodiment of the present application;

Figure 4 is a schematic diagram of a conference access interface provided by an embodiment of the present application;

Figure 5 is a flow chart of yet another conference control method provided by an embodiment of the present application;

Figure 6 is a flow chart of yet another conference control method provided by an embodiment of the present application;

Figure 7 is a schematic diagram of a conference reservation interface provided by an embodiment of the present application;

Figure 8 is a schematic diagram of a conference control device provided by an embodiment of the present application;

Figure 9 is a schematic diagram of another conference control device provided by an embodiment of the present application;

Figure 10 is a schematic diagram of yet another conference control device provided by an embodiment of the present application;

Figure 11 is a schematic diagram of yet another conference control device provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be further described below in conjunction with the accompanying drawings.

Multimedia conference refers to a virtual conference realized through communication technology. With the popularity of telecommuting, online education, online communication and other services, as well as due to the epidemic and other reasons, multimedia conferencing has become an urgent need in all walks of life, and the reliability requirements of multimedia conferencing are getting higher and higher. Cloud conferencing is a form of implementation of multimedia conferencing. Cloud conferencing has the advantages of efficiency, convenience, and low cost, and is more suitable for large-scale conference scenarios. For some large-scale cross-regional cloud conferences, the cloud conference system has gradually transformed from a traditional support system into a combat production system. Compared with traditional in-house conference systems, cloud conference systems are more complex and have more influencing factors. Once the cloud conference system fails, the impact will be greater, so the reliability requirements of cloud conference systems are higher.

In order to ensure that multimedia conferences (such as cloud conferences) can proceed under any circumstances, at least two conference rooms (or multimedia conference rooms) can be used to hold multimedia conferences. The at least two conference rooms are independent of each other and do not affect each other. Failure of one conference room will not affect the other conference room. For example, the at least two conference rooms include conference room 1 and conference room 2. Conference room 1 and conference room 2 are independent of each other and do not affect each other. Conference room 1 can usually be used to hold a multimedia conference. After conference room 1 fails, you can Switch to conference room 2 to continue the multimedia conference to ensure that the multimedia conference will not be interrupted due to the failure of conference room 1. However, switching between two independent conference rooms will bring many cost and experience problems, making implementation difficult. Especially when the two conference rooms belong to two independent conference systems, switching between the two conference rooms involves switching between the two independent conference systems. The switching cost will be higher and the difficulty will be greater. , the user experience will be worse.

The following takes Conference Room 1 and Conference Room 2 as two independent conference systems as an example. For example, conference room 1 belongs to conference system 1 and conference room 2 belongs to conference system 2. Before convening a multimedia conference, the conference booker reserves a conference (that is, a conference room) in the conference system 1 and the conference system 2 respectively. Assume that the meeting ID (identity, ID) of meeting 1 (that is, conference room 1) booked by the meeting booker from conference system 1 is conference ID1 (for example, 12345678), and that meeting 2 (that is, conference room 1) booked by the meeting booker from conference system 2 The conference ID of conference room 2 is conference ID2 (for example, 87654321). The conference booker can inform all participants of the conference ID1 and conference ID2. The meeting ID1 may be the meeting number of meeting 1 (that is, meeting room 1), and the meeting ID2 may be the meeting number of meeting 2 (that is, meeting room 2).

Assume that conference system 1 corresponds to conference client 1, and conference system 2 corresponds to conference client 2.

In a current solution: each participant prepares two conference terminals, namely conference terminal 1 and conference terminal 2. Conference terminal 1 is installed with conference client 1, and conference terminal 2 is installed with conference client 2. When starting a multimedia conference, each participant uses conference ID1 and conference client 1 to connect conference terminal 1 to conference room 1, and uses conference ID2 and conference client 2 to connect conference terminal 2 to conference room 2. When both conference room 1 and conference room 2 are normal, all participants use conference room 1 to hold a multimedia conference. Conference terminal 1 and conference system 1 interact with media streams (such as audio streams/video streams). Conference terminal 2 interacts with conference system 1. There is no media streaming interaction between systems 2. After the failure of conference room 1, the conference organizer notified all participants to switch conference rooms. All participants manually switched to conference room 2 according to the conference organizer's notification to continue the multimedia conference. After the switch, the connection between conference terminal 2 and conference system 2 There is no media flow interaction between the conference terminal 1 and the conference system 1. Since when the multimedia conference starts, all conference terminals 1 are connected to conference room 1, and all conference terminals 2 are connected to conference room 2. Therefore, after conference room 1 fails, all participants can quickly switch to the conference room. Room 2 continues to hold multimedia conferences. However, this solution requires each participant to prepare two conference terminals, and not all participants have such conditions. Therefore, the implementation cost of this solution is high. It is theoretically feasible, but it is difficult to implement.

In another current solution: each participant prepares a conference terminal, and conference client 1 and conference client 2 are installed in the conference terminal. When starting a multimedia conference, each participant uses conference ID 1 and conference client 1 to connect the conference terminal to conference room 1, and all participants use conference room 1 to hold a multimedia conference. After conference room 1 fails, the conference organizer notifies all participants to switch conference rooms. All participants use conference ID 2 and conference client 2 to connect the conference terminal to conference room 2 according to the conference organizer's notification. However, in this solution, after a failure occurs in conference room 1, participants need to use the conference ID2 of conference room 2 to rejoin the conference. The operation is very troublesome, the switching process takes a long time, and the switching efficiency is low. Since conference room 1 belongs to conference system 1 and conference room 2 belongs to conference system 2, that is, conference room 1 and conference room 2 belong to different conference systems, and the joining method of conference system 1 and the joining method of conference system 2 usually have certain differences, Therefore, the process of participants manually switching from conference room 1 to conference room 2 is prone to errors, and the implementation of this solution is also difficult.

The above description takes Conference Room 1 and Conference Room 2 as two independent conference systems as an example. When conference room 1 and conference room 2 belong to the same conference system, the above two solutions are equally applicable, and the above problems also exist. For example, conference room 1 and conference room 2 both belong to conference system 1. In one solution, conference client 1 is installed in conference terminal 1 and conference terminal 2 of each participant. When starting a multimedia conference, each participant A participant uses conference ID1 and conference client 1 to connect conference terminal 1 to conference room 1, and uses conference ID2 and conference client 1 to connect conference terminal 2 to conference room 2. When both conference room 1 and conference room 2 are normal, participants use conference room 1 to hold a multimedia conference. After the failure of conference room 1, the conference organizer notified all participants to switch to conference room 2 to continue the multimedia conference. However, this program requires Each participant prepares two conference terminals, which requires high implementation costs and is theoretically feasible, but difficult to implement. In another solution: each participant prepares a conference terminal, and the conference client 1 is installed in the conference terminal. When starting a multimedia conference, each participant uses conference ID 1 and conference client 1 to connect the conference terminal to conference room 1, and all participants use conference room 1 to hold a multimedia conference. After a failure occurs in conference room 1, all participants use conference ID 2 and conference client 1 to connect the conference terminal to conference room 2 to continue the multimedia conference. However, after a failure occurs in conference room 1, participants need to use the conference ID2 of conference room 2 to rejoin the conference. The operation is very troublesome, the switching process takes a long time, and the switching efficiency is low.

It can be seen that the above conference switching solution requires participants to perceive the existence of conference room 1 and conference room 2. Especially when conference room 1 and conference room 2 belong to different conference systems, participants need to perceive the existence of conference system 1 and conference system 2. Familiar with the joining methods of conference system 1 and conference system 2, and requiring participants to perform a lot of manual operations, the requirements for participants are high, and the actual operation is difficult. In addition, the above-mentioned conference switching solution requires the conference organizer and participants to cooperate in switching conferences, and the switching process is prone to errors. For situations where there are many participants, the cost of cooperation and communication between the conference organizer and participants is high, and the conference switching process is time-consuming. It is long, the switching efficiency is low, and the switching process is error-prone. For example, when a conference terminal drops the meeting (for example, disconnects from the conference system 1), but conference room 1 is not actually faulty, the participants of the conference terminal may mistakenly think that conference room 1 is faulty and switch to the conference Room 2 (switch the conference terminal or use conference ID2 to join the conference), causing the participant to perform an incorrect switching operation. For another example, after conference room 1 fails and participants have been switched to conference room 2, conference room 1 returns to normal. Newly joined participants may access conference room 1 normally, mistakenly thinking that conference room 1 is normal. And staying in conference room 1 affects the convening of multimedia conferences.

Embodiments of the present application provide a conference control method, device and communication system. The communication system includes a conference management device and a first conference terminal connected to the first conference. The conference management device is communicatively connected with the first conference terminal. After the conference management equipment determines that the first conference meets the switching conditions (for example, the first conference fails and the conference system to which the first conference belongs fails), the conference management equipment sends switching instruction information to the first conference terminal to instruct the first conference terminal to switch from The first conference is switched to the second conference, and the first conference terminal can switch from the first conference to the second conference according to the switching instruction information. Wherein, the first conference and the second conference described in this application are both conference rooms. For example, the first conference is the first conference room, the second conference is the second conference room, and the first conference terminal switches from the first conference to the second conference room. The second conference means that the first conference terminal switches from the first conference room to the second conference room. In this application, since the conference switching process is completed by the conference management equipment controlling the conference terminal, the conference switching process does not require manual participation. Therefore, the conference switching process is simple and not error-prone. The switching speed is fast and the switching efficiency is high. The conference can be completed in minutes. Switching, the switching process has little impact on the development of multimedia conferences. Participants who have already joined the conference have little awareness of the conference switching process, and newly joined participants have no awareness of the conference switching process.

In addition, in this application, the first conference and the second conference may belong to the same conference system or may belong to different conference systems. When the first conference and the second conference belong to different conference systems, for example, the first conference belongs to the first conference system and the second conference belongs to the second conference system, the first conference system and the second conference system can correspond to the same conference client. , whether it is the first conference system or the second conference system, the user plane uses the same conference client. Participants do not need to perceive the existence of the first conference system and the second conference system, and there is no need to prepare two conference systems. Terminal, participants can use a conference client to access the conference (that is, the conference room) created by any of the first conference system and the second conference system. Therefore, the user interface is unified, and the participants' The requirements are low, the actual operation is relatively simple, less error-prone, the implementation cost is low, and the implementability is strong. Moreover, in the technical solution provided by this application, when the first conference fails or the conference system to which the first conference belongs fails, the conference management device can control the first conference terminal to start the conference from the first conference. The conference is switched to the second conference. Therefore, the technical solution provided by this application can not only perform conference switching for conference system-level failures, but also can perform conference switching for conference-level failures. The implementation of the solution of this application has high flexibility and availability. It has strong popularity and is especially suitable for large-scale conferences. For enterprises that use conference systems as production systems, the technical solution provided by this application can effectively improve the reliability and ease of use of multimedia conferences and ensure that production work is not affected.

The technical solution of the present application will be introduced below with reference to the accompanying drawings. First, the application scenarios of this application are introduced.

The application scenario of the embodiment of the present application provides a communication system. The communication system includes a conference management device and a first conference terminal. The conference management device is communicatively connected to the first conference terminal. The conference management device can control the first conference terminal in the first conference terminal. Switch between the first session and the second session. Exemplarily, the communication system includes a plurality of conference terminals, the conference management device is communicatively connected to the plurality of conference terminals, and the first conference terminal may be at least one conference terminal among the plurality of conference terminals.

The first meeting and the second meeting described in this application are both meeting rooms (or multimedia meeting rooms). For example, the first meeting is the first meeting room, and the second meeting is the second meeting room. In this application, the first conference and the second conference may belong to the same conference system, or they may belong to different conference systems, and the different conference systems are independent of each other and do not affect each other. The application scenario of this application is introduced below by taking the first conference belonging to the first conference system and the second conference belonging to the second conference system as an example.

Please refer to Figure 1, which shows a schematic diagram of an application scenario provided by an embodiment of the present application. The communication system provided by this application scenario includes a conference management device 101, a first conference system 102, a second conference system 103 and multiple conference terminals (Figure 1 takes the conference terminal 104a and the conference terminal 104b as an example) . The conference management device 101 is communicatively connected to the first conference system 102, the second conference system 103, the conference terminal 104a and the conference terminal 104b respectively, and each conference terminal in the conference terminal 104a and the conference terminal 104b is connected to the first conference system 102, the second conference terminal 104b. The conference systems 103 are respectively connected by communication.

Among them, the conference management device 101 is used for the management and scheduling of multimedia conferences, the management and scheduling of conference systems, etc. In one example, the conference management device 101 can determine the availability of the conference system and the conference (that is, the conference room) of the conference system, and control the conference terminal to access the conference according to the determination result, control the conference terminal to switch between different conferences, etc. . For example, the first conference system 102 creates a first conference (that is, the first conference room), the second conference system 103 creates a second conference (that is, the second conference room), and the first conference is the main conference room. conference, the second conference is a backup conference. For example, the first conference system 102 is the main conference system so that the first conference created by the first conference system 102 is the main conference, and the second conference system 103 is the backup conference system so that the second conference system The second conference created by 103 is a backup conference. The conference management device 101 can determine the availability of the first conference and the availability of the second conference. When the conference management device 101 determines that both the first conference and the second conference are available (for example, neither the first conference nor the second conference fails), the conference The management device 101 controls both the conference terminal 104a and the conference terminal 104b to access the first conference (that is, the main conference); if the conference terminal 104a and the conference terminal 104b both access the first conference, the conference management device 101 determines the first conference If the first conference is unavailable due to a fault or other reasons, the conference management device 101 can control the conference terminal 104a and the conference terminal 104b to switch from the first conference to the second conference (that is, the backup conference).

In an optional embodiment, as shown in FIG. 1 , the communication system also includes a conference booking terminal 105 , and the conference management device 101 is also connected to the conference booking terminal 105 . The conference management device 101 is also used to request the first conference system 102 and the second conference system 103 to respectively create a conference (that is, create a conference room) when triggered by the conference reservation terminal 105 . The determination of the main conference and the backup conference, for example, the determination of the main conference system and the backup conference system, may be when the conference reservation terminal 105 requests a conference. When the conference management device 101 creates a conference, it is set by the conference subscriber (that is, the user of the conference reservation terminal), or it may be configured or set by the conference management device 101.

Among them, the first conference system 102 and the second conference system 103 are both used to hold multimedia conferences. The first conference system 102 and the second conference system 103 are both independent and complete conference systems. They are both composed of management services, control services, and media services. The first conference system 102 and the second conference system 103 can both provide multimedia conference services to conference terminals. The first conference system 102 and the second conference system 103 are independent of each other, do not interfere with each other, and do not affect each other. The failure of the first conference system 102 will not affect the second conference system 103, and the failure of the second conference system 103 will not affect the second conference system 103. A conference system 102. Optionally, both the first conference system 102 and the second conference system 103 are cloud conference systems, and the first conference system 102 and the second conference system 103 can be conference systems of different manufacturers. The deployment methods of the first conference system 102 and the second conference system 103 may include but are not limited to public cloud deployment, private cloud deployment, media sink deployment, etc. The first conference system 102 and the second conference system 103 each have their own reliability guarantee mechanism, and the first conference system 102 and the second conference system 103 can back up each other. When one of the first conference system 102 and the second conference system 103 After a conference system (for example, the first conference system 102) fails, the conference terminal can switch to another conference system (for example, the second conference system 103) to continue holding a multimedia conference.

Among them, both the conference terminal 104a and the conference terminal 104b can be used by participants to conduct multimedia conferences. Each of the conference terminals 104a and 104b may be a mobile phone, a netbook, a laptop, a tablet, a desktop computer or a vehicle-mounted host, etc. A conference client is installed in the conference terminal 104a and the conference terminal 104b respectively. The conference client is an application (App). Optionally, the conference client includes a first conference interface corresponding to the first conference system 102 and Corresponds to the second conference interface of the second conference system 103. The first conference interface is used for media, signaling, etc. interaction between the conference terminal and the first conference system 102. The second conference interface is used for media, signaling, etc. interaction between the conference terminal and the second conference system 103. Each conference terminal can access the conference created by the first conference system 102 through the first conference interface provided by the conference client installed in the conference terminal, or through the second conference interface provided by the conference client installed in the conference terminal. The conference interface accesses the conference created by the second conference system 103). Both the first conference interface and the second conference interface can be application program interfaces (APIs), and both can be implemented through software development kits (SDK). The first conference interface and the second conference interface Independent of each other, do not interfere with each other, do not affect each other.

Among them, the conference booking terminal 105 is used by the conference booker to book a conference. The conference reservation terminal 105 may be a mobile phone, a netbook, a laptop, a tablet, a desktop computer or a vehicle-mounted host, etc. In practical applications, any conference terminal can be used as a conference reservation terminal, and a conference reservation terminal is also a conference terminal. Therefore, the conference reservation terminal 105 can have all the functions of a conference terminal, and the conference terminal can also have a conference reservation function. For example, the conference terminal 104a or the conference terminal 104b in FIG. 1 may be used as a conference reservation terminal. When the conference terminal 104a or the conference terminal 104b is used as a conference reservation terminal, the communication system shown in FIG. 1 may not include the conference reservation terminal 105. In this application, for convenience of description, the conference reservation terminal 105 and the conference terminal are described differently. In an optional embodiment, the conference reservation terminal 105 sends a conference reservation request to the conference management device 101 under the trigger of the conference reservation person. The conference management device 101 can generate a target conference ID according to the conference reservation request and send it to the first conference system. 102 and the second conference system 103 reserve conferences respectively. In the process of the conference management device 101 reserving a conference with the first conference system 102, the first conference system 102 may create the first conference and generate a conference ID of the first conference. The conference ID of the first conference may be the conference number of the first conference. , the first conference system 102 may feed back the conference ID of the first conference to the conference management device 101. Book a conference with the second conference system 103 on the conference management device 101 In the process of The ID is fed back to the conference management device 101. The conference management device 101 may also generate an association relationship between the target conference ID and the conference ID of the first conference and the conference ID of the second conference (for example, called a target association relationship), and feed back the target conference ID to the conference reservation terminal 105 . The conference reservation terminal 105 may send the target conference ID to each conference terminal (for example, the conference terminal 104a and the conference terminal 104b, the connection relationship between the conference reservation terminal 105 and the conference terminal is not shown in Figure 1 for simplicity). Among them, the target conference ID is used for the conference terminal to access the first conference or the second conference. The target conference ID is a user-oriented logical conference ID. The target conference ID can be presented to the participants. When the participants access the conference, the participants can Enter the target conference ID in the conference access interface provided by the conference terminal. The conference ID of the first conference is the actual conference ID used for the conference terminal to access the first conference. The conference ID of the first conference is machine-oriented (for example, oriented to the conference terminal, the first conference system 102, and the conference management device 101). The conference ID of a conference does not need to be presented to the participants. The conference ID of the first conference is managed by the conference management device 101. The conference management device 101 determines the first conference ID according to the target conference ID input by the participants in the conference access interface provided by the conference terminal. The conference ID of the conference, and controls the conference terminal to access the first conference according to the conference ID of the first conference. The conference ID of the second conference is the actual conference ID used for the conference terminal to access the second conference. The conference ID of the second conference is machine-oriented (for example, oriented to the conference terminal, the second conference system 103, and the conference management device 101). The conference ID of the second conference does not need to be presented to the participants. The conference ID of the second conference is managed by the conference management device 101. The conference management device 101 determines the second conference ID according to the target conference ID input by the participant in the conference access interface provided by the conference terminal. The conference ID of the conference, and controls the conference terminal to access the second conference according to the conference ID of the second conference.

In an optional embodiment, the conference management device 101 also generates a conference entry password (or conference access password) based on the conference reservation request sent by the conference reservation terminal 105, and sends the conference entry password to each conference terminal. The joining password corresponds to the target conference ID, and the joining password can also correspond to both the conference ID of the first conference and the conference ID of the second conference (that is, the target conference ID, the conference ID of the first conference and the conference ID of the second conference). The three conference IDs can correspond to the same conference password), and the conference password is used for the conference terminal to access the first conference or the second conference. In some embodiments, the conference entry password may be set by the conference subscriber. For example, the conference subscriber sets the conference entry password when the conference reservation request is triggered. Among them, the conference reservation terminal 105 can trigger the conference reservation request through the conference client installed in the conference reservation terminal 105, or can trigger the conference reservation request through the conference portal (portal) provided by the conference reservation terminal 105, or can also trigger the conference reservation in other ways. ask. The meeting reservation request can also carry the meeting theme, meeting time, participant information, etc. For the situation where the conference password is set by the conference reservation person, the conference reservation request can also carry the conference password. This application does not limit this.

After the conference reservation terminal 105 sends the target conference ID, conference password and other information to each conference terminal, the participants of each conference terminal (for example, the conference terminal 104b) can use the conference access interface provided by the conference client installed in the conference terminal 104b. (or called the conference joining interface), input the target conference ID, conference joining password and other information, and trigger the conference terminal 104b to send a conference joining request to the conference management device 101. The conference joining request can carry the target conference ID, conference joining password and other information. After the conference management device 101 receives the conference joining request sent by the conference terminal 104b, the conference management device 101 determines the conference ID of the first conference and the second conference ID according to the target conference ID carried in the conference joining request and the target association relationship maintained by the conference management device 101. The conference ID of the conference, and determines the availability of the first conference and the second conference. If the conference management device 101 determines that the first conference (that is, the active conference) is available, the conference management device 101 sends the conference ID of the first conference to the conference terminal 104b, and the conference terminal 104b calls the conference terminal 104b according to the conference ID of the first conference. The first conference interface provided by the installed conference client accesses the first conference and performs media stream interaction with the first conference system 102 . If the conference management device 101 determines The first conference is unavailable and the second conference (that is, the backup conference) is available. The conference management device 101 sends the conference ID of the second conference to the conference terminal 104b. The conference terminal 104b calls the conference terminal 104b based on the conference ID of the second conference. The second conference interface provided by the conference client accesses the second conference and performs media stream interaction with the second conference system 103.

After the conference terminal 104b accesses the first conference, if the conference management device 101 determines that the first conference meets the switching conditions, for example, the first conference fails, or the conference system to which the first conference belongs (that is, the first conference system 102) fails. , the conference management device 101 may determine the conference ID of the second conference based on the conference ID of the first conference and the target association relationship, and send switching instruction information including the conference ID of the second conference to the conference terminal 104b. The conference terminal 104b can, based on the switching instruction information, call the second conference interface provided by the conference client installed in the conference terminal 104b to access the second conference, and perform media stream interaction with the second conference system 103, thereby realizing the conference terminal 104b Switching from the first conference to the second conference, that is, switching the conference terminal 104b from the first conference system 102 to the second conference system 103 is implemented. It can be seen that in this application, the conference management device 101 controls the conference terminal to perform conference switching. The switching process does not require manual participation, and does not require the cooperation of the conference organizer and participants. The switching process is simple and not prone to errors. The switching speed is fast and the switching efficiency is high. Conference switching can be completed at the minute level. Participants who have already joined the conference have little awareness of the switching process, while newly joined participants have no awareness of the switching process.

In addition, in this application, one conference client includes a first conference interface corresponding to the first conference system 102 and a second conference interface corresponding to the second conference system 103, so that the one conference client corresponds to the first conference system 102 and With the second conference system 103 and the two conference systems, participants do not need to perceive the existence of the first conference system 102 and the second conference system 103, and do not need to prepare two conference terminals. Participants use one conference terminal, one conference client, and one conference terminal. The conference identification (such as the target conference identification) can be connected to the conference created by any of the first conference system and the second conference system. Therefore, in the technical solution of this application, the user interface is unified and the requirements for the participants are It is lower, the implementation cost is lower, and the implementability is stronger.

Those skilled in the art should understand that the application scenario shown in Figure 1 is only used as an example and is not used to limit the technical solution of the present application. In the actual implementation process, the number of conference terminals and the equipment included in the application scenario can be configured as needed.

The above is an introduction to the application scenarios of this application, and the method embodiments of this application are introduced below.

Please refer to Figure 2, which shows a flow chart of a conference control method provided by an embodiment of the present application. The conference control method can be applied to a communication system including a conference management device and a first conference terminal, for example, to the application scenario shown in Figure 1 . As shown in Figure 2, the conference control method includes the following steps S201 to S204.

S201. The conference management device determines that the first conference meets the switching conditions.

In this embodiment of the present application, the switching condition may include one or more of the following: the first conference is unavailable, and the conference system (for example, the first conference system) to which the first conference belongs is unavailable. Wherein, the first conference is unavailable, for example, the first conference is unavailable due to a failure of the first conference, or the first conference is manually set to be unavailable, etc. The first conference system is unavailable, for example, the first conference system fails, causing the first conference to be unavailable, or the first conference system is manually set to be unavailable, etc. That is, the switching condition may include one or more of the following: the first conference fails, and the conference system to which the first conference belongs fails.

In the embodiment of this application, the failure of the first conference may include but is not limited to: the number of conference terminals that are disconnected among the multiple conference terminals accessing the first conference is greater than the preset number, and the number of conference terminals that are disconnected from the first conference is greater than the preset number. The proportion of conference terminals that are disconnected among the terminals among the plurality of conference terminals is greater than the preset proportion, the number of times that at least one conference terminal connected to the first conference is disconnected is greater than the preset number of times, the conference resources of the first conference ( For example, the conference number, conference room) is invalid or unavailable, the conference instance corresponding to the first conference in the conference system to which the first conference belongs fails, etc. Failure of the first conference system can include But it is not limited to: the number of failed meetings among the multiple meetings held simultaneously by the first conference system is greater than the target number, and the proportion of failed meetings among the multiple meetings held simultaneously by the first conference system is greater than The target ratio is that a network failure occurs in the first conference system (for example, the network is disconnected), a heartbeat abnormality occurs in the first conference system, etc.

In an optional embodiment, the switching condition includes that the conference system to which the first conference belongs (that is, the first conference system) is unavailable. After the first conference terminal accesses the first conference, the conference management device performs real-time or periodic monitoring of the first conference terminal. A conference system performs availability judgment, and determines whether the first conference meets the switching condition based on the judgment result. When the conference management device determines that the first conference system is unavailable, the conference management device determines that the first conference meets the switching condition. When the conference management device determines that the first conference system is available, the conference management device determines that the first conference does not meet the switching condition. As an example, the conference management device performs fault detection on the first conference system in real time or periodically; if the conference management device determines that the first conference system fails, the conference management device determines that the first conference system is unavailable; if the conference management device determines that the first conference system is unavailable; If the first conference system fails, the conference management device determines that the first conference system is available. For example, when the first conference system does not malfunction (that is, when the first conference system is in a normal state), the first conference system regularly sends a heartbeat signal to the conference management device, and the conference management device can send a heartbeat signal according to the signal sent by the first conference system. The heartbeat signal determines whether a heartbeat abnormality occurs in the first conference system, and further determines whether the first conference system fails. For example, if the conference management device determines that the first conference system has a heartbeat abnormality, the conference management device determines that the first conference system has failed; if the conference management device determines that the first conference system does not have a heartbeat abnormality, the conference management device determines that the first conference system does not have a heartbeat abnormality. No failure occurred. Among them, abnormal heartbeat occurs in the first conference system, for example, but is not limited to: heartbeat loss occurs in the first conference system (also known as heartbeat arrest, that is, the first conference system stops sending heartbeat signals to the conference management device), heartbeat disorder (such as heartbeat cessation, etc.). Cycle increases, decreases, heartbeat cycles are not equal), etc.

In another optional embodiment, the switching condition includes that the first conference is unavailable. After the first conference terminal accesses the first conference, the conference management device judges the availability of the first conference in real time or periodically, and determines the availability based on the judgment result. Whether the first meeting meets the switching conditions. When the conference management device determines that the first conference is unavailable, the conference management device determines that the first conference satisfies the switching condition. When the conference management device determines that the first conference is available, the conference management device determines that the first conference does not satisfy the switching condition. For example, the conference management device performs fault detection on the first conference in real time or periodically; if the conference management device determines that the first conference is faulty, the conference management device determines that the first conference is unavailable; if the conference management device determines that the first conference is not available, If a failure occurs, the conference management device determines that the first conference is available. For example, the conference management device detects in real time or periodically whether the proportion of disconnected conference terminals among the multiple conference terminals connected to the first conference is greater than the preset ratio; if multiple conference terminals connected to the first conference The proportion of the conference terminals that are offline among the conference terminals is greater than the preset proportion, and the conference management equipment determines that the first conference is faulty; if the conference terminals that are disconnected among the conference terminals connected to the first conference are The proportion of terminals in the plurality of conference terminals is not greater than the preset proportion, and the conference management device determines that the first conference is faulty.

S202. The conference management device sends switching instruction information to the first conference terminal that accesses the first conference. The switching instruction information is used to instruct the first conference terminal to switch from the first conference to the second conference.

After the conference management device determines that the first conference meets the switching conditions, the conference management device can control the first conference terminal accessing the first conference to switch from the first conference to the second conference to ensure that the first conference terminal can normally hold a multimedia conference. The first conference terminals described here include all conference terminals that have accessed the first conference when the first conference meets the switching condition. It can be understood that the number of first conference terminals may be one or more.

The first conference and the second conference may belong to the same conference system or different conference systems. One of the first conference and the second conference is the main conference, and the other is the backup conference. For example, the first conference belongs to the first conference system, The second conference belongs to the second conference system. The first conference system is the main conference system so that the first conference of the first conference system is the main conference. The second conference system is the backup conference system so that the second conference of the second conference system is the backup. Meeting.

In this embodiment of the present application, the conference management device may send switching instruction information to the first conference terminal. The switching instruction information is used to instruct the first conference terminal to switch from the first conference to the second conference. The conference management device uses the switching instruction information to Control the first conference terminal to switch from the first conference to the second conference. The switching instruction information may include the conference ID of the second conference, the conference password and other related information. When the first conference and the second conference belong to different conference systems, and the second conference belongs to the second conference system, the switching instruction information also The identifier of the second conference system may be included. The identifier of the second conference system is used to indicate or identify the second conference system. The conference ID of the second conference is used to indicate or identify the second conference. The second conference ID may be the conference number of the second conference generated when the second conference system creates the second conference. The conference joining password is used for the conference terminal to access the second conference. The conference joining password can be set by the conference booker (that is, the user of the conference booking terminal) when the conference booking terminal reserves a meeting with the conference management equipment, or it can be set by the conference management equipment. Or generated by the second conference system.

In an optional embodiment, the switching instruction information includes the conference identifier of the second conference. Before the conference management device sends the switching instruction information to the first conference terminal, the conference management device may determine the conference identifier of the second conference. For example, the conference management device first determines the conference ID of the first conference accessed by the first conference terminal, and then determines the conference ID of the second conference based on the target association relationship and the conference ID of the first conference. The target association relationship includes the association relationship between the conference ID of the first conference and the conference ID of the second conference. For example, the target association relationship is the association relationship between the target conference ID and the conference ID of the first conference and the conference ID of the second conference. , the conference ID of the first conference and the conference ID of the second conference are associated through the target conference ID in the association relationship. In the embodiment of this application, the target conference identifier is a logical conference identifier used for the conference terminal to access the first conference or the second conference. The target conference identifier can be generated by the conference management device. The target conference identifier is user-oriented. The target conference identifier It can be presented to participants. When participants join the conference, participants can enter the target conference ID in the conference access interface provided by the participant's conference terminal. The conference ID of the first conference is the actual conference ID used for the conference terminal to access the first conference. The conference ID of the first conference is used to indicate the first conference. The conference ID of the first conference may be the conference system to which the first conference belongs ( For example, the first conference system) generates the conference number of the first conference when creating the first conference. For example, the conference ID of the first conference is "12345678", and the conference ID "12345678" of the first conference can be used to indicate the first conference. . The conference ID of the second conference is the actual conference ID used for the conference terminal to access the second conference. The conference ID of the second conference is used to indicate the second conference. The conference ID of the second conference can be the conference system to which the second conference belongs ( For example, the second conference system) generates the conference number of the second conference when creating the second conference. For example, the conference ID of the second conference is "87654321", and the conference ID "87654321" of the second conference can be used to indicate the second conference. . The conference logo of the first conference and the conference logo of the second conference are both machine-oriented (such as conference terminals, conference systems, conference management equipment). Neither the conference logo of the first conference nor the conference logo of the second conference need to be presented to the participants. , the conference management device determines the conference identifier of the first conference or the conference identifier of the second conference according to the target conference identifier input by the participant in the conference access interface provided by the conference terminal, and controls the conference terminal according to the conference identifier of the first conference Access the first conference, or control the conference terminal to access the second conference according to the conference ID of the second conference.

For example, the target association relationship is the association relationship between the target conference identifier and the conference identifier of the first conference and the conference identifier of the second conference. The target association relationship may be as shown in Table 1 or Table 2 below.

Table 1

Table 2

The target association relationships shown in Table 1 and Table 2 can be generated and maintained by the conference management device. Exemplarily, before the conference management device sends the switching instruction information to the first conference terminal, the conference management device determines that the conference ID of the first conference accessed by the first conference terminal is "12345678", and the conference management device determines the conference ID of the first conference according to the conference ID of the first conference. The identifier "12345678" and the target association shown in Table 1 or Table 2 determine that the conference identifier of the second conference is "87654321".

After the conference management device determines the conference ID of the second conference, the conference management device can also determine the conference password, the ID of the conference system (for example, the second conference system) to which the second conference belongs, and other related information based on the conference ID of the second conference. For example, the conference password corresponds to the target conference identifier. After the conference management device determines the conference identifier of the second conference, the conference management device determines the target conference identifier based on the conference identifier of the second conference and the target association relationship shown in Table 1 or Table 2, and then Determine the conference password based on the target conference ID.

S203. The first conference terminal receives the switching instruction information sent by the conference management device.

Corresponding to the conference management device sending switching instruction information to the first conference terminal, the first conference terminal may receive the switching instruction information sent by the conference management device.

S204. The first conference terminal switches from the first conference to the second conference according to the switching instruction information.

After the first conference terminal receives the switching instruction information sent by the conference management device, the first conference terminal switches from the first conference to the second conference according to the switching instruction information. After the first conference terminal switches from the first conference to the second conference, media stream interaction is performed between the first conference terminal and the conference system (for example, the second conference system) to which the second conference belongs, so that different conferences of the second conference can be accessed. The terminal performs media stream interaction through the second conference system.

In an optional embodiment, the first conference belongs to the first conference system, and the second conference belongs to the second conference system. A conference client may be installed in the first conference terminal, and the conference client may include a conference client corresponding to the first conference system. A first conference interface and a second conference interface corresponding to the second conference system, the first conference interface is used for the conference terminal to interact with the first conference system, and the second conference interface is used for the conference terminal to interact with the second conference system. The first conference terminal may, according to the switching instruction information, call the second conference interface included in the conference client installed in the first conference terminal to access the second conference.

In an optional embodiment, the switching instruction information includes the identifier of the second conference system, the conference identifier of the second conference, and the conference password. The first conference terminal first determines the second conference system according to the identifier of the second conference system, and then determines the second conference system according to the second conference system identifier. The conference ID and conference password of the second conference are used to call the second conference interface to access the second conference of the second conference system. Exemplarily, the first conference terminal calls the second conference interface to send an access request to the second conference system. The access request carries the conference ID and conference password of the second conference. Use the conference ID and membership password of the second conference to access the second conference and send an access response to the first conference terminal. The access response may be an access success message to indicate that the first conference terminal has successfully connected. Enter the second meeting. If the first conference terminal fails to access the second conference successfully, the access response may be an access failure message to indicate that the first conference terminal fails to access.

Since in this embodiment of the present application, the conference client installed in the first conference terminal includes a first conference interface corresponding to the first conference system and a second conference interface corresponding to the second conference system, therefore, the first conference terminal can Through the conference client to access a conference created by any one of the first conference system and the second conference system, the first conference terminal Participants do not need to be aware of the existence of the first conference system and the second conference system. That is to say, one conference client can provide conference interfaces corresponding to at least two conference systems, and participants can access the conference created by any one of the at least two conference systems through the one conference client, and participate in the conference. Users do not need to be aware of the existence of at least two conference systems. Therefore, the requirements for participants are low, the actual operation is relatively simple, and it is not easy to make mistakes.

To sum up, according to the conference control method provided by the embodiment of the present application, when the conference management device determines that the first conference meets the switching conditions, the conference management device sends switching instruction information to the first conference terminal that accesses the first conference, and the first conference terminal Switch from the first conference to the second conference according to the switching instruction information. Since the conference switching process is completed by the conference management equipment controlling the conference terminal, the conference switching process does not require manual participation. Therefore, the conference switching process is simple and not prone to errors. The switching speed is fast and the switching efficiency is high. Conference switching can be completed at the minute level. The conference switching process It has little impact on the development of multimedia conferences. Participants who have already joined the conference have less awareness of the switching process, and newly joined participants have no awareness of the conference switching process.

In addition, the first conference may belong to the first conference system, and the second conference may belong to the second conference system. This embodiment of the present application uses two conference systems, the first conference system and the second conference system, to ensure the reliability of the multimedia conference. Moreover, the first conference system and the second conference system correspond to one conference client. Regardless of the first conference system or the second conference system, the user interface uses the same conference client, and participants do not need to be aware of the existence of two conference systems. , there is no need to prepare two conference terminals. Participants can use one conference client and one conference ID (that is, the target conference ID) to access the conference created by any conference system in the first conference system and the second conference system, so , the user interface is unified, the requirements for participants are lower, the actual operation is relatively simple, not prone to errors, the implementation cost is low, and the implementability is strong.

The technical solution of the embodiment of the present application can not only perform conference switching for conference system-level failures, but also perform conference switching for conference-level failures. This technical solution has high flexibility, strong usability and popularity, and is especially suitable for large-scale applications. For enterprises that use conference systems as their production systems, the technical solution of this application can effectively improve the reliability and ease of use of multimedia conferences and ensure that production work is not affected.

In this embodiment of the present application, before the conference management device controls the first conference terminal to switch from the first conference to the second conference, the conference management device may control the first conference terminal to access the first conference. For example, the conference management device sends the first access instruction information to the first conference terminal, and the first conference terminal can receive the first access instruction information and access the first conference according to the first access instruction information. The conference management device may actively send the first access instruction information to the first conference terminal, or may send the first access instruction information to the first conference terminal at the request of the first conference terminal. The following description takes the conference management device sending the first access instruction information to the first conference terminal at the request of the first conference terminal as an example.

Please refer to Figure 3, which shows a flow chart of another conference control method provided by an embodiment of the present application. The conference control method can be applied to a communication system including a conference management device and a first conference terminal, for example, to the application scenario shown in Figure 1 . Figure 3 mainly introduces the implementation process of the first conference terminal accessing the first conference. As shown in Figure 3, the conference control method includes the following steps S301 to S306.

S301. The first conference terminal sends a first conference joining request to the conference management device. The first conference joining request carries a target conference identifier. The target conference identifier is used by the first conference terminal to access the first conference or the second conference.

In this embodiment of the present application, a conference client is installed in the first conference terminal. The conference client can provide a conference access interface. Participants in the first conference terminal can operate in the conference access interface to trigger the second conference access interface. A conference terminal sends a first conference joining request to the conference management device. The first conference joining request carries the target conference ID and can also carry the conference joining password, etc.

As an example, the conference access interface is shown in Figure 4. The conference access interface displays a conference number input box 411, The conference password input box 412 and the join conference button 413, the conference number input box 411 is used for participants to input the conference number (that is, the conference ID), and the conference password input box 412 is used for participants to input the conference password. Participants of the first conference terminal can enter the target conference ID in the conference number input box 411, enter the conference password in the conference password input box 412, and then click the join conference button 413 to trigger the first conference terminal to send the first conference entry to the conference management device. ask.

It should be noted that the conference access interface shown in Figure 4 is only used as an example and is not used to limit the technical solution of this application. In the actual implementation process, the content displayed in the conference access interface can be flexibly set. For example, in addition to the content shown in Figure 4, the conference access interface can also display a voice switch button, a camera switch button, a cancel button, etc. The voice switch button is used by participants to choose whether to turn on voice, the camera switch button is used by participants to choose whether to turn on the camera, and the cancel button is used by participants to cancel joining the conference. For another example, the join conference button 413 in the conference access interface shown in FIG. 4 can also be replaced by an OK button, a confirmation button, a join button and other similar buttons or controls. For another example, for some multimedia conferences that do not require a password, the conference password input box 412 may not be displayed in the conference access interface. In addition, the conference access interface can also be other interfaces that can be used for participants to interact with conference terminals to trigger conference joining requests. Any interface that can be used for participants to interact with conference terminals to trigger conference joining requests belongs to the conference of this application. Protection scope of access interface.

S302. The conference management device receives the first conference joining request sent by the first conference terminal.

Corresponding to the first conference terminal sending the first conference joining request to the conference management device, the conference management device may receive the first conference joining request sent by the first conference terminal.

S303. The conference management device determines the conference identifier of the first conference system based on the target association relationship and the target conference identifier carried in the first conference joining request. The target association relationship includes the association relationship between the target conference identifier and the conference identifier of the first conference.

In this embodiment of the present application, the target conference ID is a logical conference ID used for the conference terminal to access the first conference or the second conference, and is not an actual conference ID used for the conference terminal to access the first conference or the second conference. Therefore, , after the conference management device receives the first conference joining request sent by the first conference terminal, the conference management device determines that the first conference terminal needs to access the first conference or the second conference according to the target conference identifier carried in the first conference joining request. Then, the conference The management device is based on the operation status of the first conference and the operation status of the second conference, for example, based on the operation status of the conference system to which the first conference belongs (for example, the first conference system) and the conference system to which the second conference belongs (for example, the second conference system). system), selects a conference (that is, selects a conference room) for the first conference terminal, and determines the actual conference identifier used for the conference terminal to access the selected conference.

In an optional embodiment, the conference management device first determines the availability of the first conference and the availability of the second conference. The conference management device determines the availability of the first conference and the availability of the second conference based on the determination results of the first conference and the second conference. Select the conference on the terminal. For example, the first conference is the main conference and the second conference is the backup conference; if the conference management device determines that the first conference is available, the conference management device selects the first conference for the first conference terminal; if the conference management device determines that the first conference is not available and the second conference is available, the conference management device selects the second conference for the first conference terminal. The implementation process of the conference management device judging the availability of the first conference and the availability of the second conference may refer to the relevant description in S201. In the embodiment of this application, the first conference is available as an example, and the conference management device selects the first conference for the first conference terminal.

After the conference management device selects the first conference for the first conference terminal, the conference management device may determine the actual conference identification used for the conference terminal to access the first conference. Exemplarily, the conference management device determines the conference ID of the first conference based on the target association relationship and the target conference ID carried in the first conference joining request. The conference ID of the first conference is the actual conference ID used for the conference terminal to access the first conference. . The target association relationship includes an association relationship between the target conference identifier and the conference identifier of the first conference. For example, the target association relationship is an association relationship between the target conference identifier and the conference identifier of the first conference and the conference identifier of the second conference. For example, the target association relationship is as shown in Table 1 or Table 2 above. Assume that the first membership request carries the target The standard conference ID is "43218765". The conference management device determines that the conference ID of the first conference is "12345678" based on the target association relationship shown in Table 1 or Table 2 and the target conference ID "43218765" carried in the first conference joining request.

S304. The conference management device sends first access instruction information to the first conference terminal, where the first access instruction information includes the conference identification of the first conference.

In an optional embodiment, the conference management device sends a first joining response corresponding to the first joining request to the first conference terminal, where the first joining response carries the first access indication information. The first access instruction information includes a conference identifier of the first conference, and the first access instruction information may also include an identifier of the first conference system, a conference password, and other related information.

S305. The first conference terminal receives the first access instruction information sent by the conference management device.

Corresponding to the conference management device sending the first access instruction information to the first conference terminal, the first conference terminal may receive the first access instruction information sent by the conference management device. In an optional embodiment, the first conference terminal receives a first conference joining response sent by the conference management device, and the first conference joining response carries first access indication information.

S306. The first conference terminal accesses the first conference according to the first access instruction information.

After the first conference terminal receives the first access instruction information sent by the conference management device, the first conference terminal accesses the first conference according to the first access instruction information. After the first conference terminal accesses the first conference, media stream interaction is performed between the first conference terminal and the conference system (for example, the first conference system) to which the first conference belongs. Different conference terminals that access the first conference communicate through the first conference The system performs media streaming interactions.

In this embodiment of the present application, a conference client may be installed in the first conference terminal. The conference client may include a first conference interface corresponding to the first conference system and a second conference interface corresponding to the second conference system. A conference interface is used for the conference terminal to interact with the first conference system, and a second conference interface is used for the conference terminal to interact with the second conference system. The first conference terminal may, according to the first access instruction information, call the first conference interface included in the conference client installed in the first conference terminal to access the first conference. In an optional embodiment, the first access indication information includes the identifier of the first conference system, the conference identifier of the first conference, and the conference password. The first conference terminal first determines the first conference system according to the identifier of the first conference system, and then According to the conference ID and conference password of the first conference, the first conference interface is called to access the first conference created by the first conference system. Exemplarily, the first conference terminal calls the first conference interface to send an access request to the first conference system. The access request carries the conference ID and membership password of the first conference. Using the conference ID and joining password of a conference, the first conference terminal is connected to the first conference, and an access response is sent to the first conference terminal. The access response may be an access success message to indicate that the first conference terminal has successfully connected. Enter the first meeting. If the first conference terminal fails to access the first conference successfully, the access response may be an access failure message to indicate that the first conference terminal fails to access.

To sum up, according to the conference control method provided by the embodiments of the present application, after the conference management device receives the first conference joining request sent by the first conference terminal, the conference management device determines the target conference ID according to the target association relationship and the first conference joining request. The conference identifier of the first conference is sent to the first conference terminal, and the first access instruction information including the conference identifier of the first conference is sent to the first conference terminal. The first conference terminal accesses the first conference according to the first access instruction information. Since the first conference system and the second conference system correspond to the same conference client, the conference terminal can access the first conference system and the second conference system through the one conference client and one conference ID (ie, the target conference ID). For meetings created by any conference system in the conference system, participants do not need to be aware of the existence of the first conference system and the second conference system, and there is no need to prepare two conference terminals. The requirements for participants are low and it is difficult to operate in practice. It is simpler, less error-prone and has lower implementation cost.

In this embodiment of the present application, after the first conference terminal switches from the first conference to the second conference, the conference management device may To control subsequent conference terminals to access the second conference. For example, after the conference management device controls the first conference terminal to switch from the first conference to the second conference through the switching instruction information, the conference management device sends the second access instruction information to the second conference terminal based on the switching instruction information, and the second conference The terminal may receive the second access instruction information and access the second conference according to the second access instruction information. The conference management device may actively send the second access instruction information to the second conference terminal, or may send the second access instruction information to the second conference terminal at the request of the second conference terminal. The following description takes the conference management device sending the second access instruction information to the second conference terminal at the request of the second conference terminal as an example.

Please refer to FIG. 5 , which shows a flow chart of yet another conference control method provided by an embodiment of the present application. The conference control method can be applied to a communication system including a conference management device, a first conference terminal and a second conference terminal, for example, to the application scenario shown in Figure 1 . Figure 5 mainly introduces the implementation process of the second conference terminal accessing the second conference. As shown in Figure 5, the conference control method includes the following steps S501 to S506.

S501. The second conference terminal sends a second conference joining request to the conference management device. The second conference joining request carries a target conference identifier. The target conference identifier is used by the second conference terminal to access the first conference or the second conference.

S502. The conference management device receives the second conference joining request sent by the second conference terminal.

The implementation process of S501 to S502 can refer to the implementation process of S301 to S302, which will not be described again here.

S503. The conference management device determines the conference identifier of the second conference based on the target association relationship and the target conference identifier carried in the second conference joining request. The target association relationship includes the association relationship between the target conference identifier and the conference identifier of the second conference.

The implementation process of S503 can refer to the implementation process of S303, and will not be described in detail here. It should be noted that in S503, the conference management device determines that the first conference is unavailable and the second conference is available. The conference management device selects the second conference for the second conference terminal and selects the second conference according to the target association relationship and the target carried in the second conference joining request. The conference ID determines the conference ID of the second conference.

S504. The conference management device sends second access instruction information to the second conference terminal, where the second access instruction information includes the conference identification of the second conference.

S505. The second conference terminal receives the second access instruction information sent by the conference management device.

S506. The first conference terminal accesses the second conference according to the second access instruction information.

For the implementation process of S504 to S506, please refer to the implementation process of S304 to S306, which will not be described again here. It should be noted that, in S506, the second conference terminal may call the second conference interface included in the conference client installed in the second conference terminal to access the second conference according to the second access instruction information.

To sum up, according to the conference control method provided by the embodiment of the present application, after the first conference terminal switches from the first conference to the second conference, if the conference management device receives the second conference joining request sent by the second conference terminal, the conference management The device determines the conference ID of the second conference based on the target association relationship and the target conference ID carried in the second conference joining request, and sends the second access instruction information including the conference ID of the second conference to the second conference terminal. The second conference terminal The second access instruction information accesses the second conference, thus ensuring that the second conference terminal and the first conference terminal access the same conference. Since the first conference system and the second conference system correspond to the same conference client, the conference terminal can access the first conference system and the second conference system through the one conference client and one conference ID (ie, the target conference ID). For meetings created by any conference system in the conference system, participants do not need to be aware of the existence of the first conference system and the second conference system, and there is no need to prepare two conference terminals. The requirements for participants are low and it is difficult to operate in practice. It is simpler, less error-prone and has lower implementation cost.

Before convening a multimedia conference, the conference reservation terminal and the conference management device can cooperate to reserve the first conference and the second conference to the conference system to generate the above-mentioned target conference identification, the conference identification of the first conference, the conference identification of the second conference, and The target association relationship allows the conference terminal to access the first conference or the second conference based on this information. The conference reservation terminal may be the aforementioned first conference terminal or the second conference terminal, or may be other conference terminals besides the first conference terminal and the second conference terminal, or may be a terminal dedicated to conference reservation. The application examples do not limit this.

As mentioned above, the first conference and the second conference may belong to the same conference system or different conference systems. If the first conference and the second conference belong to the same conference system, the conference reservation terminal and the conference management device can cooperate to reserve the first conference and the second conference to one conference system. If the first conference and the second conference belong to different conference systems, for example, the first conference belongs to the first conference system and the second conference belongs to the second conference system, the conference reservation terminal and the conference management device can cooperate to reserve the first conference system with the first conference system. conference, and book the second conference with the second conference system. The following takes the first meeting belonging to the first conference system and the second meeting belonging to the second conference system as an example to introduce the implementation process of scheduled meetings.

Please refer to FIG. 6 , which shows a flow chart of yet another conference control method provided by an embodiment of the present application. This conference control method can be applied to the application scenario shown in Figure 1. Figure 6 mainly introduces the implementation process of the conference booking terminal and the conference management equipment cooperating with the conference booking. As shown in Figure 6, the conference control method includes the following steps S601 to S617.

S601. The conference reservation terminal sends a conference reservation request to the conference management device.

In this embodiment of the present application, a conference client can be installed in the conference booking terminal. The conference client can provide a conference booking interface, and the conference booker (that is, the user of the conference booking terminal) can operate in the conference booking interface. to trigger the conference reservation terminal to send a conference reservation request to the conference management device. Among them, the meeting reservation request can carry the meeting topic, meeting time, meeting password, participant information, etc. The meeting time can include the meeting start time and meeting duration.

As an example, the conference reservation interface is shown in Figure 7. The conference access interface displays a conference theme input box 711, a start time input box 712, a conference duration input box 713, a conference password input box 714, and invitees ( That is, participants) input box 715, OK button 716 and Cancel button 717. The conference subject input box 711 is used by the conference subscriber to input the conference subject. The start time input box 712 is used by the conference scheduler to input the conference start time. The conference duration input box 713 is used by the conference subscriber to input the conference duration. The conference password input box 714 is used by the conference subscriber to input the conference password. The invitee input box 715 is used by the meeting scheduler to input the invitee's information, such as inputting the invitee's email address. The conference subscriber can set the conference theme in the conference theme input box 711, set the meeting start time in the start time input box 712, set the meeting duration in the conference duration input box 713, set the conference password in the conference password input box 714, and set the conference password in the conference password input box 714. After adding the invitee's information in the invitee input box 715, the conference booker can click the OK button 716 to trigger the conference booking terminal to send a conference booking request to the conference management device. Optionally, if the conference booker enters the above information and then abandons the scheduled meeting, the conference booker can also click the cancel button 717 to cancel the conference booking process, which is not limited in the embodiment of the present application.

It should be noted that the conference reservation interface shown in Figure 7 is only used as an example and is not used to limit the technical solution of this application. In the actual implementation process, the content displayed in the conference reservation interface can be flexibly set. For example, the OK button 716 in the meeting reservation interface shown in FIG. 7 can also be replaced by a save button, an add button, or other similar buttons or controls. For another example, in addition to the content shown in Figure 7, the conference reservation interface can also display content such as time zone selection controls, reminder time input boxes, camera switch buttons, password switch buttons, primary and backup conference system settings (or selection) controls, etc. The time zone selection control is used by the meeting booker to set the time zone. The reminder time input box is used by the meeting scheduler to set the meeting reminder time. The camera switch button is used by the conference booker to set whether to turn on the camera. The password switch button is used by the conference booker to determine whether to set a conference password. When the password switch button is turned on, the conference password input box 714 may be displayed in the conference reservation interface. When the password switch button is turned off, the conference password input box may not be displayed in the conference reservation interface. Block 714. In some examples, when the password switch button is turned on, the conference password input box 714 may not be displayed in the conference reservation interface. The conference management device or conference system may Wait to set the membership password. The main and backup conference system setting (or selection) control is used by the conference booker to set or select the main and backup conference systems. In addition, the meeting reservation interface may also be other interfaces that can be used by the meeting booker to interact with the meeting reservation terminal to trigger a meeting reservation request. The content of the meeting reservation interface may be displayed in multiple pages in pages. Any interface that can be used by the meeting booker to interact with the meeting booking terminal to trigger the meeting booking request falls within the protection scope of this application.

S602. The conference management device receives the conference reservation request sent by the conference reservation terminal.

Corresponding to the conference reservation terminal sending a conference reservation request to the conference management device, the conference management device may receive the conference reservation request sent by the conference reservation terminal.

S603. The conference management device generates a target conference ID according to the conference reservation request.

The conference management device determines that the conference reservation terminal needs to book a conference based on the conference reservation request sent by the conference reservation terminal. After that, the conference management device generates a logical target conference identification. For example, the target conference ID is "43218765".

S604. The conference management device sends a first conference creation request to the first conference system according to the conference reservation request.

After the conference management device determines that the conference reservation terminal needs to book a conference, the conference management device sends a first conference creation request to the first conference system according to the conference reservation request to request the first conference system to create a conference. Among them, the first conference creation request can carry the target conference ID, conference password, conference topic, conference time, participant information, etc.

In an optional embodiment, the conference management device includes a first communication interface corresponding to the first conference system, and the conference management device sends the first conference creation request to the first conference system through the first communication interface. The first communication interface may be a physical interface or an interface function, which is not limited in the embodiments of the present application.

S605. The first conference system receives the first conference creation request sent by the conference management device.

Corresponding to the conference management device sending the first conference creation request to the first conference system, the first conference system may receive the first conference creation request sent by the conference management device.

S606. The first conference system generates a conference ID of the first conference according to the first conference creation request.

After the first conference system receives the first conference creation request, the first conference system creates the first conference according to the first conference creation request and generates a conference ID of the first conference. For example, the conference ID of the first conference is "12345678".

The meeting information of the first meeting may include: the meeting ID of the first meeting, the target meeting ID carried in the first meeting creation request, the joining password, the meeting theme, the meeting time, the joining password, the participant's information, etc.

S607. The first conference system sends a first conference creation response to the conference management device, where the first conference creation response carries the conference identification of the first conference.

After the first conference system creates the first conference, the first conference system sends a first conference creation response to the conference management device. The first conference creation response may carry the conference identification of the first conference to indicate that the first conference system has successfully created the first conference. Meeting.

S608. The conference management device receives the first conference creation response sent by the first conference system.

Corresponding to the first conference system sending the first conference creation response to the conference management device, the conference management device may receive the first conference creation response sent by the first conference system. Optionally, the conference management device includes a first communication interface corresponding to the first conference system, and the conference management device receives the first conference creation response sent by the first conference system through the first communication interface.

After the conference management device receives the first conference creation response sent by the first conference system, the conference management device determines that the first conference system has successfully created the first conference according to the conference ID of the first conference carried in the first conference creation response.

S609. The conference management device sends a second conference creation request to the second conference system according to the conference reservation request.

After the conference management device determines that the conference reservation terminal needs to book a conference, the conference management device sends a second conference creation request to the second conference system according to the conference reservation request to request the second conference system to create a conference. Among them, the second meeting created The creation request can carry the target conference ID, conference password, conference topic, conference time, participant information, etc.

In an optional embodiment, the conference management device includes a second communication interface corresponding to the second conference system, and the conference management device sends the second conference creation request to the second conference system through the second communication interface. The second communication interface may be a physical interface or an interface function, which is not limited in the embodiments of the present application.

S610. The second conference system receives the second conference creation request sent by the conference management device.

Corresponding to the conference management device sending a second conference creation request to the second conference system, the second conference system may receive the second conference creation request sent by the conference management device.

S611. The second conference system generates a conference ID of the second conference according to the second conference creation request.

After the second conference system receives the second conference creation request, the second conference system creates the second conference according to the second conference creation request and generates an identifier of the second conference. For example, the conference ID of the second conference is "87654321".

The conference information of the second conference may include: the conference ID of the second conference and the target conference ID carried in the second conference creation request, conference password, conference theme, conference time, conference password, participant information, etc.

S612. The second conference system sends a second conference creation response to the conference management device, and the second conference creation response carries the conference ID of the second conference.

After the second conference system creates the second conference, the second conference system sends a second conference creation response to the conference management device. The second conference creation response may carry the conference ID of the second conference to indicate that the second conference system has successfully created the second conference. Meeting.

S613. The conference management device receives the second conference creation response sent by the second conference system.

Corresponding to the second conference system sending a second conference creation response to the conference management device, the conference management device may receive the second conference creation response sent by the second conference system. Optionally, the conference management device includes a second communication interface corresponding to the second conference system, and the conference management device receives the second conference creation response sent by the second conference system through the second communication interface.

After the conference management device receives the second conference creation response sent by the second conference system, the conference management device determines that the second conference system has successfully created the second conference according to the conference ID of the second conference carried in the second conference creation response.

S614. The conference management device generates a target association relationship. The target association relationship is an association relationship between the target conference identifier, the conference identifier of the first conference, and the conference identifier of the second conference.

After the conference management device receives the first conference creation response and the second conference creation response, the conference management device determines the target conference ID, the conference ID of the first conference carried in the first conference creation response, and the second conference carried in the second conference creation response. meeting identifier to generate a target association relationship. For example, the target association relationship is as shown in Table 1 or Table 2 above.

It should be noted that, in a possible embodiment, the conference management device also sets a primary conference and a backup conference in the first conference and the second conference. For example, the conference management device sets the main conference system and the standby conference system in the first conference system to which the first conference belongs and the second conference system to which the second conference belongs, so as to set the main conference system and the backup conference system in the first conference and the second conference. Alternate meeting. Optionally, the conference reservation request sent by the conference reservation terminal to the conference management device can carry the identity information of the conference reservation holder, such as the department where the conference reservation holder is located, the position of the conference reservation holder, etc. The identity information is used to set the main conference system and backup conference system in the first conference system and the second conference system. Exemplarily, the conference management equipment maintains a correspondence between the identity information and the primary and backup conference systems. The conference management equipment sets the primary conference system in the first conference system and the second conference system based on the identity information of the conference subscriber and the correspondence. and conference system. For example, the main conference system corresponding to the identity information 1 recorded in the correspondence relationship is the first conference system, the backup conference system is the second conference system, and the identity information of the conference subscriber is identity information 1. Therefore, the conference management device uses the identity information 1 as the identity information 1. The identity information of the conference holder and the corresponding relationship, the first conference system is the main conference system, and the second conference system is The system is a conference system. It should be noted that, in order to ensure the flexibility of the main and backup conference system settings, after the conference management equipment sets the main conference system and the backup conference system, the human-computer interaction interface (such as the conference reservation interface) of the conference reservation terminal can display the main conference system and the backup conference system. The conference reservation holder can also manually modify the main conference system and the backup conference system set by the conference management device in the human-computer interaction interface. This is not limited in the embodiment of the present application.

S615. The conference management device sends a conference reservation response to the conference reservation terminal, and the conference reservation response carries the target conference identifier.

After the conference management device determines that the first conference system and the second conference system have successfully created a conference, the conference management device may send a conference reservation response to the conference reservation terminal to inform the conference reservation terminal that the conference reservation is successful. The conference reservation response carries a target conference identifier for the conference terminal to access the first conference or the second conference. Optionally, the conference reservation response also carries the conference password, conference topic, conference time, participant information, etc.

S616. The conference reservation terminal receives the conference reservation response sent by the conference management device.

Corresponding to the conference management device sending a conference reservation response to the conference reservation terminal, the conference reservation terminal may receive the conference reservation response sent by the conference management device.

S617. The conference reservation terminal sends a conference notification message to the conference terminal, and the conference notification message carries the target conference identifier.

After the conference reservation terminal receives the conference reservation response sent by the conference management device, the conference reservation terminal determines that the conference reservation is successful based on the conference reservation response. Afterwards, the conference reservation terminal can send a conference notification message to each conference terminal. The conference notification message carries the target conference identifier, and may also carry conference information such as the conference password, conference theme, and meeting time. The conference notification message is used to inform the conference terminal of the conference information of the multimedia conference.

In an optional embodiment, the conference reservation terminal sends the conference notification message to each conference terminal through email, short message or other instant messaging message. After any conference terminal receives the conference notification message sent by the conference reservation terminal, the conference terminal can display the conference notification message, for example, the conference information carried by the conference notification message to facilitate the participants of the conference terminal. Get information about this meeting. After participants of any conference terminal understand the conference information, they can control the conference terminal to access the first conference or the second conference at the corresponding conference time based on the target conference ID, conference entry password, etc. The implementation method of the conference terminal accessing the conference can refer to the embodiment in Figure 3 or Figure 5, and will not be described again here.

To sum up, according to the conference control method provided by the embodiment of the present application, after the conference management device receives the conference reservation request sent by the conference reservation terminal, the conference management device generates a target conference identification according to the conference reservation request, and sends the target conference identification to the first conference system and the third conference system. The second conference system schedules a conference; in the process of the conference management device booking a conference to the first conference system, the first conference system can create the first conference, generate the conference ID of the first conference, and feed back the conference ID of the first conference to the conference management equipment. ; In the process of the conference management device reserving a conference to the second conference system, the second conference system can create the second conference, generate a conference identifier of the second conference, and feed back the conference identifier of the second conference to the conference management device; the conference management device can An association relationship between the target conference identification and the conference identification of the first conference and the conference identification of the second conference (that is, the target association relationship) is generated, and the target conference identification is fed back to the conference reservation terminal. In this way, after the conference management device receives the joining request carrying the target conference identifier sent by the conference terminal, the conference management device can determine the conference identifier of the first conference or the second conference according to the target association relationship and the target conference identifier carried in the joining request. conference identification, and sends access instruction information including the conference identification of the first conference or the conference identification of the second conference to the conference terminal, so that the conference terminal accesses the first conference or the second conference according to the access instruction information. Since the conference management device maintains the association between the target conference ID, the conference ID of the first conference, and the conference ID of the second conference, the participants only need to perceive the target conference ID, and do not need to perceive the conference ID of the first conference and the conference ID of the second conference. The conference ID of the conference. In this way, the first conference system and the second conference system correspond to the same conference client, and the conference terminal can access the first conference through the conference client and the target conference ID. For meetings created by any of the two conference systems, the first conference system and the second conference system, participants do not need to be aware of the existence of the first conference system and the second conference system. The requirements for participants are lower and the actual operation is relatively simple. Simple and less error-prone. The embodiment of this application does not require participants to prepare two conference terminals, and the implementation cost is low.

The embodiment shown in FIG. 6 takes as an example that the first conference belongs to the first conference system and the second conference belongs to the second conference system. If the first conference and the second conference belong to the same conference system, for example, the first conference and the second conference both belong to the first conference system. The interaction process between the conference management device and the second conference system in the embodiment shown in FIG. 6 can be replaced by the interaction process between the conference management device and the first conference system. For example, in S609, the conference management device sends a second conference creation request to the first conference system, and S610 to S612 are executed by the first conference system. Optionally, S609 and S604 can be combined into one step, S610 and S605 can be combined into one step, S611 and S606 can be combined into one step, S612 and S607 can be combined into one step, and S613 and S608 can be combined into one step. , the embodiment of the present application does not limit this.

In this embodiment of the present application, the conference management device may include a conference reservation management service and a conference system scheduling service. The conference reservation management service may perform the aforementioned steps S602 to S603, and the conference system scheduling service may perform the aforementioned steps S201 to S202, S302 to S304. , S502 to S504, S604, S608 to S609, S613 to S615, this application does not limit this.

The above is an introduction to the method embodiments of the present application. The following is an introduction to the device embodiments of the present application. The device of the present application can be used to execute the method of the present application. For details not disclosed in the device embodiments of this application, please refer to the method embodiments of this application.

FIG. 8 is a schematic diagram of a conference control device 800 provided by an embodiment of the present application. The conference control device 800 may be a conference management device or a functional component in the conference management device. Referring to Figure 8, the conference control device 800 includes:

Determining module 810, used to determine that the first conference meets the switching condition;

The sending module 820 is configured to send switching instruction information to the first conference terminal accessing the first conference, where the switching instruction information is used to instruct the first conference terminal to switch from the first conference to the second conference.

Optional, switching conditions include one or more of the following:

The first conference fails, and the conference system to which the first conference belongs fails.

Optionally, the determining module 810 is also configured to determine the conference identifier of the second conference according to the target association relationship and the conference identifier of the first conference before the sending module 820 sends the switching instruction information to the first conference terminal. The switching instruction The information includes the conference identifier of the second conference, and the target association relationship includes the association relationship between the conference identifier of the first conference and the conference identifier of the second conference.

Optionally, the sending module 820 is also configured to send first access indication information to the first conference terminal before the first conference terminal accesses the first conference. The first access indication information is used to instruct the first conference terminal to access the first conference. Enter the first meeting.

Optionally, please continue to refer to Figure 8. The conference control device 800 further includes: a receiving module 830, configured to receive the first access instruction sent by the first conference terminal before the sending module 820 sends the first access instruction information to the first conference terminal. Conference joining request, the first joining request carries the target conference identifier, and the target conference identifier is used for the conference terminal to access the first conference or the second conference;

The determination module 810 is also configured to determine the first conference ID according to the target association relationship and the target conference identifier carried in the first conference joining request. A conference identifier of a conference, the first access instruction information includes the conference identifier of the first conference, and the target association relationship includes an association relationship between the target conference identifier and the conference identifier of the first conference.

Optionally, the sending module 820 is also configured to send second access instruction information to the second conference terminal based on the switching instruction information, where the second access instruction information is used to instruct the second conference terminal to access the second conference.

Optionally, please continue to refer to Figure 8. The conference control device 800 also includes:

The receiving module 830 is used to receive the meeting reservation request sent by the meeting reservation terminal;

Generating module 840, configured to generate a target conference ID according to the conference reservation request, where the target conference ID is associated with both the conference ID of the first conference and the conference ID of the second conference;

The sending module 820 is also configured to send a conference reservation response to the conference reservation terminal, where the conference reservation response carries a target conference identifier, and the target conference identifier is used for the conference terminal to access the first conference or the second conference.

Optionally, the generation module 840 is also configured to generate a target association relationship, where the target association relationship is an association relationship between the target conference ID, the conference ID of the first conference, and the conference ID of the second conference.

Optionally, the first conference belongs to the first conference system, and the second conference belongs to the second conference system. The sending module 820 is also configured to send a conference creation request to the first conference system and the second conference system respectively according to the conference reservation request;

The receiving module 830 is also used to receive conference creation responses sent by the first conference system and the second conference system respectively. The conference creation response sent by the first conference system carries the conference identification of the first conference. The conference creation response sent by the second conference system Carry the conference ID of the second conference.

Optionally, both the first conference and the second conference belong to the first conference system, and the sending module 820 is also used to send a conference creation request to the first conference system according to the conference reservation request;

The receiving module 830 is also configured to receive a conference creation response sent by the first conference system, where the conference creation response carries the conference ID of the first conference and the conference ID of the second conference.

The above-mentioned determining module 810, sending module 820, receiving module 830 and generating module 840 can all be implemented by software, or can be implemented by hardware. Illustratively, the following will introduce the determination module 810 as an example. Similarly, the implementation of the sending module 820, the receiving module 830 and the generating module 840 can refer to the implementation of the determining module 810.

The determination module 810 is an example of a software functional unit. The determination module 810 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device, such as a conference management device), a virtual machine, and a container. Furthermore, the above computing instance may be one or more. For example, determination module 810 may include code running on multiple hosts/virtual machines/containers. It should be noted that multiple hosts/virtual machines/containers used to run the code can be distributed in the same region (region) or in different regions. Furthermore, 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 includes one data center or multiple AZs. geographically close data centers. Among them, usually a region can include multiple AZs.

Likewise, the multiple hosts/VMs/containers used to run the code can be distributed in the same virtual private cloud (VPC), or across multiple VPCs. Among them, usually a VPC is set up in a region. Cross-region communication between two VPCs in the same region and between VPCs in different regions requires a communication gateway in each VPC, and the interconnection between VPCs is realized through the communication gateway. .

As an example of a hardware functional unit, the determining module 810 may include at least one computing device, such as a server. Alternatively, the determination module 810 may also utilize an application-specific integrated circuit (application-specific integrated circuit). circuit, ASIC), or programmable logic device (PLD), etc. The above-mentioned PLD can be implemented by a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.

Multiple computing devices included in the determination module 810 may be distributed in the same region or in different regions. The multiple computing devices included in the determination module 810 may be distributed in the same AZ or in different AZs. Similarly, multiple computing devices included in the determination module 810 may be distributed in the same VPC or in multiple VPCs. The multiple computing devices may be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

It should be noted that in other embodiments, the determining module 810 can be used to perform any step of determining information about the conference management device in the above conference control method, and the sending module 820 can be used to perform sending information about the conference management device in the above conference control method. Any step of receiving information, the receiving module 830 can be used to perform any step of receiving information about the conference management equipment in the above conference control method, and the generating module 840 can be used to perform any step of generating information about the conference management equipment in the above conference control method (such as conference identification, any step of target association, etc.). For example, the determining module 810 is used to perform the above steps S201, S303 and S503, the sending module 820 is used to perform the above steps S202, S304, S504, S604 and S609, and the receiving module 830 is used to perform the above steps S302, S502, S602, S608 and S613, the generation module 840 is used to execute the above steps S603 and S614. The steps responsible for implementation by the determination module 810, the sending module 820, the receiving module 830 and the generating module 840 can be specified as needed. The determining module 810, the sending module 820, the receiving module 830 and the generating module 840 respectively implement different steps in the above conference control method. To realize all functions of the conference control device 800.

To sum up, in the conference control device provided by the embodiment of the present application, when the determination module determines that the first conference meets the switching conditions, the sending module sends switching instruction information to the first conference terminal accessing the first conference, and the first conference terminal sends the switching instruction information according to the The switching instruction information switches from the first conference to the second conference. Since the conference switching process is completed by the conference control device controlling the conference terminal, the conference switching process does not require manual participation. Therefore, the conference switching process is simple and not prone to errors. The switching speed is fast and the switching efficiency is high. Conference switching can be completed at the minute level. The conference switching process It has little impact on the development of multimedia conferences.

FIG. 9 is a schematic diagram of another conference control device 900 provided by an embodiment of the present application. The conference control device 900 may be a first conference terminal or a functional component in the first conference terminal. Referring to Figure 9, the conference control device 900 includes:

The receiving module 910 is configured to receive switching instruction information sent by the conference management device. The switching instruction information is sent after the conference management device determines that the first conference accessed by the first conference terminal meets the switching conditions;

The switching module 920 is configured to switch from the first conference to the second conference according to the switching instruction information.

Optional, switching conditions include one or more of the following:

Optionally, the first conference belongs to the first conference system, the second conference belongs to the second conference system, and a conference client is installed in the first conference terminal. The conference client includes a first conference interface corresponding to the first conference system and Corresponding to the second conference interface of the second conference system, the switching module 920 is configured to call the second conference interface to access the second conference according to the switching instruction information. discussion.

Optionally, the receiving module 910 is also configured to receive the first access instruction information sent by the conference management device before receiving the switching instruction information sent by the conference management device;

The conference control device 900 also includes: an access module 930, configured to access the first conference according to the first access instruction information.

Optionally, the conference control device 900 also includes: a sending module 940, configured to send a first conference joining request to the conference management device before the receiving module 910 receives the first access instruction information sent by the conference management device. The first conference joining request carries The target conference identifier is used for the conference terminal to access the first conference or the second conference.

The above-mentioned receiving module 910, switching module 920, access module 930 and sending module 940 can all be implemented by software, or can be implemented by hardware. For the implementation of the receiving module 910, the switching module 920, the access module 930 and the sending module 940, reference can be made to the implementation of the aforementioned determination module 810, which will not be described again here.

It should be noted that in other embodiments, the receiving module 910 can be used to perform any steps related to the first conference terminal receiving information in the above conference control method, and the switching module 920 can be used to perform the above conference control method related to the first conference. In any step of the terminal switching conferences, the access module 930 can be used to perform any steps in the above conference control method related to the first conference terminal accessing the conference, and the sending module 940 can be used to perform the above conference control method related to the first conference terminal sending any step of information. For example, the receiving module 910 is used to perform the above steps S203, S305 and S616, the switching module 920 is used to perform the above step S204, the access module 930 is used to perform the above step S306, and the sending module 940 is used to perform the above steps S301, S601 and S617. . The steps that the receiving module 910, the switching module 920, the access module 930 and the sending module 940 are responsible for implementing can be specified as needed. The receiving module 910, the switching module 920, the access module 930 and the sending module 940 respectively implement different steps in the above conference control method. steps to realize all functions of the conference control device 900.

To sum up, in the conference control device provided by the embodiment of the present application, after the receiving module receives the switching instruction information sent by the conference management device, the switching module switches from the first conference to the second conference according to the switching instruction information. Therefore, the first conference terminal performs conference switching under the control of the conference management equipment. The conference switching process does not require manual participation. The conference switching process is simple and not error-prone. The switching speed is fast and the switching efficiency is high. The conference switching can be completed in minutes.

FIG. 10 is a schematic diagram of yet another conference control device 1000 provided by an embodiment of the present application. The conference control device 1000 may be a conference management device. As shown in FIG. 10 , the conference control device 1000 includes: a bus 1002 , a processor 1004 , a memory 1006 and a communication interface 1008 . The processor 1004, the memory 1006 and the communication interface 1008 communicate through the bus 1002. It should be understood that the embodiment of the present application does not limit the number of processors and memories in the conference control device 1000.

The bus 1002 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one line is used in Figure 10, but it does not mean that there is only one bus or one type of bus. Bus 1002 may include a path for transferring information between various components of conference control device 1000 (eg, memory 1006, processor 1004, communication interface 1008).

The processor 1004 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP) or a digital signal processor (DSP). any one or more of them.

Memory 1006 may include volatile memory, such as random access memory. access memory, RAM). The processor 1004 may also include non-volatile memory (non-volatile memory), such as read-only memory (ROM), flash memory, hard disk drive (HDD) or solid state drive (solid state drive). drive, SSD), etc.

The memory 1006 stores executable program code, and the processor 1004 executes the executable program code to respectively realize the functions of the aforementioned determination module 810, the sending module 820, the receiving module 830 and the generating module 840, thereby realizing the above conference control method. At least some of the steps. That is, the memory 1006 stores instructions for executing the above conference control method.

The communication interface 1008 uses transceiver modules such as, but not limited to, network interface cards and transceivers to implement communication between the conference control device 1000 and other devices or communication networks. The functions of the aforementioned sending module 820 and receiving module 830 can also be implemented by the communication interface 1008, which is not limited in the embodiment of the present application.

Figure 11 is a schematic diagram of yet another conference control device 1100 provided by an embodiment of the present application. The conference control device 1100 may be a conference terminal. The conference control device 1100 includes: a bus 1102, a processor 1104, a memory 1106 and a communication interface 1108. The processor 1104, the memory 1106 and the communication interface 1108 communicate through a bus 1102. The structure of the conference control device 1100 is similar to the structure of the conference control device 1000 and will not be described again here. The difference is that in the conference control device 1100, the processor 1104 executes the executable program code stored in the memory 1106 to realize the functions of the aforementioned receiving module 910, switching module 920, access module 930 and sending module 940 respectively, thereby realizing At least some steps of the above conference control method. That is, the memory 1106 stores instructions for executing the above conference control method. In addition, the functions of the receiving module 910 and the sending module 940 can also be implemented by the communication interface 1108, which is not limited in the embodiment of the present application.

The embodiment of the present application provides a communication system. The communication system includes a conference management device and a first conference terminal. The conference management device and the first conference terminal are communicatively connected. The conference management device includes a conference control as shown in Figure 8 or Figure 10 device, the first conference terminal includes a conference control device as shown in Figure 9 or Figure 11. Optionally, the communication system is shown in Figure 1.

Embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium may be any available medium that can be used by a computing device (such as a conference management device, a conference terminal) to store information, or may contain one or more Data storage facilities such as data centers with available media. The available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, solid state drive), etc. The computer-readable storage medium includes computer program instructions that instruct the computing device (eg, conference management device, conference terminal) to execute all or part of the steps of the above conference control method.

Embodiments of the present application also provide a computer program product containing instructions. The computer program product may contain instructions and can be run on a computing device (such as a conference management device, a conference terminal) or stored in any available media. software or program product. When the computer program product is run on at least one computing device (eg, conference management device, conference terminal), the at least one computing device is caused to execute all or part of the steps of the above conference control method.

Embodiments of the present application also provide a chip, which includes programmable logic circuits and/or program instructions, and is used to implement all or part of the steps of the above conference control method when the chip is running.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product that includes Contains one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another, for example, the computer instructions may be transferred from a website, computer, server, or data The center transmits to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media integrated therein. The available media may be magnetic media (eg, floppy disks, hard disks, tapes), optical media, or semiconductor media (eg, solid state drives), etc.

It should be understood that the term "at least one" in this application refers to one or more, the term "plurality" refers to two or more, and the term "at least two" refers to two or more. In this application, unless otherwise stated, the symbol "/" means or, for example, A/B means A or B. The term "and/or" in this application is only an association relationship describing related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist simultaneously, alone There are three situations B. In addition, in order to facilitate clear description, in this application, words such as “first”, “second” and “third” are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as “first”, “second” and “third” do not limit the number and execution order.

Different types of embodiments such as method embodiments and device embodiments provided in the embodiments of this application can all refer to each other, and the embodiments of this application do not limit this. The sequence of operations of the method embodiments provided by the embodiments of the present application can be adjusted appropriately, and the operations can also be increased or decreased in response to the situation. Any person familiar with the technical field can easily think of changes within the technical scope disclosed in the present application. All methods are covered by the protection scope of this application, and therefore will not be described again.

In the corresponding embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other configurations. For example, the device embodiments described above are only illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into Another system, or some features can be ignored, or not implemented.

Modules described as separate components may or may not be physically separate. Components described as modules may or may not be physical modules that may be located in one place or may be distributed to multiple devices (such as conference terminals, conference management equipment). Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above are only exemplary embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of various equivalents within the technical scope disclosed in the present application. Any modification or replacement shall be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A conference control method, characterized in that the method includes:

The conference management equipment determines that the first conference meets the switching conditions;

The conference management device sends switching instruction information to the first conference terminal accessing the first conference, where the switching instruction information is used to instruct the first conference terminal to switch from the first conference to the second conference.
The method according to claim 1, characterized in that:

The first conference and the second conference belong to different conference systems.
The method according to claim 1 or 2, characterized in that the switching conditions include one or more of the following:

The first conference fails, and the conference system to which the first conference belongs fails.
The method according to any one of claims 1 to 3, characterized in that, before the conference management device sends the switching instruction information to the first conference terminal, the method further includes:

The conference management device determines the conference identifier of the second conference according to the target association relationship and the conference identifier of the first conference. The switching instruction information includes the conference identifier of the second conference. In the target association relationship, It includes an association relationship between the conference ID of the first conference and the conference ID of the second conference.
The method according to any one of claims 1 to 4, characterized in that, before the first conference terminal accesses the first conference, the method further includes:

The conference management device sends first access instruction information to the first conference terminal, where the first access instruction information is used to instruct the first conference terminal to access the first conference.
The method according to claim 5, characterized in that, before the conference management device sends the first access indication information to the first conference terminal, the method further includes:

The conference management device receives a first conference joining request sent by the first conference terminal. The first conference joining request carries a target conference identification. The target conference identification is used for the conference terminal to access the first conference or the third conference. 2 meetings;

The conference management device determines the conference identification of the first conference according to the target association relationship and the target conference identification carried in the first joining request, and the first access indication information includes the conference identification of the first conference. The target association relationship includes an association relationship between the target conference identifier and the conference identifier of the first conference.
The method according to any one of claims 1 to 6, characterized in that the method further includes:

The conference management device sends second access instruction information to the second conference terminal based on the switching instruction information, where the second access instruction information is used to instruct the second conference terminal to access the second conference.
The method according to any one of claims 1 to 7, characterized in that the method further includes:

The conference management device receives the conference reservation request sent by the conference reservation terminal;

The conference management device generates a target conference identification according to the conference reservation request, and the target conference identification is identical to the The conference ID of the first conference and the conference ID of the second conference are both associated;

The conference management device sends a conference reservation response to the conference reservation terminal. The conference reservation response carries the target conference identifier. The target conference identifier is used for the conference terminal to access the first conference or the second conference. .
The method of claim 8, further comprising:

The conference management device generates a target association relationship, where the target association relationship is an association relationship between the target conference identifier, the conference identifier of the first conference, and the conference identifier of the second conference.
The method according to claim 8 or 9, characterized in that the first conference belongs to a first conference system, the second conference belongs to a second conference system, and the method further includes:

The conference management device sends a conference creation request to the first conference system and the second conference system respectively according to the conference reservation request;

The conference management device receives conference creation responses sent by the first conference system and the second conference system respectively. The conference creation response sent by the first conference system carries the conference identification of the first conference. The conference creation response sent by the second conference system carries the conference identifier of the second conference.
A conference control method, characterized in that the method includes:

The first conference terminal receives the switching instruction information sent by the conference management device. The switching instruction information is sent after the conference management device determines that the first conference accessed by the first conference terminal meets the switching condition;

The first conference terminal switches from the first conference to the second conference according to the switching instruction information.
The method according to claim 11, characterized in that:

The first conference and the second conference belong to different conference systems.
The method according to claim 11 or 12, characterized in that the switching conditions include one or more of the following:

The first conference fails, and the conference system to which the first conference belongs fails.
The method according to any one of claims 11 to 13, characterized in that the first conference belongs to a first conference system, the second conference belongs to a second conference system, and a conference terminal is installed in the first conference terminal. Client, the conference client includes a first conference interface corresponding to the first conference system and a second conference interface corresponding to the second conference system, and the first conference terminal switches from The first conference is switched to the second conference, including:

The first conference terminal calls the second conference interface to access the second conference according to the switching instruction information.
The method according to any one of claims 11 to 14, characterized in that, before the first conference terminal receives the switching instruction information sent by the conference management device, the method further includes:

The first conference terminal receives the first access instruction information sent by the conference management device;

The first conference terminal accesses the first conference according to the first access indication information.
The method according to claim 15, characterized in that, receiving the conference management information at the first conference terminal Before the first access indication information is sent by the device, the method further includes:

The first conference terminal sends a first conference joining request to the conference management device. The first conference joining request carries a target conference identification. The target conference identification is used for the conference terminal to access the first conference or the second conference. Meeting.
A conference control device, characterized in that it is applied to conference management equipment, and the device includes:

Determining module, used to determine that the first conference meets the switching conditions;

A sending module, configured to send switching instruction information to the first conference terminal accessing the first conference, where the switching instruction information is used to instruct the first conference terminal to switch from the first conference to the second conference.
The device according to claim 17, characterized in that:

The first conference and the second conference belong to different conference systems.
The device according to claim 17 or 18, characterized in that the switching condition includes one or more of the following:

The first conference fails, and the conference system to which the first conference belongs fails.
The device according to any one of claims 17 to 19, characterized in that,

The determining module is also configured to determine the conference of the second conference according to the target association relationship and the conference identification of the first conference before the sending module sends the switching instruction information to the first conference terminal. The switch indication information includes a conference identifier of the second conference, and the target association relationship includes an association relationship between the conference identifier of the first conference and the conference identifier of the second conference.
The device according to any one of claims 17 to 20, characterized in that:

The sending module is further configured to send first access instruction information to the first conference terminal before the first conference terminal accesses the first conference, where the first access instruction information is used to indicate The first conference terminal accesses the first conference.
The device according to claim 21, characterized in that:

The device further includes: a receiving module configured to receive the first conference joining request sent by the first conference terminal before the sending module sends the first access instruction information to the first conference terminal, the The first conference joining request carries a target conference identifier, and the target conference identifier is used for a conference terminal to access the first conference or the second conference;

The determination module is further configured to determine the conference identification of the first conference according to the target association relationship and the target conference identification carried in the first joining request, and the first access indication information includes the first A conference identifier of the conference, and the target association relationship includes an association relationship between the target conference identifier and the conference identifier of the first conference.
The device according to any one of claims 17 to 22, characterized in that:

The sending module is further configured to send second access instruction information to a second conference terminal based on the switching instruction information, where the second access instruction information is used to instruct the second conference terminal to access the third conference terminal. Two meetings.
The device according to any one of claims 17 to 23, characterized in that the device further includes:

The receiving module is used to receive the conference booking request sent by the conference booking terminal;

A generation module configured to generate a target conference identifier according to the conference reservation request, where the target conference identifier is associated with both the conference identifier of the first conference and the conference identifier of the second conference;

The sending module is also configured to send a conference reservation response to the conference reservation terminal, where the conference reservation response carries the target conference identifier, and the target conference identifier is used for the conference terminal to access the first conference or the first conference. Second meeting.
The device according to claim 24, characterized in that:

The generating module is further configured to generate a target association relationship, where the target association relationship is an association relationship between the target conference identifier, the conference identifier of the first conference, and the conference identifier of the second conference.
The device according to claim 24 or 25, characterized in that the first conference belongs to a first conference system, and the second conference belongs to a second conference system,

The sending module is also configured to send a conference creation request to the first conference system and the second conference system respectively according to the conference reservation request;

The receiving module is also configured to receive conference creation responses sent by the first conference system and the second conference system respectively. The conference creation response sent by the first conference system carries the conference identification of the first conference, The conference creation response sent by the second conference system carries the conference identification of the second conference.
A conference control device, characterized in that it is applied to a first conference terminal, and the device includes:

A receiving module configured to receive switching instruction information sent by the conference management device, where the switching instruction information is sent after the conference management device determines that the first conference accessed by the first conference terminal meets the switching condition;

A switching module, configured to switch from the first conference to the second conference according to the switching instruction information.
The device according to claim 27, characterized in that:

The first conference and the second conference belong to different conference systems.
The device according to claim 27 or 28, characterized in that the switching condition includes one or more of the following:

The first conference fails, and the conference system to which the first conference belongs fails.
The device according to any one of claims 27 to 29, characterized in that:

The first conference belongs to a first conference system, the second conference belongs to a second conference system, a conference client is installed in the first conference terminal, and the conference client includes a computer corresponding to the first conference system. a first conference interface and a second conference interface corresponding to the second conference system,

The switching module is configured to call the second conference interface to access the second conference according to the switching instruction information.
The device according to any one of claims 27 to 30, characterized in that:

The receiving module is further configured to receive the first access instruction information sent by the conference management device before receiving the switching instruction information sent by the conference management device;

The device further includes: an access module, configured to access the first conference according to the first access indication information.
The device of claim 31, further comprising:

A sending module, configured to send a first joining request to the conference management device before the receiving module receives the first access instruction information sent by the conference management device, where the first joining request carries a target conference identifier. , the target conference identification is used for a conference terminal to access the first conference or the second conference.
A conference control device, characterized by including a memory and a processor;

The memory is used to store computer programs;

The processor is configured to execute a computer program stored in the memory so that the conference control device executes the method according to any one of claims 1 to 10.
A conference control device, characterized by including a memory and a processor;

The memory is used to store computer programs;

The processor is configured to execute a computer program stored in the memory so that the conference control device executes the method according to any one of claims 11 to 16.
A communication system, characterized in that the communication system includes a conference management device and a first conference terminal, and the conference management device and the first conference terminal are communicatively connected,

The conference management equipment includes a conference control device as described in any one of claims 17 to 26 or claim 33, and the first conference terminal includes a conference control device as described in any one of claims 27 to 32 or claim 34. control device.
A computer-readable storage medium, characterized by comprising computer program instructions that, when executed by a conference management device, cause the conference management device to perform the method according to any one of claims 1 to 10 .
A computer-readable storage medium, characterized in that it includes computer program instructions that, when executed by a conference terminal, cause the conference terminal to perform the method according to any one of claims 11 to 16.
A computer program product containing instructions, characterized in that when the instructions are executed by a conference management device, the conference management device is caused to perform the method according to any one of claims 1 to 10.
A computer program product containing instructions, characterized in that, when the instructions are executed by a conference terminal, the conference terminal causes the conference terminal to execute the method according to any one of claims 11 to 16.