WO2010111867A1 - 分布式多点会议系统中的管理方法、装置及系统 - Google Patents

分布式多点会议系统中的管理方法、装置及系统 Download PDF

Info

Publication number
WO2010111867A1
WO2010111867A1 PCT/CN2009/075382 CN2009075382W WO2010111867A1 WO 2010111867 A1 WO2010111867 A1 WO 2010111867A1 CN 2009075382 W CN2009075382 W CN 2009075382W WO 2010111867 A1 WO2010111867 A1 WO 2010111867A1
Authority
WO
WIPO (PCT)
Prior art keywords
control device
multipoint
multipoint control
conference
topology relationship
Prior art date
Application number
PCT/CN2009/075382
Other languages
English (en)
French (fr)
Inventor
卢少防
陈剑青
Original Assignee
华为终端有限公司
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 华为终端有限公司 filed Critical 华为终端有限公司
Publication of WO2010111867A1 publication Critical patent/WO2010111867A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1854—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with non-centralised forwarding system, e.g. chaincast

Definitions

  • the present invention relates to a distributed multipoint conference system, and more particularly to management techniques in a distributed multipoint conference system.
  • a typical distributed multipoint conference system includes a multipoint control device (for example, a Multipoint Control Unit (MCU), a Media Resource Server (MRS), a multimedia terminal (hereinafter referred to as a terminal), and Communications network.
  • a multi-point control device can handle calls sent by multiple terminals through the communication network, and the multi-point control device and the terminal form a point-to-point connection to coordinate and establish a multipoint conference.
  • the terminal may be a video terminal, an audio terminal, or a combination of audio and video.
  • the communication network is used to connect the multipoint control device and the terminal, and may specifically include a gateway, a router or a firewall.
  • a multipoint conference is managed centrally by a multipoint control (MC, Multipoint Control), and the MC controls the multipoint processing (MP, Multipoint Process) part for video, audio, and data stream processing.
  • the multipoint control device can include MC at the same time.
  • the part and the MP part may also include only the MC part or the MP part.
  • Each office site may have at least one multipoint control device and at least one terminal, and the multipoint control device and terminal of each office site form an area.
  • the current management scheme in a distributed multipoint conference system is: a multipoint control device provides a built-in management station (for example, Web), and the administrator directly logs in to the multipoint control device after determining the IP address of the multipoint control device ( For example, logging in via Web) for management, such as managing a multipoint control device
  • the body or its controlled terminal When a conference is held, the multipoint control device corresponding to the terminal that needs to participate in the conference needs to be cascaded.
  • the administrator needs to log in to multiple multipoint control devices to cascade these multipoint control devices. The operation is that the administrator performs a conference on these multipoint control devices, and then manually cascades these multipoint control devices.
  • the inventor of the present invention found in the process of implementing the present invention that the built-in management station can only manage a single multi-point control device, and if it is necessary to manage multiple multi-point control devices, the administrator must remember each multi-point control device. The name or IP address of the talent can be logged in for management.
  • the administrator needs to pre-determine which multi-point control devices are cascaded, and then log in separately to the determined multi-point control devices for cascading operations. It can be seen that the management scheme in the existing distributed multipoint conference system not only has higher requirements for administrators, but also realizes complicated management. Summary of the invention
  • the embodiments of the present invention provide a management method, a device, a multipoint control device, and a distributed multipoint conference system in a distributed multipoint conference system, so as to reduce requirements for administrators and realize management complexity.
  • a management method in a distributed multipoint conference system comprising: obtaining a topology relationship of a multipoint control device in the distributed multipoint conference system, wherein a topology relationship of the multipoint control device is used to indicate multiple points Controlling a communication connection relationship between the devices; performing a management operation according to the obtained topology relationship.
  • a management device in a distributed multipoint conference system comprising: an obtaining unit, configured to obtain a topology relationship of a multipoint control device in the distributed multipoint conference system, and a topology relationship of the multipoint control device
  • the management unit is configured to perform a management operation according to the topology relationship obtained by the obtaining unit.
  • a multipoint control device includes the management device in the distributed multipoint conference system described above.
  • a distributed multipoint conference system comprising a plurality of multipoint control devices; a multipoint control device that has established a communication connection with other multipoint control devices has a topology of a multipoint control device in the distributed multipoint conference system Relationship, the topology relationship of the multipoint control device is used to represent a communication connection relationship between the multipoint control devices, each having a topology of the multipoint control device in the distributed multipoint conference system The relationship is managed according to the topology relationship.
  • each multi-point control device that obtains the topology relationship of the multi-point control device is managed according to the topology relationship, and the administrator does not need to remember the name or IP address of each multi-point control device, and does not need to manage.
  • the administrator can manage the corresponding multi-point control devices on the topology through the topology relationship as long as they have the corresponding rights. Therefore, the requirements of the administrator of the embodiment of the present invention are not high, and the management is relatively simple.
  • 1 is a schematic diagram of the composition of a distributed multipoint conference system
  • FIG. 2 is a flowchart of a management method in a distributed multipoint conference system according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a management apparatus in a distributed multipoint conference system according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a distributed multipoint conference system in which a multipoint control device is configured with a prefix according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a network environment applied to two preferred embodiments of the present invention.
  • Figure 6 is a flow chart of a first preferred embodiment of the present invention.
  • Figure 7 is a flow chart of a second preferred embodiment of the present invention. detailed description
  • the multi-point conference system includes a plurality of areas, each area having at least one multi-point control device, each multi-point control device controlling at least one terminal, and the inter-area conference is held by the multi-point control device cascade between the plurality of areas.
  • the multipoint control device may refer to a device having a multipoint control function such as an MCU or an MRS.
  • the distributed multipoint conference system includes three areas, the area one has MCU1 and multiple terminals, the area two has MCU2 and multiple terminals, the area three has MCU3 and multiple terminals, and the MCU1 is physically connected with the MCU2.
  • MCU1 is physically connected to MCU3. If MCU1 establishes communication connection with MCU2 and MCU1 establishes communication connection with MCU3, then area 1, area 2 and area 3 are connected through the communication connection between MCU2 and MCU1 and the communication connection between MCU1 and MCU3. Three regional meetings.
  • the management method in a distributed multipoint conference system is as shown in FIG. 2, and includes:
  • S201 Obtain a topology relationship of the multipoint control device in the distributed multipoint conference system, where the topology relationship of the multipoint control device is used to indicate a communication connection relationship between the multipoint control devices;
  • the topology relationship of the multipoint control device in the distributed multipoint conference system may refer to all topology relationships of the multipoint control device, and may also refer to a partial topology relationship of the multipoint control device.
  • MCU2 can obtain only the communication connection relationship with MCU1, the communication connection relationship with MCU1, and the communication connection relationship between MCU1 and MCU3.
  • the topology relationship of the multipoint control device in the distributed multipoint conference system can be obtained in various manners.
  • the topology relationship of the multipoint control device in the distributed multipoint conference system is locally configured in advance, and when the topology relationship is required, the pre-configured multipoint in the distributed multipoint conference system is obtained locally.
  • Control the topology of the device For another example, other multipoint control devices provide a topology relationship of the multipoint control device in the distributed multipoint conference system, or obtain more of the distributed multipoint conference system provided by other multipoint control devices. Point control device topology.
  • the topology relationship of the multipoint control device in the distributed multipoint conference system provided by other multipoint control devices, for example, requesting establishment of a multipoint control device having a physical connection with itself. a communication connection; obtaining a topology relationship of the multipoint control device in the distributed multipoint conference system provided by the multipoint control device having the physical connection with itself. Requesting a communication connection to a multipoint control device having a physical connection with itself can be performed after powering up.
  • the topology relationship used by the multipoint control device may be static or dynamic. Specifically, whether the topology relationship of the multipoint control device in the distributed multipoint conference system is locally configured in advance, or the multipoint control in the distributed multipoint conference system is obtained from other multipoint control devices.
  • the topology relationship of the device as long as the topology relationship of the multipoint control device in the distributed multipoint conference system is obtained for the first time, in a later management process, in the distributed multipoint conference system
  • the topology relationship of the multipoint control device can be kept unchanged or updated as the communication connection relationship between the multipoint control devices changes.
  • the topology relationship used by the multipoint control device is to keep static. In the specific implementation, there are multiple ways to perform management operations according to the obtained topology relationship. Here are a few typical management operations.
  • the obtained topology relationship can be synchronized to other multipoint control devices.
  • the multipoint control device having physical connection with itself may issue a request for establishing a communication connection to itself, that is, obtaining a request for establishing a communication connection by a multipoint control device having a physical connection with itself, and then, to the A multipoint control device having its own physical connection provides the obtained topology relationship.
  • the timing at which the multipoint control device having its physical connection to itself issues a request to establish a communication connection may be after the multipoint control device having a physical connection with itself is powered on.
  • the distributed multipoint conference system originally includes MCU1, MCU2, MCU3, MCU4, and MCU5.
  • the topology relationship obtained by MCU4 is as follows: MCU1 and MCU2 have communication connection relationship, MCU1 and MCU4 have communication connection relationship, MCU3 Have communication connection with MCU4
  • MCU4 and MCU5 have a communication connection relationship.
  • the MCU 4 can provide the above-mentioned topology relationship obtained by the MCU 4 to the MCU 6.
  • the topology relationship of the multipoint control device in the distributed multipoint conference system can be updated.
  • the topology relationship of the multipoint control device changes, for example, when a new multipoint control device is added to the topology or there is a multipoint control device to exit the topology.
  • the updated distributed multipoint conference system may be The topology relationship of the multipoint control device is provided to itself, that is, the topology relationship of the multipoint control device in the updated distributed multipoint conference system provided by the multipoint control device having the communication connection with itself can be obtained; After obtaining a request for establishing a communication connection by a multipoint control device having a physical connection with itself, adding the multipoint control device having physical connection with itself to the multipoint control device in the distributed multipoint conference system a topology relationship; when it is determined that the multipoint control device having a communication connection with itself exits the topology, the topology multipoint control device is exited from the topology relationship of the multipoint control device in the distributed multipoint conference system delete.
  • the MCU 4 adds the communication connection relationship with the MCU 6 to the topology relationship originally owned by the MCU 4, and updates the topology relationship or
  • the communication connection between MCU4 and MCU6 is synchronized to MCU1, MCU3 and MCU5.
  • MCU6 exits the topology relationship, and then MCU4 deletes the communication connection relationship with MCU6 in its topology relationship, and synchronizes the updated topology relationship to MCU1, MCU3, and MCU5.
  • updating the topology relationship of the multipoint control device in the distributed multipoint conference system may also be other situations, for example, the communication connection relationship between the multipoint control devices changes, and is not illustrated here.
  • the topology relationship of the multipoint control device in the updated distributed multipoint conference system may be synchronized.
  • each multipoint control device in the topology relationship can synchronize the topology relationship of the multipoint control device in the updated distributed multipoint conference system to the multipoint control device having communication connection with itself.
  • the topological relationship of the multipoint control device in the distributed multipoint conference system currently used by all the multipoint control devices in the topology relationship is consistent.
  • a conference request is sent to the multipoint control device corresponding to the terminal that needs to participate in the conference according to the obtained topology relationship. If the multipoint control device corresponding to the terminal that needs to participate in the conference is not a multipoint control device having a communication connection relationship with itself, according to the obtained topology relationship, a conference request is sent to the multipoint control device having a communication connection relationship with itself. And the multi-point control device having the communication connection relationship with itself forwards the meeting request directly or indirectly to the multi-point control device corresponding to the terminal that needs to participate in the conference.
  • the term "indirect” as used herein means that if the multipoint control device having a communication connection relationship with itself does not have a communication connection relationship with the multipoint control device corresponding to the terminal that needs to participate in the conference, the communication connection relationship with itself is performed.
  • the multipoint control device forwards the meeting request to the multipoint control device with which it has a communication connection relationship, and so on, until the meeting request reaches the multipoint control device corresponding to the terminal that needs to attend the conference. If the multipoint control device corresponding to the terminal that needs to participate in the conference is a multipoint control device that has a communication connection relationship with itself, then a conference request can be directly sent to it. This explanation can also be referred to indirectly as described below.
  • the conference response returned by the multipoint control device corresponding to the terminal that needs to participate in the conference may be directly or indirectly obtained.
  • the multi-point control device corresponding to the terminal that needs to participate in the conference can control the terminal that needs to participate in the conference after receiving the conference request.
  • the terminal that needs to participate in the conference is added to the conference.
  • the requested multipoint control device returns a successful meeting response, otherwise, the return fails.
  • the meeting response can also carry other information, no longer here - for example.
  • the conference request may be directly or indirectly according to the obtained topology relationship. Forward to the multipoint control device corresponding to the terminal that needs to participate in the conference. After the meeting request is directly or indirectly forwarded to the multi-point control device corresponding to the terminal that needs to participate in the meeting, when the meeting response of the multi-point control device corresponding to the terminal that needs to participate in the meeting is directly or indirectly obtained, the meeting may be performed. The response is forwarded to the multipoint control device that has a communication connection relationship with the issuing conference request.
  • each multi-point control device can exchange the status of each site, such as the status of each site, so that each multipoint control device in the distributed multipoint conference system can provide the entire conference situation to the administrator.
  • the MCU1 needs to call the terminal under the MCU3 and the terminal under the MCU6 to meet.
  • the MCU1 sends a conference request to the MCU4, and the MCU4 finds that the terminal under the MCU3 is not called, but calls the terminal under the MCU3 and the MCU6.
  • the terminal is in a meeting, and then MCU4 forwards the meeting request to MCU3 and MCU6. If MCU3 successfully joins the terminal under it to the conference, MCU6 successfully joins the terminal under it to the conference, then MCU3 and MCU6 can return a successful conference response to MCU4, and MCU4 returns the successful conference response to MCU1. .
  • the multipoint control device that the administrator logs in should provide the meeting status to the administrator.
  • the access authority of the administrator is determined, and the administrator is provided with the topology relationship and the conference situation of the multipoint control device that is compatible with the access authority.
  • Providing the administrator with a topology relationship of the multipoint control device may be a topology relationship indicating that the administrator displays the multipoint control device, and providing the administrator with the conference status may be directed to the administrator to display the site status.
  • Providing the administrator with a topology relationship and a conference situation of the multipoint control device adapted to the access authority may include: if the administrator has access to all the multipoint control devices in the distributed multipoint conference system Permission to provide the distributed to the administrator The full topology of the multipoint control device in the multipoint conference system and the conference situation on the entire topology relationship; if the administrator only has the right to access the multipoint control device of the region in which it is located, then The administrator provides a topology relationship of the multipoint control device in the area where the administrator is located and a conference situation on the topology relationship of the multipoint control device in the region where the user is located.
  • Administrator privileges can be flexibly configured according to actual needs. Administrator privileges include, for example, device management and conference management. Device management privileges control whether an administrator can access multipoint control devices and configure multipoint control devices. Conference management permissions control whether administrators can control conferences cascaded to other multipoint control devices. For example, suppose that administrator A can access multipoint control devices in other regions and can control conferences on multipoint control devices that are cascaded to other regions. After administrator A logs in to the multipoint control device in the local area, the interface used by administrator A can display the current device connection status of the entire network. Administrator A can directly enter any multipoint control device for maintenance and management.
  • Administrator A can see the list of conferences and venues on each multipoint control device, and can control the conferences on each multipoint control device. Assume that Administrator B can only access multipoint control devices and conferences within the region. After administrator B logs in to the multi-point control device in the local area, administrator B can only see the status of each multi-point control device in the area. For the inter-area conference, administrator B can only see the site in the local area. Waiting for the meeting, but not meeting the meeting in other areas.
  • an administrator can manage another multipoint control device on one multipoint control device. Specifically, when obtaining management information of a multipoint control device by an administrator logging in to itself or logging in to another multipoint control device, the management information is directly or indirectly forwarded to the device according to the obtained topology relationship. A multipoint control device that management information ultimately needs to arrive.
  • the MCU1 generates the management information of the administrator on the MCU6, the MCU1 provides the management information to the MCU4, and the MCU4 forwards the management information to the MCU6.
  • the execution body of S201 and S202 may be a multipoint control device.
  • an embodiment of the present invention provides a management apparatus in a distributed multipoint conference system.
  • the management apparatus includes: an obtaining unit 31, configured to obtain a topology relationship of a multipoint control device in the distributed multipoint conference system, where a topology relationship of the multipoint control device is used The communication connection relationship between the multi-point control devices is indicated; the management unit 32 is configured to perform a management operation according to the topology relationship obtained by the obtaining unit 31.
  • the topology relationship of the multipoint control device in the distributed multipoint conference system may refer to all topology relationships of the multipoint control device, and may also refer to a partial topology relationship of the multipoint control device.
  • MCU2 can obtain only the communication connection relationship with MCU1, the communication connection relationship with MCU1, and the communication connection relationship between MCU1 and MCU3.
  • the obtaining unit 31 can obtain the topology relationship of the multipoint control device in the distributed multipoint conference system in various ways. For example, the obtaining unit 31 obtains locally the topology relationship of the multipoint control device in the distributed multipoint conference system, or the obtaining unit 31 obtains the distributed multipoint conference provided by other multipoint control devices. Multipoint control in the system controls the topology of the device. In a specific implementation, the obtaining unit 31 can obtain the topology relationship of the multipoint control device in the distributed multipoint conference system provided by other multipoint control devices in multiple manners, for example, to the device shown in FIG.
  • the multipoint control device in which the multipoint control device has a physical connection requests to establish a communication connection, and obtains the distributed multi-point control device provided by the multipoint control device having the physical connection with the multipoint control device in which the device shown in FIG.
  • the topology of the multipoint control device in the point conference system may include: a requesting subunit 311, configured to request to establish a communication connection to a multipoint control device having a physical connection with the multipoint control device where the device shown in FIG. 3 is located; obtaining the subunit 312, For obtaining a communication connection between the request subunit and the multipoint control device having a physical connection with the multipoint control device in which the device shown in FIG.
  • the control device has a topological relationship of multipoint control devices in the distributed multipoint conference system provided by a physically connected multipoint control device.
  • the obtaining unit 31 requests the establishment of the communication connection to the multipoint control device having the physical connection with the multipoint control device in which the device shown in FIG. 3 is located, and can be executed after the multipoint control device in which the device shown in FIG. 3 is located is turned on. It should be noted that the topology relationship obtained by the obtaining unit 31 may be static or dynamic.
  • the obtaining unit 31 obtains the topology relationship of the multipoint control device in the distributed multipoint conference system
  • the topology relationship of the multipoint control device in the distributed multipoint conference system can be maintained neither
  • the change can also be updated as the communication connection relationship between the multipoint control devices changes.
  • the management unit 32 can synchronize the obtained topology relationship to other multipoint control devices.
  • the management unit 32 may include a first synchronization sub-unit 321 for synchronizing the obtained topology relationship to other multi-point control devices after the obtaining unit 31 obtains the topology relationship.
  • the multipoint control device having a physical connection with the multipoint control device in which the device shown in FIG. 3 is located may issue a request to establish a communication connection to the multipoint control device in which the device shown in FIG. 3 is located, that is, the obtaining unit 31 Obtaining a request for establishing a communication connection from a multipoint control device having a physical connection with the multipoint control device in which the device shown in FIG.
  • the management unit 32 controls the multipoint control of the device shown in FIG.
  • the multipoint control device with the device having a physical connection provides the obtained topology relationship.
  • the timing at which the multipoint control device having the physical connection with the multipoint control device in which the device shown in FIG. 3 is physically connected to the multipoint control device in which the device shown in FIG. 3 is located may be in the same manner as shown in FIG.
  • the multipoint control device in which the device is located has a physically connected multipoint control device after booting.
  • the management unit 32 updates the topology relationship of the multipoint control device in the distributed multipoint conference system.
  • the management unit 32 may include an update subunit 322, configured to update the distributed multipoint conference system if a topology relationship of the multipoint control device in the distributed multipoint conference system changes.
  • the multi-point control device's topological relationship The topology relationship of the multipoint control device changes, for example, when a new multipoint control device is added to the topology or a multipoint control device is used to exit the topology.
  • the update may be performed after the update.
  • the topology relationship of the multipoint control device in the distributed multipoint conference system is provided to the multipoint control device in which the device shown in FIG. 3 is located, that is, the obtaining unit 31 can obtain the device shown in FIG.
  • the multipoint control device has a topology relationship of the multipoint control device in the updated distributed multipoint conference system provided by the multipoint control device of the communication connection; when the obtaining unit 31 obtains the device shown in FIG.
  • the multipoint control device After the multipoint control device of the multipoint control device has a physical connection, the multipoint control device issues a request for establishing a communication connection, and the management unit 32 can connect the multipoint control device physically connected to the multipoint control device where the device shown in FIG. a topology relationship of a multipoint control device added to the distributed multipoint conference system; when the management unit 32 determines a multipoint control device having a communication connection with the multipoint control device in which the device shown in FIG. 3 is connected, exits the topology Thereafter, the management unit 32 deletes the topology multipoint control device from the topology relationship of the multipoint control device in the distributed multipoint conference system.
  • the updating of the topology relationship of the multipoint control device in the distributed multipoint conference system by the management unit 32 may also be other situations, and is not illustrated here.
  • the management unit 32 may expand the multipoint control device in the updated distributed multipoint conference system.
  • the Park relationship is synchronized to a multipoint control device having a communication connection with the multipoint control device in which the device shown in Fig. 3 is located.
  • the management unit 32 may include a second synchronization subunit 323, configured to: after the update subunit updates the topology relationship of the multipoint control device in the distributed multipoint conference system, the update The topology relationship of the multipoint control device in the distributed multipoint conference system is synchronized to a multipoint control device having a communication connection with itself.
  • each multipoint control device in the topology relationship can synchronize the topology relationship of the multipoint control device in the updated distributed multipoint conference system to the multipoint control device having communication connection with itself.
  • the topological relationship of the multipoint control device in the distributed multipoint conference system currently used by all the multipoint control devices in the topology relationship is consistent.
  • the management unit 32 may send a conference request to the multipoint control device corresponding to the terminal that needs to participate in the conference according to the obtained topology relationship.
  • the management unit 32 may include a request sub-unit 324, configured to send a meeting request to the multi-point control device corresponding to the terminal that needs to participate in the conference according to the obtained topology relationship when the conference needs to be called. If you need to participate in the conference, the corresponding multipoint control device The multi-point control device is not in a communication connection relationship with the multi-point control device in which the device shown in FIG. 3 is located, and the management unit 32 can provide multiple points to the device shown in FIG.
  • the multipoint control device having the communication connection relationship of the control device issues a meeting request, and the multipoint control device having the communication connection relationship with the multipoint control device where the device shown in FIG. 3 has a communication connection directly or indirectly forwards the meeting request to the participant to participate
  • the multipoint control device corresponding to the terminal of the conference The indirect term described herein means that the multipoint control device having the communication connection relationship with the multipoint control device in which the device shown in FIG. 3 has a communication connection relationship with the multipoint control device corresponding to the terminal that needs to participate in the conference does not have a communication connection relationship. Then, the multipoint control device having the communication connection relationship with the multipoint control device in which the device shown in FIG.
  • the multipoint control device corresponding to the terminal that needs to participate in the conference is a multipoint control device having a communication connection relationship with the multipoint control device in which the device shown in FIG. 3 is located, a conference request can be directly sent thereto. This explanation can also be referred to indirectly as described below.
  • the obtaining unit 31 can directly or indirectly obtain the meeting response returned by the multipoint control device corresponding to the terminal that needs to participate in the conference.
  • the multi-point control device corresponding to the terminal that needs to participate in the conference can control the terminal that needs to participate in the conference after receiving the conference request.
  • the terminal that needs to participate in the conference is added to the conference, and after the join is successful, the conference is sent.
  • the requested multipoint control device returns a successful meeting response, otherwise, a failed meeting response is returned.
  • the meeting response can also carry other information, no longer here - for example.
  • the obtaining unit 31 also obtains a meeting request from a multipoint control device having a communication connection relationship with the multipoint control device in which the device shown in FIG. 3 is located, if the multipoint control device in which the device shown in FIG. 3 is located is controlled
  • the management unit 32 may forward the meeting request directly or indirectly to the multipoint control device corresponding to the terminal that needs to participate in the conference according to the obtained topology relationship.
  • the management unit 32 may include a first forwarding sub-unit 325, configured to send the multi-point control device that has a communication connection relationship with itself when the obtaining unit further obtains
  • the conference request is directly or indirectly forwarded to the multipoint control device corresponding to the terminal that needs to participate in the conference according to the obtained topology relationship.
  • the management unit 32 may forward the meeting response to the multipoint control device that has a communication connection relationship with the calling request.
  • each multi-point control device can exchange the status of each site, such as the status of each site, so that each multipoint control device in the distributed multipoint conference system can provide the entire conference situation to the administrator.
  • the management unit 32 may first determine the access authority of the administrator, and then to the administrator. Provides topology relationships and conferences for multipoint control devices that are commensurate with their access rights.
  • the management unit 32 may include: a permission check sub-unit 326, configured to determine an access right of the administrator when the obtaining unit further obtains a request for an administrator to access itself; and provide a sub-unit 327, configured to The administrator is provided with the topology relationship and the conference situation of the multipoint control device determined by the authority checking subunit 326 and adapted to the administrator access authority.
  • Providing the administrator with a topology relationship of the multipoint control device may be a topology relationship indicating that the administrator displays the multipoint control device, and providing the administrator with the conference status may be directed to the administrator to display the site status.
  • the topology relationship and the conference situation of the multipoint control device that the management unit 32 provides to the administrator according to the access authority may specifically include: if the administrator has access to all the multipoints in the distributed multipoint conference system Controlling the rights of the device, the management unit 32 provides the administrator with all the topology relationships of the multipoint control device in the distributed multipoint conference system and the conference situation on the entire topology relationship; The administrator only has the right to access the multi-point control device of the area where the user is located, and the management unit 32 provides the administrator with the topology relationship of the multi-point control device of the area in which the administrator is located and the area in which the self is located. Point control of the conference situation on the topology of the device.
  • Administrator privileges can be flexibly configured according to actual needs. Administrator privileges include, for example, devices. Management and meeting management. Device management permissions control whether an administrator can access multipoint control devices and configure multipoint control devices. Conference management permissions control whether administrators can control conferences cascaded to other multipoint control devices. For example, suppose that administrator A can access multipoint control devices in other areas and can control conferences on multipoint control devices that are cascaded to other areas. After administrator A logs in to the multipoint control device in the local area, the interface used by administrator A can display the current device connection status of the entire network. Administrator A can directly enter any multipoint control device for maintenance and management.
  • administrator A can view the conference and site list on each multi-point control device, and can control the conferences on each multi-point control device. Assume that Administrator B can only access multipoint control devices and conferences within the region. After administrator B logs in to the multi-point control device in the local area, administrator B can only see the status of each multi-point control device in the area. For the inter-area conference, administrator B can only see the site in the local area. Waiting for the meeting, but not meeting the meeting in other areas.
  • the management unit 31 when the obtaining unit 31 also obtains management information for a multipoint control device that is logged in to the multipoint control device where the device shown in FIG. 3 is located or is logged in to another multipoint control device, the management unit The management information may be directly or indirectly forwarded to the multipoint control device that the management information finally needs to reach according to the obtained topology relationship.
  • the management unit may include a second forwarding sub-unit 328, configured to, when the obtaining unit further obtains management information for a multi-point control device by an administrator logging in to itself or logging in to another multi-point control device, And according to the obtained topology relationship, the management information is directly or indirectly forwarded to the multipoint control device that the management information finally needs to arrive.
  • each of the units shown in FIG. 3 can be disposed on a multi-point control device that operates on the multi-point control device in the same manner as the device shown in FIG. , I won't go into details here.
  • the multipoint control device is an integral part of the distributed multipoint conference system, and the multipoint control device is improved according to the embodiment of the present invention, or a new multipoint control device is provided. Therefore, the distributed multipoint conference system will also change.
  • an embodiment of the present invention provides a distributed multipoint conference system, where the system includes multiple multipoint control devices; wherein, the multipoint control device that has established a communication connection with other multipoint control devices has the distribution
  • the topology relationship of the multipoint control device in the multipoint conference system the topology relationship of the multipoint control device is used to indicate a communication connection relationship between the multipoint control devices, each having the distributed multipoint conference
  • the topology relationship of the multipoint control device in the system is managed according to the topology relationship.
  • each multipoint control device can be configured with one or more identifiers (also referred to as prefixes) for distinguishing terminals connected through multipoint control devices.
  • the prefix can be the phone number area code of the location where the multipoint control device is located, or it can be a domain name. As shown in Figure 4, the prefix of MCU1 is 0755, the number of the terminal controlled by MCU1 can be 07551000, 07551001, etc.
  • the prefix of MCU2 is 0756. The number of the terminal controlled by MCU2 can be 07562000, 07562001, etc.
  • the prefix of MCU4 is 010, the number of the terminal controlled by the MCU4 may be 0106000, 0106001, etc., the prefix of the MCU6 may be 021, and the number of the terminal controlled by the MCU6 may be 0218000, 0218001, and the like.
  • MCU1 and MCU2 belong to IP private network A.
  • MCU3 and MCU4 belong to IP public network.
  • MCU5 and MCU6 belong to IP private network B.
  • IP public network can communicate with IP private network A and IP private network B respectively.
  • IP private network A and IP private network B cannot communicate directly.
  • MCU1 and MCU4 can communicate directly
  • MCU5 and MCU4 can communicate directly
  • MCU1 and MCU5 cannot communicate directly.
  • MCU1, MCU5 and MCU6 are already powered on.
  • MCU4 When the MCU4 is powered on, as shown in Figure 6, it includes:
  • MCU4 sends an online notification to MCU1, MCU5 and MCU6 respectively;
  • S602 MCU1, MCU5, and MCU6 respectively return the topology relationship of each of them to the MCU4;
  • S604 The MCU4 sends the generated topology relationship to the MCU1, the MCU5, and the MCU6, respectively.
  • the topological relationship of the ⁇ MCU is as shown by the dotted line in Fig. 5, and it is assumed that the MCU1 convene the conference, and the terminals that need to participate in the conference are respectively controlled by MCU2, MCU4, and MCU6.
  • the process of convening a meeting is shown in Figure 7, including:
  • S701 MCU1 sends a meeting request to MCU2, and MCU1 sends a meeting request to MCU4.
  • MCU1 sends a request to MCU4 to request a meeting of MCU6, and MCU4 forwards the meeting request to
  • MCU2 returns a meeting response to MCU1
  • MCU4 returns a meeting response to MCU1.
  • MCU6 returns a meeting response to MCU4, and MCU4 forwards the meeting response to MCU1.
  • each MCU can exchange meeting status such as the respective site status.
  • the administrator can log in to any MCU to see the complete conference situation, and can control the conference situation.
  • the multipoint control device can display the topology map of the multipoint control device, the administrator can conveniently access the plurality of distributed multipoint conference systems on a multipoint control device.
  • Point control device since the multipoint control device can display the topology map of the multipoint control device, the administrator can conveniently access the plurality of distributed multipoint conference systems on a multipoint control device. Point control device.
  • an administrator can convene a multi-point conference across multiple regions on a multi-point control device, and multiple multi-point control devices automatically converge to convene a conference, without manually controlling multiple multi-point control devices.
  • the administrator can monitor and control the status of the conference convened by multiple multi-point control devices on a multi-point control device, which facilitates the administrator to monitor and control the multi-point conference.
  • the access authority is set for the administrator, and the multipoint control device displays the topology relationship and the conference situation of the multipoint control device that is compatible with the access authority of the administrator to the administrator, thereby ensuring distributed multipoint.
  • Security of management in the conferencing system In addition, in the existing management scheme in a distributed multipoint conference system, a separate management server (also referred to as a management station in some scenarios) is used to uniformly manage the multipoint control device, the management server, and each A multipoint control device establishes a communication connection, and the management server can manage all the multipoint control devices. When a multipoint conference is held, the management server is responsible for coordinating the allocation of resources by each multipoint control device.
  • the management server also needs to coordinate. In this scenario, an additional server is required to install the management server software.
  • the administrator needs to install and maintain the management server software additionally, which increases the equipment cost and maintenance cost. If the communication port between the management server software and the multipoint control device is It is private, so you need to modify the firewall configuration, which increases the risk of network security and the difficulty of installation. If the management server fails, or the network in the area where the management server is located fails, the multipoint conference service of the entire network cannot be used.
  • each multi-point control device that obtains the topology relationship of the multi-point control device is managed according to the topology relationship, and no additional server installation management server software is required, and the administrator does not need additional installation and maintenance.
  • Manage server software saving equipment costs and maintenance costs; Since there is no need to install management server software, it naturally does not involve modifying the firewall configuration, reducing the risk of network security and installation difficulty; because the management server does not uniformly manage multi-point control devices Therefore, the multipoint conference service of the entire network cannot be used because the management server is faulty or the network in the area where the management server is located is faulty.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

分布式多点会议系统中的管理方法、 装置及系统 本申请要求于 2009 年 03 月 31 日提交中国专利局、 申请号为 200910129579.0的中国专利申请的优先权，其全部内容通过引用结合在本申请 中。 技术领域
本发明涉及分布式多点会议系统，尤其涉及分布式多点会议系统中的管理 技术。
背景技术
视频和 /或音频的多点会议是越来越重要的一种通信方式。 典型的分布式 多点会议系统包括多点控制设备（例如： 多点控制单元 （ MCU , Multipoint Control Unit )、 媒体资源服务器（ MRS , Media Resource Server ) )、 多媒体终端 (以下筒称为终端 )以及通信网络。一个多点控制设备可以处理多个终端通过 通信网络发出的呼叫， 多点控制设备与终端构成点对点的连接，协调建立多点 会议。 终端可以是视频终端、 音频终端或音视频相结合的终端。 通信网络用于 连接多点控制设备和终端， 具体可以包括网关、 路由器或防火墙。 一个多点会 议要由一个多点控制（ MC, Multipoint Control )部分集中管理， MC控制多点 处理（MP, Multipoint Process )部分进行视频、 音频、 数据流的处理， 多点控 制设备可以同时包括 MC部分和 MP部分，也可以只包括 MC部分或 MP部分。
随着网络的不断扩展，企业分散在各地的办公地可以越来越方便的通过多 点会议系统进行通信。每个办公地都可以有至少一个多点控制设备和至少一个 终端， 每个办公地的多点控制设备和终端形成一个区域。
目前的一种分布式多点会议系统中的管理方案为：多点控制设备提供内置 管理台（例如 Web ), 管理员在确定多点控制设备的 IP地址后， 直接登录到多 点控制设备（例如通过 Web方式登录）进行管理， 例如管理多点控制设备本 身或其控制的终端。 当召开会议时， 需要参加会议的终端所对应的多点控制设 备需要级联，在具体实现时， 管理员需要登录到多个多点控制设备上才能将这 些多点控制设备级联，典型的操作是， 管理员在这些多点控制设备上分别进行 召开会议的操作， 然后通过手工方式将这些多点控制设备级联。
本发明的发明人在实现本发明的过程中发现：内置管理台只能管理单个多 点控制设备，如果需要管理多个多点控制设备， 那么管理员就必须要记住每个 多点控制设备的名称或 IP地址， 才能——登录， 从而进行管理。 另外， 如果 通过手工方式将多个多点控制设备级联，那么管理员需要预先确定哪些多点控 制设备级联， 之后再分别登录到确定后的这些多点控制设备上进行级联操作。 由此可见，现有的分布式多点会议系统中的管理方案不但对管理员的要求比较 高， 而且实现管理比较复杂。 发明内容
本发明实施例提供分布式多点会议系统中的管理方法、装置、 多点控制设 备及分布式多点会议系统， 以降低对管理员的要求和实现管理的复杂度。
一种分布式多点会议系统中的管理方法， 包括： 获得所述分布式多点会议 系统中的多点控制设备的拓朴关系，所述多点控制设备的拓朴关系用于表示多 点控制设备之间的通信连接关系； 根据所述获得的拓朴关系进行管理操作。
一种分布式多点会议系统中的管理装置， 包括： 获得单元， 用于获得所述 分布式多点会议系统中的多点控制设备的拓朴关系 ,所述多点控制设备的拓朴 关系用于表示多点控制设备之间的通信连接关系； 管理单元， 用于根据所述获 得单元获得的拓朴关系进行管理操作。
一种多点控制设备， 包括上述的分布式多点会议系统中的管理装置。 一种分布式多点会议系统， 包括多个多点控制设备； 已经与其他多点控制 设备建立通信连接的多点控制设备具有所述分布式多点会议系统中的多点控 制设备的拓朴关系，所述多点控制设备的拓朴关系用于表示多点控制设备之间 的通信连接关系，每个具有所述分布式多点会议系统中的多点控制设备的拓朴 关系根据拓朴关系进行管理操作。
在本发明实施例中，每个获得多点控制设备的拓朴关系的多点控制设备根 据拓朴关系进行管理， 无须管理员记住每个多点控制设备的名称或 IP地址， 也无须管理员通过手工方式将多个多点控制设备级联， 只要具有相应的权限， 管理员就可以通过拓朴关系对拓朴上的相应多点控制设备进行管理。所以， 本 发明实施例对管理员的要求不高， 而且实现管理相对筒单。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施 例或现有技术描述中所需要使用的附图作筒单地介绍，显而易见地， 下面描述 中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲，在不付 出创造性劳动的前提下， 还可以根据这些附图获得其他的附图。
图 1为一种分布式多点会议系统的组成示意图；
图 2为本发明实施例的一种分布式多点会议系统中的管理方法的流程图； 图 3 为本发明实施例的一种分布式多点会议系统中的管理装置的结构示 意图；
图 4 为本发明实施例的多点控制设备配置有前缀的一种分布式多点会议 系统的组成示意图；
图 5为本发明的两个优选实施例应用的网络环境示意图；
图 6为本发明的第一个优选实施例的流程图；
图 7为本发明的第二个优选实施例的流程图。 具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。基于本发明中的实施例， 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
首先对本发明实施例应用的网络场景进行说明。本发明实施例所述的分布 式多点会议系统包括多个区域，每个区域具有至少一个多点控制设备，每个多 点控制设备控制至少一个终端，多个区域之间通过多点控制设备级联举行跨区 域的会议。 多点控制设备可以是指 MCU、 MRS等具有多点控制功能的设备。 以图 1为例， 分布式多点会议系统包括三个区域， 区域一具有 MCU1和多个 终端， 区域二具有 MCU2和多个终端， 区域三具有 MCU3和多个终端， MCU1 与 MCU2物理连接， MCU1与 MCU3物理连接， 如果 MCU1与 MCU2建立 通信连接， MCU1与 MCU3建立通信连接， 那么区域一、 区域二和区域三通 过 MCU2与 MCU1之间的通信连接和 MCU1与 MCU3之间的通信连接举行跨 三个区域的会议。
下面对本发明实施例的分布式多点会议系统中的管理方法、装置、 多点控 制设备及系统进行说明。
本发明实施例提供的一种分布式多点会议系统中的管理方法如图 2所示， 包括：
S201 : 获得所述分布式多点会议系统中的多点控制设备的拓朴关系，所述 多点控制设备的拓朴关系用于表示多点控制设备之间的通信连接关系；
S202: 根据所述获得的拓朴关系进行管理操作。
所述分布式多点会议系统中的多点控制设备的拓朴关系可以是指多点控 制设备的全部拓朴关系，也可以是指多点控制设备的部分拓朴关系。还是以图 1为例， MCU2既可以只获得其与 MCU1之间的通信连接关系，也可以获得其 与 MCU1之间的通信连接关系和 MCU1与 MCU3之间的通信连接关系。
在具体实现时，可以有多种方式获得所述分布式多点会议系统中的多点控 制设备的拓朴关系。例如，预先在本地配置所述分布式多点会议系统中的多点 控制设备的拓朴关系， 当需要拓朴关系时，从本地获得预先配置的所述分布式 多点会议系统中的多点控制设备的拓朴关系。再例如， 其他多点控制设备提供 所述分布式多点会议系统中的多点控制设备的拓朴关系， 或者说， 获得其他多 点控制设备提供的所述分布式多点会议系统中的多点控制设备的拓朴关系。在 具体实现时，有多种方式获得其他多点控制设备提供的所述分布式多点会议系 统中的多点控制设备的拓朴关系， 例如， 向与自身具有物理连接的多点控制设 备请求建立通信连接；获得所述与自身具有物理连接的多点控制设备提供的所 述分布式多点会议系统中的多点控制设备的拓朴关系。向与自身具有物理连接 的多点控制设备请求建立通信连接可以在开机后执行。
需要说明的是， 多点控制设备使用的拓朴关系可以是静态的，也可以是动 态的。具体来说， 无论是预先在本地配置所述分布式多点会议系统中的多点控 制设备的拓朴关系，还是从其他多点控制设备获得所述分布式多点会议系统中 的多点控制设备的拓朴关系，只要是第一次获得了所述分布式多点会议系统中 的多点控制设备的拓朴关系， 那么在以后的管理过程中， 所述分布式多点会议 系统中的多点控制设备的拓朴关系既可以保持不变，也可以随多点控制设备之 间的通信连接关系的变化而得到更新。多点控制设备使用的拓朴关系是保持静 在具体实现时， 可以有多种方式根据所述获得的拓朴关系进行管理操作。 下面介绍几种典型的管理操作。
第一种方式
当获得分布式多点会议系统中的多点控制设备的拓朴关系后，可以将所述 获得的拓朴关系同步给其他多点控制设备。 具体的， 与自身具有物理连接的多 点控制设备可以向自身发出建立通信连接的请求， 即， 获得与自身具有物理连 接的多点控制设备发出的建立通信连接的请求，之后， 向所述与自身具有物理 连接的多点控制设备提供所述获得的拓朴关系。与自身具有物理连接的多点控 制设备向自身发出建立通信连接的请求的时机可以是在与自身具有物理连接 的多点控制设备开机后。
以图 5为例，假设分布式多点会议系统原来包括 MCU1、 MCU2、 MCU3、 MCU4和 MCU5 , MCU4获得的拓朴关系为： MCU1与 MCU2具有通信连接 关系、 MCU1与 MCU4具有通信连接关系、 MCU3与 MCU4具有通信连接关 系、 MCU4与 MCU5具有通信连接关系。 当 MCU6向 MCU4发出建立通信连 接的请求后， MCU4可以将其获得的上述拓朴关系提供给 MCU6。
第二种方式
如果分布式多点会议系统中的多点控制设备的拓朴关系发生变化，则可以 更新所述分布式多点会议系统中的多点控制设备的拓朴关系。多点控制设备的 拓朴关系发生变化例如为有新的多点控制设备加入拓朴或者有多点控制设备 退出拓朴等情形。具体的， 当与自身具有通信连接的多点控制设备更新所述分 布式多点会议系统中的多点控制设备的拓朴关系后，可以将更新后的所述分布 式多点会议系统中的多点控制设备的拓朴关系提供给自身， 即， 可以获得与自 身具有通信连接的多点控制设备提供的更新后的所述分布式多点会议系统中 的多点控制设备的拓朴关系；当获得与自身具有物理连接的多点控制设备发出 建立通信连接的请求后，将所述与自身具有物理连接的多点控制设备加入到所 述分布式多点会议系统中的多点控制设备的拓朴关系；当确定与自身具有通信 连接的多点控制设备退出拓朴后，将退出拓朴的多点控制设备从所述分布式多 点会议系统中的多点控制设备的拓朴关系中删除。
以图 5和第一种方式为例， 当 MCU6加入到拓朴关系后， MCU4将其与 MCU6具有的通信连接关系增加到 MCU4原来具有的拓朴关系中， 并将更新 后的拓朴关系或 MCU4与 MCU6具有的通信连接关系同步给 MCU1、 MCU3 和 MCU5。 再^殳 MCU6退出拓朴关系， 那么 MCU4在其具有的拓朴关系中 将其与 MCU6 具有的通信连接关系删除， 并将更新后的拓朴关系同步给 MCU1、 MCU3和 MCU5。
当然，更新所述分布式多点会议系统中的多点控制设备的拓朴关系还可以 是其他情形， 例如多点控制设备之间的通信连接关系发生变化， 这里不再—— 举例说明。
更新所述分布式多点会议系统中的多点控制设备的拓朴关系后，可以将所 述更新后的所述分布式多点会议系统中的多点控制设备的拓朴关系同步给与 自身具有通信连接的多点控制设备。 实质上，拓朴关系中的每一个多点控制设 备都可以将更新后的所述分布式多点会议系统中的多点控制设备的拓朴关系 同步给与自身具有通信连接的多点控制设备，以使拓朴关系中的所有多点控制 设备当前使用的所述分布式多点会议系统中的多点控制设备的拓朴关系都保 持一致。
由于分布式多点会议系统一个核心的任务就是召开视频和 /或音频会议， 所以， 召集会议的操作是分布式多点会议系统的管理操作中的一项重要的操 作。
第三种方式
当需要召集会议时，根据获得的拓朴关系， 向需要参加会议的终端对应的 多点控制设备发出开会请求。如果需要参加会议的终端对应的多点控制设备不 是与自身具有通信连接关系的多点控制设备， 则根据所述获得的拓朴关系， 向 与自身具有通信连接关系的多点控制设备发出开会请求，由所述与自身具有通 信连接关系的多点控制设备将开会请求直接或间接转发给需要参加会议的终 端对应的多点控制设备。这里所述的间接是指，如果所述与自身具有通信连接 关系的多点控制设备与需要参加会议的终端对应的多点控制设备不具有通信 连接关系，那么所述与自身具有通信连接关系的多点控制设备将开会请求转发 给与其具有通信连接关系的多点控制设备， 以此类推， 直至开会请求到达需要 参加会议的终端对应的多点控制设备。如果需要参加会议的终端对应的多点控 制设备是与自身具有通信连接关系的多点控制设备，那么直接向其发出开会请 求即可。 下文所述的间接也可以参考这个解释。
向需要参加会议的终端对应的多点控制设备发出开会请求后，还可以直接 或间接获得需要参加会议的终端对应的多点控制设备返回的开会响应。 具体 的， 需要参加会议的终端对应的多点控制设备收到开会请求后， 可以对需要参 加会议的终端进行控制， 例如， 将需要参加会议的终端加入到会议中， 加入成 功后， 向发出开会请求的多点控制设备返回成功的开会响应， 否则， 返回失败 的开会响应。 当然， 开会响应也可以携带其他信息， 这里不再——举例说明。 当获得与自身具有通信连接关系的多点控制设备发出的开会请求时，如果 自身控制的所有终端都不需要参加会议， 则可以根据所述获得的拓朴关系， 将 所述开会请求直接或间接转发给需要参加会议的终端对应的多点控制设备。将 所述开会请求直接或间接转发给需要参加会议的终端对应的多点控制设备后， 当直接或间接获得需要参加会议的终端对应的多点控制设备发出的开会响应 时，可以将所述开会响应转发给所述发出开会请求的与自身具有通信连接关系 的多点控制设备。
会议召开成功后，各个多点控制设备之间可以相互交换各自会场的状态等 会议情况， 这样， 分布式多点会议系统中的每个多点控制设备都可以向管理员 提供整个会议情况。
以图 5为例，假设 MCU1需要召集 MCU3下的终端和 MCU6下的终端开 会， MCU1向 MCU4发出开会请求， MCU4会发现没有召集其下的终端开会， 而是召集 MCU3下的终端和 MCU6下的终端开会， 于是， MCU4将开会请求 转发给 MCU3 和 MCU6。 如果 MCU3将其下的终端成功的加入到会议中， MCU6将其下的终端成功的加入到会议中，那么 MCU3和 MCU6可以向 MCU4 返回成功的开会响应， MCU4再将成功的开会响应返回给 MCU1。
第四种方式
有时， 管理员需要查看会议情况， 此时， 管理员所登录的多点控制设备应 该将会议情况提供给管理员。 具体的， 当获得管理员访问自身的请求时， 确定 所述管理员的访问权限，向所述管理员提供与其访问权限相适应的多点控制设 备的拓朴关系及会议情况。向管理员提供多点控制设备的拓朴关系可以是指向 管理员显示多点控制设备的拓朴关系，向管理员提供会议情况可以是指向管理 员显示会场状态等情况。向所述管理员提供与其访问权限相适应的多点控制设 备的拓朴关系及会议情况具体可以包括：如果所述管理员具有访问所述分布式 多点会议系统中的所有多点控制设备的权限，则向所述管理员提供所述分布式 多点会议系统中的多点控制设备的全部拓朴关系及在所述全部拓朴关系上的 会议情况； 如果所述管理员仅具有访问自身所在的区域的多点控制设备的权 限，则向所述管理员提供自身所在的区域的多点控制设备的拓朴关系及在所述 自身所在的区域的多点控制设备的拓朴关系上的会议情况。
管理员的权限可以根据实际需要而灵活配置，管理员的权限例如包括设备 管理和会议管理。设备管理权限可以控制管理员是否能够访问多点控制设备以 及对多点控制设备进行配置。会议管理权限可以控制管理员是否能够对级联到 其他多点控制设备上的会议进行控制。 例如， 假设管理员 A可以访问其他区 域的多点控制设备，并可以对级联到其他区域的多点控制设备上的会议进行控 制。 当管理员 A登录到本区域的多点控制设备后， 管理员 A使用的界面可以 显示整个网络当前的设备连接状态， 管理员 A可以直接进入任意一台多点控 制设备进行维护和管理。 对于级联到多个多点控制设备的会议， 管理员 A可 以看到各多点控制设备上的会议和会场列表，可以对各多点控制设备上的会议 进行控制。 假设， 管理员 B 只能访问本区域内的多点控制设备和会议。 当管 理员 B登录到本区域的多点控制设备后， 管理员 B只能看到本区域的各个多 点控制设备的情况， 对于跨区域的会议， 管理员 B 只能看到本区域的会场等 会议情况， 而看不到其他区域的会场等会议情况。
另外， 管理员可以在一个多点控制设备上对另一个多点控制设备进行管 理。具体的， 当获得登录到自身或登录到其他多点控制设备的管理员对一个多 点控制设备的管理信息时，根据所述获得的拓朴关系，将所述管理信息直接或 间接转发给所述管理信息最终需要到达的多点控制设备。还是以图 5为例，假 设管理员在 MCU1上需要对 MCU6进行管理， MCU1产生管理员对 MCU6的 管理信息， MCU1 将管理信息提供给 MCU4 , MCU4 再将管理信息转发给 MCU6。
需要说明的是， 上述几个管理操作可以在实际应用中分别进行。
还需要说明的是， S201和 S202的执行主体可以是一个多点控制设备。 对应图 2所示的方法，本发明实施例提供一种分布式多点会议系统中的管 理装置。 如图 3所示， 所述管理装置包括： 获得单元 31 , 用于获得所述分布 式多点会议系统中的多点控制设备的拓朴关系 ,所述多点控制设备的拓朴关系 用于表示多点控制设备之间的通信连接关系； 管理单元 32, 用于根据所述获 得单元 31获得的拓朴关系进行管理操作。
所述分布式多点会议系统中的多点控制设备的拓朴关系可以是指多点控 制设备的全部拓朴关系，也可以是指多点控制设备的部分拓朴关系。还是以图 1为例， MCU2既可以只获得其与 MCU1之间的通信连接关系，也可以获得其 与 MCU1之间的通信连接关系和 MCU1与 MCU3之间的通信连接关系。
获得单元 31可以有多种方式获得所述分布式多点会议系统中的多点控制 设备的拓朴关系。 例如， 获得单元 31从本地获得预先配置的所述分布式多点 会议系统中的多点控制设备的拓朴关系， 或者， 获得单元 31获得其他多点控 制设备提供的所述分布式多点会议系统中的多点控制设备的拓朴关系。在具体 实现时， 获得单元 31可以有多种方式获得其他多点控制设备提供的所述分布 式多点会议系统中的多点控制设备的拓朴关系， 例如， 向与图 3所示的装置所 在的多点控制设备具有物理连接的多点控制设备请求建立通信连接，获得所述 与图 3 所示的装置所在的多点控制设备具有物理连接的多点控制设备提供的 所述分布式多点会议系统中的多点控制设备的拓朴关系。在具体实现时， 获得 单元 31可以包括： 请求子单元 311 , 用于向与图 3所示的装置所在的多点控 制设备具有物理连接的多点控制设备请求建立通信连接； 获得子单元 312, 用 于在所述请求子单元向与图 3 所示的装置所在的多点控制设备具有物理连接 的多点控制设备请求建立通信连接后，获得所述与图 3所示的装置所在的多点 控制设备具有物理连接的多点控制设备提供的所述分布式多点会议系统中的 多点控制设备的拓朴关系。 获得单元 31向与图 3所示的装置所在的多点控制 设备具有物理连接的多点控制设备请求建立通信连接可以在图 3 所示的装置 所在的多点控制设备开机后执行。 需要说明的是， 获得单元 31获得的拓朴关系可以是静态的， 也可以是动 态的。 具体来说， 获得单元 31获得所述分布式多点会议系统中的多点控制设 备的拓朴关系后，所述分布式多点会议系统中的多点控制设备的拓朴关系既可 以保持不变， 也可以随多点控制设备之间的通信连接关系的变化而得到更新。
获得单元 31获得拓朴关系后，管理单元 32可以将所述获得的拓朴关系同 步给其他多点控制设备。 在具体实现时， 管理单元 32可以包括第一同步子单 元 321 , 用于在获得单元 31获得拓朴关系后， 将所述获得的拓朴关系同步给 其他多点控制设备。具体的， 与图 3所示的装置所在的多点控制设备具有物理 连接的多点控制设备可以向图 3 所示的装置所在的多点控制设备发出建立通 信连接的请求， 即， 获得单元 31获得与图 3所示的装置所在的多点控制设备 具有物理连接的多点控制设备发出的建立通信连接的请求， 之后， 管理单元 32向所述与图 3所示的装置所在的多点控制设备具有物理连接的多点控制设 备提供所述获得的拓朴关系。与图 3所示的装置所在的多点控制设备具有物理 连接的多点控制设备向图 3 所示的装置所在的多点控制设备发出建立通信连 接的请求的时机可以是在与图 3 所示的装置所在的多点控制设备具有物理连 接的多点控制设备开机后。
如果所述分布式多点会议系统中的多点控制设备的拓朴关系发生变化，则 所述管理单元 32 更新所述分布式多点会议系统中的多点控制设备的拓朴关 系。 在具体实现时， 管理单元 32可以包括更新子单元 322, 用于如果所述分 布式多点会议系统中的多点控制设备的拓朴关系发生变化，则更新所述分布式 多点会议系统中的多点控制设备的拓朴关系。多点控制设备的拓朴关系发生变 化例如为有新的多点控制设备加入拓朴或者有多点控制设备退出拓朴等情形。 具体的，当与图 3所示的装置所在的多点控制设备具有通信连接的多点控制设 备更新所述分布式多点会议系统中的多点控制设备的拓朴关系后，可以将更新 后的所述分布式多点会议系统中的多点控制设备的拓朴关系提供给图 3 所示 的装置所在的多点控制设备， 即， 获得单元 31可以获得与图 3所示的装置所 在的多点控制设备具有通信连接的多点控制设备提供的更新后的所述分布式 多点会议系统中的多点控制设备的拓朴关系； 当获得单元 31获得与图 3所示 的装置所在的多点控制设备具有物理连接的多点控制设备发出建立通信连接 的请求后， 管理单元 32可以将所述与图 3所示的装置所在的多点控制设备具 有物理连接的多点控制设备加入到所述分布式多点会议系统中的多点控制设 备的拓朴关系； 当管理单元 32确定与图 3所示的装置所在的多点控制设备具 有通信连接的多点控制设备退出拓朴后， 管理单元 32将退出拓朴的多点控制 设备从所述分布式多点会议系统中的多点控制设备的拓朴关系中删除。 当然， 管理单元 32更新所述分布式多点会议系统中的多点控制设备的拓朴关系还可 以是其他情形， 这里不再——举例说明。
管理单元 32更新所述分布式多点会议系统中的多点控制设备的拓朴关系 后， 管理单元 32可以将所述更新后的所述分布式多点会议系统中的多点控制 设备的拓朴关系同步给与图 3 所示的装置所在的多点控制设备具有通信连接 的多点控制设备。 在具体实现时， 管理单元 32可以包括第二同步子单元 323 , 用于在所述更新子单元更新所述分布式多点会议系统中的多点控制设备的拓 朴关系后 ,将所述更新后的所述分布式多点会议系统中的多点控制设备的拓朴 关系同步给与自身具有通信连接的多点控制设备。 实质上，拓朴关系中的每一 个多点控制设备都可以将更新后的所述分布式多点会议系统中的多点控制设 备的拓朴关系同步给与自身具有通信连接的多点控制设备，以使拓朴关系中的 所有多点控制设备当前使用的所述分布式多点会议系统中的多点控制设备的 拓朴关系都保持一致。
当图 3 所示的装置所在的多点控制设备需要召集会议时， 所述管理单元 32 可以根据所述获得的拓朴关系， 向需要参加会议的终端对应的多点控制设 备发出开会请求。 在具体实现时， 管理单元 32可以包括请求子单元 324, 用 于当需要召集会议时，根据所述获得的拓朴关系， 向需要参加会议的终端对应 的多点控制设备发出开会请求。如果需要参加会议的终端对应的多点控制设备 不是与图 3 所示的装置所在的多点控制设备具有通信连接关系的多点控制设 备， 则管理单元 32可以根据所述获得的拓朴关系， 向与图 3所示的装置所在 的多点控制设备具有通信连接关系的多点控制设备发出开会请求，由所述与图 3 所示的装置所在的多点控制设备具有通信连接关系的多点控制设备将开会 请求直接或间接转发给需要参加会议的终端对应的多点控制设备。这里所述的 间接是指，如果所述与图 3所示的装置所在的多点控制设备具有通信连接关系 的多点控制设备与需要参加会议的终端对应的多点控制设备不具有通信连接 关系 ,那么所述与图 3所示的装置所在的多点控制设备具有通信连接关系的多 点控制设备将开会请求转发给与其具有通信连接关系的多点控制设备，以此类 推， 直至开会请求到达需要参加会议的终端对应的多点控制设备。如果需要参 加会议的终端对应的多点控制设备是与图 3 所示的装置所在的多点控制设备 具有通信连接关系的多点控制设备， 那么直接向其发出开会请求即可。 下文所 述的间接也可以参考这个解释。
管理单元 32 向需要参加会议的终端对应的多点控制设备发出开会请求 后， 获得单元 31还可以直接或间接获得需要参加会议的终端对应的多点控制 设备返回的开会响应。具体的， 需要参加会议的终端对应的多点控制设备收到 开会请求后， 可以对需要参加会议的终端进行控制， 例如， 将需要参加会议的 终端加入到会议中，加入成功后， 向发出开会请求的多点控制设备返回成功的 开会响应， 否则，返回失败的开会响应。 当然，开会响应也可以携带其他信息， 这里不再——举例说明。
当所述获得单元 31还获得与图 3所示的装置所在的多点控制设备具有通 信连接关系的多点控制设备发出的开会请求时，如果图 3所示的装置所在的多 点控制设备控制的所有终端都不需要参加会议， 则所述管理单元 32可以根据 所述获得的拓朴关系，将所述开会请求直接或间接转发给需要参加会议的终端 对应的多点控制设备。 在具体实现时， 管理单元 32可以包括第一转发子单元 325 , 用于当所述获得单元还获得与自身具有通信连接关系的多点控制设备发 出的开会请求时，如果自身控制的所有终端都不需要参加会议， 则根据所述获 得的拓朴关系，将所述开会请求直接或间接转发给需要参加会议的终端对应的 多点控制设备。 管理单元 32将所述开会请求直接或间接转发给需要参加会议 的终端对应的多点控制设备后， 当获得单元 31直接或间接获得需要参加会议 的终端对应的多点控制设备发出的开会响应时， 管理单元 32可以将所述开会 响应转发给所述发出开会请求的与自身具有通信连接关系的多点控制设备。
会议召开成功后，各个多点控制设备之间可以相互交换各自会场的状态等 会议情况， 这样， 分布式多点会议系统中的每个多点控制设备都可以向管理员 提供整个会议情况。
当所述获得单元 31还获得管理员访问图 3所示的装置所在的多点控制设 备的请求时， 所述管理单元 32可以首先确定所述管理员的访问权限， 之后再 向所述管理员提供与其访问权限相适应的多点控制设备的拓朴关系及会议情 况。 在具体实现时， 管理单元 32可以包括： 权限检查子单元 326, 用于当所 述获得单元还获得管理员访问自身的请求时，确定所述管理员的访问权限； 提 供子单元 327, 用于向所述管理员提供所述权限检查子单元 326确定的与所述 管理员访问权限相适应的多点控制设备的拓朴关系及会议情况。向管理员提供 多点控制设备的拓朴关系可以是指向管理员显示多点控制设备的拓朴关系，向 管理员提供会议情况可以是指向管理员显示会场状态等情况。 管理单元 32向 所述管理员提供与其访问权限相适应的多点控制设备的拓朴关系及会议情况 具体可以包括：如果所述管理员具有访问所述分布式多点会议系统中的所有多 点控制设备的权限， 则管理单元 32向所述管理员提供所述分布式多点会议系 统中的多点控制设备的全部拓朴关系及在所述全部拓朴关系上的会议情况；如 果所述管理员仅具有访问自身所在的区域的多点控制设备的权限，则管理单元 32 向所述管理员提供自身所在的区域的多点控制设备的拓朴关系及在所述自 身所在的区域的多点控制设备的拓朴关系上的会议情况。
管理员的权限可以根据实际需要而灵活配置，管理员的权限例如包括设备 管理和会议管理。设备管理权限可以控制管理员是否能够访问多点控制设备以 及对多点控制设备进行配置。会议管理权限可以控制管理员是否能够对级联到 其他多点控制设备上的会议进行控制。 例如， 假设管理员 A可以访问其他区 域的多点控制设备，并可以对级联到其他区域的多点控制设备上的会议进行控 制。 当管理员 A登录到本区域的多点控制设备后， 管理员 A使用的界面可以 显示整个网络当前的设备连接状态， 管理员 A可以直接进入任意一台多点控 制设备进行维护和管理。 对于级联到多个多点控制设备的会议， 管理员 A可 以看到各多点控制设备上的会议和会场列表，可以对各多点控制设备上的会议 进行控制。 假设， 管理员 B 只能访问本区域内的多点控制设备和会议。 当管 理员 B登录到本区域的多点控制设备后， 管理员 B只能看到本区域的各个多 点控制设备的情况， 对于跨区域的会议， 管理员 B 只能看到本区域的会场等 会议情况， 而看不到其他区域的会场等会议情况。
另外， 当所述获得单元 31还获得登录到图 3所示的装置所在的多点控制 设备或登录到其他多点控制设备的管理员对一个多点控制设备的管理信息时， 所述管理单元 32可以根据所述获得的拓朴关系， 将所述管理信息直接或间接 转发给所述管理信息最终需要到达的多点控制设备。在具体实现时， 管理单元 可以包括第二转发子单元 328, 用于当所述获得单元还获得登录到自身或登录 到其他多点控制设备的管理员对一个多点控制设备的管理信息时，根据所述获 得的拓朴关系，将所述管理信息直接或间接转发给所述管理信息最终需要到达 的多点控制设备。
需要说明的是，图 3所示的装置中的每个单元都可以设置在多点控制设备 上，这些单元在多点控制设备上的工作方式与在图 3所示的装置中的工作方式 相同， 这里不再赘述。
本领域技术人员都应该知道，多点控制设备是分布式多点会议系统的组成 部分， 由于本发明实施例对多点控制设备进行了改进， 或者说， 提供了一种新 的多点控制设备， 所以， 分布式多点会议系统也会发生变化。 对此， 本发明实施例提供了一种分布式多点会议系统， 所述系统包括多个 多点控制设备； 其中， 已经与其他多点控制设备建立通信连接的多点控制设备 具有所述分布式多点会议系统中的多点控制设备的拓朴关系 ,所述多点控制设 备的拓朴关系用于表示多点控制设备之间的通信连接关系，每个具有所述分布 式多点会议系统中的多点控制设备的拓朴关系根据拓朴关系进行管理操作。
为协调多个多点控制设备召开级联的多点会议，每个多点控制设备都可以 配置一个或多个标识（也可以称为前缀）， 用于区分通过多点控制设备连接的 终端， 前缀可以是多点控制设备所在地的电话号码区号， 也可以是域名。 以图 4为例， MCU1的前缀是 0755 , MCU1控制的终端的号码可以是 07551000、 07551001 等形式， MCU2 的前缀是 0756, MCU2控制的终端的号码可以是 07562000、 07562001等形式， MCU4的前缀是 010, MCU4控制的终端的号码 可以是 0106000、 0106001等形式， MCU6的前缀可以是 021 , MCU6控制的 终端的号码可以是 0218000、 0218001等形式。
有关上述分布式多点会议系统中的多点控制设备及多点控制设备之间的 通信可以参照图 2所示的方法和图 3所示的装置中的有关描述，这里不再赘述。
为使本领域技术人员更加清楚的理解本发明实施例，下面再介绍两个优选 实施例。
这两个优选实施例应用的网络环境如图 5所示。 MCU1和 MCU2同属于 IP私网 A, MCU3和 MCU4同属于 IP公网， MCU5和 MCU6同属于 IP私网 B, IP公网可以分别与 IP私网 A和 IP私网 B直接通信， IP私网 A与 IP私网 B不能直接通信。 例如， MCU1与 MCU4可以直接通信， MCU5与 MCU4可 以直接通信， MCU1与 MCU5不能直接通信。
在第一个优选实施例中，假设 MCU1、 MCU5和 MCU6已经开机。当 MCU4 开机时， 如图 6所示， 包括：
S601: MCU4分别向 MCU1、 MCU5和 MCU6发出上线通知；
S602: MCU1、 MCU5和 MCU6分别向 MCU4返回各自所在的拓朴关系； S603: MCU4生成至少包括 MCUl , MCU4、 MCU5和 MCU6在内的拓 朴关系；
S604: MCU4分别向 MCU1、 MCU5和 MCU6发送生成的拓朴关系。 在第二个优选实施例中， 殳 MCU的拓朴关系如图 5中的虚线所示， 再 假设 MCU1召集会议， 需要参加会议的终端分别由 MCU2、 MCU4和 MCU6 控制。 召集会议的流程如图 7所示， 包括：
S701 : MCU1向 MCU2发出开会请求， MCU1向 MCU4发出开会请求，
MCU1向 MCU4发出请求 MCU6开会的开会请求， MCU4将开会请求转发给
MCU6;
S702: MCU2向 MCU1返回开会响应， MCU4向 MCU1返回开会响应，
MCU6向 MCU4返回开会响应， MCU4将开会响应转发给 MCU1。
如果 MCU2、 MCU4和 MCU6返回的都是成功的开会响应，那么各个 MCU 就可以相互交换各自的会场状态等会议情况。 管理员在任何一个 MCU上登录 都可以看到完整的会议情况， 可以对会议情况进行控制操作。
在本发明实施例中， 由于多点控制设备可以显示多点控制设备的拓朴图， 所以，管理员可以在一个多点控制设备上方便的访问到分布式多点会议系统中 的多个多点控制设备。
在本发明实施例中，管理员在一个多点控制设备上就可以召集跨区域的多 点会议， 多个多点控制设备会自动级联召开会议， 不需人工将多个多点控制设 备级联。
在本发明实施例中，管理员在一个多点控制设备上就可以对通过多个多点 控制设备召集的会议的情况进行状态监视和控制，方便了管理员对多点会议的 监视和控制。
在本发明实施例中， 为管理员设置访问权限， 多点控制设备将与管理员的 访问权限相适应的多点控制设备的拓朴关系和会议情况显示给管理员，保证了 分布式多点会议系统中的管理的安全性。 另外，在现有的一种分布式多点会议系统中的管理方案中，使用单独的管 理服务器（在某些场景下， 也可以称为管理台）统一管理多点控制设备， 管理 服务器和各多点控制设备之间建立通信连接，管理服务器可以管理全部的多点 控制设备。当召开多点会议时，管理服务器负责协调各多点控制设备分配资源， 如果需要多点控制设备级联， 管理服务器也要进行协调。 在这种方案中， 需要 额外使用一台服务器安装管理服务器软件，管理员需要额外安装和维护管理服 务器软件，增加了设备成本和维护成本； 管理服务器软件和多点控制设备之间 的通信端口如果是私有的， 那么需要修改防火墙配置，增加了网络安全的风险 和安装难度； 如果管理服务器发生故障， 或者管理服务器所在区域的网络发生 故障， 那么整个网络的多点会议业务都无法使用。 而在本发明实施例中， 每个 获得多点控制设备的拓朴关系的多点控制设备根据拓朴关系进行管理，无须额 外使用一台服务器安装管理服务器软件，无须管理员需要额外安装和维护管理 服务器软件， 节省了设备成本和维护成本； 由于无须安装管理服务器软件， 所 以自然不涉及修改防火墙配置的问题， 降低了网络安全的风险和安装难度； 由 于不是由管理服务器统一管理多点控制设备， 所以， 不会因管理服务器发生故 障或者管理服务器所在区域的网络发生故障，而导致整个网络的多点会议业务 都无法使用。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程， 是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算 机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。 其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory, ROM )或随机存储记忆体（Random Access Memory, RAM )等。
以上所述仅是本发明的优选实施方式，应当指出，对于本技术领域的普通 技术人员来说， 在不脱离本发明原理的前提下， 还可以作出若干改进和润饰， 这些改进和润饰也应视为本发明的保护范围。

