CN106254814B - Conference recovery method, service management center and system - Google Patents

Conference recovery method, service management center and system Download PDF

Info

Publication number
CN106254814B
CN106254814B CN201610619102.0A CN201610619102A CN106254814B CN 106254814 B CN106254814 B CN 106254814B CN 201610619102 A CN201610619102 A CN 201610619102A CN 106254814 B CN106254814 B CN 106254814B
Authority
CN
China
Prior art keywords
mcu
conference
smc
terminal
slave
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201610619102.0A
Other languages
Chinese (zh)
Other versions
CN106254814A (en
Inventor
李青华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201610619102.0A priority Critical patent/CN106254814B/en
Publication of CN106254814A publication Critical patent/CN106254814A/en
Priority to PCT/CN2017/093404 priority patent/WO2018019158A1/en
Application granted granted Critical
Publication of CN106254814B publication Critical patent/CN106254814B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/15—Conference systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H04L65/4038—Arrangements for multi-party communication, e.g. for conferences with floor control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The invention discloses a conference recovery method, a service management center and a system, and belongs to the field of communication. The method comprises the following steps: a first Service Management Center (SMC) determines a first Multipoint Control Unit (MCU) which is used for holding a conference and is abnormal, wherein the first SMC is any SMC used for holding the conference; the first SMC determines a first meeting place terminal accessed to the first MCU according to the corresponding relation of the meeting number of the MCU and the terminal number of the meeting place terminal; the first SMC allocates a second MCU to the first session terminal; and the first SMC recovers the conference through the second MCU. The invention can restore the conference in time and continue to hold the video conference when partial equipment in the system breaks down to cause the video conference to be interrupted in the video conference holding process.

Description

Conference recovery method, service management center and system
Technical Field
The present invention relates to the field of communications, and in particular, to a method, a service management center, and a system for conference recovery.
Background
The video system is a system for holding a remote conference by using a network. The video system includes a plurality of domains, each domain represents a region, and each domain is deployed with a Service Manager Center (SMC), each SMC is responsible for managing conference resources included in its domain, where the conference resources include a Multipoint Control Unit (MCU), a conference terminal, and the like.
In a video system, a user can request the SMC of the domain where the user is located to allocate conference resources, namely, allocate a conference terminal and an MCU, and then hold a conference by using the allocated conference terminal and MCU. During the conference holding process, an allocated MCU may be abnormal, which causes interruption of the conference being carried out and the conference cannot be held continuously.
Disclosure of Invention
In order to enable a system to timely recover a conference and continue holding when a video conference is interrupted due to the fact that a part of equipment in the system breaks down, the embodiment of the invention provides a conference recovery method, a service management center and a conference recovery system. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides a method for conference recovery, where the method is applied to a video system, and includes: the method comprises the steps that a first SMC determines a first multipoint control unit MCU which is used for holding a conference and is abnormal, the first SMC determines a first meeting place terminal accessed to the first MCU according to the corresponding relation of the conference number of the MCU and the terminal number of a meeting place terminal, and distributes a second MCU to the first meeting place terminal, and the conference is recovered through the second MCU. The scheme provided by the embodiment can determine the first meeting place terminal accessed to the abnormal first MCU, so that the second MCU can be allocated to the first meeting place terminal, the conference is recovered through the second MCU, and the conference can be continuously held.
In one possible design, if the first MCU is not a master MCU, the first SMC allocates a conference number to the second MCU, transmits the terminal number of the first conference site terminal and the conference number of the master MCU to the second MCU, and transmits the conference number of the second MCU to the master MCU. Therefore, the second MCU can establish conference connection with the first meeting place terminal, the main MCU and the second MCU can establish a cascade channel between the main MCU and the second MCU, and the connection between the meeting place terminals is recovered, so that the conference is recovered in time and is continuously held.
In a possible design, the first SMC may further obtain, from a correspondence between a conference number of an MCU and a terminal number of a conference site terminal, a correspondence between the conference number of the first MCU and the terminal number of the first conference site terminal, and update the conference number of the first MCU stored in the obtained correspondence to the conference number of the second MCU. In this embodiment, because the first MCU is abnormal, the first meeting place terminal accessed to the first MCU needs to be accessed to the second MCU again, so that the correspondence between the conference number of the MCU and the terminal number of the meeting place terminal is updated, the accuracy of the stored data can be ensured, and when the MCU is abnormal again, the meeting place terminal accessed to the abnormal MCU can be accurately determined according to the correspondence.
In one possible design, the first SMC may further obtain, from a correspondence between a conference number of a master MCU and a conference number of a slave MCU, a correspondence including the conference number of the master MCU and the conference number of the first MCU, and update the conference number of the first MCU stored in the obtained correspondence to the conference number of the second MCU. In this embodiment, when the first MCU is abnormal, the first SMC may find the conference number of the master MCU according to the conference number of the first MCU, the correspondence between the conference number of the slave MCU and the conference number of the master MCU. After the second MCU is allocated, the conference number of the first MCU stored in the corresponding relation between the conference number of the main MCU and the conference number of the slave MCU is updated to the conference number of the second MCU, so that the accuracy of stored data can be ensured, and when the MCU is abnormal again, the conference number of the main MCU can be searched in a preparation manner according to the conference number of the abnormal MCU.
In one possible design, if the first MCU is a master MCU, the first SMC may determine that the second MCU is a master MCU and allocate a conference number to the second MCU, send the terminal number of the first venue terminal and the conference number of each slave MCU used to hold the conference to the second MCU, and send the conference number of the second MCU to each slave MCU. Therefore, the second MCU can establish conference connection with the first conference site terminal, and each slave MCU and the second MCU respectively establish a cascade channel between each slave MCU and the second MCU so as to recover the connection between the conference site terminals and realize recovery of the conference.
In one possible design, the first SMC may further determine each second meeting place terminal, which is accessed to the slave MCU included in the conference and located in the domain where the first SMC is located, to obtain meeting place information of the second meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed to the second meeting place terminal and the second MCU, and update meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information. By the scheme provided by the embodiment, the meeting place information of each second meeting place terminal can be respectively sent to each second meeting place terminal according to the corresponding relation between the terminal number and the meeting place information when the conference is continuously held, so that each second meeting place terminal can correctly display the meeting place information.
In another aspect, an embodiment of the present application provides a method for conference recovery, where the method is applied to a video system, and includes: the method comprises the steps that a first SMC determines a second SMC which is used for holding a conference and is abnormal, the first SMC is a backup SMC of the second SMC, a first meeting place terminal which is located in a domain corresponding to the second SMC and used for holding the conference is determined, a first multipoint control unit MCU is distributed to the first meeting place terminal from an MCU included in the corresponding domain, and the conference is recovered through the first MCU. According to the scheme provided by the embodiment, the first meeting place terminal in the area where the abnormal second SMC is located can be determined, so that the first MCU can be allocated to the first meeting place terminal, the conference is recovered through the first MCU, and the conference can be continuously held.
In one possible design, if the second SMC is not a master SMC, the first SMC allocates a conference number to the first MCU, transmits the terminal number of the first venue terminal and the conference number of a master MCU used to hold the conference to the first MCU, and transmits the conference number of the first MCU to the master MCU. Therefore, the first MCU can establish conference connection with the first meeting place terminal, and the main MCU and the first MCU can establish a cascade channel between the main MCU and the first MCU to recover the connection between the meeting place terminals and recover the conference.
In one possible design, if the second SMC is a master SMC, the first SMC may select an MCU from an MCU set as a master MCU, where the MCU set includes the allocated first MCU, allocates a conference number to the master MCU, and sends a terminal number of a corresponding first conference terminal to the master MCU. According to the scheme provided by the embodiment, one main MCU can be selected from the MCU set, and the terminal number of the first meeting place terminal corresponding to the main MCU is sent to the main MCU, so that the main MCU can establish conference connection with the corresponding first meeting place terminal, and then the interrupted conference can be recovered.
In one possible design, the first SMC determines an MCU not selected in the MCU set as a first slave MCU, allocates a conference number to the first slave MCU, sends the conference number of the first slave MCU to the master MCU, and sends the conference number of the master MCU and a terminal number of a first conference site terminal corresponding to the first slave MCU. Therefore, the first slave MCU establishes conference connection with the corresponding first conference site terminal, and the first slave MCU and the master MCU establish a cascade channel between the first slave MCU and the master MCU.
In another aspect, the present invention provides a service management center SMC, where the SMC is applied to a video system, and the SMC is configured to perform a behavior function of a first SMC in the method provided in the above aspect. The behavior function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.
In one possible design, the SMC further updates meeting place information corresponding to the terminal number of the first meeting place terminal stored in the correspondence between the terminal number and the meeting place information to the acquired meeting place information by acquiring meeting place information of the first meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the main MCU and the second MCU. Therefore, when the conference is recovered and held continuously, the correct conference site information is provided for the first conference site terminal through the corresponding relation of the terminal number and the conference site information.
In one possible design, the SMC further obtains meeting place information of the second meeting place terminal by determining each second meeting place terminal, which is accessed to the slave MCU included in the conference and is located in the domain, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed to the second meeting place terminal and the second MCU, and updates the meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information. Thus, when the conference is recovered and held continuously, the second conference terminal is provided with correct conference information through the corresponding relation of the terminal number and the conference information.
In another aspect, the present invention provides a service management center SMC, which is applied to a video system, and is configured to perform the behavior function of the first SMC in the method provided in the above another aspect. The behavior function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.
In one possible design, the SMC further includes a second slave MCU by determining a domain in which a slave SMC for holding the conference is located; and sending the conference number of the master MCU to the second slave MCU, and sending the conference number of the second slave MCU to the master MCU, so that the master MCU and the second slave MCU can be ensured to establish a cascade channel between the master MCU and the second slave MCU.
In one possible design, the SMC further obtains meeting place information of the second meeting place terminal by determining each second meeting place terminal, which is accessed to the slave MCU included in the conference and is located in the domain, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed to the second meeting place terminal and the first MCU, and updates the meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information. Thus, when the conference is recovered and held continuously, the second conference terminal is provided with correct conference information through the corresponding relation of the terminal number and the conference information.
In another aspect, an embodiment of the present application provides a system for conference recovery, where the system is applied to a video system, and the system includes: the system comprises a first service management center SMC, a first multipoint control unit MCU and a second MCU; the first SMC determines a first MCU which is used for holding a conference and is abnormal, determines a first meeting place terminal accessed to the first MCU according to the corresponding relation of the conference number of the MCU and the terminal number of the meeting place terminal, wherein the first SMC is any SMC used for holding the conference, and allocates a second MCU for the first meeting place terminal; and restoring the conference through the second MCU. The scheme provided by the embodiment can determine the first meeting place terminal accessed to the abnormal first MCU, so that the second MCU can be allocated to the first meeting place terminal, the conference is recovered through the second MCU, and the conference can be continuously held.
In another aspect, a system for restoring a conference, the system being applied to a video system, the system comprising: the system comprises a first service management center SMC, a second SMC and a first multipoint control unit MCU; the first SMC determines a second SMC which is used for holding a conference and is abnormal, determines a first meeting place terminal which is positioned in a domain corresponding to the second SMC and used for holding the conference, wherein the first SMC is a backup SMC of the second SMC, and allocates a first multipoint control unit MCU for the first meeting place terminal from MCUs included in the corresponding domain; and restoring the conference through the first MCU. According to the scheme provided by the embodiment, the first meeting place terminal in the area where the abnormal second SMC is located can be determined, so that the first MCU can be allocated to the first meeting place terminal, the conference is restored through the first MCU, and the conference can be continuously held.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1-1 is a schematic diagram of a networking architecture for holding a conference according to an embodiment of the present invention;
fig. 1-2 is a schematic diagram of another networking architecture for holding a conference according to an embodiment of the present invention;
fig. 1-3 are schematic diagrams of another networking architecture for holding a conference according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating an SMC structure according to an embodiment of the present invention;
fig. 3-1 is a flowchart of a method for restoring a conference according to an embodiment of the present invention;
fig. 3-2 is a schematic diagram of another networking architecture for holding a conference according to an embodiment of the present invention;
FIG. 4-1 is a flow chart of another method for conference recovery according to an embodiment of the present invention;
fig. 4-2 is a schematic diagram of another networking architecture for holding a conference according to an embodiment of the present invention;
FIG. 5-1 is a flow chart of another method for conference recovery according to an embodiment of the present invention;
fig. 5-2 is a schematic diagram of another networking architecture for holding a conference according to an embodiment of the present invention;
FIG. 6-1 is a flow chart of another method for conference recovery according to an embodiment of the present invention;
fig. 6-2 is a schematic diagram of another networking architecture for holding a conference according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a device for conference recovery according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another conference resuming device provided in the embodiment of the present invention;
fig. 9 is a schematic structural diagram of a system for recovering a conference according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of another system for conference recovery according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
A video system is a conference system, and data transmitted in the video system may include only audio data or both audio data and video data. In a video system, each SMC is used to manage the conference resources included in its domain, and the conference resources may include hardware resources such as a conference terminal and an MCU. Each domain in the video system may be a network of conference resources, and each domain may be a network of conference resources deployed in a region, a network of conference resources deployed in an industry domain, or a network of conference resources deployed in an enterprise, etc. For example, a network formed by SMC deployed in beijing, MCU and conference resources such as conference terminals may be called a domain, and SMC deployed in beijing may manage MCU and conference terminals deployed in beijing.
When a video system holds a conference, conference resources are required to be allocated and used for establishing the conference, and the conference resources comprise at least one SMC, at least one MCU and at least two meeting place terminals. For example, referring to fig. 1-1, it is assumed that a conference exists, conference resources used by the conference include an SMC a, an MCU a, a meeting place terminal 1 and a meeting place terminal 2, the MCU a, the meeting place terminal 1 and the meeting place terminal 2 are located in the domain of the SMC a, the meeting place terminal 1 establishes a conference connection with the MCU a, and the meeting place terminal 2 establishes a conference connection with the MCU a, so that the meeting place terminal 1 and the meeting place terminal 2 can hold the conference.
For another example, referring to fig. 1-2, it is assumed that a conference exists, and conference resources used by the conference include SMC a, SMC B, SMC C, MCU a, MCU B, MCU C, conference site terminal 1, conference site terminal 2, conference site terminal 3, conference site terminal 4, and conference site terminal 5. The identity of the SMC A is a master SMC, the identities of the SMC B and the SMC C are slave SMCs, and the identity of the MCU A is a master MCU, and the identities of the MCU B and the MCU C are slave MCUs. The MCU A corresponds to the SMC A and is positioned in the domain of the SMC A, and conference connections are respectively established between the conference site terminal 1 and the conference site terminal 2 and the MCU A. The MCU B corresponds to the SMC B and is positioned in the domain of the SMC B, and conference connections are respectively established between the conference site terminal 3 and the conference site terminal 4 and the MCU B. The MCU C corresponds to the SMC C and is positioned in the domain of the SMC C, and a conference connection is established between the conference place terminal 5 and the MCU C. And a cascade channel is established between the MCU A and the MCU B and between the MCU A and the MCU C respectively. Thus, the conference terminal 1, the conference terminal 2, the conference terminal 3, the conference terminal 4, and the conference terminal 5 can hold a conference.
And for any SMC in the at least one SMC, the SMC stores the corresponding relation between the conference number of the master MCU and the conference number of the slave MCU, the corresponding relation between the conference number of the MCU and the terminal number of the conference site terminal, and the corresponding relation between the terminal number and the conference site information. When the conference resource is allocated, if the SMC is a master SMC, the SMC stores the conference number of the master MCU and the conference number of the slave MCU for holding the conference in the corresponding relationship between the conference number of the master MCU and the conference number of the slave MCU, and if the SMC is a slave SMC, the SMC stores the conference number of the master MCU and the conference number of the slave MCU in the corresponding domain for holding the conference in the corresponding relationship between the conference number of the master MCU and the conference number of the slave MCU. In addition, no matter what identity the SMC is, the SMC stores the conference number of each MCU corresponding to the SMC and the terminal number of the conference site terminal accessing the MCU in the correspondence relationship between the conference number of the MCU and the terminal number of the conference site terminal. When the conference is established, the SMC also obtains the conference site information of each conference site terminal accessed to the corresponding slave MCU, the conference site information includes the cascade channel name and the channel number between the slave MCU and the master MCU, the cascade channel name may include the conference number of the slave MCU and the conference number of the master MCU, and the terminal number and the conference site information of the conference site terminal are stored in the corresponding relationship between the terminal number and the conference site information.
For example, for SMC a, SMC a is a master SMC, and its corresponding MCU includes MCU a and is a master MCU, so when allocating conference resources, SMC a obtains a conference number ID B of a slave MCU B and a conference number ID C of an MCU C for holding a conference, pairs the conference number ID a of the master MCU a and the conference number ID B of the slave MCU B, and stores them in the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU as shown in table 1; pairing the conference number ID A of the master MCU A with the conference number ID C of the slave MCU C and storing the paired conference numbers in the corresponding relation of the conference number of the master MCU and the conference number of the slave MCU shown in the table 1; then, the main conference number ID a of the main MCU, the terminal number 010001 of the conference site terminal 1 and the terminal number 010002 of the conference site terminal 2 which are accessed to the main MCU are stored in the correspondence relationship between the conference number of the MCU and the terminal number of the conference site terminal shown in table 2.
TABLE 1
Conference number of main MCU Conference number from MCU
ID A ID B
ID A ID C
TABLE 2
MCU conference number Terminal number of meeting place terminal
ID A
010001
ID A 010002
For SMC B, there is a slave MCU B corresponding to SMC B, and SMC B stores the conference number ID a of the master MCU a and the conference number ID B of the slave MCU B in the correspondence between the conference number of the master MCU and the conference number of the slave MCU as shown in table 3 when allocating conference resources. The conference number ID B of the slave MCU B and the terminal number 0755001 of the conference site terminal 3 are paired and stored in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 4, and the conference number ID B of the slave MCU B and the terminal number 0755002 of the conference site terminal 4 are paired and stored in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 4. When a conference is held, the SMC B obtains the meeting place information 3 of the meeting place terminal 3, the meeting place information 3 includes a cascade channel name and a channel number ID AB between the master MCU a and the slave MCU B, the cascade channel name includes the master conference number ID a of the master MCU and the slave conference number ID B of the slave MCU B, and the terminal number 0755001 of the meeting place terminal 3 is paired with the meeting place information 3 and stored in the correspondence between the terminal number and the meeting place information as shown in table 5; the conference place information 4 of the conference place terminal 4 is acquired, the conference place information 4 includes a cascade channel name and a channel number ID AB between the master MCU a and the slave MCU B, the cascade channel name includes a conference number ID a of the master MCU and a conference number ID B of the slave MCU B, and the terminal number 0755002 of the conference place terminal 4 is paired with the conference place information 4 and stored in the correspondence between the terminal number and the conference place information as shown in table 5.
TABLE 3
Conference number of main MCU Conference number from MCU
ID A ID B
TABLE 4
MCU conference number Terminal number of meeting place terminal
ID B
0755001
ID B 0755002
TABLE 5
Terminal number Meeting place information
0755001 Meeting place information 3
0755002 Meeting place information 4
For the SMC C, there is a slave MCU C corresponding to the SMC C, and the SMC C pairs and stores the conference number ID a of the master MCU a and the conference number ID C of the slave MCU C in the correspondence between the conference number of the master MCU and the conference number of the slave MCU as shown in table 6 when allocating conference resources. The conference number ID C of the slave MCU C and the terminal number 0512001 of the venue terminal 5 are paired and stored in the correspondence between the conference number of the MCU and the terminal number of the venue terminal as shown in table 7. When a conference is held, the SMC C obtains the meeting place information 5 of the meeting place terminal 5, where the meeting place information 5 includes a cascade channel name and a channel number ID AC between the master MCU a and the slave MCU C, the cascade channel name includes the conference number ID a of the master MCU and the conference number ID C of the slave MCU C, and the terminal number 0512001 of the meeting place terminal 5 is paired with the meeting place information 5 and stored in the correspondence between the terminal number and the meeting place information as shown in table 8.
TABLE 6
Conference number of main MCU Conference number from MCU
ID A ID C
TABLE 7
MCU conference number Terminal number of meeting place terminal
ID C
0512001
TABLE 8
Terminal number Meeting place information
0512001 Meeting place information 5
Among them, it should be noted that: each SMC in the video system also corresponds to at least one backup SMC, the backup SMC is used for backing up the SMC, and the corresponding relation between the conference number of the master MCU and the conference number of the slave MCU, the corresponding relation between the conference number of the MCU and the terminal number of the conference site terminal, and the corresponding relation between the terminal number and the conference site information are also stored in the backup SMC. And when any corresponding relation stored in the SMC sends an update, the backup SMC also synchronously updates.
For example, referring to fig. 1 to 3, SMC a corresponds to two backup SMCs, SMC a1 and SMC a2, respectively, and the correspondence between the conference number of the master MCU and the conference number of the slave MCU stored in SMC a as shown in table 1, and the correspondence between the conference number of the MCU and the terminal number of the venue terminal as shown in table 2 are stored in both SMC a1 and SMC a 2. The SMC B corresponds to two backup SMCs, which are SMC B1 and SMC B2, respectively, and the correspondence between the conference number of the master MCU and the conference number of the slave MCU, which is stored in the SMC B, as shown in table 3, the correspondence between the conference number of the MCU and the terminal number of the conference site terminal, as shown in table 4, and the correspondence between the terminal number and the conference site information, as shown in table 5, are stored in both SMC B1 and SMC B2.
In the process of holding the conference, when an abnormal condition occurs in a certain MCU or a certain SMC used for holding the conference, the conference may be interrupted and cannot be held continuously. In order to allow the conference to continue, the conference may be resumed by any of the following embodiments. Among them, it should be noted that: the MCU is abnormal, namely the MCU fails, the MCU is powered off, the MCU is restarted or the MCU is disconnected with other MCUs, SMCs or meeting place terminals for holding the conference; the abnormal SMC means the fault of the SMC, the power failure of the SMC, the restart of the SMC or the disconnection between the SMC and other SMCs or MCUs for holding the conference.
Referring to fig. 2, fig. 2 is a block diagram of a structure of an SMC200 according to an embodiment of the present invention, where the SMC200 is any one of the SMCs in the video system.
SMC200 may vary widely due to configuration or performance differences and may include one or more receivers 201, processors 202 and transmitters 203, one or more storage media 206 (e.g., one or more mass storage devices) storing applications 204 or data 205. Storage medium 206 may be, among other things, transient or persistent storage. The program stored on the storage medium 206 may include one or more modules (not shown), each of which may include a series of instruction operations. Still further, the processor 202 may be configured to communicate with the storage medium 206 to execute a series of instruction operations in the storage medium 206 on the SMC 200.
The SMC200 may also include one or more power supplies 207, one or more wired or wireless network interfaces 208, one or more input-output interfaces 209, and/or one or more operating systems 210, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and the like.
In the present invention, when the SMC200 is a master SMC or a slave SMC of a video system, the processor 202 of the SMC200 has the following functions:
the processor 202 is configured to determine, when detecting that a first multipoint control unit MCU used for holding a conference is abnormal, a first conference terminal accessed to the first MCU according to a correspondence between a stored conference number of the MCU and a terminal number of a conference terminal, where the first SMC is any SMC used for holding the conference; distributing a corresponding second MCU for the first meeting place terminal; and restoring the conference through the second MCU.
Optionally, the processor 202 is configured to allocate a conference number to the second MCU if the first MCU is not the master MCU;
the transmitter 203 is configured to transmit a terminal number of the first meeting place terminal and a meeting number of the main MCU to the second MCU, and transmit a meeting number of the second MCU to the main MCU, where the terminal number is used for the second MCU to establish a meeting connection with the first meeting place terminal, and the meeting number of the main MCU and the meeting number of the second MCU are used for the main MCU and the second MCU to establish a cascade channel between the main MCU and the second MCU, so as to recover the meeting.
Optionally, the transmitter 203 is configured to send, if the SMC200 is a slave SMC, a restoration request message to a master SMC corresponding to a domain where the master MCU is located, where the restoration request message carries a conference number of the second MCU and is used by the master SMC to send the conference number of the second MCU to the master MCU.
Optionally, the processor 202 is further configured to obtain meeting place information of the first meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the main MCU and the second MCU, and update meeting place information corresponding to the terminal number of the first meeting place terminal stored in the correspondence between the terminal number and the meeting place information to the obtained meeting place information.
Optionally, the processor 202 is configured to determine that the second MCU is a master MCU and allocate a conference number to the second MCU if the first MCU is the master MCU;
the transmitter 203 is configured to transmit a terminal number of the first meeting place terminal and a meeting number of each slave MCU used to hold the meeting to the second MCU, and transmit a meeting number of the second MCU to each slave MCU, where the terminal number is used for the second MCU to establish a meeting connection with the first meeting place terminal, and the meeting number of each slave MCU and the meeting number of the master MCU are used for the each slave MCU and the second MCU to establish a cascade channel between each slave MCU and the second MCU, respectively, so as to recover the meeting.
Optionally, the transmitter 203 is configured to send, if the slave MCU is an MCU included in a domain where the slave SMC is located, a resume request message to the slave SMC, where the resume request message carries a conference number of the second MCU and is used for the slave SMC to send a master conference number of the second MCU to the slave MCU.
Optionally, the processor 202 is further configured to determine each second meeting place terminal, which is accessed to the slave MCU included in the conference and located in the domain where the second meeting place terminal is located, obtain meeting place information of the second meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed to the second meeting place terminal and the second MCU, and update meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information. Alternatively, the first and second electrodes may be,
in the present invention, when the SMC200 is a backup SMC of a video system, the processor 202 of the SMC200 has the following functions:
the processor 202 is configured to, when detecting that a second SMC used for holding a conference is abnormal, determine a first venue terminal located in a domain corresponding to the second SMC and used for holding the conference, where the first SMC is a backup SMC of the second SMC; distributing a first multipoint control unit MCU for the first session terminal from the MCUs included in the corresponding domain; and restoring the conference through the first MCU.
Optionally, the processor 202 is further configured to assign a conference number to the first MCU if the second SMC is not a master SMC;
the transmitter 203 is configured to transmit a terminal number of the first meeting place terminal and a conference number of a main MCU used for holding the conference to the first MCU, and transmit the conference number of the first MCU to the main MCU, where the terminal number is used for the first MCU to establish a conference connection with the first meeting place terminal, and the conference number of the main MCU and the conference number of the first MCU are used for the main MCU and the first MCU to establish a cascade channel between the main MCU and the first MCU, so as to recover the conference.
Optionally, the processor 202 is further configured to obtain meeting place information of the first meeting place terminal, where the meeting place information includes a name and a channel number of a cascade channel between the first MCU and the main MCU, and store a corresponding relationship between a terminal number of the first meeting place terminal and the meeting place information.
Optionally, the processor 202 is configured to select an MCU from an MCU set as a master MCU if the second SMC is a master SMC, and allocate a conference number to the master MCU, where the MCU set includes an allocated first MCU;
the transmitter 203 is configured to transmit a terminal number of the corresponding first meeting place terminal to the master MCU, where the terminal number is used for the master MCU to establish a conference connection with the corresponding first meeting place terminal.
Optionally, the processor 202 is configured to determine an unselected second MCU as a first slave MCU, and allocate a conference number to the first slave MCU;
the transmitter 203 is configured to transmit the conference number of the first slave MCU to the master MCU; and sending the conference number of the master MCU and the terminal number of a first conference site terminal corresponding to the first slave MCU, wherein the terminal numbers are used for the first slave MCU to establish conference connection between the first conference site terminal corresponding to the first slave MCU, and the conference number of the master MCU and the conference number of the first slave MCU are used for the first slave MCU and the master MCU to establish a cascade channel between the first slave MCU and the master MCU.
Optionally, the processor 202 is further configured to determine a second slave MCU included in a slave SMC used for holding the conference;
the transmitter 203 is further configured to transmit the conference number of the master MCU to the second slave MCU, and transmit the conference number of the second slave MCU to the master MCU, where the conference number of the master MCU and the conference number of the second slave MCU are used for the master MCU and the second slave MCU to establish a cascade channel between the master MCU and the second slave MCU.
Optionally, the processor 202 is further configured to determine each second meeting place terminal, which is accessed to the slave MCU included in the conference and located in the domain where the second meeting place terminal is located, obtain meeting place information of the second meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed to the second meeting place terminal and the first MCU, and update meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information.
The embodiment of the invention provides a method for restoring a conference, and conference resources used by the conference comprise an SMC, an MCU and a plurality of conference place terminals accessed to the MCU, and the MCU is called as a first MCU for convenience of description. The SMC detects the first MCU, when the first MCU is detected to be abnormal, a second MCU is allocated to the plurality of meeting place terminals from other MCUs except the first MCU in the domain, the second MCU has idle resources, and the terminal number of each meeting place terminal in the plurality of meeting place terminals is sent to the second MCU; and the second MCU respectively establishes conference connection with each conference site terminal according to the terminal number of each conference site terminal so as to recover the conference.
The embodiment of the invention provides a method for recovering a conference, wherein conference resources used by the conference comprise a plurality of SMC (sheet molding compounds), a plurality of MCU (microprogrammed control unit) and a plurality of meeting place terminals. The method is applied to restoring the conference when an abnormality occurs in a slave MCU used for holding the conference. Referring to fig. 3-1, the method includes:
step 301: the first SMC detects the MCU in the domain where the first SMC is located for holding the conference, and executes step 302 when detecting that the first MCU is abnormal.
The first SMC is any SMC used for holding the conference, and detects abnormal MCUs by detecting heartbeat information transmitted between the first SMC and each MCU in the domain where the first SMC is located for holding the conference.
Step 302: and the first SMC determines the identity of the first MCU, and determines a first meeting place terminal accessed to the first MCU according to the stored corresponding relation of the conference number of the MCU and the terminal number of the meeting place terminal when the identity is determined as the slave MCU.
The first SMC can acquire the conference number of the first MCU, and the first SMC stores the corresponding relation between the conference number of the master MCU and the conference number of the slave MCU, and the corresponding relation between the conference number of the MCU and the terminal number of the conference site terminal. Correspondingly, the steps can be as follows:
the first SMC judges whether the conference number of the main MCU stored in the corresponding relation between the conference number of the main MCU and the conference number of the slave MCU includes the conference number of the first MCU, and determines that the identity of the first MCU is the slave MCU if the judged result is not included, then acquires the terminal number of the corresponding conference site terminal from the corresponding relation between the stored conference numbers of the MCU and the terminal numbers of the conference site terminals according to the conference number of the first MCU, and determines the first conference site terminal corresponding to the acquired terminal number.
For example, the SMC B stores therein a correspondence between the conference number of the master MCU and the conference number of the slave MCU as shown in table 3, and a correspondence between the conference number of the MCU and the terminal number of the venue terminal as shown in table 4. In this step, the SMC B may obtain that the conference number of the MCU B is ID B, determine that the conference number of the master MCU stored in the correspondence between the conference number of the master MCU and the conference number of the slave MCU shown in table 3 does not include the conference number of the MCU B, thereby determine that the identity of the MCU B is the slave MCU, and obtain, according to the conference number ID B of the MCU B, a terminal number 0755001 of the corresponding conference site terminal 3 and a terminal number 0755002 of the conference site terminal 4 from the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 4, where the conference site terminal 3 corresponding to the terminal number 0755001 and the conference site terminal 4 corresponding to the terminal number 0755002 are the first conference site terminal accessed to the MCU B.
Step 303: and the first SMC allocates a second MCU for the first session terminal.
Specifically, the first SMC judges whether the MCU with idle resources exists in the other MCUs except the first MCU in the domain where the first SMC is located, and if the MCU with idle resources exists, the first SMC allocates a corresponding second MCU to each first session terminal from the MCU with idle resources; and if the MCU with the idle resources is judged not to be included, the conference recovery fails, and the operation is finished.
For example, suppose that the domain in which SMC B resides includes MCU D and MCU E in addition to MCU B, and both MCU D and MCU E have idle resources. In this way, the SMC B allocates second MCUs from the MCUs D and E to the venue terminal 3 and the venue terminal 4, respectively, assuming that the allocated second MCUs are both the MCUs D.
Step 304: and the first SMC sends a connection establishment request message to the second MCU, wherein the connection establishment request message carries the terminal number of the first meeting place terminal and the conference number of the main MCU.
Specifically, the first SMC obtains the corresponding conference number of the master MCU from the correspondence between the conference number of the master MCU and the conference number of the slave MCU according to the conference number of the first MCU, and sends a connection establishment request message to the second MCU, where the connection establishment request message carries the terminal number of the first conference terminal and the conference number of the master MCU.
Step 305: and the second MCU receives the connection establishment request message and establishes conference connection with the first meeting place terminal according to the terminal number of the first meeting place terminal carried by the connection establishment request message.
For example, the SMC B obtains the conference number ID a of the master MCU a from the correspondence between the conference number of the master MCU and the conference number of the slave MCU as shown in table 3 according to the conference number ID B of the MCU B, and sends a connection establishment request message to the MCU D, where the connection establishment request message carries the conference number ID a of the master MCU a, the terminal number 0755001 of the conference site terminal 3, and the terminal number 0755002 of the conference site terminal 4. The MCU D receives the connection establishment request message, establishes a conference connection with the conference site terminal 3 according to the terminal number 0755001 of the conference site terminal 3, and establishes a conference connection with the conference site terminal 4 according to the terminal number 0755002 of the conference site terminal 4.
Step 306: and if the first SMC is a slave SMC, the first SMC sends a recovery request message to a master SMC corresponding to the domain where the master MCU is located, wherein the recovery request message carries the conference number of the second MCU.
Specifically, if the first SMC is a slave SMC, the second MCU is also a slave MCU, the first SMC allocates a conference number to the second MCU, determines a master SMC corresponding to a domain where the master MCU is located, and sends a resume request message to the master SMC, where the resume request message carries the conference number of the second MCU. Further, the recovery request message also carries the conference number of the master MCU and the conference number of the first MCU.
Further, the first SMC may further obtain a correspondence relationship between the conference number of the master MCU and the conference number of the first MCU from the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU, and update the conference number of the first MCU stored in the obtained correspondence relationship to the conference number of the second MCU.
Further, the first SMC may further obtain a correspondence between the conference number of the first MCU and the terminal number of the first conference site terminal from the correspondence between the conference number of the MCU and the terminal number of the conference site terminal, and update the conference number of the first MCU stored in the obtained correspondence to the conference number of the second MCU.
If the SMC B is not a master SMC but a slave SMC, the identity of the MCU D is a slave MCU, the SMC B allocates a conference number ID D for the MCU D, determines that the master SMC corresponding to the domain where the master MCU A is located is SMC A, and sends a recovery request message to the SMC A, wherein the recovery request message carries the conference number ID D of the MCU D, the conference number ID B of the MCU B and the conference number ID A of the master MCU A.
Further, the SMC B may further obtain a correspondence relationship between the conference number ID a of the master MCU a and the conference number ID B of the slave MCU B from the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU shown in table 3, update the conference number ID B of the slave MCU B stored in the obtained correspondence relationship to the conference number ID D of the MCU D, and the updated result is shown in table 9.
TABLE 9
Conference number of main MCU Conference number from MCU
ID A ID D
Further, the SMC B may further obtain, from the correspondence between the conference number of the MCU and the terminal number of the meeting place terminal shown in table 4, a correspondence 1 including the conference number ID B of the MCU B and the terminal number 0755001 of the meeting place terminal 1, and a correspondence 2 including the conference number ID B of the MCU B and the terminal number 0755002 of the meeting place terminal 2; the acquired conference number ID B of the MCU B stored in the correspondence relationship 1 and the correspondence relationship 2 is updated to the conference number ID D of the MCU D, respectively, and the updated results are shown in table 10.
Watch 10
MCU conference number Terminal number of meeting place terminal
ID D
0755001
ID D 0755002
Step 307: and the main SMC receives the recovery request message and sends the recovery request message to the main MCU.
Specifically, the host SMC receives the recovery request message, and sends the recovery request message to the host MCU according to the conference number of the host MCU carried in the recovery request message.
Further, the master SMC may further obtain, from the correspondence between the conference number of the master MCU and the conference number of the slave MCU, a correspondence including the conference number of the master MCU and the conference number of the first MCU, and update the conference number of the first MCU stored in the obtained correspondence to the conference number of the second MCU.
For example, the SMC a receives a restoration request message, which carries the conference number ID D of the MCU D, the conference number ID B of the MCU B, and the conference number ID a of the master MCU a, and sends the restoration request message to the master MCU a according to the conference number ID a of the master MCU a.
Further, the correspondence relationship between the conference number of the master MCU a and the conference number of the MCU B, which is shown in table 1, may be obtained from the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU, the conference number ID B of the MCU B stored in the correspondence relationship is updated to the conference number ID D of the MCU D, and the update result is shown in table 11.
TABLE 11
Conference number of main MCU Conference number from MCU
ID A ID D
ID A ID C
Step 308: and if the first SMC is a master SMC, the first SMC sends a recovery request message to the master MCU, wherein the recovery request message carries the conference number of the second MCU.
Step 309: the main MCU receives the recovery request message, establishes a cascade channel from the main MCU to the second MCU according to the conference number of the second MCU carried by the recovery request message, and establishes a cascade channel from the second MCU to the main MCU according to the conference number of the main MCU.
For example, the MCU a receives the resume request message, which carries the conference number ID D of the MCU D, and then the MCU a establishes the cascade channel from the MCU a to the MCU D according to the conference number ID D of the MCU D, and the MCU D establishes the cascade channel from the MCU D to the MCU a according to the conference number ID a of the MCU a, as shown in fig. 3-2.
Further, the first SMC also obtains meeting place information of the first meeting place terminal, where the meeting place information includes a name and a channel number of a cascade channel between the main MCU and the second MCU, obtains a corresponding relationship including a terminal number of the first meeting place terminal from a corresponding relationship between the terminal number and the meeting place information, and updates the meeting place information stored in the obtained corresponding relationship to the obtained meeting place information.
For example, the SMC B obtains meeting place information 6 of the meeting place terminal 3, where the meeting place information 6 includes a cascade channel name and a channel number between the host MCU a and the MCU D, obtains a correspondence relationship including the terminal number 0755001 of the meeting place terminal 3 from the correspondence relationship between the terminal number and the meeting place information shown in table 5, and updates the meeting place information 3 stored in the obtained correspondence relationship to the meeting place information 6; meeting place information 7 of meeting place terminal 4 is acquired, the meeting place information 7 includes a name and a channel number of a cascade channel between main MCU a and MCU D, a correspondence including terminal number 0755002 of meeting place terminal 4 is acquired from the correspondence between terminal numbers and meeting place information shown in table 5, meeting place information 4 stored in the acquired correspondence is updated to meeting place information 7, and the obtained update result is shown in table 12.
TABLE 12
Terminal number Meeting place information
0755001 Meeting place information 6
0755002 Meeting place information 7
In the embodiment of the invention, when a slave MCU is abnormal, a first meeting place terminal accessed to the slave MCU is obtained, a corresponding second MCU is distributed to the first meeting place terminal, the terminal number of the first meeting place terminal and the conference number of the master MCU are sent to the second MCU, so that the second MCU establishes conference connection with the first meeting place terminal, the conference number of the second MCU is sent to the master MCU, and the master MCU and the second MCU establish a mutual cascade channel, thereby recovering the interrupted conference.
The embodiment of the invention provides a method for recovering a conference, wherein conference resources used by the conference comprise a plurality of SMC (sheet molding compounds), a plurality of MCU (microprogrammed control unit) and a plurality of meeting place terminals. The method is applied to restoring the conference when the main MCU for holding the conference is abnormal. Referring to fig. 4-1, the method includes:
step 401: the same as in step 301, and will not be described in detail here.
For example, for a master SMC a as in fig. 1-2, SMC a detects that MCU a is abnormal.
Step 402: and the first SMC determines the identity of the first MCU, and determines a first meeting place terminal accessed to the first MCU according to the stored corresponding relation of the conference number of the MCU and the terminal number of the meeting place terminal when the first SMC determines the MCU as the main MCU.
The first SMC stores the corresponding relation between the conference number of the master MCU and the conference number of the slave MCU, and the corresponding relation between the conference number of the MCU and the terminal number of the conference site terminal. Correspondingly, the steps can be as follows:
the first SMC judges whether the conference number of the first MCU is included in the conference numbers of the main MCU stored in the corresponding relation between the conference number of the main MCU and the conference number of the slave MCU, if so, the identity of the first MCU is determined to be the main MCU, then the terminal number of the corresponding conference place terminal is obtained from the corresponding relation between the terminal numbers of the saved conference place terminals of the MCU according to the conference number of the first MCU, and the first conference place terminal corresponding to the obtained terminal number is determined.
For example, the SMC a stores the correspondence between the conference number of the master MCU and the conference number of the slave MCU, and the correspondence between the conference number of the MCU and the terminal number of the venue terminal, as shown in table 1. In this step, the SMC B determines that the conference number of the master MCU stored in the correspondence relationship between the conference number of the master MCU in table 1 and the conference number of the slave MCU includes the conference number ID a of the MCU a, and determines that the identity of the MCU a is the master MCU, and obtains the terminal number 010001 of the corresponding conference site terminal 1 and the terminal number 010002 of the conference site terminal 2 from the correspondence relationship between the conference number of the MCU and the terminal number of the conference site terminal shown in table 2 according to the conference number ID a of the MCU a, where the conference site terminal 1 corresponding to the terminal number 010001 and the conference site terminal 2 corresponding to the terminal number 010002 are the first conference site terminal accessed to the MCU a.
Step 403: as in step 303, this will not be described in detail.
For example, suppose that the domain in which SMC a is located includes MCU F and MCU G in addition to MCU a, and both MCU F and MCU G have idle resources. In this way, the SMC a allocates second MCUs from the MCUs F and G to the meeting place terminal 1 and the meeting place terminal 2, respectively, and it is assumed that the allocated second MCUs are both the MCUs F.
Step 404: and the first SMC sets the identity of the second MCU as a master MCU and sends a connection establishment request message to the second MCU, wherein the connection establishment request message carries the terminal number of the first meeting place terminal and the conference number of each slave MCU for holding the conference.
Specifically, the first SMC determines that the identity of the second MCU is the master MCU, obtains, according to the conference number of the first MCU, the conference number of each slave MCU used for holding the conference from the correspondence between the conference of the master MCU and the conference number of the slave MCU, and sends a connection establishment request message to the second MCU, where the connection establishment request message carries the terminal number of the first venue terminal and the conference number of each slave MCU used for holding the conference.
Further, the first SMC may further obtain a correspondence relationship between the conference number of the first MCU and the conference number of the slave MCU from the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU, and update the conference number of the first MCU stored in the obtained correspondence relationship to the conference number of the second MCU.
Further, the first SMC may further obtain a correspondence between the conference number of the first MCU and the terminal number of the first conference site terminal from the correspondence between the conference number of the MCU and the terminal number of the conference site terminal, and update the conference number of the first MCU stored in the obtained correspondence to the conference number of the second MCU.
For example, since the MCU a is the master MCU, the conference number of the slave MCU for holding the conference, including the conference number ID B of the MCU B and the conference number ID C of the MCU C, is obtained from the correspondence between the conference number of the master MCU and the conference number of the slave MCU as shown in table 1 according to the conference number ID a of the MCU a, and then a connection establishment request message is sent to the MCU F, where the connection establishment request message carries the terminal number 010001 of the conference site terminal 1, the terminal number 010002 of the conference site terminal 2, the conference number ID B of the MCU B, and the conference number ID C of the MCU C.
The SMC a further obtains the correspondence relationship including the conference number ID a of the MCU a from the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU shown in table 1, updates the conference number ID a of the MCU a stored in the obtained correspondence relationship to the conference number ID F of the MCU F, and the update result is shown in table 13.
Watch 13
Conference number of main MCU Conference number from MCU
ID F ID B
ID F ID C
The SMC a may further obtain a correspondence relationship including the conference number ID a of the MCU a from the correspondence relationship between the conference number of the MCU and the terminal number of the conference site terminal shown in table 2, update the conference number ID a of the MCU a stored in the obtained correspondence relationship to the conference number ID F of the MCU F, and the update result is shown in table 14.
TABLE 14
MCU conference number Terminal number of meeting place terminal
ID F
010001
ID F 010002
Step 405: as with step 305, this will not be described in detail.
For example, the MCU F establishes a conference connection with the conference site terminal 1 and a conference connection with the conference site terminal 2, respectively, based on the terminal number 010001 of the conference site terminal 1 and the terminal number 010002 of the conference site terminal 2 carried in the connection establishment request message.
Step 406: and the first SMC sends a recovery request message to a slave SMC for holding the conference, wherein the recovery request message carries the conference number of the second MCU.
Specifically, the first SMC determines a slave SMC corresponding to a slave MCU for holding the conference, and sends a recovery request message to the slave SMC, wherein the recovery request message carries the conference number of the second MCU and the conference number of the slave MCU.
For example, the SMC A determines an SMC B corresponding to the MCU B, and sends a recovery request message to the SMC B, wherein the recovery request message carries the conference number ID F of the MCU F and the conference number ID B of the MCU B; and determining the SMC C corresponding to the slave MCU C, and sending a recovery request message to the SMC C, wherein the recovery request message carries the conference number ID F of the MCU F and the conference number ID C of the slave MCU C.
Step 407: the resume request message is received from the SMC, and is transmitted to each slave MCU for holding the conference.
Specifically, the slave SMC receives the recovery request message, and sends the recovery request message to the slave MCU according to the conference number of the slave MCU carried in the recovery request message.
Step 408: and the slave MCU receives the recovery request message, establishes a cascade channel from the MCU to the second MCU according to the conference number of the second MCU carried by the recovery request message, and establishes a cascade channel from the second MCU to the slave MCU according to the conference number of the slave MCU.
For example, the SMC B receives the recovery request message, and sends the recovery request message to the MCUB according to the conference number ID B of the MCU B carried in the recovery request message. The MCU B receives the recovery request message, and establishes a cascade channel between the MCU F and the MCU B according to the conference number ID F of the MCU F carried by the recovery request message and the conference number ID B of the MCU F according to the MCU B; the SMC receives the recovery request message, and sends the recovery request message to the MCU C according to the conference number ID C of the MCU C carried by the recovery request message. The MCU C receives the recovery request message, establishes a cascade channel from the MCU C to the MCU F according to the conference number ID F of the MCU F carried by the recovery request message, and establishes a cascade channel from the MCU F to the MCU C according to the conference number ID C of the MCU C, and the established cascade channel is as shown in figure 4-2.
Further, the slave SMC also acquires meeting place information of the meeting place terminal accessed to the slave MCU, acquires a corresponding relationship including the terminal number of the meeting place terminal from the corresponding relationship between the terminal number and the meeting place information, and updates the meeting place information stored in the acquired corresponding relationship to the acquired meeting place information.
In the embodiment of the invention, when a certain main MCU is abnormal, a first meeting place terminal accessed to the main MCU is obtained, a corresponding second MCU is distributed to the first meeting place terminal, the terminal number of the first meeting place terminal and the conference number of each slave MCU are sent to the second MCU, so that the second MCU establishes conference connection with the first meeting place terminal, the conference number of the second MCU is sent to each slave MCU, and the second MCU and each MCU establish a mutual cascade channel, thereby recovering the interrupted conference.
The embodiment of the invention provides a method for restoring a conference, and conference resources used by the conference comprise an SMC, an MCU and a plurality of conference place terminals accessed to the MCU, and the SMC is called as a first SMC for convenience of description. The first SMC corresponds to at least one backup SMC, and each backup SMC detects the first SMC. When a backup SMC detects that a first SMC is abnormal, the backup SMC allocates a first MCU to the meeting place terminals from the MCU in the domain where the backup SMC is located, and transmits the terminal number of each meeting place terminal in the meeting place terminals to the first MCU; and the first MCU respectively establishes conference connection with each meeting place terminal according to the terminal number of each meeting place terminal so as to recover the conference.
The embodiment of the invention provides a method for recovering a conference, wherein conference resources used by the conference comprise a plurality of SMC (sheet molding compounds), a plurality of MCU (microprogrammed control unit) and a plurality of meeting place terminals. The method is applied to restoring a conference when an exception occurs in a certain slave SMC used for holding the conference. Referring to fig. 5-1, the method includes:
step 501: the first SMC detects a second SMC, and if an abnormality in the second SMC is detected, step 502 is executed, where the first SMC is a backup SMC for the second SMC, and the second SMC is a slave SMC.
The second SMC is any slave SMC for holding the conference, and the first SMC is one of at least one backup SMC corresponding to the second SMC. The first SMC detects whether the second SMC is abnormal or not by detecting heartbeat information transmitted between the first SMC and the second SMC.
Wherein, the backup SMCs of the second SMC can send the sizes of the idle conference resources which are currently managed by each other.
Further, when the first SMC detects that the second SMC is abnormal, the first SMC judges whether the idle conference resources currently managed in the backup SMC of the second SMC are the most, and if so, the subsequent steps are executed.
For example, with respect to SMC B1 shown in fig. 1-3, SMC B1 detects an anomaly in SMC B by detecting heartbeat information transmitted with SMC B.
Step 502: and the first SMC determines a first meeting place terminal which is positioned in a domain corresponding to the second SMC and used for holding the meeting.
Specifically, the first SMC obtains the stored terminal number of the meeting place terminal from the stored correspondence between the meeting number of the MCU and the terminal number of the meeting place terminal, and determines the first meeting place terminal corresponding to the obtained terminal number.
For example, the SMC B1 obtains the stored terminal number 0755001 of the conference site terminal 3 and the terminal number 0755002 of the conference site terminal 4 from the correspondence between the conference number stored in the MCU and the terminal number of the conference site terminal shown in table 4, and specifies the conference site terminal 4 corresponding to the acquired terminal number 0755001 and the conference site terminal 3 corresponding to the terminal number 0755002.
Step 503: and the first SMC allocates a first MCU for the first session terminal from the MCUs included in the corresponding domain.
Further, the first SMC allocates a conference number to the first MCU when allocating the first MCU.
For example, assume that the domain corresponding to SMC B1 includes MCU D and MCU E, SMC B1 allocates the first MCUs from MCU D and MCU E for venue terminal 3 and venue terminal 4, respectively, and assumes that all the allocated MCUs are MCU D.
Step 504: and the first SMC sends a connection establishment request message to the first MCU, wherein the connection establishment request message carries the terminal number of the first meeting place terminal and the conference number of the main MCU for holding the conference.
Specifically, the first SMC obtains a conference number of a second MCU, to which the first conference terminal is accessed, from a corresponding relationship between the conference number of the MCU and a terminal number of the conference site terminal, obtains a conference number of a corresponding master MCU from a corresponding relationship between the conference number of the master MCU and the conference number of the slave MCU according to the conference number of the second MCU, and sends a connection establishment request message to the first MCU, where the connection establishment request message carries the terminal number of the first conference terminal and the conference number of the master MCU.
For example, the SMC B1 obtains the second MCU as MCU B from the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 4 according to the terminal number 0755001 of the conference site terminal 3, obtains the conference number of the master MCU a as ID a from the correspondence between the conference number of the master MCU and the conference number of the slave MCU as shown in table 3 according to the conference number ID B of the MCU B, and sends a connection establishment request message to the MCU D, where the connection establishment request message carries the terminal number 0755001 of the conference site terminal 3, the terminal number 0755002 of the conference site terminal 4, and the conference number ID a of the MCU a.
Step 505: and the first SMC sends a recovery request message to a main SMC corresponding to the domain where the main MCU is located, wherein the recovery request message carries the conference number of the first MCU.
Further, the recovery request message also carries the conference number of the master MCU and the conference number of the second MCU.
Further, the first SMC may also clear the content stored in the correspondence between the conference number of the master MCU and the conference number of the slave MCU, pair the conference number of the master MCU with the conference number of the first MCU, and store the paired conference number in the correspondence between the conference number of the master MCU and the conference number of the slave MCU.
Further, the first SMC may also empty content stored in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal, pair the conference number of the first MCU with the terminal number of the first conference site terminal, and store the paired conference number of the first MCU in the correspondence between the conference number of the slave MCU and the terminal number of the conference site terminal.
For example, the SMC B1 sends a recovery request message to the SMC a corresponding to the domain where the host MCU a is located, where the recovery request message carries the conference number ID D of the MCU D, the conference number ID a of the host MCU a, and the conference number ID B of the MCU B. The contents stored in the correspondence between the conference number of the master MCU and the conference number of the slave MCU shown in table 3 are cleared, and the conference number ID a of the master MCU a and the conference number ID D of the slave MCU D are paired and stored in the correspondence between the conference number of the master MCU and the conference number of the slave MCU shown in table 15.
Watch 15
Conference number of main MCU Conference number from MCU
ID A ID D
Further, the SMC B1 may also clear the content stored in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 4, pair and store the conference number ID D of the MCU D and the terminal number 0755001 of the conference site terminal 1 in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 16, and pair and store the conference number ID D of the MCU D and the terminal number 0755002 of the conference site terminal 2 in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal shown in table 16.
TABLE 16
MCU conference number Terminal number of meeting place terminal
ID D
0755001
ID D 0755002
Step 506: and the first MCU receives the connection establishment request message and establishes conference connection with the first meeting place terminal according to the terminal number of the first meeting place terminal carried by the connection establishment request message.
For example, the MCU D receives the connection establishment request message, which carries the terminal number 0755001 of the conference site terminal 3, the terminal number 0755002 of the conference site terminal 4, and the conference number ID a of the MCU a; the conference connection between the conference site terminals 3 and the conference connection between the conference site terminals 4 are established based on the terminal number 0755001 of the conference site terminal 3 and the terminal number 0755002 of the conference site terminal 4, respectively.
Step 507: and the main SMC receives the recovery request message and sends the recovery request message to the main MCU.
The host SMC may send the restoration request message to the host MCU according to the conference number of the host MCU carried in the restoration request message.
Further, the master SMC obtains a correspondence relationship between the conference number of the master MCU and the conference number of the second MCU from the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU, and updates the conference number of the second MCU stored in the obtained correspondence relationship to the conference number of the first MCU.
For example, the SMC a receives the recovery request message, and sends the recovery request message to the host MCU a according to the conference number ID a of the host MCU a carried in the recovery request message. Further, the correspondence relationship between the conference number of the master MCU a and the conference number of the MCU B may be obtained from the conference numbers of the master MCU and the slave MCUs shown in table 1, the conference number of the MCU B stored in the correspondence relationship is updated to the conference number ID D of the MCU D, and the update result is shown in table 17.
TABLE 17
Conference number of main MCU Conference number from MCU
ID A ID D
ID A ID C
Step 508: the main MCU receives the recovery request message, establishes a cascade channel from the main MCU to the first MCU direction according to the conference number of the first MCU carried by the recovery request message, and establishes a cascade channel from the main MCU to the first MCU direction according to the conference number of the main MCU.
For example, the MCU a receives the resume request message, which carries the conference number ID D of the MCU D, and then the MCU a establishes the cascade channel from the MCU a to the MCU D according to the conference number ID D of the MCU D, and the MCU D establishes the cascade channel from the MCU D to the MCU a according to the conference number ID a of the MCU a, as shown in fig. 5-2.
Further, the first SMC also obtains meeting place information of the first meeting place terminal, where the meeting place information includes a name and a channel number of a cascade channel between the main MCU and the second MCU, obtains a corresponding relationship including a terminal number of the first meeting place terminal from a corresponding relationship between the terminal number and the meeting place information, and updates the meeting place information stored in the obtained corresponding relationship to the obtained meeting place information.
For example, SMC B1 obtains meeting place information 6 of meeting place terminal 3, where meeting place information 6 includes the name and channel number of the cascade channel between host MCU a and MCU D, obtains the correspondence including terminal number 0755001 of meeting place terminal 3 from the correspondence between the terminal number and the meeting place information shown in table 5, and updates meeting place information 3 stored in the obtained correspondence to meeting place information 6; meeting place information 7 of meeting place terminal 4 is acquired, the meeting place information 7 includes a name and a channel number of a cascade channel between main MCU a and MCU D, a correspondence including terminal number 0755002 of meeting place terminal 4 is acquired from the correspondence between terminal numbers and meeting place information shown in table 5, meeting place information 4 stored in the acquired correspondence is updated to meeting place information 7, and the obtained update result is shown in table 18.
Watch 18
Terminal number Meeting place information
0755001 Meeting place information 6
0755002 Meeting place information 7
Further, the first SMC also sends a notification message to each backup SMC except the first SMC in the backup SMCs of the second SMC. And after each other backup SMC receives the notification message, the first SMC is backed up and updated according to the corresponding relation saved by the first SMC.
In the embodiment of the invention, when a certain slave SMC is abnormal, a first meeting place terminal which is positioned in a corresponding domain of the slave SMC and used for holding a conference is obtained, a corresponding first MCU is distributed to the first meeting place terminal, the terminal number of the first meeting place terminal and the conference number of a main MCU are sent to the first MCU, the first MCU establishes conference connection with the first meeting place terminal, the conference number of the first MCU is sent to the main MCU, and the main MCU and the first MCU establish a mutual cascade channel, so that the interrupted conference is recovered.
The embodiment of the invention provides a method for recovering a conference, wherein conference resources used by the conference comprise a plurality of SMC (sheet molding compounds), a plurality of MCU (microprogrammed control unit) and a plurality of meeting place terminals. The method is applied to restoring the conference when the abnormality occurs in the main SMC for holding the conference. Referring to fig. 6-1, the method includes:
step 601: the first SMC detects a second SMC, and if an abnormality in the second SMC is detected, step 602 is executed, where the first SMC is a backup SMC for the second SMC, and the second SMC is a master SMC.
The second SMC is a master SMC for holding the conference, and the first SMC is one of at least one backup SMC corresponding to the second SMC. The detailed procedure of the detection of the second SMC by the first SMC is described in step 501, and is not described in detail herein.
For example, with respect to SMC a1 shown in fig. 1-3, SMC a1 detects an anomaly in SMC a by detecting heartbeat information transmitted with SMC a.
Step 602: as with step 502, this will not be described in detail.
For example, SMC a1 obtains the stored terminal number 010001 of conference terminal 1 and terminal number 010002 of conference terminal 2 from the correspondence between the conference number and the terminal number of the conference terminal that stores the MCU shown in table 2, and specifies the conference terminal 2 corresponding to the acquired terminal number 010001 and the terminal number 010002.
Step 603: as with step 503, this will not be described in detail.
For example, assume that the domain corresponding to SMC a1 includes MCU F and MCU G, SMC a1 allocates the first MCUs from MCU F and MCU G for venue terminal 1 and venue terminal 2, respectively, and assumes that the allocated MCUs are both MCU F.
Step 604: the method comprises the steps that a first SMC selects a master MCU from an MCU set, other unselected MCUs in the MCU set are determined to be first slave MCUs, and a second slave MCU included in a slave SMC used for holding the conference is determined, wherein the MCU set comprises the allocated first MCU.
For example, the SMC a1 determines the MCU F as the master MCU, and acquires the slave MCU B included in the SMC B for holding the conference and the slave MCU C included in the SMC C for holding the conference.
Further, the first SMC may also clear content stored in a correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU, pair and store the conference number of the first MCU and the conference number of the first slave MCU in the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU, and pair and store the conference number of the first MCU and the conference number of the second slave MCU in the correspondence relationship between the conference number of the master MCU and the conference number of the slave MCU.
Further, the first SMC may also empty the content stored in the correspondence between the conference number of the MCU and the terminal number of the conference site terminal, pair the conference number of the first MCU with the terminal number of the conference site terminal corresponding to the first MCU, and store the correspondence between the conference number of the MCU and the terminal number of the conference site terminal.
Step 605: and the first SMC sends a connection establishment request message to the master MCU, wherein the connection establishment request message carries the terminal number of the first meeting place terminal, the conference number of the first slave MCU and the conference number of the second slave MCU corresponding to the master MCU.
For example, SMC a1 transmits to MCU F a connection establishment request message carrying terminal number 010001 of conference site terminal 1, terminal number 010002 of conference site terminal 2, conference number ID B of MCU B, and conference number ID C of MCU C.
Step 606: and the first SMC sends a connection establishment request message to the first slave MCU, wherein the connection establishment request message carries the terminal number of the first session terminal corresponding to the first slave MCU and the conference number of the master MCU.
Step 607: and the first SMC sends a recovery request message to a slave SMC corresponding to the domain where the second slave MCU is located, wherein the recovery request message carries the conference number of the master MCU.
Further, the recovery request message may also carry a conference number of the second slave MCU. For example, the SMC a1 sends a recovery request message to the slave SMC B corresponding to the domain where the MCU B is located, where the recovery request message carries the conference number ID F of the MCU F and the conference number ID B of the MCU B; and sending a recovery request message to the slave SMC C corresponding to the domain where the MCU C is located, wherein the recovery request message carries the conference number ID F of the MCU F and the conference number ID C of the MCU C.
Step 608: and the main MCU receives the connection establishment request message and establishes conference connection with the first meeting place terminal according to the connection establishment request message carrying the terminal number of the corresponding first meeting place terminal.
For example, the MCU F receives the connection establishment request message, where the connection establishment request message carries the terminal number 010001 of the conference terminal 1, the terminal number 010002 of the conference terminal 2, the conference number ID B of the MCU B, and the conference number ID C of the MCU C; and respectively establishing conference connection between the conference site terminals 1 and conference connection between the conference site terminals 2 according to the terminal number 010001 of the conference site terminal 1 and the terminal number 010002 of the conference site terminal 2.
Step 609: the first slave MCU receives the connection establishment request message, establishes conference connection with the first meeting place terminal according to the connection establishment request message carrying the terminal number of the corresponding first meeting place terminal, establishes a cascade channel from the first slave MCU to the master MCU according to the conference number of the master MCU, and establishes a cascade channel from the master MCU to the first slave MCU according to the conference number of the first slave MCU.
Step 610: and receiving the recovery request message from the SMC, and transmitting the recovery request message to the second slave MCU.
The slave SMC may send the resume request message to the second slave MCU according to the conference number of the second slave MCU carried in the resume request message.
Further, the slave SMC also obtains a corresponding relationship including the conference number of the second slave MCU from the corresponding relationship between the conference number of the master MCU and the conference number of the slave MCU, and updates the conference number of the master MCU stored in the obtained corresponding relationship to the conference number of the master MCU carried in the resume request message.
For example, the SMC B receives a recovery request message, the recovery request message carries the conference number ID F of the MCU F and the conference number ID B of the MCU B, and the recovery request message is sent to the MCU B according to the conference number ID B of the MCU B; the SMC receives a recovery request message, the recovery request message carries the conference number ID F of the MCU F and the conference number ID C of the MCU C, and the recovery request message is sent to the MCU C according to the conference number ID C of the MCU C.
Step 611: and the second slave MCU receives the recovery request message, establishes a cascade channel from the second slave MCU to the master MCU according to the conference number of the master MCU carried in the recovery request message, and establishes a cascade channel from the master MCU to the second slave MCU according to the conference number of the second slave MCU.
For example, the MCU B receives a recovery request message, where the recovery request message carries a conference number ID F of the MCUF, and then the MCU B establishes a cascade channel from the MCU B to the MCU F according to the conference number ID F of the MCU F, and the MCUF establishes a cascade channel from the MCUF to the MCUB according to the conference number ID B of the MCUB; the MCU C receives the resume request message, which carries the conference number ID F of the MCU F, and then the MCU C establishes a cascade channel from the MCU C to the MCU F direction according to the conference number ID F of the MCU F, and the MCU F establishes a cascade channel from the MCU F to the MCU C direction according to the conference number ID C of the MCU C, as shown in fig. 6-2.
Further, the first SMC also sends a notification message to each backup SMC except the first SMC in the backup SMCs of the second SMC. And after each other backup SMC receives the notification message, the first SMC is backed up and updated according to the corresponding relation saved by the first SMC.
In the embodiment of the invention, when the main SMC is abnormal, a first meeting place terminal which is positioned in a corresponding domain of the main SMC and used for holding a meeting is obtained, a corresponding first MCU is distributed to the first meeting place terminal, a main MCU is selected from the first MCUs, the terminal number of the corresponding first meeting place terminal, the meeting number of the unselected first slave MCU and the meeting number of a second slave MCU in the slave SMC are sent to the main MCU, the main MCU is enabled to establish meeting connection with the first meeting place terminal, the main MCU respectively establishes mutual cascade channels with the first slave MCU and the second slave MCU, and the interrupted meeting is recovered.
Referring to fig. 7, an embodiment of the present invention provides an apparatus 700 for restoring a conference, which can be used to perform the method for restoring a conference in the method embodiment shown in fig. 3-1 or 4-1, where the apparatus 700 is applied to a video system, and the apparatus 700 includes: a determination unit 701, an allocation unit 702, and a recovery unit 703;
the determining unit 701 is configured to determine, when a first multipoint control unit MCU used for holding a conference and having an abnormality is determined, a first conference terminal accessed to the first MCU according to a correspondence relationship between a conference number of the stored MCU and a terminal number of a conference terminal; alternatively, the determining unit 701 may determine the first session terminal according to the operation of step 302 in the method embodiment shown in fig. 3-1 or according to the operation of step 402 in the method embodiment shown in fig. 4-1.
The allocating unit 702 is configured to allocate a corresponding second MCU to the first session terminal; alternatively, the allocating unit 702 may allocate the second MCU according to the operation of step 303 in the method embodiment shown in fig. 3-1 or according to the operation of step 403 in the method embodiment shown in fig. 4-1.
The recovery unit 703 is configured to recover the conference through the second MCU. Optionally, the recovery unit 703 may recover the conference according to the operation of step 304 and 309 in the method embodiment shown in fig. 3-1 or according to the operation of step 404 and 408 in the method embodiment shown in fig. 4-1.
Optionally, the apparatus 700 further includes a sending unit;
the recovery unit 703 is configured to allocate a conference number to the second MCU if the first MCU is not the master MCU;
the sending unit is used for sending the terminal number of the first meeting place terminal and the meeting number of the main MCU to the second MCU, sending the meeting number of the second MCU to the main MCU, wherein the terminal number is used for the second MCU to establish meeting connection with the first meeting place terminal, and the meeting number of the main MCU and the meeting number of the second MCU are used for the main MCU and the second MCU to establish a cascade channel between the main MCU and the second MCU so as to recover the meeting.
Optionally, the sending unit is configured to send, if the device is a slave service management center SMC, a restoration request message to a master SMC corresponding to a domain where the master MCU is located, where the restoration request message carries a conference number of the second MCU and is used by the master SMC to send the conference number of the second MCU to the master MCU. Optionally, the transmitting unit may transmit information to the host MCU or the second MCU according to the operations of steps 304, 306, 308 in the method embodiment shown in fig. 3-1 or according to the operations of steps 404 and 406 in the method embodiment shown in fig. 4-1.
Optionally, the apparatus 700 further includes: a processing unit;
and the processing unit is used for acquiring meeting place information of the first meeting place terminal, wherein the meeting place information at least comprises a cascade channel name and a channel number between the main MCU and the second MCU, and updating the meeting place information corresponding to the terminal number of the first meeting place terminal stored in the corresponding relation between the terminal number and the meeting place information into the acquired meeting place information.
Optionally, the recovering unit 703 is configured to determine that the identity of the second MCU is a master MCU and allocate a conference number to the second MCU if the first MCU is the master MCU;
the sending unit is configured to send a terminal number of the first meeting place terminal and a meeting number of each slave MCU used to hold the meeting to the second MCU, and send the meeting number of the second MCU to each slave MCU, where the terminal number is used for the second MCU to establish a meeting connection with the first meeting place terminal, and the meeting number of each slave MCU and the meeting number of the master MCU are used for the each slave MCU and the second MCU to establish a cascade channel between each slave MCU and the second MCU, respectively, so as to recover the meeting.
Optionally, the sending unit is configured to send, if the slave MCU is an MCU included in a domain where the slave SMC is located, a resume request message to the slave SMC, where the resume request message carries a conference number of the second MCU and is used for the slave SMC to send a master conference number of the second MCU to the slave MCU.
Optionally, the processing unit is further configured to determine each second meeting place terminal of the slave MCU included in the conference accessed in the domain where the processing unit is located, obtain meeting place information of the second meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed in the second meeting place terminal and the second MCU, and update meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information.
In the embodiment of the invention, the first meeting place terminal accessed with the abnormal first MCU can be determined, so that the second MCU can be allocated to the first meeting place terminal, the conference is recovered through the second MCU, and the conference can be continuously held.
Referring to fig. 8, an embodiment of the present invention provides an apparatus 800 for restoring a conference, which can be used to perform the method for restoring a conference in the method embodiment shown in fig. 5-1 or fig. 6-1, where the apparatus 800 is applied to a video system, and the apparatus 800 includes: a determination unit 801, an allocation unit 802, and a recovery unit 803;
the determining unit 801 is configured to determine a second service management center SMC that is used for holding a conference and is abnormal, and determine a first meeting place terminal that is located in a domain corresponding to the second SMC and is used for holding the conference; alternatively, the determining unit 801 may determine the first session terminal according to the operation of step 502 in the method embodiment shown in fig. 5-1 or according to the operation of step 602 in the method embodiment shown in fig. 6-1.
The allocating unit 802 is configured to allocate a first multipoint control unit MCU to the first session terminal from MCUs included in the corresponding domain; alternatively, the allocating unit 802 may allocate the first MCU according to the operation of step 503 in the method embodiment shown in fig. 5-1 or according to the operation of step 603 in the method embodiment shown in fig. 6-1.
The recovery unit 803 is configured to recover the conference through the first MCU. Optionally, the recovery unit 803 may recover the conference according to the operation of step 504 and step 508 in the method embodiment shown in fig. 5-1 or according to the operation of step 604 and step 611 in the method embodiment shown in fig. 6-1.
Optionally, the apparatus 800 further includes: a transmitting unit;
the recovery unit is used for allocating a conference number to the first MCU if the second SMC is not a master SMC;
the sending unit is used for sending the terminal number of the first meeting place terminal and the meeting number of a main MCU used for holding the meeting to the first MCU, sending the meeting number of the first MCU to the main MCU, wherein the terminal number is used for the first MCU to establish meeting connection with the first meeting place terminal, and the meeting number of the main MCU and the meeting number of the first MCU are used for the main MCU and the first MCU to establish a cascade channel between the main MCU and the first MCU so as to recover the meeting.
Optionally, the apparatus 800 further includes: a processing unit;
the processing unit is used for acquiring meeting place information of the first meeting place terminal, the meeting place information comprises a cascade channel name and a channel number between the first MCU and the main MCU, and the corresponding relation between the terminal number of the first meeting place terminal and the meeting place information is stored.
Optionally, the recovering unit 803 is configured to, if the second SMC is a master SMC, select an MCU from an MCU set as a master MCU, and allocate a conference number to the master MCU, where the MCU set includes an allocated first MCU;
and the sending unit is used for sending the terminal number of the corresponding first meeting place terminal to the main MCU, and the terminal number is used for the main MCU to establish conference connection with the corresponding first meeting place terminal.
Optionally, the allocating unit 802 is further configured to determine an unselected second MCU as a first slave MCU, and allocate a conference number to the first slave MCU;
the transmitting unit is further configured to transmit the conference number of the first slave MCU to the master MCU; and sending the conference number of the master MCU and the terminal number of a first conference site terminal corresponding to the first slave MCU, wherein the terminal numbers are used for the first slave MCU to establish conference connection between the first conference site terminal corresponding to the first slave MCU, and the conference number of the master MCU and the conference number of the first slave MCU are used for the first slave MCU and the master MCU to establish a cascade channel between the first slave MCU and the master MCU.
Optionally, the determining unit 801 is further configured to determine, by the first SMC, a second slave MCU included in a domain where a slave SMC for holding the conference is located;
the sending unit is further configured to send the conference number of the master MCU to the second slave MCU, and send the conference number of the second slave MCU to the master MCU, where the conference number of the master MCU and the conference number of the second slave MCU are used for the master MCU and the second slave MCU to establish a cascade channel between the master MCU and the second slave MCU. Alternatively, the transmitting unit may transmit information to the master MCU, the first slave MCU or the second slave MCU according to the operations of steps 504 and 505 in the method embodiment shown in fig. 5-1 or according to the operations of steps 605, 606 and 607 in the method embodiment shown in fig. 6-1.
Optionally, the processing unit is configured to determine each second meeting place terminal of the slave MCU included in the conference accessed in the domain where the processing unit is located, obtain meeting place information of the second meeting place terminal, where the meeting place information at least includes a name and a channel number of a cascade channel between the slave MCU accessed in the second meeting place terminal and the first MCU, and update meeting place information corresponding to the terminal number of the second meeting place terminal stored in the correspondence relationship between the terminal number and the meeting place information to the obtained meeting place information.
In the embodiment of the invention, the first meeting place terminal in the area where the abnormal second SMC is located can be determined, so that the first MCU can be allocated to the first meeting place terminal, the conference is recovered through the first MCU, and the conference can be continuously held.
Referring to fig. 9, an embodiment of the present invention provides a conference system 900, where the system 900 is applied to a video system, and the system 900 includes: a first SMC901, a first MCU902, and a second MCU 903; the conference system 900 provided in this embodiment may be the method example shown in fig. 3-1 or the conference system applied in the method embodiment shown in fig. 4-1, the first SMC901 may be the method example shown in fig. 3-1 or the first SMC in the method embodiment shown in fig. 4-1, the first MCU901 may be the method example shown in fig. 3-1 or the first MCU in the method embodiment shown in fig. 4-1, and the second MCU may be the method example shown in fig. 3-1 or the second MCU in the method embodiment shown in fig. 4-1.
Optionally, the first SMC901 is configured to determine a first MCU902 used for holding a conference and having an abnormal situation, and determine a first conference terminal accessed to the first MCU901 according to a correspondence between a stored conference number of the MCU and a terminal number of a conference terminal, where the first SMC901 is any SMC used for holding the conference;
the first SMC901 is further configured to allocate a second MCU902 to the first session terminal; the conference is resumed through the second MCU 902.
In the embodiment of the invention, the first SMC can determine the first meeting place terminal accessed with the abnormal first MCU, so that the second MCU can be allocated to the first meeting place terminal, the conference is recovered through the second MCU, and the conference can be continuously held.
Referring to fig. 10, an embodiment of the present invention provides a conference system 1000, which is applied to a video system, and includes: a first SMC1001, a second SMC1002, and a first MCU 1003; the conference system 1000 provided in this embodiment may be a conference system applied to the method example shown in fig. 5-1 or the method embodiment shown in fig. 6-1, the first SMC1001 may be the method example shown in fig. 5-1 or the first SMC in the method embodiment shown in fig. 6-1, the second SMC1002 may be the method example shown in fig. 5-1 or the second SMC in the method embodiment shown in fig. 6-1, and the first MCU may be the first MCU in the method example shown in fig. 5-1 or the method embodiment shown in fig. 6-1.
The first SMC1001 is used for determining a second SMC1002 which is used for holding a conference and has an abnormality, and determining a first meeting place terminal which is positioned in a domain corresponding to the second SMC and is used for holding the conference, wherein the first SMC1001 is a backup SMC of the second SMC;
the first SMC1001 is further configured to allocate a first MCU1003 to the first venue terminal from MCUs included in a corresponding domain; the conference is resumed through the first MCU 1003.
In the embodiment of the invention, the first SMC can determine the first meeting place terminal in the area where the abnormal second SMC is located, so that the first MCU can be allocated to the first meeting place terminal, and the conference is recovered through the first MCU, thereby being capable of continuing to hold the conference.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims (22)

1. A method of conference resumption, the method comprising:
a first Service Management Center (SMC) determines a first Multipoint Control Unit (MCU) which is used for holding a conference and is abnormal, wherein the first SMC is any SMC used for holding the conference;
the first SMC determines a first meeting place terminal accessed to the first MCU according to the corresponding relation of the meeting number of the MCU and the terminal number of the meeting place terminal;
the first SMC allocates a second MCU for the first session terminal from MCUs with idle resources except the first MCU in the domain where the first SMC is located;
if the first MCU is not a main MCU, the first SMC allocates a conference number for the second MCU, sends a terminal number of the first meeting place terminal and a conference number of the main MCU to the second MCU, sends the conference number of the second MCU to the main MCU, the terminal number is used for the second MCU to establish conference connection with the first meeting place terminal, the conference number of the main MCU and the conference number of the second MCU are used for the main MCU to establish a cascade channel to the direction of the second MCU and a cascade channel to the direction of the main MCU, the main MCU and the second MCU are two MCUs used for holding the conference, and the main MCU and the second MCU are in master-slave relationship.
2. The method of claim 1, wherein said transmitting the conference number of the second MCU to the master MCU comprises:
and if the first SMC is a slave SMC, the first SMC sends a recovery request message to a master SMC corresponding to the domain where the master MCU is located, wherein the recovery request message carries the conference number of the second MCU and is used for the master SMC to send the conference number of the second MCU to the master MCU.
3. The method of claim 1, wherein after the first SMC resumes the conference by the second MCU, further comprising:
and the first SMC acquires meeting place information of the first meeting place terminal, wherein the meeting place information at least comprises a cascade channel name and a channel number between the main MCU and the second MCU, and the meeting place information corresponding to the terminal number of the first meeting place terminal stored in the corresponding relation between the terminal number and the meeting place information is updated into the acquired meeting place information.
4. The method of claim 1, wherein the first SMC resumes the conference by the second MCU, comprising:
if the first MCU is a master MCU, the first SMC determines that the identity of the second MCU is a master MCU and allocates a conference number for the second MCU, sends the terminal number of the first conference terminal and the conference number of each slave MCU for holding the conference to the second MCU, and sends the conference number of the second MCU to each slave MCU, wherein the terminal number is used for the second MCU to establish conference connection with the first conference terminal, and the conference number of each slave MCU and the conference number of the master MCU are used for the each slave MCU and the second MCU to respectively establish a cascade channel between each slave MCU and the second MCU.
5. The method of claim 4, wherein said transmitting the conference number of the second MCU to each of the slave MCUs comprises:
and if the slave MCU is the MCU included in the domain of the slave SMC, the first SMC sends a recovery request message to the slave SMC, wherein the recovery request message carries the conference number of the second MCU and is used for the slave SMC to send the master conference number of the second MCU to the slave MCU.
6. The method of claim 4, wherein after the first SMC resuming the conference with the second MCU, further comprising:
the first SMC determines each second meeting place terminal of the slave MCU which is included in the access conference in the domain of the first SMC, obtains the meeting place information of the second meeting place terminal, the meeting place information at least comprises a cascade channel name and a channel number between the slave MCU which is accessed by the second meeting place terminal and the second MCU, and updates the meeting place information corresponding to the terminal number of the second meeting place terminal stored in the corresponding relation of the terminal number and the meeting place information into the obtained meeting place information.
7. A method of conference resumption, the method comprising:
a first service management center SMC determines a second SMC which is used for holding a conference and is abnormal, wherein the first SMC is a backup SMC of the second SMC, and the backup SMCs of the second SMC send the sizes of idle conference resources which are currently managed by the first SMC;
when judging that the idle conference resources currently managed by the first SMC in the backup SMC are the most, the first SMC determines a first meeting place terminal which is positioned in a domain corresponding to the second SMC and is used for holding the conference;
the first SMC distributes a first multipoint control unit MCU for the first meeting place terminal from the MCUs in the corresponding domain;
if the second SMC is not a main SMC, the first SMC allocates a conference number for the first MCU, sends a terminal number of the first meeting place terminal and a conference number of a main MCU used for holding the conference to the first MCU, sends the conference number of the first MCU to the main MCU, the terminal number is used for the first MCU to establish conference connection with the first meeting place terminal, the conference number of the main MCU and the conference number of the first MCU are used for the main MCU to establish a cascade channel to the first MCU direction and the first MCU to establish a cascade channel to the main MCU direction, the main MCU and the second MCU are two MCUs used for holding the conference, and the main MCU and the second MCU are in master-slave relationship.
8. The method of claim 7, wherein after the first SMC resuming the conference with the first MCU, further comprising:
and the first SMC acquires meeting place information of the first meeting place terminal, wherein the meeting place information comprises a cascade channel name and a channel number between the first MCU and the main MCU, and stores the corresponding relation between the terminal number of the first meeting place terminal and the meeting place information.
9. The method of claim 7, wherein the first SMC resuming the conference with the first MCU includes:
if the second SMC is a master SMC, the first SMC selects one MCU from an MCU set as a master MCU, and allocates a conference number to the master MCU, wherein the MCU set comprises the allocated first MCU;
and the first SMC sends the terminal number of the corresponding first meeting place terminal to the main MCU, and the terminal number is used for the main MCU to establish conference connection with the corresponding first meeting place terminal.
10. The method of claim 9, wherein after selecting one MCU from the set of MCUs as the master MCU, further comprising:
the first SMC determines the MCU which is not selected in the MCU set as a first slave MCU, allocates a conference number to the first slave MCU, and sends the conference number of the first slave MCU to the master MCU;
the first SMC sends a conference number of the main MCU and a terminal number of a first session terminal corresponding to the first slave MCU, the terminal numbers are used for the first slave MCU to establish conference connection with the corresponding first session terminal, and the conference number of the main MCU and the conference number of the first slave MCU are used for the first slave MCU and the main MCU to establish a cascade channel between the first slave MCU and the main MCU.
11. The method of claim 9, wherein after assigning the conference number to the master MCU, further comprising:
the first SMC determines a second slave MCU included in a domain where a slave SMC for holding the conference is located, sends a conference number of the master MCU to the second slave MCU, and sends the conference number of the second slave MCU to the master MCU, wherein the conference number of the master MCU and the conference number of the second slave MCU are used for the master MCU and the second slave MCU to establish a cascade channel between the master MCU and the second slave MCU.
12. The method of claim 9, wherein after the first SMC resumes the conference by the first MCU, further comprising:
the first SMC determines each second meeting place terminal of the slave MCU which is included in the access conference in the domain of the first SMC, obtains the meeting place information of the second meeting place terminal, the meeting place information at least comprises a cascade channel name and a channel number between the slave MCU which is accessed by the second meeting place terminal and the first MCU, and updates the meeting place information corresponding to the terminal number of the second meeting place terminal stored in the corresponding relation of the terminal number and the meeting place information into the obtained meeting place information.
13. A service management center, SMC, wherein the SMC comprises: a determination unit, an allocation unit and a recovery unit;
the determining unit is used for determining a first meeting place terminal accessed to a first Multipoint Control Unit (MCU) according to the corresponding relation between the meeting number of the MCU and the terminal number of the meeting place terminal when the MCU which is used for holding the meeting and is abnormal;
the allocating unit is used for allocating a corresponding second MCU for the first session terminal from the MCUs with idle resources except the first MCU in the domain where the SMC is located;
the recovery unit is used for recovering the conference through the second MCU;
wherein the SMC further comprises a transmitting unit;
the recovery unit is used for distributing a conference number to the second MCU if the first MCU is not the main MCU;
the sending unit is used for sending the terminal number of the first meeting place terminal and the meeting number of the main MCU to the second MCU, sending the meeting number of the second MCU to the main MCU, wherein the terminal number is used for the second MCU to establish meeting connection with the first meeting place terminal, the meeting number of the main MCU and the meeting number of the second MCU are used for the main MCU to establish a cascade channel in the direction of the second MCU and the second MCU to establish a cascade channel in the direction of the main MCU, the main MCU and the second MCU are two MCUs used for holding the meeting, and the main MCU and the second MCU are in master-slave relationship.
14. The SMC of claim 13, wherein the sending unit is configured to send, if the SMC is a slave SMC, a resume request message to a master SMC corresponding to a domain where the master MCU is located, where the resume request message carries a conference number of the second MCU, and is used by the master SMC to send the conference number of the second MCU to the master MCU.
15. The SMC of claim 13, wherein the SMC further includes: a transmitting unit;
the recovery unit is used for determining the identity of the second MCU as a main MCU and distributing a conference number to the second MCU if the first MCU is the main MCU;
the sending unit is configured to send, to the second MCU, a terminal number of the first conference site terminal and a conference number of each slave MCU used to hold the conference, and send, to each slave MCU, the conference number of the second MCU, where the terminal number is used for the second MCU to establish a conference connection with the first conference site terminal, and the conference number of each slave MCU and the conference number of the master MCU are used for the each slave MCU and the second MCU to establish a cascade channel between each slave MCU and the second MCU, respectively.
16. The SMC of claim 15, wherein the sending unit is configured to send a resume request message to the slave SMC if the slave MCU is an MCU included in a domain where the slave SMC is located, the resume request message carrying a conference number of the second MCU for the slave SMC to send a master conference number of the second MCU to the slave MCU.
17. A service management center SMC, wherein the SMC is applied to a video system, and the SMC comprises: a determination unit, an allocation unit and a recovery unit;
the determining unit is configured to determine a second service management center SMC used for holding a conference and having an abnormal occurrence, and determine a first session terminal located in a domain corresponding to a second SMC and used for holding the conference when it is determined that idle conference resources currently managed by the SMC are the most in backup SMCs of the second SMC, where the backup SMCs of the second SMC send sizes of the idle conference resources currently managed by the backup SMCs of the second SMC;
the distribution unit is used for distributing a first multipoint control unit MCU for the first session terminal from the MCUs included in the corresponding domain;
the recovery unit is used for recovering the conference through the first MCU;
wherein the SMC further comprises: a transmitting unit;
the recovery unit is used for allocating a conference number to the first MCU if the second SMC is not a master SMC;
the sending unit is used for sending the terminal number of the first meeting place terminal and the meeting number of a main MCU used for holding the meeting to the first MCU, sending the meeting number of the first MCU to the main MCU, wherein the terminal number is used for the first MCU to establish meeting connection with the first meeting place terminal, the meeting number of the main MCU and the meeting number of the first MCU are used for the main MCU to establish a cascade channel in the direction of the first MCU and the first MCU to establish a cascade channel in the direction of the main MCU, the main MCU and the second MCU are two MCUs used for holding the meeting, and the main MCU and the second MCU are in a master-slave relationship.
18. The SMC of claim 17, wherein the SMC further includes: a processing unit;
the processing unit is used for acquiring meeting place information of the first meeting place terminal, the meeting place information comprises a cascade channel name and a channel number between the first MCU and the main MCU, and the corresponding relation between the terminal number of the first meeting place terminal and the meeting place information is stored.
19. The SMC of claim 17, wherein the SMC further includes: a transmitting unit;
the recovery unit is used for selecting one MCU from an MCU set as a main MCU if the second SMC is a main SMC, and allocating a conference number to the main MCU, wherein the MCU set comprises an allocated first MCU;
and the sending unit is used for sending the terminal number of the corresponding first meeting place terminal to the main MCU, and the terminal number is used for the main MCU to establish conference connection with the corresponding first meeting place terminal.
20. The SMC of claim 19, wherein the allocating unit is further configured to determine an MCU of the set of MCUs that is not selected as a first slave MCU, to allocate a conference number to the first slave MCU;
the transmitting unit is further configured to transmit the conference number of the first slave MCU to the master MCU; and sending the conference number of the master MCU and the terminal number of a first conference site terminal corresponding to the first slave MCU, wherein the terminal numbers are used for the first slave MCU to establish conference connection between the first conference site terminal corresponding to the first slave MCU, and the conference number of the master MCU and the conference number of the first slave MCU are used for the first slave MCU and the master MCU to establish a cascade channel between the first slave MCU and the master MCU.
21. A conferencing system, the system being applied to a video system, the system comprising: the system comprises a first service management center SMC, a first multipoint control unit MCU and a second MCU;
the first SMC is used for determining a first MCU which is used for holding a conference and is abnormal, and determining a first meeting place terminal accessed to the first MCU according to the corresponding relation between the conference number of the MCU and the terminal number of the meeting place terminal, wherein the first SMC is any SMC used for holding the conference;
the first SMC is further used for allocating a second MCU for the first session terminal from the MCUs with idle resources except the first MCU in the domain where the SMC is located;
if the first MCU is not a main MCU, the first SMC allocates a conference number for the second MCU, sends a terminal number of the first meeting place terminal and a conference number of the main MCU to the second MCU, sends the conference number of the second MCU to the main MCU, the terminal number is used for the second MCU to establish conference connection with the first meeting place terminal, the conference number of the main MCU and the conference number of the second MCU are used for the main MCU to establish a cascade channel to the direction of the second MCU and a cascade channel to the direction of the main MCU, the main MCU and the second MCU are two MCUs used for holding the conference, and the main MCU and the second MCU are in master-slave relationship.
22. A conferencing system, the system being applied to a video system, the system comprising: the system comprises a first service management center SMC, a second SMC and a first multipoint control unit MCU;
the first SMC is used for determining a second SMC which is used for holding a conference and has an abnormality, wherein backup SMCs of the second SMC send the sizes of idle conference resources currently managed by the backup SMCs, and when judging that the idle conference resources currently managed by the first SMC in the backup SMCs of the second SMC are the most, the first SMC determines a first meeting place terminal which is positioned in a domain corresponding to the second SMC and used for holding the conference, and the first SMC is the backup SMC of the second SMC;
the first SMC is also used for distributing a first multipoint control unit MCU for the first meeting place terminal from the MCUs included in the corresponding domain;
if the second SMC is not a main SMC, the first SMC allocates a conference number for the first MCU, sends a terminal number of the first meeting place terminal and a conference number of a main MCU used for holding the conference to the first MCU, sends the conference number of the first MCU to the main MCU, the terminal number is used for the first MCU to establish conference connection with the first meeting place terminal, the conference number of the main MCU and the conference number of the first MCU are used for the main MCU to establish a cascade channel to the first MCU direction and the first MCU to establish a cascade channel to the main MCU direction, the main MCU and the second MCU are two MCUs used for holding the conference, and the main MCU and the second MCU are in master-slave relationship.
CN201610619102.0A 2016-07-29 2016-07-29 Conference recovery method, service management center and system Active CN106254814B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201610619102.0A CN106254814B (en) 2016-07-29 2016-07-29 Conference recovery method, service management center and system
PCT/CN2017/093404 WO2018019158A1 (en) 2016-07-29 2017-07-18 Conference resumption method, service management center, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610619102.0A CN106254814B (en) 2016-07-29 2016-07-29 Conference recovery method, service management center and system

Publications (2)

Publication Number Publication Date
CN106254814A CN106254814A (en) 2016-12-21
CN106254814B true CN106254814B (en) 2021-03-05

Family

ID=57606276

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610619102.0A Active CN106254814B (en) 2016-07-29 2016-07-29 Conference recovery method, service management center and system

Country Status (2)

Country Link
CN (1) CN106254814B (en)
WO (1) WO2018019158A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106254814B (en) * 2016-07-29 2021-03-05 华为技术有限公司 Conference recovery method, service management center and system
CN110099240B (en) * 2018-01-29 2022-01-25 视联动力信息技术股份有限公司 Control method and device for video conference
CN109040658B (en) * 2018-09-25 2020-10-13 视联动力信息技术股份有限公司 Conference control method and device
CN110225293B (en) * 2019-06-19 2021-11-26 苏州市科远软件技术开发有限公司 Conference cascading method and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1452405A (en) * 2002-04-18 2003-10-29 华为技术有限公司 All-process backup video communication system
CN101668161A (en) * 2009-09-21 2010-03-10 中兴通讯股份有限公司 Video conference cross stage control method and system
CN101753339A (en) * 2008-12-09 2010-06-23 中兴通讯股份有限公司 Method for realizing conference backup function of multi-point control unit and system thereof
CN105357469A (en) * 2015-11-06 2016-02-24 国家电网公司 MCU (multi control unit) resource pool deploying method and apparatus

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100479518C (en) * 2003-09-02 2009-04-15 华为技术有限公司 Primary use spare MCU interchanging device and method
US7937442B2 (en) * 2006-09-22 2011-05-03 Microsoft Corporation Multipoint control unit (MCU) failure detection and rollover
CN1946164A (en) * 2006-09-30 2007-04-11 华为技术有限公司 System and method for meeting information backup in multipoint meeting
CN105657328B (en) * 2016-01-04 2019-07-09 杭州华为企业通信技术有限公司 A kind of method, apparatus and system of port operation meeting resource
CN106254814B (en) * 2016-07-29 2021-03-05 华为技术有限公司 Conference recovery method, service management center and system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1452405A (en) * 2002-04-18 2003-10-29 华为技术有限公司 All-process backup video communication system
CN101753339A (en) * 2008-12-09 2010-06-23 中兴通讯股份有限公司 Method for realizing conference backup function of multi-point control unit and system thereof
CN101668161A (en) * 2009-09-21 2010-03-10 中兴通讯股份有限公司 Video conference cross stage control method and system
CN105357469A (en) * 2015-11-06 2016-02-24 国家电网公司 MCU (multi control unit) resource pool deploying method and apparatus

Also Published As

Publication number Publication date
CN106254814A (en) 2016-12-21
WO2018019158A1 (en) 2018-02-01

Similar Documents

Publication Publication Date Title
CN107295080B (en) Data storage method applied to distributed server cluster and server
US10140112B2 (en) Update management system and update management method
CN106254814B (en) Conference recovery method, service management center and system
US20210176310A1 (en) Data synchronization method and system
US10880779B2 (en) User plane resource management method, user plane network element, and control plane network element
CN106060088B (en) Service management method and device
CN107800565B (en) Inspection method, inspection device, inspection system, computer equipment and storage medium
US9992058B2 (en) Redundant storage solution
CN104320459A (en) Node management method and device
CN105677380B (en) Method and device for board-by-board upgrading of double master control isolations
CN113347037B (en) Data center access method and device
CN110971702A (en) Service calling method and device, computer equipment and storage medium
CN111708668B (en) Cluster fault processing method and device and electronic equipment
CN105554099A (en) Method and device for balancing load of acquisition servers
CN111930515B (en) Data acquisition and distribution method, device, server and storage medium
CN104503861A (en) Abnormality handling method and system, agency device and control device
CN102307194B (en) Graceful restarting method and device for universal protocol process
CN113467873A (en) Virtual machine scheduling method and device, electronic equipment and storage medium
CN114302350B (en) Service provider failover method and device, electronic equipment and storage medium
CN110972170B (en) Configuration method of base station and base station
CN109245911B (en) Method and device for realizing BRAS hot standby and computer readable storage medium
CN106534758B (en) Conference backup method and device
US11153173B1 (en) Dynamically updating compute node location information in a distributed computing environment
US10476744B2 (en) Coordinator in cluster membership management protocol
CN112948177A (en) Disaster recovery backup method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant