JP2008034900A - Multipoint conference system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an inter-multipoint conference system capable of relieving a load on an inter-multipoint controller even when a plurality of conferences are held since the inter-multipoint controller leaves control system signal processing to the route terminal of each conference in common to the MCU type inter-multipoint conference system and the MCU less type inter-multipoint conference system. <P>SOLUTION: A representative terminal is selected for each conference as the route terminal, and the inter-multipoint controller distributes processing to each route terminal so as to relieve the processing load on the inter-multipoint controller itself. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a multipoint conference system that realizes a conference between conference terminals at a plurality of sites using a communication line, and more particularly to management of control system signals thereof.

  A multipoint conference system is known as a mechanism for providing an environment in which people who are far away from each other gather at the same place to have a meeting. As shown in Figure 4, the multipoint control system of MCU (Multi-point Control Unit) type is a multipoint system with each of conference terminals 22 to 25, conference terminals 32 to 35, and conference terminals 42 to 45 installed at multiple locations. Control system signals (signaling) for session control such as voice and video such as SIP (Session Initiation Protocol), H.323, MGCP or MEGACO / H.248 are transmitted and received between the inter-control devices 1 Connect between devices. When the connection is established, the multipoint control device 1 receives communication data such as video and audio from any conference terminal, application data, whiteboard function data, and chat function data, and receives the received data at its destination. Delivered to a plurality of conference terminals. In addition, in the case of the MCU-less type, as shown in FIG. 5, all the conference terminals 22 to 25, all the conference terminals 32 to 35, all the conference terminals 42 to 45, and the control signal 500 between the multipoint control device 1 are used. After transmitting and receiving ˜511 to establish a connection, communication data is directly transmitted and received between the conference terminals without going through the multipoint control apparatus 1.

  As an improvement of this multipoint conference system, for example, there is a technique described in Patent Document 1. In the technique described in this document, a part of the functions of the multipoint control device 1 is distributed and processed in a plurality of servers installed in advance for each conference.