Claims

权 利 要 求 书
1.一种分布式多点会议系统中的管理方法， 其特征在于， 包括：
获得所述分布式多点会议系统中的多点控制设备的拓朴关系 ,所述多点控 制设备的拓朴关系用于表示多点控制设备之间的通信连接关系；
根据所述获得的拓朴关系进行管理操作。
2.如权利要求 1所述的方法， 其特征在于， 获得所述分布式多点会议系统 中的多点控制设备的拓朴关系包括：从本地获得预先配置的所述分布式多点会 议系统中的多点控制设备的拓朴关系， 或者， 获得其他多点控制设备提供的所 述分布式多点会议系统中的多点控制设备的拓朴关系。
3.如权利要求 2所述的方法， 其特征在于， 获得其他多点控制设备提供的 所述分布式多点会议系统中的多点控制设备的拓朴关系包括：
向与自身具有物理连接的多点控制设备请求建立通信连接；
获得所述与自身具有物理连接的多点控制设备提供的所述分布式多点会 议系统中的多点控制设备的拓朴关系。
4.如权利要求 1-3任意一项所述的方法， 其特征在于， 根据所述获得的拓 朴关系进行管理操作包括： 将所述获得的拓朴关系同步给其他多点控制设备。
5.如权利要求 4所述的方法， 其特征在于， 将所述获得的拓朴关系同步给 其他多点控制设备包括：
获得与自身具有物理连接的多点控制设备发出的建立通信连接的请求； 向所述与自身具有物理连接的多点控制设备提供所述获得的拓朴关系。
6.如权利要求 1-3任意一项所述的方法， 其特征在于， 根据所述获得的拓 朴关系进行管理操作包括：如果所述分布式多点会议系统中的多点控制设备的 拓朴关系发生变化，则更新所述分布式多点会议系统中的多点控制设备的拓朴 关系。
7.如权利要求 6所述的方法， 其特征在于， 更新所述分布式多点会议系统 中的多点控制设备的拓朴关系包括：获得与自身具有通信连接的多点控制设备 提供的更新后的所述分布式多点会议系统中的多点控制设备的拓朴关系。
8.如权利要求 6所述的方法， 其特征在于， 更新所述分布式多点会议系统 中的多点控制设备的拓朴关系后还包括：将所述更新后的所述分布式多点会议 系统中的多点控制设备的拓朴关系同步给与自身具有通信连接的多点控制设 备。
9.如权利要求 1-3任意一项所述的方法， 其特征在于， 根据所述获得的拓 朴关系进行管理操作包括： 当需要召集会议时， 根据所述获得的拓朴关系， 向 需要参加会议的终端对应的多点控制设备发出开会请求。
10.如权利要求 9所述的方法， 其特征在于， 如果需要参加会议的终端对 应的多点控制设备不是与自身具有通信连接关系的多点控制设备，则所述当需 要召集会议时，根据所述获得的拓朴关系， 向需要参加会议的终端对应的多点 控制设备发出开会请求包括： 根据所述获得的拓朴关系， 向与自身具有通信连 接关系的多点控制设备发出开会请求，由所述与自身具有通信连接关系的多点 控制设备将开会请求直接或间接转发给需要参加会议的终端对应的多点控制 设备。
11.如权利要求 9所述的方法， 其特征在于， 向需要参加会议的终端对应 的多点控制设备发出开会请求后还包括：直接或间接获得需要参加会议的终端 对应的多点控制设备返回的开会响应。
12.如权利要求 1-3任意一项所述的方法，其特征在于，根据所述获得的拓 朴关系进行管理操作包括：当获得与自身具有通信连接关系的多点控制设备发 出的开会请求时，如果自身控制的所有终端都不需要参加会议， 则根据所述获 得的拓朴关系，将所述开会请求直接或间接转发给需要参加会议的终端对应的 多点控制设备。
13.如权利要求 12所述的方法， 其特征在于， 将所述开会请求直接或间接 转发给需要参加会议的终端对应的多点控制设备后还包括：当直接或间接获得 需要参加会议的终端对应的多点控制设备发出的开会响应时，将所述开会响应 转发给所述发出开会请求的与自身具有通信连接关系的多点控制设备。
14.如权利要求 1-3任意一项所述的方法，其特征在于，根据所述获得的拓 朴关系进行管理操作包括： 当获得管理员访问自身的请求时，确定所述管理员 的访问权限，向所述管理员提供与其访问权限相适应的多点控制设备的拓朴关 系及会议情况。
15.如权利要求 1-3任意一项所述的方法，其特征在于，根据所述获得的拓 朴关系进行管理操作包括：当获得登录到自身或登录到其他多点控制设备的管 理员对一个多点控制设备的管理信息时，根据所述获得的拓朴关系，将所述管 理信息直接或间接转发给所述管理信息最终需要到达的多点控制设备。
16.—种分布式多点会议系统中的管理装置， 其特征在于， 包括： 获得单元，用于获得所述分布式多点会议系统中的多点控制设备的拓朴关 系， 所述多点控制设备的拓朴关系用于表示多点控制设备之间的通信连接关 系；
管理单元， 用于根据所述获得单元获得的拓朴关系进行管理操作。
17.如权利要求 16所述的装置， 其特征在于， 所述获得单元具体用于从本 地获得预先配置的所述分布式多点会议系统中的多点控制设备的拓朴关系，或 者 ,所述获得单元获得其他多点控制设备提供的所述分布式多点会议系统中的 多点控制设备的拓朴关系。
18.如权利要求 16或 17所述的装置， 其特征在于， 所述管理单元包括： 第一同步子单元， 用于将所述获得的拓朴关系同步给其他多点控制设备。
19.如权利要求 16或 17所述的装置， 其特征在于， 所述管理单元包括： 更新子单元，用于如果所述分布式多点会议系统中的多点控制设备的拓朴关系 发生变化， 则更新所述分布式多点会议系统中的多点控制设备的拓朴关系。
20.如权利要求 19所述的装置， 其特征在于， 所述管理单元还包括： 第二 同步子单元，用于在所述更新子单元更新所述分布式多点会议系统中的多点控 制设备的拓朴关系后，将所述更新后的所述分布式多点会议系统中的多点控制 设备的拓朴关系同步给与自身具有通信连接的多点控制设备。
21.如权利要求 16或 17所述的装置， 其特征在于， 所述管理单元包括： 请求子单元， 用于当需要召集会议时， 根据所述获得的拓朴关系， 向需要参加 会议的终端对应的多点控制设备发出开会请求。
22.如权利要求 16或 17所述的装置， 其特征在于， 所述管理单元包括： 第一转发子单元，用于当所述获得单元还获得与自身具有通信连接关系的多点 控制设备发出的开会请求时，如果自身控制的所有终端都不需要参加会议， 则 根据所述获得的拓朴关系，将所述开会请求直接或间接转发给需要参加会议的 终端对应的多点控制设备。
23.如权利要求 16或 17所述的装置， 其特征在于， 所述管理单元包括： 确定所述管理员的访问权限；
提供子单元，用于向所述管理员提供所述权限检查子单元确定的与所述管 理员访问权限相适应的多点控制设备的拓朴关系及会议情况。
24.如权利要求 16或 17所述的装置， 其特征在于， 所述管理单元包括： 第二转发子单元，用于当所述获得单元还获得登录到自身或登录到其他多点控 制设备的管理员对一个多点控制设备的管理信息时， 根据所述获得的拓朴关 系，将所述管理信息直接或间接转发给所述管理信息最终需要到达的多点控制 设备。
25.—种多点控制设备，其特征在于， 包括如权利要求 17-24任意一项所述 的装置。
26.—种分布式多点会议系统， 其特征在于， 包括多个多点控制设备； 已经与其他多点控制设备建立通信连接的多点控制设备具有所述分布式 多点会议系统中的多点控制设备的拓朴关系，所述多点控制设备的拓朴关系用 于表示多点控制设备之间的通信连接关系，每个具有所述分布式多点会议系统 中的多点控制设备的拓朴关系根据拓朴关系进行管理操作。
27.如权利要求 26所述的系统， 其特征在于， 每个多点控制设备都具有一 个标识， 所述标识为电话号码区号或域名。
PCT/CN2009/075382 2009-03-31 2009-12-08 分布式多点会议系统中的管理方法、装置及系统 WO2010111867A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910129579.0 2009-03-31
CN2009101295790A CN101515948B (zh) 2009-03-31 2009-03-31 分布式多点会议系统中的管理方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2010111867A1 true WO2010111867A1 (zh) 2010-10-07

Family

ID=41040239

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/075382 WO2010111867A1 (zh) 2009-03-31 2009-12-08 分布式多点会议系统中的管理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN101515948B (zh)
WO (1) WO2010111867A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2587778A1 (en) * 2011-10-31 2013-05-01 Research In Motion Limited Automatic management control of external resources
US8611877B2 (en) 2011-10-31 2013-12-17 Blackberry Limited Automatic management control of external resources
US9020119B2 (en) 2011-10-31 2015-04-28 Blackberry Limited Moderation control method for participants in a heterogeneous conference call
US10044516B2 (en) 2016-07-15 2018-08-07 International Business Machines Corporation Adaptive multi-control unit load balancing in a Voice-over-IP system
US10212206B2 (en) 2016-07-15 2019-02-19 International Business Machines Corporation Adaptive multi-control unit load balancing in a voice-over-IP system

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101515948B (zh) * 2009-03-31 2012-04-25 华为终端有限公司 分布式多点会议系统中的管理方法、装置及系统
CN102298735B (zh) * 2011-07-28 2017-04-26 中兴通讯股份有限公司 一种业务管理系统级联操作的处理方法和装置
CN102932462B (zh) * 2012-11-06 2015-07-22 北京星网锐捷网络技术有限公司 远程实验接入装置及方法
CN103856643B (zh) * 2012-11-30 2016-11-23 中国移动通信集团公司 一种多媒体会议控制方法及系统
CN110971861A (zh) * 2018-09-28 2020-04-07 中兴通讯股份有限公司 多点控制单元、视频会议系统、会议管理方法及存储介质
CN110062260B (zh) * 2019-04-23 2021-10-22 湖南楚风科技有限责任公司 一种分布式音视频控制系统

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005004481A1 (en) * 2003-07-07 2005-01-13 Tandberg Telecom As Distributed mcu
CN1604559A (zh) * 2003-09-29 2005-04-06 王生安 Ip网多媒体会议系统中分布式多点控制单元的部署方法
CN1976435A (zh) * 2006-12-04 2007-06-06 中国联合通信有限公司 一种视频会议中资源调配的方法
US20070126862A1 (en) * 1999-11-08 2007-06-07 Polycom Israel Ltd. System and method for controlling one or more multipoint control units as one multipoint control unit
CN101047828A (zh) * 2006-03-31 2007-10-03 联想(北京)有限公司 分布式会议系统
WO2008134301A1 (en) * 2007-04-27 2008-11-06 Cisco Technology, Inc. Optimizing bandwidth in a multipoint video conference
CN101515948A (zh) * 2009-03-31 2009-08-26 深圳华为通信技术有限公司 分布式多点会议系统中的管理方法、装置及系统

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070126862A1 (en) * 1999-11-08 2007-06-07 Polycom Israel Ltd. System and method for controlling one or more multipoint control units as one multipoint control unit
WO2005004481A1 (en) * 2003-07-07 2005-01-13 Tandberg Telecom As Distributed mcu
CN1604559A (zh) * 2003-09-29 2005-04-06 王生安 Ip网多媒体会议系统中分布式多点控制单元的部署方法
CN101047828A (zh) * 2006-03-31 2007-10-03 联想(北京)有限公司 分布式会议系统
CN1976435A (zh) * 2006-12-04 2007-06-06 中国联合通信有限公司 一种视频会议中资源调配的方法
WO2008134301A1 (en) * 2007-04-27 2008-11-06 Cisco Technology, Inc. Optimizing bandwidth in a multipoint video conference
CN101515948A (zh) * 2009-03-31 2009-08-26 深圳华为通信技术有限公司 分布式多点会议系统中的管理方法、装置及系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2587778A1 (en) * 2011-10-31 2013-05-01 Research In Motion Limited Automatic management control of external resources
US8611877B2 (en) 2011-10-31 2013-12-17 Blackberry Limited Automatic management control of external resources
US9020119B2 (en) 2011-10-31 2015-04-28 Blackberry Limited Moderation control method for participants in a heterogeneous conference call
US10044516B2 (en) 2016-07-15 2018-08-07 International Business Machines Corporation Adaptive multi-control unit load balancing in a Voice-over-IP system
US10212206B2 (en) 2016-07-15 2019-02-19 International Business Machines Corporation Adaptive multi-control unit load balancing in a voice-over-IP system
US10397299B2 (en) 2016-07-15 2019-08-27 International Business Machines Corporation Adaptive multi-control unit load balancing in a Voice-over-IP system