Japanese Patent Laid-Open No. 2003-18302

  In a conventional MCU-type and MCU-less multipoint conference system, the multipoint control device 1 or a plurality of distributed servers provides information for setting all conference terminals and the communication state between these conference terminals. Since the control system signals including transmission and reception are collectively performed, when the number of conferences and conference terminals is large, it takes time to process the multipoint control device 1 or a plurality of distributed servers, and the load is large. Further, in the MCU type, a multipoint control device or a plurality of distributed servers also relay all communication data transmitted / received between conference terminals, which further increases the load and processing delay.

  In addition, if you set the firewall at the location where the multipoint control device 1 or multiple distributed servers are installed to filter by specifying the address information and port number of all conference terminals of each conference member, the setting amount Becomes a huge number and management becomes very complicated. Furthermore, it is necessary to secure a line capacity for a plurality of conferences at the server installation location for the multipoint control apparatus 1 or a plurality of distributed servers, which causes a cost problem.

  The representative terminal is selected as a root terminal in each of a plurality of conferences, and the multipoint control device distributes the processing to the root terminals of each conference, thereby reducing the processing load of the multipoint control device itself.

  In the present invention, in common with the MCU type and the MCU-less type, in order to delegate control system signal processing from the multipoint control device to the root terminal of each conference, even when there are multiple conferences, The load can be reduced. Similarly, the processing of MCU-type communication data is delegated from the multipoint control device to the root terminal of each conference, so the load on the multipoint control device can be reduced.

  In the present invention, the load related to the processing of the multipoint control device or the plurality of distributed servers is not changed, but the overall control of the plurality of conferences by the multipoint control device or the plurality of distributed servers itself is not changed. Reduce. When a conference is held, control signals are exchanged between conference terminals that are members of the conference in each conference, and when a failure occurs in the root terminal that is the representative terminal of the conference and the root terminal A sub route terminal which is a sub representative terminal to be operated is selected. Next, the root terminal and the sub route terminal request the multipoint control apparatus for approval to perform part of the processing of the multipoint control apparatus. The multipoint control apparatus approves the root terminal and the sub-root terminal in each conference, and delegates authority to these terminals, thereby distributing the load of the multipoint control apparatus.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 shows a configuration of a multipoint conference system as an embodiment of the present invention. The multipoint control device 1 manages the conference terminals 20 to 23, the conference terminals 30 to 33, and the conference terminals 40 to 43 of all the conferences 2, the conference 3, the conference 4, and all the members of each conference. For example, the conference 2 refers to a group of these terminals configured by the conference terminals 20-23. In this embodiment, there are four members of the conference 2, the conference terminal 20, the conference terminal 21, the conference terminal 22, and the conference terminal 23. The number of members of the conference 3 is four: a conference terminal 30, a conference terminal 31, a conference terminal 32, and a conference terminal 33. There are four members of the conference 4, the conference terminal 40, the conference terminal 41, the conference terminal 42, and the conference terminal 43.

  The multipoint control device 1 holds a conference database shown in FIG. This database stores the conference name 7-0, the route terminal 7-1 and the sub route terminal 7-2 selected corresponding to each conference, and other terminals 7-3 and 7-4. . In the status 7-5 column, status numbers corresponding to each status are stored in accordance with the progress status of the multipoint conference.

  A selection sequence of the root terminal and the sub-root terminal in the conference 2 will be described with reference to FIG. In the initial state, the conference database of the multipoint control device 1 in FIG. 6 is not yet input (state 0) (8-0). Next, the administrator manually registers the conference 2 and its constituent members in the database of the multipoint control device 1 as shown in the first line of FIG. Here, the administrator assigns the conference number 7-0, the temporary root terminal 7-1, the temporary secondary root terminal 7-2, the other terminals 7-3 and 7-4, and the state number 7-5 to identify the conference. Register temporarily. At this time, "1" (temporary registration) is entered in the status number, and thereby conference 2 is in status 1 (8-1). Note that the multipoint control device may automatically update the state number 7-5 according to the input to the database.

  Next, the multipoint control device 1 is promoted to the root terminal and the root terminal at the time of failure of the root terminal with respect to the conference terminals 20 to 23 of all members who are going to be registered in the multipoint control device 1 as the conference 2 The fact that the sub-route terminal is selected is transmitted in a multicast frame to the conference terminals 20 to 23 of all the members of the conference 2, and the state transitions to state 2. (8-2). The conference terminals 20 to 23 of all the members of the conference 2 return the CPU processing performance, the memory capacity, the remaining capacity of the hard disk, etc. of the own terminal to the multipoint control device 1.

  The multipoint control device 1 holds a selection database shown in FIG. In this database, the CPU performance 70-1 of the conference terminal belonging to each conference, the memory capacity 70-2, other information 70-3 that serves as a guideline for comparing performance, and the selection order 70-4 indicating the ranking according to the performance of these terminals Is memorized. The selection order may be determined by weighting each item. Other information that can be used as a guideline for performance comparison includes factors that can be a major factor in determining the performance of the terminal, such as the communication speed via the network and the number of installed processors. The multipoint control device 1 stores the information received from the conference terminals 20 to 23 of all the conference members in the selection database in FIG. Then, the multipoint control device 1 shifts to the state 3, and selects the root terminal and the sub-root terminal in the order of, for example, the first priority item: CPU performance and the second priority item: memory capacity (8-3).

  Then, according to the selection result, the multipoint control device 1 rewrites information such as the route terminal 7-1, the sub route terminal 7-2, and the other terminals 7-3 and 7-4 in the conference database in FIG. Update the contents of the database and move to state 4. The multipoint control device 1 notifies the selection result of the root terminal and the sub-root terminal to the conference terminals 20 to 23 of all the members of the conference 2. Each conference terminal 20-23 knows who has been selected as a root terminal and a sub-root terminal, and receives connection information such as an IP address. Further, the multipoint control apparatus 1 sends a request message instructing the root terminal and the sub-root terminal to use the server function. Upon receiving this message, the root terminal and the sub-root terminal return a response message indicating that the message has been accepted to the multipoint control apparatus 1. As a result, the multipoint control device 1 delegates the authority of the server function related to the conference 2 to the selected root terminal (8-4).

  A functional configuration when the conference terminal 20 becomes the root terminal in the conference 2 is shown in FIG. When the authority of the server function 90 of the conference 2 is delegated from the multipoint control device 1, the server function of the conference terminal 20 can be used. Then, the conference database for conference 2 in the first row of FIG. 6 used for the conference server function, and initial setting information (SIP (Session Initiation Protocol), H.323, etc.) used for control signal processing as needed. (Initial setting information on the control protocol used) The initial setting information is the same as that of the conventional multipoint conference system, and is not an essential part of the present invention, so the details are omitted. At this time, the database information used for the server function related to the conference 2 is copied and passed from the multipoint control device 1 to both the root terminal 20 and the sub route terminal 21 of the conference 2. Further, information on the server function 900 and server function 901 possessed by the root terminal 20 is periodically copied to the sub-root terminal 21 and the multipoint control apparatus 1. Then, the conference is started, and the state shifts to the ready state 5 (8-5). If there is a change in the conference database, return to state 1 (8-1).

  Next, the conference flow will be described with reference to FIG. In the initial state, Conference 2 is not held (80-0). When each member of the conference 2, for example, the conference terminal 22 and the conference terminal 23 try to participate in the conference 2, these terminals transmit a conference participation request to the root terminal 20 (80-1). The root terminal 20 authenticates that these conference terminals are members of the conference 2 based on the conference database related to the conference 2 in the first line of FIG. Connect to 20 server functions (80-2). Note that if a failure occurs in the root terminal 20 when the conference 2 is held, the conference terminal 22 or 23 requests the multipoint control device 1 to reselect the root terminal and the sub-root terminal. That is, the process returns to the state 1 (8-1) in FIG. After the reselection, the newly selected root terminal belonging to the conference 2 acts as the multipoint control device.

  The root terminal 20 that is operating normally authenticates the conference members, calls the conference, and holds the conference (80-3). The server function information possessed by the root terminal 20 is periodically copied from the root terminal 20 to the sub-root terminal 21 and the multipoint control device 1. The conference participation terminal performs communication by exchanging communication data such as voice and image (80-4). The way of the multipoint conference via the route terminal 20 is the same as that of the past, except that the multipoint control device 1 is replaced with the route terminal 20. In the case of the MCU type, the root terminal 20 mediates communication data transmitted and received between the conference participation terminals. When the conference ends, the initial state (80-0) is restored.

  If any trouble occurs in the root terminal 20 during the period from the time the conference is held to the end, all information is taken over by the sub-root terminal 21. After the sub-route terminal 21 takes over, the normal operation is the same. In order to realize this, the root terminal 20 and the sub-root terminal 21 regularly exchange information for confirming that the other party is operating normally, for example, a keep alive message. For example, the setting may be changed so that the sub-root terminal 21 operates as a new root terminal 21 when a certain time elapses after the root terminal 20 stops exchanging messages.

  When the above sequence is completed, the MCU type is configured as shown in FIG. Communication data 2000-2002 and control system signals 200-202 such as video, voice, application data, whiteboard function data, chat function data, and control system signals 200-202 are transmitted from all the conference terminals 20-23 to the root terminal 20. The function of the conference server is executed on behalf of the multipoint control apparatus 1. For the other conferences 3 and 4, the root terminal selected in each conference performs the same processing. That is, the route terminal 20, the route terminal 30, and the route terminal 40 behave like the multipoint control device 1, and process both communication data and control system signals in each conference. In addition, the root terminal 20, the root terminal 30, and the root terminal 40 are arranged between the multipoints by combining the control system signal 120, the control system signal 130, and the control system signal 140 such as information related to the conference periodically or when necessary. Contact the control device 1.

  In the case of the MCU-less type, as shown in FIG. 3, the processing of the communication data 2003 to 2008 is directly exchanged between the conference terminals 20 to 23 as in the conventional case. 23 to the root terminal 20, and the root terminal 20 performs processing on behalf of the multipoint control apparatus 1. The root terminal 20 behaves like the multipoint control device 1 and processes the control system signals 200 to 202. In addition, the root terminal 20 collectively communicates the control system signal 120 such as information related to the conference, the control system signal 130, and the control system signal 140 to the multipoint control apparatus 1 when necessary periodically or when changing.

  In the above description of the embodiment, the conference 2 is specifically described, but the same processing is performed for the other conferences 3 and 4.

  As described above, the present invention is common to the MCU type and the MCU-less type, and the route terminal 20, the route terminal 30, and the route terminal 40 process the control system signal instead of the multipoint control device 1, so that the multipoint control device 1 These firewall settings may be filtered by specifying address information and port numbers only for the root terminal 20, the root terminal 30, and the root terminal 40 of each of the conference 2, the conference 3, and the conference 4.