Also Published As

Publication number Publication date
CN101515948B (zh) 2012-04-25
CN101515948A (zh) 2009-08-26

Similar Documents

Publication Publication Date Title
WO2010111867A1 (zh) 分布式多点会议系统中的管理方法、装置及系统
AU2004211407B2 (en) Systems and methods for collaborative communication
CN107925743A (zh) 视频会议控制系统
US8868658B2 (en) Client assisted multicasting for audio and video streams
US9357164B2 (en) Establishing a remotely hosted conference initiated with one button push
WO2013131437A1 (zh) 一种远程会议控制方法、终端设备、mcu及视讯系统
US8650309B2 (en) Cascading architecture for audio and video streams
US9001700B2 (en) Scheduling and resourcing allocation across multiple domains
US10701116B2 (en) Method, computer-readable storage device and apparatus for establishing persistent messaging sessions
US20150350601A1 (en) Domain trusted video network
CN101841422A (zh) 语音会议中实现私人聊天的方法和系统
WO2004098125A1 (fr) Systeme de conference multimedia distribue fonde sur web ip
US10348714B1 (en) Systems and methods for setting up a collaborative communication system
CN113766436B (zh) 一种无线内部通话方法及系统
WO2019161721A1 (zh) 一种基于互通rcs系统的对应关系处理方法及装置
EP4287612A1 (en) Audio/video conference implementation method, audio/video conference system and related apparatus
KR100267378B1 (ko) 컴퓨터 그룹통신 장치 및 그 제어방법
EP3072285A1 (en) Control system, communication system, computer program, controlling method, and computer program product
KR20000041068A (ko) 분산형 멀티미디어 회의 제어 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09842523

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09842523

Country of ref document: EP

Kind code of ref document: A1