It is a figure explaining the structure of the multipoint conference system in connection with embodiment of this invention. It is a figure explaining one Example of the MCU type | mold multipoint conference system by this invention. It is a figure explaining one Example of the MCU less type multipoint conference system by this invention. It is a figure explaining the structure of the conventional MCU type | mold multipoint conference system. It is a figure explaining the structure of the conventional MCU-less type multipoint conference system. It is a figure explaining one Example of the database of the meeting and meeting member in this invention. It is a figure explaining one Example of the database for selection of the root terminal in this invention, and a subroot terminal. It is a figure explaining one Example of the sequence of selection of the root terminal in this invention, and a subroot terminal. It is a figure explaining one Example of the sequence of meeting holding in this invention. It is a figure explaining one Example of the functional block of the root terminal in this invention, and a subroot terminal.

Explanation of symbols

1 Multipoint controller
2 Meeting 1
3 Meeting 2
4 Meeting 3
20,30,40 Root terminal for each meeting and meeting member terminal
21,31,41 Sub-root terminal for each meeting and meeting member terminal
22,23,24,25,32,33,34,35,42,43,44,45 Conference member terminals for each conference
7 Meeting information table data
70 Conference terminal information table data
8 Root terminal selection sequence data
80 Conference holding sequence data
90,91 server functions
95,96,97,98 Client function
900,901 Server function processing units

Claims (4)

In an operation method of a multipoint conference system including a control device that processes control signals transmitted and received between conference terminals to execute a multipoint conference, and a plurality of conference terminal groups each including a plurality of conference terminals ,
Inquiring the performance of each conference terminal to a plurality of conference terminals belonging to an arbitrary conference terminal group by the control device;
Receiving a performance notification message from the conference terminal by the control device, and comparing the performance of conference terminals belonging to the arbitrary conference terminal group based on the performance included in the received message;
The controller selects one of the conference terminals belonging to the arbitrary conference terminal group as a representative terminal based on the performance comparison result;
Notifying which conference terminal has become a representative terminal to all conference terminals belonging to the arbitrary conference terminal group by the control device;
And a step of giving the representative terminal authority to process the control system signal in the arbitrary conference terminal group by the control device. In the operation method of the multipoint conference system according to claim 1,
A representative terminal authorized by the control device to receive a conference participation request from a conference terminal belonging to the arbitrary conference terminal group;
Authenticating the conference terminal that has received the participation request by the representative terminal;
And a step of transmitting a meeting invitation message to the authenticated conference terminal by the representative terminal. In the operation method of the multipoint conference system according to claim 2,
An operation method of a multipoint conference system, wherein communication data transmitted from an arbitrary conference terminal is relayed to another conference terminal by a representative terminal that has transmitted the conference call message. In the operation method of the multipoint conference system according to claim 1,
A method of operating a multipoint conference system, wherein, when the selected representative terminal fails, the control device selects a sub representative terminal for performing the function of the representative terminal in place of the failed conference terminal.

Images