JP6725035B2 - Management system, transmission system, transmission management method, and program - Google Patents

Description

The present invention relates to a management system, a transmission system, a transmission management method, and a program.

2. Description of the Related Art In recent years, a video conference system that conducts a video conference via a communication network such as the Internet has become widespread in response to a request to reduce travel expenses and travel time. In such a video conference system, when a call is started between a plurality of terminals, call data such as image data and audio data is transmitted and received, and a video conference can be realized.

Also, due to the enhancement of the broadband environment in recent years, it has become possible to transmit and receive high-quality image data and high-quality sound data between a plurality of call terminals. As a result, it becomes easier to grasp the situation of the other party in the video conference, and it is possible to improve the degree of communication through conversation.

In addition, there is known a video conference system that has a function of creating a virtual conference room that distinguishes communication on a network for each conference and allows a user to select the conference room and start communication between terminals. Patent Document 1 discloses an invention of a conference system that suppresses resource consumption of the conference system by controlling according to the number of terminals participating in the conference when communicating in a virtual conference room.

However, in a transmission system such as a conventional video conference system that provides a virtual conference room on a network, if the information such as the conference name is not known, it participates in communication performed using the virtual conference room. I couldn't.

The present invention has been made in view of the above, and management for enabling communication with a destination terminal using a virtual conference room even if information for identifying a conference such as a conference name is not accurately known. An object is to provide a system, a transmission system, a transmission management method, and a program.

To solve the above problems and achieve the object, the present invention provides a management system for managing communications terminus you send and receive content data, the identification information of the first terminal, the first and the destination terminal information management unit for managing in association with identification information a second terminal of the communication terminal 1 or more candidates of the destination of the first terminal managed by the destination terminal information management unit and identification information of the one or more second devices associated with identification information, among the conference identification information for identifying the possible participation meeting one or more terminals that are specified by the operation accepted in the terminal, the 1 and a transmission unit that transmits said conference identification information associated with one of the end or the second end to the first terminal. From said first terminal, among the identification information of the one or more second terminal that is displayed on the display screen, start the identification information of the second terminal that is selected in the first communication destined when receiving the request, executing a plurality of terminals connected control for establishing the communication for transmitting the content data can participate including the terminal identified by the identification information of the second terminal said selected However, when the conference identified by the conference identification information transmitted by the transmitting unit is received and the second communication start request associated with the conference selected on the display screen is received, the selection is performed. and executes the connection control for the one or more second devices associated with the conference to establish a communication for transmitting said content data can participate.

According to the present invention, it is possible to communicate with a destination terminal by using a virtual conference room even if the information for identifying the conference such as the conference name is not exactly known.

FIG. 1 is a schematic diagram of a transmission system according to an embodiment of the present invention. FIG. 2 is an external view of the terminal according to the present embodiment. FIG. 3 is a hardware configuration diagram of the terminal according to the embodiment of the present invention. FIG. 4 is a hardware configuration diagram of the management system, the relay device, the program providing system, or the maintenance system according to the embodiment of the present invention. FIG. 5 is a functional block diagram of each terminal, device, and system configuring the transmission system according to the embodiment of the present invention. FIG. 6 is a functional block diagram showing the state management unit 53 of FIG. 5 in detail. FIG. 7 is a functional block diagram showing the relay device selection unit 56 of FIG. 5 in detail. FIG. 8 is a conceptual diagram showing the relay device management table. FIG. 9 is a conceptual diagram showing a terminal authentication management table. FIG. 10 is a conceptual diagram showing a terminal management table. FIG. 11 is a conceptual diagram showing the destination list management table. FIG. 12 is a conceptual diagram showing a session management table. FIG. 13 is a conceptual diagram showing a relay device selection management table. FIG. 14 is a conceptual diagram showing the entry management table. FIG. 15 is a conceptual diagram showing a conference room management table. FIG. 16 is a sequence diagram showing a process of managing status information indicating the operating status of each relay device. FIG. 17 is a conceptual diagram showing a transmission/reception state of image data, audio data, and various management information in the transmission system. FIG. 18 is a diagram showing an image including destination terminal status list information. FIG. 19 is a sequence diagram showing a process of displaying an image including the destination terminal status list information on the terminal. FIG. 20 is a sequence diagram showing a process of requesting the start of communication. FIG. 21 is a sequence diagram showing a process of permitting a request to start communication. FIG. 22 is a sequence diagram showing a process of rejecting a request to start communication. FIG. 23 is a sequence diagram showing a process of requesting relay of call data. FIG. 24 is a sequence diagram showing a process of requesting participation in a call data session. FIG. 25 is a sequence diagram showing a process of requesting exit from a call data session. FIG. 26 is a diagram showing a function list image showing a function list of the terminal. FIG. 27 is a diagram showing a conference room list image showing a conference room list. FIG. 28 is a diagram showing a newly created conference room image displayed when a new conference room is created. FIG. 29 is a sequence diagram showing a process of displaying a conference room list and creating a new conference room. FIG. 30 is a diagram showing a conference room detailed image showing detailed information of the conference room. FIG. 31 is a diagram showing a conference room edited image displayed when the conference room information is edited. FIG. 32 is a sequence diagram showing a process of displaying a conference room list and editing a conference room. FIG. 33 is a sequence diagram showing processing when entering a conference room from the conference room list. FIG. 34 is a flowchart showing the processing according to the result of the entry determination. FIG. 35 is a sequence diagram showing a process for selecting a destination terminal on the ON line (during a call) from the destination list and starting communication. FIG. 36 is a flowchart showing a process when selecting an ON-line (callable) destination terminal from the destination list and entering the conference room.

<<Overall Configuration of Embodiment>>
An embodiment of the present invention will be described below with reference to FIGS. 1 to 36. FIG. 1 is a schematic diagram of a transmission system 1 according to an embodiment of the present invention. First, the outline of the present embodiment will be described using FIG.

The transmission system includes a data providing system for unidirectionally transmitting content data from one terminal to the other terminal via a management system, and information and emotions are mutually transmitted between a plurality of terminals via the management system. A communication system is included. This communication system is a system for mutually transmitting information, feelings, and the like between a plurality of communication terminals (corresponding to "terminals") via a communication management system (corresponding to "management system"), and is a video conference system. Examples thereof include a videophone system, a voice conference system, a voice telephone system, and a PC (Personal Computer) screen sharing system.

In the present embodiment, assuming a video conference system as an example of a communication system, a video conference management system as an example of a communication management system, and a video conference terminal as an example of a communication terminal, a transmission system, a management system, and The terminal will be described. That is, the terminal and management system of the present invention is applied not only to a video conference system but also to a communication system or a transmission system.

The transmission system 1 shown in FIG. 1 includes a plurality of terminals (10aa, 10ab,... ), a display (120aa, 120ab,...) For each terminal (10aa, 10ab,... ), and a plurality of relay devices (30a, 30b, 30c). , 30d, 30e), a management system 50, a program providing system 90, and a maintenance system 100.

In the present embodiment, the term “terminal 10” is used when referring to any of the terminals (10aa, 10ab,... ). When any one of the displays (120aa, 120ab,...) Is shown, it is simply referred to as "display 120". When referring to any relay device among the relay devices (30a, 30b, 30c, 30d, 30e), it is simply referred to as "relay device 30".

The terminal 10 transmits and receives image data and audio data as an example of content data. That is, the call in the present embodiment includes not only the transmission/reception of voice data but also the transmission/reception of image data. That is, the terminal 10 in the present embodiment sends and receives image data and audio data. However, the terminal 10 may transmit/receive audio data instead of transmitting/receiving image data.

In the present embodiment, the case where the image of the image data is a moving image will be described, but it may be a still image as well as a moving image. The image of the image data may include both moving images and still images.

The relay device 30 relays image data and audio data between the plurality of terminals 10. The management system 50 manages the communication of the plurality of terminals 10 that transmits and receives the content data. The information related to the communication of the terminal 10 includes information related to the terminal 10, information related to the relay device 30 that relays communication between the terminals 10 and 10 and setting of communication using the terminal 10 and the relay device 30. It is the information concerned. More specifically, the management system 50 stores the operating state of the relay device 30, information for each relay device 30 such as an IP address, information for determining the relay device 30 used by the terminal 10, and the like. .. Further, the management system 50 includes authentication information (terminal ID and password) for the terminal 10 to log in to the transmission system 1, information of a terminal that is a communication destination registered for each terminal 10, and the terminal 10 and the relay device. Information related to communication (session) using 30 is stored. The management system 50 also stores information related to communication settings in which one or more designated terminals 10 can participate. Details of the information stored in the management system 50 will be described later.

Further, the plurality of routers (70a, 70b, 70c, 70d, 70ab, 70cd) shown in FIG. 1 select the optimum route of the image data and the audio data. In the present embodiment, the "router 70" is used to indicate any router among the routers (70a, 70b, 70c, 70d, 70ab, 70cd).

The program providing system 90 includes an HD (Hard Disk) (not shown) in which a terminal program for realizing various functions or various means in the terminal 10 is stored, and transmits the terminal program to the terminal 10. be able to. The HD of the program providing system 90 also stores a relay device program for causing the relay device 30 to realize various functions or various means, and the relay device program can be transmitted to the relay device 30. .. Further, the HD of the program providing system 90 also stores a transmission management program for realizing various functions or various means in the management system 50, and the transmission management program can be transmitted to the management system 50. ..

The maintenance system 100 is a computer for performing maintenance, management, or maintenance of at least one of the terminal 10, the relay device 30, the management system 50, and the program providing system 90. For example, when the maintenance system 100 is installed in Japan and the terminal 10, the relay device 30, the management system 50, or the program providing system 90 is installed overseas, the maintenance system 100 is remotely installed via the communication network 2. Maintenance of at least one of the terminal 10, the relay device 30, the management system 50, and the program providing system 90 is performed. In addition, the maintenance system 100 does not use the communication network 2 and has at least one of the terminal 10, the relay device 30, the management system 50, and the program providing system 90 a model number, a manufacturing number, a sales destination, a maintenance inspection, Alternatively, maintenance such as management of failure history is performed.

Further, the terminals (10aa, 10ab, 10ac, 10a...), the relay device 30a, and the router 70a are communicably connected by a LAN 2a. The terminals (10ba, 10bb, 10bc, 10b...), the relay device 30b, and the router 70b are communicably connected by a LAN 2b. The LAN 2a and the LAN 2b are communicably connected by a dedicated line 2ab including a router 70ab, and are constructed in a predetermined area A. For example, the area A is Japan, the LAN 2a is built in the office in Tokyo, and the LAN 2b is built in the office in Osaka.

On the other hand, the terminals (10ca, 10cb, 10cc, 10c...), the relay device 30c, and the router 70c are communicatively connected by a LAN 2c. The terminals (10da, 10db, 10dc, 10d...), the relay device 30d, and the router 70d are communicably connected by a LAN 2d. The LAN 2c and the LAN 2d are communicably connected by a dedicated line 2cd including a router 70cd, and are constructed in a predetermined area B. For example, Region B is the United States, LAN2c is built in a New York office, and LAN2d is Washington D.C. C. It is built in the office. Regions A and B are communicably connected to each other via routers (70ab, 70cd) via the Internet 2i.

Further, the management system 50 and the program providing system 90 are communicatively connected to the terminal 10 and the relay device 30 via the Internet 2i. The management system 50 and the program providing system 90 may be installed in the area A or the area B, or may be installed in an area other than these areas.

The relay device 30e is communicatively connected to all the terminals 10 of the transmission system 1 via the communication network 2. The relay device 30e is always in operation, and is installed in a region other than these in order to make it less likely to be affected by the communication amount in the local area of the region A or the region B. Thus, when the terminal 10 talks with a terminal installed in another local area, the relay device 30e is used as a relay device for relaying call data. Further, when a call is made between terminals in the same local area, the relay device 30e is used as an emergency relay device even when the relay device installed in this local area is not operating.

In the present embodiment, the communication network 2 of the present embodiment is constructed by the LAN 2a, LAN 2b, dedicated line 2ab, Internet 2i, dedicated line 2cd, LAN 2c, and LAN 2d. The communication network 2 may have a place where not only wired communication but also wireless communication is performed.

Further, in FIG. 1, the four sets of numbers shown below each terminal 10, each relay device 30, the management system 50, each router 70, the program providing system 90, and the maintenance system 100 are in general IPv4. The IP address is simply shown. For example, the IP address of the terminal 10aa is “1.2.1.3”. Although IPv6 may be used instead of IPv4, IPv4 will be used for the sake of simplicity.

<<Hardware Configuration of Embodiment>>
Next, the hardware configuration of this embodiment will be described.

FIG. 2 is an external view of the terminal 10 according to this embodiment. Hereinafter, the longitudinal direction of the terminal 10 will be described as the X-axis direction, the direction orthogonal to the X-axis direction in the horizontal plane will be the Y-axis direction, and the direction orthogonal to the X-axis direction and the Y-axis direction (vertical direction) will be the Z-axis direction.

As shown in FIG. 2, the terminal 10 includes a housing 1100, an arm 1200, and a camera housing 1300. Of these, the front side wall surface 1110 of the housing 1100 is provided with an intake surface (not shown) formed by a plurality of intake holes, and the rear side wall surface 1120 of the housing 1100 is formed with a plurality of exhaust holes. An exhaust surface 1121 is provided. Thereby, by driving the cooling fan built in the housing 1100, outside air behind the terminal 10 can be taken in through the intake surface (not shown) and exhausted to the rear of the terminal 10 through the exhaust surface 1121. A sound collection hole 1131 is formed on the right wall surface 1130 of the housing 1100, and sounds such as voice, object sound, and noise can be collected by a built-in microphone 114 described later.

An operation panel 1150 is formed on the right wall surface 1130 side of the housing 1100. The operation panel 1150 is provided with a plurality of operation buttons (108a to 108e) described later, a power switch 109 described below, and an alarm lamp 119 described below, and outputs an output sound from a built-in speaker 115 described below. A sound output surface 1151 formed by a plurality of sound output holes for passing is formed. Further, a housing portion 1160 as a recess for housing the arm 1200 and the camera housing 1300 is formed on the left wall surface 1140 side of the housing 1100. A right wall surface 1130 of the housing 1100 is provided with a plurality of connection ports (1132a to 1132c) for electrically connecting a cable to an external device connection I/F 118 described later. On the other hand, a left wall surface 1140 of the housing 1100 is provided with a connection port (not shown) for electrically connecting the cable 120c for the display 120 to an external device connection I/F 118 described later.

In the following, the "operation button 108" is used to indicate any operation button among the operation buttons (108a to 108e), and the "operation button 108" is used to indicate any connection port among the connection ports (1132a to 1132c). The connection port 1132" will be used for description.

Next, the arm 1200 is attached to the housing 1100 via a torque hinge 1210, and the arm 1200 is configured to be rotatable with respect to the housing 1100 in a vertical direction within a tilt angle θ1 of 135 degrees. ing. FIG. 2 shows a state in which the tilt angle θ1 is 90 degrees.

The camera housing 1300 is provided with a built-in type camera 1021 described later, and can capture images of users, documents, rooms, and the like. A torque hinge 1310 is formed on the camera housing 1300. The camera housing 1300 is attached to the arm 1200 via a torque hinge 1310. The camera housing 1300 is attached to the arm 1200 via the torque hinge 1310, and the camera housing 1300 has a pan angle θ2 of ±180 degrees with respect to the arm 1200 when the state shown in FIG. 2 is 0 degree. And a tilt angle .theta.3 of .+-.45 degrees are rotatable in the vertical and horizontal directions.

Since the relay device 30, the management system 50, the program providing system 90, and the maintenance system 100 are the same as the external appearance of a general server computer, respectively, the external description will be omitted.

FIG. 3 is a hardware configuration diagram of the terminal 10 according to the embodiment of the present invention. As shown in FIG. 3, the terminal 10 according to the present embodiment includes a CPU (Central Processing Unit) 101 that controls the operation of the entire terminal 10, a ROM (Read Only Memory) 102 that stores a terminal program, and a CPU 101. A RAM (Random Access Memory) 103 used as a work area, a flash memory 104 for storing various data such as image data and audio data, and an SSD (for controlling reading and writing of various data from and to the flash memory 104 under the control of the CPU 101). Solid State Drive) 105, media drive 107 that controls reading or writing (storage) of data to recording medium 106 such as flash memory, operation button 108 that is operated when selecting the destination of terminal 10, power supply of terminal 10 A power switch 109 for switching ON/OFF of the communication network, and a network I/F (Interface) 111 for transmitting data using the communication network 2 are provided.

In addition, the terminal 10 includes a built-in camera 112 that captures an image of a subject and obtains an image under the control of the CPU 101, an image sensor I/F 113 that controls driving of the camera 112, a built-in speaker 115 that outputs sound, and a CPU 101. A voice input/output I/F 116 that processes input/output of a voice signal between the microphone 114 and the speaker 115 according to control, a display I/F 117 that transmits image data to an external display 120 under the control of the CPU 101, shown in FIG. FIG. 2 shows an external device connection I/F 118 attached to the connected connection ports 1132a to 1132c for connecting various external devices, an alarm lamp 119 for notifying abnormalities of various functions of the terminal 10, and the above-mentioned components. As described above, a bus line 110 such as an address bus and a data bus for electrically connecting is provided.

The display 120 is a display unit configured by a liquid crystal or an organic EL that displays a subject image, an operation icon, and the like. Further, the display 120 is connected to the display I/F 117 by the cable 120c. The cable 120c may be a cable for analog RGB (VGA) signals, a cable for component video, HDMI (registered trademark) (High-Definition Multimedia Interface), or DVI (Digital Video). It may be a cable for an Interactive signal.

The camera 112 includes a lens and a solid-state image sensor that converts light into electric charge to digitize an image (video) of a subject. As the solid-state image sensor, a CMOS (Complementary Metal Oxide Semiconductor) or a CCD (Charge Coupled Device) is provided. Etc. are used.

External devices such as an external camera, an external microphone, and an external speaker can be connected to the external device connection I/F 118 by a USB (Universal Serial Bus) cable or the like. When an external camera is connected, the external camera is driven in preference to the built-in camera 112 under the control of the CPU 101. Similarly, when the external microphone is connected or when the external speaker is connected, the external microphone and the internal microphone 114 are given priority over the internal microphone 114 and the internal speaker 115, respectively, under the control of the CPU 101. An external speaker drives.

The recording medium 106 is configured to be attachable to and detachable from the terminal 10. Further, as long as it is a non-volatile memory that reads or writes data under the control of the CPU 101, not only the flash memory 104 but also an EEPROM (Electrically Erasable and Programmable ROM) or the like may be used.

Further, the terminal program may be a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 106 and distributed.

FIG. 4 is a hardware configuration diagram of the management system according to the embodiment of the present invention. The management system 50 controls a CPU 201 that controls the overall operation of the management system 50, a ROM 202 that stores a transmission management program, a RAM 203 that is used as a work area of the CPU 201, an HD (Hard Disk) 204 that stores various data, and a control of the CPU 201. According to the above, an HDD (Hard Disk Drive) 205 that controls reading or writing of various data to the HD 204, a media drive 207 that controls reading or writing (storage) of data to a recording medium 206 such as a flash memory, a cursor, a menu, a window, A display 208 for displaying various information such as characters or images, a network I/F 209 for data transmission using the communication network 2, and a plurality of keys for inputting characters, numerical values, various instructions, etc. A keyboard 211, a mouse 212 for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like, and reading or writing data to or from a CD-ROM (Compact Disc Read Only Memory) 213 as an example of a removable recording medium. 4, and a bus line 210 such as an address bus or a data bus for electrically connecting the above-mentioned components to each other as shown in FIG.

The transmission management program is a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 for distribution. ..

Further, since the relay device 30 has the same hardware configuration as the management system 50, the description thereof will be omitted. However, in the ROM 202, a relay device program for controlling the relay device 30 is recorded. Also in this case, the relay device program is a file in an installable format or an executable format, and is recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 for distribution. Good.

Further, since the program providing system 90 has the same hardware configuration as the management system 50, its description will be omitted. However, in the ROM 202, a program providing program for controlling the program providing system 90 is recorded. Also in this case, the program providing program is a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 and distributed. Good.

Further, since the maintenance system 100 has the same hardware configuration as the management system 50, the description thereof will be omitted. However, the ROM 202 stores a maintenance program for controlling the maintenance system 100. Also in this case, the maintenance program may be a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 and distributed. ..

In addition, as another example of the removable recording medium, it is configured to be provided by being recorded on a computer-readable recording medium such as a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), and a Blu-ray disc. You may.

<<Functional Configuration of Embodiment>>
Next, the functional configuration of this embodiment will be described. FIG. 5 is a functional block diagram of each terminal, device, and system constituting the transmission system 1 of this embodiment. In FIG. 5, the terminal 10, the relay device 30, and the management system 50 are connected so as to be able to perform data communication via the communication network 2. Further, the program providing system 90 and the maintenance system 100 shown in FIG. 1 are omitted in FIG. 5 because they are not directly related to the communication of the video conference.

<Functional configuration of terminal>
The terminal 10 includes a transmission/reception unit 11, an operation input reception unit 12, a login request unit 13, an imaging unit 14, a voice input unit 15a, a voice output unit 15b, a display control unit 16, a storage/readout processing unit 17, and a destination list creation unit. Have eighteen. Each of these units is a function or means realized by any one of the components shown in FIG. 3 being operated by an instruction from the CPU 101 according to a program stored in the ROM 102. The terminal 10 also has a volatile storage unit 1100 constructed by the RAM 103 shown in FIG. 3 and a non-volatile storage unit 1000 constructed by the flash memory 104 shown in FIG.

<Functional parts of the terminal>
Next, each unit of the terminal will be described in detail.

The transmission/reception unit 11 is realized by the network I/F 111 shown in FIG. 3 and transmits/receives various data to/from other terminals, devices or systems via the communication network 2. The transmission/reception unit 11 starts receiving each state information indicating the state of each terminal as a destination candidate from the management system 50 before starting a call with a desired destination terminal. It should be noted that this state information is not only the operating state of each terminal 10 (state of ON line or OFF line), but also detailed state of whether the line is still active or on standby even if it is ON line. Indicates. Further, this state information is not limited to the operating state of each terminal 10, but the cable is disconnected from the terminal 10 at the terminal 10, the sound is output but the image is not output, or the sound is not output ( MUTE) and various other states. Hereinafter, as an example, a case where the state information indicates the operating state will be described.

An example of various data that the transmission/reception unit 11 transmits/receives to/from another terminal, device, or system via the communication network 2 will be described. For example, the transmission/reception unit 11 transmits start request information to the management system 50 when the user specifies a destination terminal from a destination terminal status list image (FIG. 18) described later and starts communication. The start request information includes start request information for normal transmission and start request information for entry to the room.

The start request information by normal transmission (corresponding to “start request for first communication”) is transmitted when requesting start of communication in which any terminal 10 can participate (hereinafter, referred to as “first communication”). It is the information to do. The normal call start request information includes a terminal ID for identifying the request source terminal, a terminal ID for identifying the destination terminal, and information “Invite” indicating that the call start by the first communication is requested. ..

The start request information (corresponding to “start request for second communication”) by calling into the room is performed by a communication in which one or more terminals 10 designated in advance can participate (hereinafter, referred to as “second communication”). This is information to be transmitted when requesting the start of. The start request information for entering the room includes a terminal ID for identifying the request source terminal, a terminal ID for identifying the destination terminal, and information “Invite+Room” indicating that a call start by the second communication is requested. .. The conference held by the second communication is identified by the conference room ID. It should be noted that the start request information from the entry call may include the conference room ID instead of the terminal ID so that the second communication can be identified from the start request information from the entry call. Thereby, the conference management unit 58, which will be described later, of the management system 50 uses the terminal ID of the destination terminal as a search key to search the terminal ID of the entry management DB 5007, which will be described later, and acquires the conference room ID of the retrieved record. Thus, the process of specifying the conference room used for communication can be omitted.

After transmitting the start request information to the management system 50, the transmission/reception unit 11 receives the session ID for identifying communication and the relay device connection information from the management system 50. The relay device connection information is information necessary for connecting to the relay device 30 used for communication (IP address, port number of the relay device 30, authentication information necessary for connecting the relay device 30, etc.).

Further, the transmission/reception unit 11 receives the start response information from the management system 50. The start response information is information indicating whether communication with the destination terminal is possible. The start response information includes the terminal ID of the destination terminal, information indicating permission (Accept) or rejection (Reject) of starting the communication, and a session ID for identifying the communication. When the start response information received from the management system 50 indicates that communication with the destination terminal is possible, the transmission/reception unit 11 transmits the session ID of the communication and the relay device connection information to the relay device 30.

Further, the transmission/reception unit 11 transmits a room entry request to the management system 50 when the user selects a conference room (meeting name) from a conference room list image (see FIG. 27) described later and starts communication. The room entry request includes the terminal ID of the request source terminal, the information “Invite+Room” indicating that the call start by the second communication is requested, and the conference room ID of the conference room.

The operation input receiving unit 12 is realized by the operation button 108 and the power switch 109 shown in FIG. 3, and receives various inputs by the user. For example, when the user turns on the power switch 109 shown in FIG. 3, the operation input receiving unit 12 shown in FIG. 5 receives the power ON and turns the power ON. In addition, when the operation input acceptance unit 12 accepts an operation input for selecting a destination terminal from a destination terminal status list image (see FIG. 18) described later, the start request information by the entry call or the start request information by the normal call is sent. , Request the transmitting/receiving unit 11 to transmit to the management system 50. Further, when the operation input reception unit 12 receives an operation input for selecting a conference room from a conference room list image (see FIG. 27) described later, the operation input reception unit 12 requests the transmission/reception unit 11 to transmit an entry request to the management system 50. To do.

The login request unit 13 is realized by a command from the CPU 101 shown in FIG. 3, and upon reception of the power ON, authentication is performed (login) from the transmission/reception unit 11 to the management system 50 via the communication network 2. The login request information indicating the request and the current IP address of the terminal 10 as the request source are automatically transmitted. The login request information includes a terminal ID for identifying the terminal 10 that is the requesting own terminal and a password for logging in to the transmission system 1. When the user turns off the power switch 109 from the ON state, the transmission/reception unit 11 transmits state information indicating that the power is turned off to the management system 50, and then the operation input reception unit 12 completely turns off the power. Turn it off. This allows the management system 50 side to recognize that the power of the terminal 10 has been switched from ON to OFF.

The image capturing unit 14 is realized by a command from the CPU 101 shown in FIG. 3, the camera 112 shown in FIG. 3, and the image sensor I/F 113, and captures an image of a subject and obtains the image by the image capturing. Output image data. The voice input unit 15a is realized by the voice input/output I/F 116 shown in FIG. 3, and after the voice of the user is converted into a voice signal by the microphone 114, the voice data related to this voice signal is input. The audio output unit 15b is realized by the command from the CPU 101 shown in FIG. 3 and the audio input/output I/F 116 shown in FIG. 3, and outputs an audio signal related to audio data to the speaker 115, The voice is output from 115.

The display control unit 16 is realized by a command from the CPU 101 shown in FIG. 3 and performs control for displaying image data on the external display 120. For example, the display control unit 16 controls to display a destination terminal state list image (see FIG. 18) described later, a conference room list image (see FIG. 27) described below, and the like on the display 120.

Further, the storage/read processing unit 17 is executed by the instruction from the CPU 101 shown in FIG. 3 and the SSD 105 shown in FIG. 3 as an example, and stores various data in the nonvolatile storage unit 1000 or the nonvolatile storage unit 1000. A process of reading various data stored in the unit 1000 is performed. The non-volatile storage unit 1000 stores a terminal ID (Identification) for identifying the terminal 10, a password, and the like. Further, the storage/readout processing unit 17 also performs processing of storing various data in the volatile storage unit 1100 and reading out various data stored in the volatile storage unit 1100. In the volatile storage unit 1100, image data and audio data received when a call is made with the destination terminal are overwritten and stored each time they are received. Among these, the image is displayed on the display 120 by the image data before being overwritten, and the sound is output from the speaker 115 by the audio data before being overwritten.

The terminal ID of the present embodiment and the relay device ID described later are identification information for uniquely identifying the terminal 10 and the relay device 30, respectively. The identification information is a language, characters, symbols, various indicia, or the like. Further, the terminal ID and the relay device ID may be identification information in which at least two of the above language, characters, symbols, and various indicia are combined. The same applies to the session ID and the conference room ID.

(Functional configuration of relay device)
Next, the function or means of the relay device 30 will be described. The relay device 30 includes a transmission/reception unit 31, a state detection unit 32, and a storage/readout processing unit 33. Each of these units is a function or means realized by any one of the components shown in FIG. 4 being operated by an instruction from the CPU 201 according to a program stored in the ROM 202. Further, the relay device 30 has a non-volatile storage unit 3000 that is constructed by the HD 204 shown in FIG. 4 and that stores various data and information even when the power of the relay device 30 is turned off.

<Functional parts of relay device>
Next, each functional configuration of the relay device 30 will be described in detail. It should be noted that in the following description, in describing each unit of the relay device 30, the relationship with the main components for realizing each unit of the relay device 30 among the respective components shown in FIG. 4 will also be described.

The transmission/reception unit 31 of the relay device 30 shown in FIG. 5 is realized by the network I/F 209 shown in FIG. 4, and other terminals, devices, or systems and various data (or data) via the communication network 2 (or Send and receive information). For example, the transmission/reception unit 31 receives the session ID and the relay device connection information from the terminal 10.

The state detection unit 32 is realized by an instruction from the CPU 201 shown in FIG. 4, and detects the operating state of the relay device 30 having the state detection unit 32. The operating state includes “ON line”, “OFF line”, and “during failure”. The state detection unit 32 transmits the operating state to the management system 50 via the transmission/reception unit 31.

The storage/readout processing unit 33 performs processing of storing various data in the non-volatile storage unit 3000 and reading out various data stored in the non-volatile storage unit 3000.

<Functional configuration of management system>
Next, the function or means of the management system 50 will be described. First, the information stored in the management system 50 will be described. The management system 50 is constructed by the HD 204 shown in FIG. 4, and has a non-volatile storage unit 5000 that maintains the storage of various data and information even when the power of the management system 50 is turned off. Further, the management system 50 has a volatile storage unit 5100 constructed by the RAM 203 shown in FIG.

(Relay device management table)
In the non-volatile storage unit 5000, a relay device management DB 5001 including a relay device management table as shown in FIG. 8 is constructed. In this relay device management table, for each relay device ID of each relay device 30, the operating status of each relay device 30, the reception date and time when the management system 50 received the status information indicating the operating status, and the IP address of the relay device 30. , And the maximum data transmission rate (Mbps) in the relay device 30 are associated and managed. For example, in the relay device management table shown in FIG. 8, the relay device 30a having the relay device ID “111a” has an operating state of “ON line”, and the date and time when the management system 50 receives the state information is “ At 13:00 on November 10, 2009, it is shown that the IP address of the relay device 30a is "1.2.1.2" and the maximum data transmission rate in the relay device 30a is 100 Mbps. ing.

(Terminal authentication management table)
Furthermore, in the non-volatile storage unit 5000, a terminal authentication management DB 5002 configured by a terminal authentication management table as shown in FIG. 9 is constructed. In this terminal authentication management table, a password for logging in to the transmission system 1 is associated with each terminal ID of all the terminals 10 managed by the management system 50 and managed. For example, the terminal authentication management table shown in FIG. 9 indicates that the terminal ID of the terminal 10aa is “01aa” and the password is “aaaa”. The information of the terminal authentication management table is registered in advance by the user or the administrator of the management system 50.

(Terminal management table)
Further, in the non-volatile storage unit 5000, a terminal management DB 5003 configured by a terminal management table as shown in FIG. 10 is constructed. In this terminal management table, for each terminal ID of each terminal 10, the terminal name when each terminal 10 is the destination, the operating state of each terminal 10, the reception date and time when the login request information was received by the management system 50, and the terminal Ten IP addresses are associated and managed. For example, in the terminal management table shown in FIG. 10, the terminal 10aa with the terminal ID "01aa" has the terminal name "Japan Tokyo Office AA terminal" and the operating state "ON line (callable)". It is shown that the date and time when the login request information is received by the management system 50 is "13:40 on November 10, 2009" and the IP address of this terminal 10aa is "1.2.1.3". Has been done.

(Recipient list management table)
Further, in the non-volatile storage unit 5000, a destination list management DB 5004 configured by a destination list management table as shown in FIG. 11 is constructed. In this destination list management table, a destination terminal ID is associated with each request source terminal ID and managed. The request source terminal ID is information for identifying the request source terminal that requests the start of the call. The destination terminal ID is information for identifying a destination terminal that is a candidate for the destination terminal of the communication of the request source terminal that requests the start of the call. This destination terminal candidate is updated by being added or deleted in response to a request from the requesting terminal to the management system 50 for addition or deletion. For example, in the destination list management table shown in FIG. 11, the destination terminal candidates that can request the start of the call in the video conference from the request source terminal (terminal 10aa) with the terminal ID “01aa” are the terminals. In the terminal 10ab having the ID “01ab”, the terminal 10ba having the terminal ID “01ba”, the terminal 10bb having the terminal ID “01bb”, the terminal 10ca having the terminal ID “01ca”, and the terminal 10db having the terminal ID “01db”. It has been shown to be.

(Session management table)
In addition, a session management DB 5005 configured by a session management table as shown in FIG. 12 is constructed in the non-volatile storage unit 5000. In this session management table, for each session ID for identifying communication between terminals, the relay apparatus ID of the relay apparatus 30 used for relaying image data and audio data, the terminal ID of the request source terminal, and the terminal of the destination terminal. IDs are associated and managed. For example, in the session management table shown in FIG. 12, the relay device 30e (relay device ID “111e”) selected in the session executed using the session ID “se1” has the terminal ID “01aa”. The image data and the audio data are relayed between the request source terminal (terminal 10aa), the destination terminal (terminal 10ab) whose terminal ID is "01ab", and the destination terminal (terminal 10db) whose terminal ID is "01db". Have been shown.

(Relay device selection management table)
Further, in the non-volatile storage unit 5000, a relay device selection management DB 5006 configured by a relay device selection management table as shown in FIG. 13 is constructed. In this quality control table, the relay device IDs of the relay devices 30 used for relaying image data and audio data are associated with each terminal ID of all the terminals 10 managed by the management system 50 and managed. ..

(Entry control table)
Further, in the non-volatile storage unit 5000, an entry management DB 5007 configured by an entry management table as shown in FIG. 14 is constructed. This entry management table includes a conference room ID for identifying the conference and a terminal ID of the designated one or more terminals 10 for each conference held by the second communication in which the designated one or more terminals 10 can participate. Are stored in association with each other.

(Meeting room management table)
Furthermore, in the non-volatile storage unit 5000, a conference room management DB 5008 including a conference room management table as shown in FIG. 15 is constructed. This conference room management table is identified by the conference room ID for identifying the conference, the conference name, and the conference room ID for each conference held by the second communication in which one or more designated terminals 10 can participate. And the session ID of the second communication that is stored. The conference room ID is conference identification information for identifying a virtually created conference room or a conference to be held.

(Each functional part of the management system)
Next, each functional unit of the management system 50 will be described in detail. It should be noted that, in describing the respective parts of the management system 50, the relationship with the main constituent elements for realizing the respective parts of the management system 50 among the respective constituent elements shown in FIG. 4 will also be described below. The management system 50 includes a transmission/reception unit 51, a terminal authentication unit 52, a status management unit 53, a terminal extraction unit 54, a terminal status acquisition unit 55, a relay device selection unit 56, a session management unit 57, a conference management unit 58, a determination unit 59, and It has a storage/readout processing unit 60. Each of these units is a function or means realized by any one of the components shown in FIG. 4 being operated by an instruction from the CPU 201 according to a program stored in the ROM 202.

The transmission/reception unit 51 is executed by the network I/F 209 shown in FIG. 4, and transmits/receives various data to/from other terminals, devices or systems via the communication network 2.

For example, the transmission/reception unit 51, when the user of the terminal 10 specifies a destination terminal and starts communication from a destination terminal status list image (FIG. 18) described later, start request information by entering room or start request by normal calling. Information is received from the terminal 10.

After receiving the start request information from the terminal 10, the transmitter/receiver 51 transmits the session ID for identifying the communication and the relay device connection information to the terminal 10.

Further, the transmission/reception unit 51 receives the start request information from the communication requesting terminal 10 and then transmits the start request information, the relay device connection information, and the IP address of the management system 50 to the communication destination terminal 10. Send.

Further, the transmission/reception unit 51 transmits the start response information to the communication requesting terminal 10 after receiving the start response information from the communication destination terminal 10.

The terminal authentication unit 52 uses the terminal ID and password included in the login request information received via the transmission/reception unit 51 as a search key to search the terminal authentication management table (see FIG. 9) of the non-volatile storage unit 5000. The terminal authentication is performed by determining whether the same terminal ID and password are managed in the terminal authentication management table.

The state management unit 53 uses the terminal management table (see FIG. 10) to manage the operating state of the request source terminal that has made the login request, by using the terminal ID of the request source terminal, the terminal name of the request source terminal, and the request source terminal. The operating state, the reception date and time when the management system 50 receives the login request information, and the IP address of the request source terminal are stored in association with each other and managed. Therefore, the state management unit 53 realizes the state setting unit 53a and the state acquisition unit 53b shown in FIG. 6 by the instruction from the CPU 201 shown in FIG.

Of these, the state setting unit 53a sets (changes) the state information of the terminal 10 in the terminal management table (see FIG. 10) when the information indicating that the state of the terminal 10 has been changed is received from the terminal 10. To do. For example, when the user of the terminal 10 turns on the power switch 109 of the terminal 10 from the off state, the terminal 10 transmits to the management system 50 the state information indicating that the power is turned on. When the status setting unit 53a receives the status information via the transmitting/receiving unit 51, the status setting unit 53a changes the operating status of the terminal 10 in the terminal management table (see FIG. 10) from “OFF line” to “ON line (communication available)”. Change to. When the user turns off the power switch 109 of the terminal 10 from the on state, the terminal 10 transmits state information to the management system 50 to the effect that the power is turned off. When the status setting unit 53a receives the status information via the transmission/reception unit 51, the status setting unit 53a changes the operating status of the terminal 10 in the terminal management table (see FIG. 10) from “ON line (communication available)” to “OFF line”. Change to.

The status acquisition unit 53b, when receiving the destination list request information or the like that requires the status information of the destination terminal from the request source terminal, displays the status information of at least one of the request source terminal and the destination terminal in the terminal management table (see FIG. 10). To get from.

The terminal extraction unit 54 searches for the request source terminal ID in the destination list management table (see FIG. 11) using the terminal ID of the request source terminal that made the login request as a search key, and extracts the destination terminal ID of the retrieved record. The terminal extraction unit 54 extracts the terminal 10 identified by the extracted destination terminal ID as a candidate for a destination terminal that can communicate with the request source terminal.

The terminal state acquisition unit 55 searches for a terminal ID in the terminal management table (see FIG. 10) using the terminal ID as a search key for each terminal ID of the destination terminal candidate extracted by the terminal extraction unit 54, and searches. Reads the operating status of the specified record. As a result, the terminal status acquisition unit 55 can acquire the operating status of the candidate of the destination terminal that can communicate with the request source terminal that has made the login request.

The relay device selection unit 56 performs a process of finally narrowing down from the plurality of relay devices 30 to one relay device 30. Therefore, the relay device selection unit 56 realizes the session ID generation unit 56a, the relay device extraction unit 56b, and the selection unit 56c shown in FIG. 7 by the command from the CPU 201 shown in FIG.

Of these, the session ID generation unit 56a generates a session ID for identifying a session in which call data is communicated between terminals. The relay device extraction unit 56b, based on the terminal ID of the request source terminal and the terminal ID of the destination terminal included in the start request information sent from the request source terminal, the relay device selection management table (see FIG. 13). By searching for each corresponding relay device ID. The selecting unit 56c selects the relay device ID of the relay device 30 whose operating state is “ON line” among the relay devices 30 managed by the relay device management table (see FIG. 8), thereby performing the relay. The device 30 is selected.

The session management unit 57 associates the session management table (see FIG. 12) of the non-volatile storage unit 5000 with the session ID generated by the session ID generation unit 56a, the terminal ID of the request source terminal, and the terminal ID of the destination terminal. Remember and manage. Further, the session management unit 57 stores and manages, for each session ID, the relay device ID of the relay device 30 finally selected as one, for each session ID. In addition, the session management unit 57 stores the session ID of the second communication identified by the conference room ID in association with the conference room ID in the conference room management table.

The conference management unit 58 associates and stores the conference room ID and the terminal ID in the entry management table (see FIG. 14) of the non-volatile storage unit 5000. Further, the conference management unit 58 stores the conference room ID, the conference name, and the session ID in association with each other in the conference room management table (see FIG. 15) of the non-volatile storage unit 5000 for management.

The determination unit 59 receives, via the transmission/reception unit 51, the entrance request for starting entry indicating the start of the second communication, which is identified by the conference room ID, from the terminal 10 that is the source of the communication request. The request to start entering the room includes the terminal ID of the request source terminal and information for specifying the meeting room to enter (the meeting room ID or the terminal ID of the destination terminal). The determination unit 59 identifies the conference room ID of the conference room to enter from the information for identifying the conference room included in the entry transmission start request, and determines the terminal ID of the requesting terminal 10 included in the entry transmission start request. It is determined whether or not it is associated with the conference room ID. If the determination unit 59 is associated, the determination unit 59 requests the session management unit 57 to perform the session management process of the second communication related to the entry call initiation request. The session management processing is processing related to generation of a session (when the operation status of the destination terminal is “ON line (call enabled)”) or participation in an existing session (when the operation status of the destination terminal is “ON line (call enabled)”). Middle)”).

The storage/readout processing unit 60 (corresponding to the destination terminal information management unit) stores various data in the non-volatile storage unit 5000 or the volatile storage unit 5100, or is stored in the non-volatile storage unit 5000 or the volatile storage unit 5100. The process of reading various data is performed.

<<Process or Operation of Embodiment>>
The above is a description of the configuration and functions (or means) of the transmission system 1 according to the present embodiment, and subsequently, the processing method in the transmission system 1 according to the present embodiment will be described using FIGS. 16 to 36. ..

First, a process of managing the state information indicating the state of each relay device 30 transmitted from each relay device 30 to the management system 50 will be described with reference to FIG. FIG. 16 is a sequence diagram showing a process of managing state information indicating the operating state of each relay device 30. First, in each relay device 30, the state detection unit 32 illustrated in FIG. 5 periodically detects the operating state of the relay device 30 that is the self device (steps S1-1 to S1-4). Then, in order for the management system 50 side to manage the operating state of each relay device 30 in real time, the transmission/reception unit 31 of each relay device 30 periodically transmits each status information to the management system 50 via the communication network 2. (Steps S2-1 to S2-4). Each of these pieces of state information includes a relay device ID for each relay device 30 and an operating state detected by the state detection unit 32 of the relay device 30 related to each relay device ID. In the present embodiment, the relay devices (30a, 30b, 30d) are normally operating and are in the “ON line”, while the relay device 30c is in operation, but the relay operation of the relay device 30c is performed. There is shown a case in which the program for executing is in the "OFF line" due to some trouble.

Next, in the management system 50, the transmission/reception unit 51 receives each status information sent from each relay device 30, and the relay device management table of the nonvolatile storage unit 5000 (see FIG. 8), the state information is stored and managed for each relay device ID (steps S3-1 to S3-4). As a result, in the relay device management table as shown in FIG. 8, the operating state of either “ON line”, “OFF line”, or “in failure” is stored and managed for each relay device ID. It At this time, the reception date and time at which the status information is received by the management system 50 is also stored and managed for each relay device ID. If status information is not sent from the relay device 30, the field part of the operating status and the field part of the reception date and time in each record of the relay device management table shown in FIG. 8 become blank, or The operating status and the reception date and time at the time of the previous reception are shown.

Next, with reference to FIG. 17, a concept showing a transmission/reception state of image data, audio data, and various management information in the transmission system 1 will be described. FIG. 17 is a conceptual diagram showing a transmission/reception state of image data, audio data, and various management information in the transmission system 1. As shown in FIG. 17, in the transmission system 1, a management information session sei for transmitting and receiving various management information is established between the terminals 10A, 10B, and 10C via the management system 50. To be done. Further, between the terminal 10A, the terminal 10B, and the terminal 10C, four pieces of data of high-resolution image data, medium-resolution image data, low-resolution image data, and audio data are transmitted and received via the relay device 30. 4 sessions are established. Here, these four sessions are collectively shown as an image/audio data session sed.

Next, a process of displaying an image including the destination terminal state list information (destination terminal state list image) on the terminal 10aa will be described with reference to FIGS. 18 and 19.

FIG. 18 is a diagram showing an image including destination terminal status list information. The destination terminal status list image includes destination terminal status information including information indicating a destination terminal associated with the communication request source terminal and information indicating whether a conference room is associated with the destination terminal (image 1504). It is an image showing one or more destination terminal status list information. The destination terminal information including the image 1504 indicates that the second communication (virtual conference room) in which the destination terminal can participate is registered in the management system 50. The example of the destination terminal status list image in FIG. 18 also shows operating status information (image 1501, image 1502, or image 1503) indicating the operating status of the destination terminal. An image 1501 indicates that the destination terminal is “ON line (communication possible)”. An image 1502 indicates that the destination terminal is “ON line (during a call)”. The image 1503 indicates that the destination terminal is “OFF line”.

FIG. 19 is a sequence diagram showing a process of displaying an image including the destination terminal status list information on the terminal. In FIG. 19, all communication between the terminal 10 and the management system 50 is performed using the management information session sei.

First, when the user of the terminal 10aa turns on the power switch 109 shown in FIG. 3, the operation input receiving unit 12 shown in FIG. 5 receives the power ON and turns the power ON (step S21). Then, the login request unit 13 automatically transmits the login request information indicating the login request from the transmission/reception unit 11 to the management system 50 via the communication network 2 upon receiving the power ON (step S22). This login request information includes a terminal ID for identifying the terminal 10aa, which is the requester's own terminal, and a password. These terminal ID and password are data read from the non-volatile storage unit 1000 via the storage/readout processing unit 17 and sent to the transmission/reception unit 11. When the login request information is transmitted from the terminal 10aa to the management system 50, the management system 50 on the reception side can recognize the IP address of the terminal 10aa on the transmission side.

Next, the terminal authentication unit 52 of the management system 50 uses the terminal ID and password included in the login request information received via the transmission/reception unit 51 as a search key, and stores the terminal authentication management table (see FIG. 9)), and terminal authentication is performed by determining whether or not there is a terminal ID and password matching the search key in the terminal authentication management DB 5002 (step S23).

When the terminal ID and password that match the search key are in the terminal authentication management DB 5002, the state management unit 53 searches the terminal ID in the terminal management table (see FIG. 10) with the terminal ID of the search key and is searched. The date and time when the login request information is received is set in the reception date and time field of the record that has been recorded. The state management unit 53 also stores the IP address included in the login request information in the IP address field of the terminal of the retrieved record (step S24-1). As a result, in the terminal management table shown in FIG. 10, the terminal ID “01aa”, the reception date and time “2009.11.10.13:40”, and the terminal IP address “1.2.1.3” are displayed. It will be managed in association with each other.

Subsequently, the state setting unit 53a of the state management unit 53 sets the operating state "ON line (communication possible)" of the terminal 10aa in the operating state field of the retrieved record (step S24-2). As a result, the terminal management table shown in FIG. 10 manages the terminal ID “01aa” in association with the operating state “ON line (communication possible)”.

Then, the transmission/reception unit 51 of the management system 50 transmits the authentication result information indicating the authentication result obtained by the terminal authentication unit 52 via the communication network 2 to the request source terminal (terminal 10aa) that has made the login request. (Step S25). In the present embodiment, a case in which the terminal authentication unit 52 determines that the terminal has a valid usage right will be continuously described below.

When the terminal 10aa receives the authentication result information indicating that the terminal 10aa has been determined to have the proper usage authority, the transmitting/receiving unit 11 indicates to the management system 50 via the communication network 2 that the destination list is requested. The sent destination list request information is transmitted (step S26). As a result, the transmission/reception unit 51 of the management system 50 receives the destination list request information.

Next, the terminal extraction unit 54 searches the destination list management table (see FIG. 11) using the terminal ID “01aa” of the request source terminal (terminal 10aa) that made the login request as a search key, and the request source terminal (terminal 10aa). It extracts by reading out the terminal ID of the candidate of the destination terminal which can talk with (step S27). Further, the terminal extraction unit 54 searches the terminal management table (see FIG. 10) using the extracted terminal ID as a search key, and extracts the destination name corresponding to this terminal ID by reading. Here, the terminal IDs of the destination terminals (10ab, 10ba, 10bb, 10ca, and 10db) corresponding to the terminal ID “01aa” of the request source terminal (terminal 10aa) (“01ab”, “01ba”, “01bb”, “01ca” and “01db”) and terminal names corresponding to these (“Japan Tokyo office AB terminal”, “Japan Osaka office BA terminal”, “Japan Osaka office BB terminal”, “New York office CA of the United States”) "Terminal" and "Washington, USA DB terminal") are extracted.

Next, the storage/readout processing unit 60 of the management system 50 reads out the layout information indicating the display format of the image showing the list of the destination terminals from the non-volatile storage unit 5000 (step S28), and at the same time, extracts the layout information and the terminal. The "destination list information (layout information, terminal ID, destination name)" including the terminal ID and the destination name extracted by the unit 54 is transmitted to the request source terminal (terminal 10aa) (step S29). As a result, in the request source terminal (terminal 10aa), the transmission/reception unit 11 receives the destination list information, and the storage/read processing unit 17 stores the destination list information in the volatile storage unit 1100 (step S30).

As described above, in this embodiment, the management system 50 centrally manages the destination list information of all the terminals, instead of managing the destination list information in each terminal 10. Therefore, a new terminal 10 is included in the transmission system 1, a new model terminal 10 is included in place of the terminal 10 that is already included, and the appearance of the destination list display is changed. Even if this happens, the management system 50 side will deal with it collectively, so that it is possible to save the trouble of changing the destination list information on each terminal 10 side.

Further, the terminal status acquisition unit 55 of the management system 50 uses the terminal IDs of the destination terminal candidates extracted by the terminal extraction unit 54 (“01ab”, “01ba”, “01bb”, “01ca”, and “01db”). Using the search key as a search key, the terminal management table (see FIG. 10) is searched, and the corresponding operating state is read for each terminal ID extracted by the terminal extraction unit 54, whereby terminals (10ab, 10ba, Each operating state of 10bb, 10ca, and 10db is acquired (step S31).

Next, the transmitting/receiving unit 51 uses the terminal IDs (“01ab”, “01ba”, “01bb”, “01ca”, and “01db”) used as the search key in step S31 and the corresponding destination terminals (10ab, The "terminal status information" including the operating statuses of 10ba, 10bb, 10ca and 10db) is transmitted to the request source terminal (terminal 10aa) via the communication network 2 (step S32).

Next, the storage/read processing unit 17 of the request source terminal (terminal 10aa) stores the terminal status information received from the management system 50 in the volatile storage unit 1100 (step S33). As a result, it is possible to acquire the current operating states of the terminals 10 that are candidates for the destination terminals that can talk with the request source terminal (terminal 10aa).

In addition, the conference management unit 58 of the management system 50 outputs the terminal IDs (“01ab”, “01ba”, “01bb”, “01ca”, and “01db”) of the destination terminal candidates extracted by the terminal extraction unit 54. As a search key, the entry management table (see FIG. 14) is searched, and if each terminal ID extracted by the terminal extraction unit 54 has a meeting room ID associated with the terminal ID, the meeting room ID Is read (step S34).

Next, the conference management unit 58 of the management system 50 transmits the conference room presence information including the terminal ID and the conference room ID associated with the terminal ID to the terminal 10aa via the transmission/reception unit 51 (step S35). ). Next, the storage/read processing unit 17 of the request source terminal (terminal 10aa) stores the conference room presence information received from the management system 50 via the transmission/reception unit 11 in the volatile storage unit 1100 (step S36). Next, the destination list creation unit 18 of the terminal 10aa creates a destination list (destination terminal status list information) based on the destination list information, the status information, and the conference room presence information. Next, the display control unit 16 of the request source terminal (terminal 10aa) displays the destination list on the display 120 shown in FIG. 3 as a destination terminal status list image (see FIG. 18) (step S37).

Through the above processing, the management system 50 causes the display 120aa of the terminal 10aa to display an image including the destination terminal status list information of FIG. In the destination terminal status list image of this embodiment, information indicating whether or not there is a conference room associated with the destination terminal is represented by the presence or absence of a conference room icon displayed for each destination terminal status information (image 1504). ..

In the description of FIG. 19, the management system 50 separately transmits the destination list information (step S29), the terminal status information (step S32), and the conference room presence information (step S35). There is. However, the management system 50 may transmit these pieces of information at once. In addition, the management system 50 may create the destination list created by the terminal 10aa in step S37 described above and send the destination list to the terminal 10aa. That is, the destination list may be created on the management system 50 side without creating the destination list on the terminal 10aa side.

Next, with reference to FIG. 20, a process in the case where a terminal requests the start of communication with another terminal (first communication without using a virtual conference room) will be described. FIG. 20 is a sequence diagram showing a process of requesting the start of communication. In FIG. 20, all communication between the terminal 10 and the management system 50 is performed using the management information session sei. Further, in the present embodiment, the request source terminal (terminal 10aa) has the operating state of “ON line (communication possible)” among the terminals 10 as the destination candidates shown in the destination terminal list image (see FIG. 18). It is possible to request the start of communication with at least one of the terminals (terminals 10ab and 10db) that are ". Therefore, a case will be described below in which the user of the request source terminal (terminal 10aa) selects to start a call with the destination terminal (terminals 10ab and 10db).

First, when the user of the request source terminal (terminal 10aa) presses the operation button 108 shown in FIG. 3 to select the destination terminal (terminal 10ab) and the destination terminal (terminal 10db), it is shown in FIG. The operation input accepting unit 12 accepting the request accepts a request to start a call with the terminals 10ab and 10db (step S41). Then, the transmission/reception unit 11 of the terminal 10aa, the terminal ID “01aa” of the request source terminal (terminal 10aa), the terminal ID “01ab” of the destination terminal (terminal 10ab), the terminal ID “01db” of the destination terminal (terminal 10db), And start request information including the information "Invite" indicating that the request for starting the call by the first communication is included in the management system 50 (step S42). As a result, the transmission/reception unit 51 of the management system 50 receives the start request information and grasps the IP address “1.2.1.3” of the request source terminal (terminal 10aa) that is the transmission source. ..

Next, the session ID generation unit 56a identifies a session ID “session ID for identifying communication (call data (image/voice data) session sed)” with each destination terminal requested by the request source terminal (terminal 10aa). "se1" is generated (step S43). When the session ID is generated, the session management unit 57 stores the session ID “se1” and the number of destination terminals “2” in the volatile storage unit 5100. This number of destination terminals is used to determine whether or not the change request information “Reject” has been received from all the destination terminals when the change request information “Reject” for refusing the start of communication is received later. Used for.

Subsequently, the relay device selection unit 56 of the management system 50 relays the call between the request source terminal (terminal 10aa) and the destination terminal (terminals 10ab and 10db) based on the relay device management DB 5001 and the relay device selection management DB 5006. The relay device 30 is selected (step S44). In this case, first, the relay device extraction unit 56b determines the terminal ID “01aa” of the request source terminal (terminal 10aa) included in the start communication information sent from the request source terminal (10aa) and the destination terminal (terminal 10ab). Corresponding to the terminals (10aa, 10ab, 10db) by searching the relay device selection management table (see FIG. 13) based on the terminal ID “01ab” of) and the terminal ID “01db” of the destination terminal (terminal 10db). The relay device ID (“111a”, “111a”, “111d”) that is to be extracted is extracted.

If all the extracted relay device IDs are the same, the selection unit 56c determines whether the extracted relay device ID is in the operating state of the relay device 30 managed by the relay device management table (see FIG. 8). Refer to the status. Here, when the operating state of the relay device ID is “ON line”, the selection unit 56c selects the extracted relay device as the relay device for relaying the call. If the extracted relay device IDs are not the same, or as a result of the above reference, the operation state of the relay device ID is “OFF line”, the relay device 30e having the relay device ID “111e” is called. Is selected as a relay device for relaying. In the present embodiment, the case where the relay device 30e is selected by the selection unit 56c will be continuously described below.

When the selection process of the relay device 30 is completed, the session management unit 57, in the session management table (see FIG. 12) of the non-volatile storage unit 5000, the request source terminal ID and the destination terminal ID of the record including the session ID “se1”. In the field portion of the relay device ID, the terminal ID “01aa” of the request source terminal (terminal 10aa), the terminal ID “01ab” of the destination terminal (terminal 10ab), and the terminal ID “01db” of the destination terminal (terminal 10db), The relay device ID “111e” of the selected relay device 30e is stored and managed (step S45).

Next, the transmission/reception unit 51 shown in FIG. 5 selects the session ID generated by the session ID generation unit 56a and the selection unit 56c to the request source terminal (terminal 10aa) via the communication network 2. The relay device connection information used for connecting to the relay device 30e is transmitted (step S46). The relay device connection information may include the IP address “1.1.1.3” of the relay device 30e, the authentication information, the port number, and the like. Thereby, the terminal 10aa can grasp the relay device connection information used for connecting to the relay device 30e used for relaying the call data in the execution of the session with the session ID “se1”.

Next, the transmission/reception unit 51 includes the terminal ID “01aa” of the request source terminal (terminal 10aa), the change request information “Invite” indicating that a call with the destination terminal is requested to start, and the session ID “se1”. The start request information, the relay device connection information used for connecting to the relay device 30e, and the IP address of the management system 50 are transmitted to all the destination terminals (10ab, 10db) (steps S47-1, S47-2). ). As a result, the transmission/reception unit 51 of the destination terminal (terminals 10ab, 10db) receives the start request information, relay device connection information used for connecting to the relay device 30e used for relaying call data, and transmission. The IP address “1.1.1.2” of the original management system 50 is grasped.

Then, using FIG. 21, the user of the destination terminal (terminal 10db) that has received the start request information depresses the operation button 108 shown in FIG. 3 to request the terminal (terminal 10aa). ) Will be described when a response to the effect of permitting the start of communication with is received. FIG. 21 is a sequence diagram showing a process of permitting a request to start communication. The operation button 108 of the destination terminal (terminal 10db) accepts a response indicating that the start of communication with the request source terminal (terminal 10aa) is permitted (step S48). Next, the transmitting/receiving unit 11 of the destination terminal (terminal 10db) indicates that the terminal ID “01db” of the destination terminal (terminal 10db), the terminal ID “01aa” of the request source terminal (terminal 10aa), and the start of communication are permitted. The start response information including the indicated information “Accept” and the session ID “se1” is transmitted to the management system 50 (step S49).

When the transmission/reception unit 51 of the management system 50 receives the start response information, the state management unit 53 uses the terminal ID “01aa” of the request source terminal (terminal 10aa) and the terminal ID “01db” of the destination terminal (terminal 10db). , In the terminal management table (see FIG. 10), the field portion of the operating state of the record including the terminal ID “01aa” and the terminal ID “01db” is changed from “ON line (call enabled)” to “ON line (call enabled)”. Medium)" (step S50).

Next, the transmission/reception unit 51 includes the terminal ID “01db” of the destination terminal (terminal 10db), the change request information “Accept” indicating that the request to start the call with the destination terminal is permitted, and the session ID “se1”. The start response information is transmitted to the request source terminal (terminal 10aa) (step S51). Upon receiving the start response information, the request source terminal (terminal 10aa) transmits the session ID “se1” and the relay device connection information acquired in step S46 to the relay device 30e by the transmission/reception unit 11, thereby repeating the relay device 30e. It connects with 30e (step S52). On the other hand, the destination terminal (terminal 10db) is connected to the relay device 30e by transmitting the session ID "se1" and the relay device connection information acquired in step S47-2 to the relay device 30e by the transmission/reception unit 11 ( Step S53).

Next, using FIG. 22, the user of the destination terminal (terminal 10ab) that received the start request information in step S47-1 presses the operation button 108 shown in FIG. The process when a response to the effect that the start of communication with the terminal 10aa) is rejected is accepted will be described. FIG. 22 is a sequence diagram showing a process of rejecting a request to start communication. When a response to the effect that the start of communication with the request source terminal (terminal 10aa) is rejected is accepted by the operation button 108 of the destination terminal (terminal 10ab) (step S54), the transmission/reception unit of the destination terminal (terminal 10ab) Reference numeral 11 denotes start response information including the terminal ID “01ab” of the destination terminal (terminal 10ab), the change request information “Reject” indicating that the request to start the communication is rejected, and the session response “se1”. To (step S55).

Next, the session management unit 57, in the session management table (see FIG. 12) of the non-volatile storage unit 5000, from the field portion of the destination terminal of the record including the session ID “se1” to the terminal ID of the destination terminal (terminal 10ab). “01ab” is deleted (step S56). Further, the transmission/reception unit 51 transmits the start ID information including the terminal ID “01ab” of the destination terminal (terminal 10ab), the response information “Reject” indicating that the request to start the communication is rejected, and the session ID “se1”, The data is transmitted to the request source terminal (terminal 10aa) (step S57). Thus, the request source terminal (terminal 10aa) recognizes that the request to start communication with the request source terminal (terminal 10bb) has been rejected.

Next, a process in which the relay device 30e starts relaying call data communicated between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db) will be described with reference to FIG. Note that, in FIG. 23, all communication until the image/voice communication session is established is performed using the management information session sei.

First, the request source terminal (terminal 10aa) has a terminal ID “01aa” and a session ID of the request source terminal (terminal 10aa) at a predetermined timing after connecting to the relay device 30e (see step S52). The relay request information including “se1” and the information “Join” indicating that the start of relay is requested is transmitted to the management system 50 (step S61-1).

When the transmission/reception unit 51 of the management system 50 receives the relay request information, connection control for establishing communication is executed. First, the management system 50 transmits the relay start request information including the terminal ID “01aa” of the request source terminal (terminal 10aa) and the session ID “se1” to the relay device 30e (step S62-1). Upon receiving the relay start request information, the relay device 30e transmits the relay start permission information including the notification information "OK" indicating that the relay start is permitted to the management system 50 (step S63-1). Upon receiving this response, the transmission/reception unit 51 of the management system 50 transmits this relay start permission information to the request source terminal (terminal 10aa) (step S64-1). As a result, the call data session sed between the request source terminal (terminal 10aa) and the relay device 30a is established (step S65-1).

On the other hand, the destination terminal (terminal 10db) has the terminal ID “01db” and the session ID “se1” of the destination terminal (terminal 10db) at a predetermined timing after connecting to the relay device 30e (see step S53). , And relay request information including information “Join” indicating that the relay start is requested (step S61-2).

Subsequently, the management system 50 and the relay device 30e execute the same processing as steps S62-1, S63-1, and S64-1 to call data between the destination terminal (terminal 10db) and the relay device 30e. Session sed is established (steps S62-2, S63-2, S64-2, S65-2). When the call data session sed between the request source terminal (terminal 10aa) and the relay device 30e and the call data session sed between the destination terminal (terminal 10aa) and the relay device 30e are established, the relay device 30a It is possible to relay three pieces of image data of low resolution, medium resolution, and high resolution, and audio data between the terminals (10aa, 10db). This allows the terminals (10aa, 10db) to start a video conference.

Subsequently, using FIG. 24, after a call data session is established between the request source terminal (terminal 10aa), the destination terminal (terminal 10ab), and the destination terminal (terminal 10db), the terminal 10cb displays the call data. The process of participating in the business session will be described. FIG. 24 is a sequence diagram showing a process of requesting participation in a call data session. Note that all communication in the sequence diagram of FIG. 24 is performed using the management information session sei.

From the destination terminal list image, the terminal 10cb accepts the selection of the destination terminal (the terminal 10aa, the terminal 10ab, or the terminal 10db) in which the operating state of the destination terminal is in a call, thereby requesting participation in the existing call data session. Accept (step S101). Here, it is accepted that the user of the terminal 10cb selects the destination terminal (terminal 10aa) by pressing the operation button 108 shown in FIG. 3 to request participation in this call data session. The case will be described as an example. As a result, the transmission/reception unit 11 of the terminal 10cb requests the terminal ID “01cb” of the request source terminal (terminal 10cb), the terminal ID “01aa” of the destination terminal (terminal 10aa), and participation in the call data session. The session participation request information including the change request information “Call” that indicates to the effect is transmitted to the management system 50 (step S102).

Next, the session management unit 57 of the management system 50 indicates that the terminal ID “01aa” of the destination terminal (terminal 10aa) included in the session participation request information is a record of the session management table (see FIG. 12) of the non-volatile storage unit 5000. The record included in the request source terminal ID or the destination terminal ID is searched, and the session ID (“se1”) of the searched record is extracted. Next, the session management unit 57 of the management system 50 adds the terminal ID “01cb” of the request source terminal (terminal 10cb) included in the session participation request information to the destination terminal ID of the retrieved record (step S103). ).

Next, the transmission/reception unit 51 of the management system 50 starts a call data session sed with a participation notification including the terminal ID “01cb” and the session ID “se1” of the terminal 10cb participating in the call data session sed. To the requesting terminal (terminal 10aa), the destination terminal (terminal 10ab) and the destination terminal (terminal 10db) (steps S104-1, S104-2 and step S104-3). Accordingly, the request source terminal (terminal 10aa), the destination terminal (terminal 10ab), and the destination terminal (terminal 10db) can recognize that the destination terminal (terminal 10db) participates in the call data session. In addition, the transmission/reception unit 51 of the management system 50 sends a participation permission notification including the session ID “se1” that participates in the call data session sed and the relay device connection information used to connect to the relay device 30e, to the call data. It transmits to the destination terminal (terminal 10cb) which starts the use session sed (step S104-4).

Upon receiving the participation permission notification, the terminal 10cb connects to the relay device 30e by transmitting the session ID "se1" and the relay device connection information included in the participation permission notification to the relay device 30e by the transmission/reception unit 11 (step S105). As a result, the call data session sed between the terminal 10cb and the relay device 30e is established. When the call data session sed is established, the relay device 30e can relay the image data and the voice data between the terminals (10aa, 10ab, 10cb, and 10db). Thereby, the terminals (10aa, 10ab, 10cb and 10db) can start the video conference.

Next, using FIG. 25, after the call data session is established between the request source terminal (terminal 10aa) and the destination terminal (terminal 10ab, terminals 10cb, 10db), the request source terminal (terminal 10aa) A process of exiting from the call data session will be described. FIG. 25 is a sequence diagram showing a process of requesting exit from a call data session. Note that all communication in the sequence diagram of FIG. 25 is performed using the management information session sei.

First, the user of the request source terminal (terminal 10aa) presses the operation button 108 shown in FIG. 3 to accept a request to leave the call data session (step S111). Then, the transmission/reception unit 11 of the request source terminal (terminal 10aa) has the terminal ID "01aa" of the request source terminal (terminal 10aa), the change request information "Leave" indicating the request to leave the call data session, and the session ID ". The session withdrawal request information including "se1" is transmitted to the management system 50 (step S112).

Next, the session management unit 57, in the session management table (see FIG. 12) of the non-volatile storage unit 5000, changes from the field portion of the request source terminal of the record including the session ID “se1” to the request source terminal (terminal 10aa). The terminal ID “01aa” is deleted (step S113). The management system 50 transmits, to the relay device 30e, a notification that a request for leaving the session including the terminal ID “01aa” of the request source terminal (terminal 10aa) and the session ID “se1” is made (step S114). As a result, the relay device 30e stops the call data session with the request source terminal (terminal 10aa) and disconnects the connection with the request source terminal (terminal 10aa). Subsequently, the relay device 30e transmits, to the management system 50, a notification that the exit request including the terminal ID "01aa" and the session ID "se1" of the request source terminal (terminal 10aa) is permitted (step S115). ).

When the management system 50 receives the notification that the exit request is permitted, the transmission/reception unit 51 causes the requester terminal (terminal 10aa) to have the terminal ID “01aa”, the change request information “Leave”, the session ID “se1”, and exit. The session exit permission information including the notification information “OK” indicating that the request is permitted is transmitted to the request source terminal (terminal 10aa) (step S116). Based on the terminal ID “01aa” of the request source terminal (terminal 10aa) included in the session exit request information, the state management unit 53 of the management system 50 determines that the terminal ID “01aa” is in the terminal management table (see FIG. 10). The operating state of the included record is changed from "ON line (during a call)" to "ON line (during a call)" (step S117).

Next, the terminal 10aa receives the power-off request by pressing the power switch 109 shown in FIG. 3 (step S118). When the power-off request is accepted, the transmission/reception unit 11 transmits to the management system 50 disconnection request information including notification information indicating that the connection between the terminal ID “01aa” of the terminal 10aa and the management system 50 will be disconnected ( Step S119).

When the transmission/reception unit 51 of the management system 50 receives the disconnection request information, the state management unit 53 determines the terminal management table (FIG. 10) based on the terminal ID “01aa” of the request source terminal (terminal 10aa) included in the disconnection request information. In reference), the operating state of the record including the terminal ID “01aa” is changed from “ON line (communication possible)” to “OFF line” (step S120). Subsequently, the transmission/reception unit 51 transmits disconnection permission information indicating that the disconnection request is permitted to the request source terminal (terminal 10aa) (step S121). As a result, the management system 50 stops the management data session with the request source terminal (terminal 10aa) and disconnects the connection with the request source terminal (terminal 10aa).

Upon receiving the disconnection permission information, the request source terminal (terminal 10aa) turns off the power and completes the process (step S122). The terminal 10ab, the terminal 10cb, and the terminal 10db can also exit the call data session sed and complete the call between the terminals in the same manner as the processes of the steps S111 to S121 of the terminal 10aa.

Next, the conference room function of the transmission system 1 of this embodiment will be described. The conference room function is a function for performing the second communication, in which participation between the request source terminal and the destination terminal is restricted, using a virtual conference room on the transmission system 1. First, a conference room list image showing a list of conference rooms will be described. In the transmission system 1 of the present embodiment, the conference room list image is displayed when the user selects the conference room application from the function list image showing the list of functions of the terminal 10. FIG. 26 is a diagram showing an image showing a list of functions of the terminal. FIG. 27 is a diagram showing an image showing a list of conference rooms. When the operation input reception unit 12 of the terminal 10 receives an operation input for selecting a conference room application from the function list image of FIG. 26, the display control unit 16 of the terminal 10 displays the conference room list image of FIG. 27.

The meeting room list image in FIG. 27 is an example in the case where information indicating two meeting rooms (sales promotion meeting and complaint correspondence meeting) is included. Also, a new creation button and a return button are displayed at the lower right of the conference room list image. The new creation button is a button that the user presses when creating a new conference room. The return button is a button that the user presses when returning to the display of the function list image.

When the operation input reception unit 12 of the terminal 10 receives an operation input indicating the pressing of the new creation button for the conference room list image from the user, the display control unit 16 of the terminal 10 displays the newly created conference room image on the terminal 10. .. FIG. 28 is a diagram showing a newly created conference room image displayed when a new conference room is created.

Here, the flow of processing of the terminal 10 and the management system 50 when the user selects a conference room application and newly creates a conference room will be described by taking the case of the user of the terminal 10ab as an example. FIG. 29 is a sequence diagram showing a process of displaying a conference room list and creating a new conference room.

The operation input receiving unit 12 of the terminal 10ab receives an operation input for selecting a conference room application from the function list image of FIG. 26 (step S201). Next, the transmission/reception unit 11 of the terminal 10ab transmits a conference name list acquisition request including the terminal ID “01ab” of the terminal 10ab to the management system 50 (step S202).

Next, the conference management unit 58 of the management system 50 receives the conference name list acquisition request via the transmission/reception unit 51. The meeting management unit 58 acquires the meeting room ID and the meeting room name of the meeting room related to the terminal ID “01ab” of the terminal 10ab based on the terminal ID “01ab” of the terminal 10ab included in the meeting room list acquisition request. (Step S203). Specifically, the conference management unit 58 first searches for a record in the entry management DB 5007 using the terminal ID “01ab” of the terminal 10ab included in the conference room list acquisition request as a search key, and the conference of the searched record Acquire the room ID (1 and 3). Next, the meeting management unit 58 refers to the meeting room management DB 5008 and acquires the meeting room name (sales promotion meeting and complaint handling meeting) of the meeting room ID (1 and 3).

Next, the conference management unit 58 transmits the conference room list information including the conference room ID and the conference room name acquired in step S203 to the terminal 10ab via the transmission/reception unit 51 (step S204). The display control unit 16 of the terminal 10ab receives the conference room list information via the transmission/reception unit 11. The display control unit 16 of the terminal 10ab displays the conference room list image including the conference room name of the conference room list information on the terminal 10ab (step S205).

Next, the operation input reception unit 12 of the terminal 10ab receives an operation input indicating pressing of the new creation button of the conference room list image from the user (step S206). The transmitting/receiving unit 11 of the terminal 10ab transmits a destination terminal information acquisition request including the terminal ID “01ab” of the terminal 10ab to the management system 50 (step S207).

The terminal extraction unit 54 of the management system 50 receives the destination terminal information acquisition request via the transmission/reception unit 51. Based on the terminal ID “01ab” of the terminal 10ab included in the destination terminal information acquisition request, the terminal extraction unit 54 obtains the destination terminal information (terminal ID, terminal name, and operating state) of the destination terminal associated with the terminal 10ab. It is acquired (step S208). Specifically, the terminal extraction unit 54 first searches for the request source terminal ID in the destination list management DB 5004 by using the terminal ID “01ab” of the terminal 10ab included in the destination terminal information acquisition request as a search key. The destination terminal IDs (“01aa”, “01ca”, and “01cb”) of the recorded record are acquired. Next, the terminal extraction unit 54 searches for the terminal ID in the terminal management DB 5003 using each of the destination terminal IDs (“01aa”, “01ca”, and “01cb”) as a search key, and the terminal of the searched record. Get name and operating status. For example, when the search key is “01aa”, the terminal extraction unit 54 acquires the terminal name “Japan Tokyo Office AA terminal” and the operating status “ON line (call enabled)” from the record of the terminal management DB 5003. ..

Next, the terminal extraction unit 54 transmits the destination terminal information including the terminal ID, the terminal name, and the operating status acquired in step S208 to the terminal 10ab via the transmission/reception unit 51 (step S209). The display control unit 16 of the terminal 10ab receives the destination terminal information via the transmission/reception unit 11. The display control unit 10ab displays the newly created conference room image (see FIG. 28) including the terminal ID of the destination terminal information, the terminal name, and the operating state on the terminal 10ab. The operation input reception unit 12 of the terminal 10ab receives an operation input indicating the conference name and the selection of the terminal 10 that can participate in the conference (step S210). The operation input reception unit 12 of the terminal 10ab transmits the conference room new creation information including the conference name and the terminal ID of the terminal 10 capable of participating in the conference to the management system 50 via the transmission/reception unit 11 (step S211).

Next, the conference management unit 58 of the management system 50 receives the newly created conference room information via the transmission/reception unit 51. The meeting management unit 58 newly creates a meeting room ID corresponding to the meeting name included in the newly created meeting room information. The conference management unit 58 creates a record in which the conference room ID and the conference name are associated with each other in the conference room management DB 5008. The conference management unit 58 also creates a record in the entry management DB 5007 in which the conference room ID and the terminal ID included in the new conference room creation information are associated with each other (step S212).

The conference management unit 58 transmits a conference room information registration notification indicating that a new conference room has been created to the terminal 10ab via the transmission/reception unit 51 (step S213). Upon receiving the conference room information registration notification via the transmitting/receiving unit 11, the display control unit 16 of the terminal 10ab displays a registration completion image including information indicating that the registration of the conference room is completed on the terminal 10ab (step S214). ..

Next, a flow of processing of the terminal 10 and the management system 50 when displaying detailed information of the conference room and editing the conference room information (the conference name and the terminal 10 that can participate) will be described. First, a conference room detailed image showing detailed information of the conference room will be described. FIG. 30 is a diagram showing a conference room detailed image showing detailed information of the conference room. The detailed image of the conference room in FIG. 30 includes a conference name, information on the terminals 10 that can participate (terminal ID, terminal name and operating state), a room entry button, an edit button and a cancel button. The meeting name is the name of the meeting room. The information of the terminal 10 that can participate (terminal ID, terminal name, and operating state) is information of the terminal 10 associated with the conference. The room entry button is a button that the user presses when starting communication using the conference room having the conference name. The edit button is a button that the user presses when editing the conference room information (the conference name and the terminals 10 that can participate) of the conference room having the conference name. The cancel button is a button that the user presses when returning to the conference room list image.

When the operation input reception unit 12 of the terminal 10 receives the press of the edit button, the display control unit 16 of the terminal 10 displays the conference room edited image on the terminal 10. FIG. 31 is a diagram showing a conference room edited image displayed when the conference room information is edited. The conference room edited image includes a conference name, information on the terminal 10 that can be registered for participation (terminal ID, terminal name, and operating state), information indicating the currently designated terminal 10 among the terminals 10 that can be registered for participation, an update button, Includes a cancel button. The meeting name is the name of the meeting room. The information (terminal ID, terminal name, and operating status) of the terminal 10 that can be registered for participation is the information of the destination terminal associated with the terminal 10 that edits the conference room information. The information indicating the currently designated terminal 10 among the terminals 10 that can be registered for participation is information indicating the terminal 10 specified by the terminal ID associated with the conference room ID corresponding to the conference name. In the example of FIG. 31, the checked terminal information is information indicating the currently designated terminal 10 among the terminals 10 that can be registered for participation. The update button is a button that the user presses when confirming the edited conference room information. The cancel button is a button that the user presses to cancel the editing of the conference room information and return to the conference room detailed image.

Here, the processing flow of the terminal 10 and the management system 50 when the user selects the conference room application and edits the conference room information will be described by taking the case of the user of the terminal 10aa as an example. FIG. 32 is a sequence diagram showing a process of displaying a conference room list and editing a conference room.

Steps S221 to S225 are the same as steps S201 to S205 in FIG. 29, and therefore description thereof will be omitted.

Next, the operation input reception unit 12 of the terminal 10aa receives an operation input indicating the selection of the sales promotion conference included in the conference room list image from the user (step S226). The transmission/reception unit 11 of the terminal 10aa transmits the destination terminal information acquisition request including the conference room ID “1” of the sales promotion conference to the management system 50 (step S227).

The conference management unit 58 of the management system 50 receives the destination terminal information acquisition request via the transmission/reception unit 51. The conference managing unit 58, based on the conference room ID “1” of the sales promotion conference included in the destination terminal information acquisition request, the terminal IDs (“01ab” and “01ab” of the destination terminals associated with the conference room ID “1”. 01ba” and “01bb”). Next, the terminal extraction unit 54 searches for the terminal ID in the terminal management DB 5003 using each of the destination terminal IDs (“01ab”, “01ba”, and “01bb”) as a search key, and the terminal of the searched record. Get name and operating status. For example, when the search key is “01ab”, the terminal extraction unit 54 acquires the terminal name “Japan Tokyo Office AB terminal” and the operating status “OFF line” from the record of the terminal management DB 5003 (step S228). ..

Next, the terminal extraction unit 54 transmits the destination terminal information including the terminal ID, the terminal name, and the operating status acquired in step S228 to the terminal 10aa via the transmission/reception unit 51 (step S229). The display control unit 16 of the terminal 10aa receives the destination terminal information via the transmission/reception unit 11. The display control unit 16 displays the conference room detailed image (see FIG. 30) including the terminal ID of the destination terminal information, the terminal name, and the operating state on the terminal 10aa (step S230). Next, the operation input reception unit 12 of the terminal 10aa receives the press of the edit button (step S231). Next, the transmission/reception unit 51 of the terminal 10aa transmits an edit candidate destination terminal information acquisition request including the terminal ID “01aa” of the terminal 10aa to the management system 50 (step S232).

The terminal extraction unit 54 of the management system 50 receives the edit candidate destination terminal information acquisition request via the transmission/reception unit 51. The terminal extraction unit 54, based on the terminal ID “01aa” of the terminal 10aa included in the edit candidate destination terminal information acquisition request, the destination terminal information (terminal ID, terminal name, and operating state) of the destination terminal associated with the terminal 10aa. ) Is acquired (step S233). Specifically, the terminal extracting unit 54 first searches for the request source terminal ID in the destination list management DB 5004 using the terminal ID “01aa” of the terminal 10aa included in the edit destination terminal information acquisition request as a search key, and then searches. The destination terminal ID (“01ab”, “01ba”, “01bb”, “01ca”, and “01db”) of the recorded record is acquired. Next, the terminal extraction unit 54 searches for the terminal ID in the terminal management DB 5003 using each of the destination terminal IDs (“01ab”, “01ba”, “01bb”, “01ca”, and “01db”) as a search key. Then, the terminal name and the operating status of the retrieved record are acquired. For example, when the search key is “01ab”, the terminal extraction unit 54 acquires the terminal name “Japan Tokyo Office AB terminal” and the operating state “OFF line” from the record of the terminal management DB 5003.

Next, the terminal extraction unit 54 transmits the edit candidate destination terminal information (destination terminal state information) including the terminal ID, the terminal name, and the operating state acquired in step S233 to the terminal 10aa via the transmission/reception unit 51 (step S234). ). Upon receiving the editing candidate destination terminal information via the transmitting/receiving unit 11, the display control unit 16 of the terminal 10aa displays the conference room edited image (see FIG. 31) of the sales promotion conference including the editing candidate destination terminal information on the terminal 10aa. (Step S235). In the edited image of the conference room in FIG. 31, the checked destination terminal information is the destination terminal information of the currently designated destination terminal, and the unchecked destination terminal information is the destination that can be designated by the terminal 10aa. This is destination terminal information of the terminal.

The operation input reception unit 12 of the terminal 10aa receives an operation input related to the editing of the conference room information (the conference name and the terminal 10 that can participate) of the sales promotion conference (step S236). When the operation input reception unit 12 of the terminal 10aa receives the press of the update button, the transmission/reception unit 11 displays the conference room editing information including the conference room ID, the conference name, the terminal ID, and information indicating addition or deletion of the terminal ID. It transmits to the management system 50 (step S237).

Next, the conference management unit 58 of the management system 50 receives the conference room editing information via the transmission/reception unit 51. The meeting management unit 58 adds or deletes the record of the entry management DB 5007 for the combination of the meeting room ID and the terminal ID included in the meeting room editing information according to the information indicating the addition or deletion of the terminal ID. Further, the conference management unit 58 searches for the conference room ID in the conference room management DB 5008 using the conference room ID included in the conference room editing information as a search key, and includes the conference name of the retrieved record in the conference room editing information. The conference name is updated (step S238).

The conference management unit 58 transmits a conference room information update notification indicating that the update of the conference room information has been completed to the terminal 10aa via the transmission/reception unit 51 (step S239). Upon receiving the conference room information update notification via the transmission/reception unit 11, the display control unit 16 of the terminal 10aa displays an update completion image including information indicating that the update of the conference room is completed on the terminal 10aa (step S240). ..

Next, processing of the terminal 10 and the management system 50 when starting communication using the conference room will be described. First, a case will be described in which a conference name is selected from the conference room list image to enter the conference room (communication is started using the conference room having the conference name).

FIG. 33 is a sequence diagram showing processing when entering a conference room from the conference room list. Since steps S241 to S250 are the same as steps S221 to S230 of FIG. 32, description thereof will be omitted.

The operation input reception unit 12 of the terminal 10 (request source terminal) receives an operation input indicating pressing of the entry button of the conference room detailed image (see FIG. 30) (step S251). Next, the transmission/reception unit 11 of the terminal 10 transmits the terminal ID of the request source terminal that has pressed the room entry button, the information “Invite+Room” indicating that the call of the second communication is requested, and the conference room of the conference room. An entry request including the ID is transmitted to the management system 50 (step S252). The conference management unit 58 of the management system 50 receives the entry request via the transmission/reception unit 51. The meeting management unit 58 determines whether or not the record matching the combination of the meeting room ID and the terminal ID included in the entry request is in the entry management DB 5007 (step S253).

The conference management unit 58 performs processing according to the determination result of step S253 (step S254). FIG. 34 is a flowchart showing the processing according to the result of the entry determination.

When there is no record in the entry management DB 5007 that matches the combination of the conference room ID and the terminal ID included in the entry request, and the entry determination result of the determination unit 59 of the management system 50 is not entry OK (step S254-1, No), the transmission/reception unit 51 transmits error information indicating that entry is not possible to the request source terminal that has transmitted the entry request (step S254-7).

When the record that matches the combination of the conference room ID and the terminal ID included in the entry request is in the entry management DB 5007 and the entry determination result of the determination unit 59 of the management system 50 is entry OK (step S254-1). , Yes), and proceeds to the processing of step S254-2.

The session management unit 57 determines whether or not communication using the conference room specified by the conference room ID included in the entry request has already been performed (whether or not the session has already been established) (step S254-). 2). Specifically, the session management unit 57 searches the conference room management DB 5008 by using the conference room ID included in the entry request as a search key, and whether the session ID is set in the session ID field of the retrieved record. Determine whether or not. That is, the session management unit 57 determines that the session has already been established when the session ID is set in the session ID field of the retrieved record.

When the session has already been established (step S254-2, Yes), the session management DB 5005 is searched using the session ID as a search key, and the request included in the entry request is included in the destination terminal ID field of the searched record. The terminal ID of the original terminal is added (step S254-3), and the process proceeds to step S254-6.

When the session has not been established yet (step S254-2, No), the session management unit 57 newly creates a session ID and a new record in the session management DB 5005 (step S254-4). The specific process related to the new creation of the session ID is the same as steps S43 to S45 in FIG. 20, but in step S45, the destination terminal ID field has the same value as the request source terminal ID field. The difference is that you set.

Next, the meeting management unit 58 searches the meeting room management DB 5008 using the meeting room ID included in the entry request as a search key, and newly creates it in the session ID field of the searched record in step S254-4. A session ID is set (step S254-5).

Next, the transmission/reception unit 51 transmits the session ID and the relay device connection information (IP address, authentication information, port number, etc. of the relay device 30) to the request source terminal that transmitted the entry request (step S254-6). .. Through the above processing, the processing for connecting the request source terminal to the relay device is completed. Next, the request source terminal transmits the relay request information to the management system 50 and starts the process of requesting the relay of the call data (see step S61-1 to step S65-1 in FIG. 23). As a result, the request source terminal that has transmitted the entry request by accepting the selection of the conference name included in the conference room list from the user starts communication using the conference room.

Next, a case will be described in which a destination terminal is selected from the destination terminal list image (see FIG. 18) to enter the conference room (communication is started using the conference room having the conference name).

First, from the destination terminal list information of the destination terminal list image, selection of destination terminal information in which the operating state is “ON line (call in progress)” and the conference room icon (see image 1504 in FIG. 18) is displayed The case of accepting will be described.

FIG. 35 is a sequence diagram showing a process for selecting a destination terminal on the ON line (during a call) from the destination list and starting communication. From the destination terminal list information shown in the destination terminal list image, the operation input reception unit 12 of the terminal 10 has the operating state of “ON line (during a call)” and the conference room icon (see FIG. 18, image 1504). The selection of the destination terminal information for which () is displayed is accepted (step S261).

Next, the transmission/reception unit 11 transmits a communication method confirmation request including the terminal ID of the selected destination terminal to the management system 50 (step S262). The session management unit 57 of the management system 50 receives the communication method confirmation request via the transmission/reception unit 51. The session management unit 57 uses the terminal ID included in the communication method confirmation request as a search key to search the request source terminal ID field and the destination terminal ID field of the session management DB 5005, and specifies the session ID from the searched record ( Step S263).

Next, the conference management unit 58 searches the session ID field of the conference room management DB 5008 using the session ID as a search key, and determines whether or not there is a record in which the session ID is set. The communication method is specified (step S264). That is, when there is a record in which the session ID is set, the conference management unit 58 identifies that the communication identified by the session ID is the second communication using the conference room.

The transmission/reception unit 51 transmits a notification including information indicating the communication method specified in step S264 to the terminal 10 (step S265). Next, when the transmission/reception unit 11 of the terminal 10 receives the notification of the communication method from the management system 50 (step S266), the transmission/reception unit 11 performs transmission according to the notification (step S267). That is, the transmission/reception unit 11 transmits the start request information by the normal call or the start request information by the entry call to the management system 50. The normal call start request information includes a terminal ID for identifying the request source terminal, a terminal ID for identifying the destination terminal, and information “Invite” indicating that the call start by the first communication is requested. .. The start request information for entering the room includes a terminal ID for identifying the request source terminal, a terminal ID for identifying the destination terminal, and information “Invite+Room” indicating that a call start by the second communication is requested. ..

Next, from the destination terminal list information of the destination terminal list image, the destination terminal information whose operating state is “ON line (communication possible)” and the conference room icon (see image 1504 in FIG. 18) is displayed. The case where the selection is accepted will be described.

FIG. 36 is a flowchart showing a process when selecting an ON-line (callable) destination terminal from the destination list and entering the conference room. From the destination terminal list information shown in the destination terminal list image, the operation input reception unit 12 of the terminal 10 has the operating state of “ON line (communication possible)” and the conference room icon (see FIG. 18, image 1504). ) Is accepted to select the destination terminal information (step S271). Next, the display control unit 16 of the terminal 10 displays an image for the user to select whether to use the conference room to make a call (entry call) or a call that does not use the meeting room (normal call). Is displayed (step S272).

The operation input reception unit 12 specifies the communication (transmission) method by receiving the operation input indicating the selection of the communication method from the user (step S273).

When the communication method is the communication using the conference room (step S273, use of the conference room), the transmission/reception unit 11 notifies the terminal ID of the request source terminal and the information “Invite+Room” indicating that the start of the call by the second communication is requested. ], and start request information by entry call transmission including information for identifying a conference room used for communication (step S274). The information for identifying the conference room used for communication is the conference room ID or the terminal ID of the destination terminal. In the case of the terminal ID of the destination terminal, the conference management unit 58 of the management system 50 uses the terminal ID of the destination terminal as a search key to search for the terminal ID in the entry management DB 5007, and acquires the conference room ID of the searched record. By doing so, the conference room used for communication is specified.

When the communication method is not the communication using the conference room (step S273, normal), the transmission/reception unit 11 transmits start request information by normal transmission including the terminal ID of the request source terminal and the terminal ID of the destination terminal (step S275). ..

Here, the reception processing of the start request information on the management system 50 side will be described. In the case of start request information by normal transmission, in FIG. 20 (process for requesting start of communication), FIG. 21 (process for permitting request for start of communication) and FIG. 22 (process for rejecting request for start of communication). Since it is explained, it is omitted.

The case of the start request information by calling into the room will be described. The entry request information for entering the room includes the terminal ID of the request source terminal and the information for identifying the meeting room to enter (the meeting room ID or the terminal ID of the destination terminal).

First, a case where the information for identifying the conference room to enter is the conference room ID will be described. When the determination unit 59 of the management system 50 receives the entry request start request information via the transmission/reception unit 51, the conference room ID included in the start request information and the terminal ID of the request source terminal included in the start request information are received. Is associated with. When associated, the session management unit 57 permits the start of the second communication identified by the conference room ID. Specifically, the session management unit 57 performs the session management process related to the generation of the session for starting the second communication identified by the conference room ID (see step S254-4 to step S254-6 in FIG. 34). )I do.

Next, a case where the information for identifying the conference room to enter is the terminal ID of the destination terminal will be described. When the determination unit 59 of the management system 50 receives the entry request information for entering the room via the transmission/reception unit 51, the determination unit 59 identifies the meeting room ID associated with the terminal ID of the destination terminal included in the entry request information, and specifies the conference room ID. It is determined whether the conference room ID is associated with the terminal ID of the request source terminal included in the start request information. When associated, the session management unit 57 permits the start of the second communication identified by the conference room ID. Specifically, the session management unit 57 performs the session management process related to the generation of the session for starting the second communication identified by the conference room ID (see step S254-4 to step S254-6 in FIG. 34). )I do.

Note that the processing on the destination terminal side is the same as in FIG. 21 (processing for permitting a request to start communication) and FIG. 22 (processing for rejecting a request to start communication), even in the case of start request information due to entry into a room. Therefore, the description is omitted.

Returning to FIG. 36, the transmission/reception unit 11 receives start response information indicating whether communication with the destination terminal is possible from the management system 50 (step S276). The transmission/reception unit 11 refers to the start response information and determines whether or not communication with the destination terminal is possible (step S277). When communication is possible (step S277, Yes), the transmission/reception unit 11 starts communication with the destination terminal (step S278). When communication is not possible (No in step S277), the display control unit 16 displays error information indicating the reason why communication with the destination terminal is not possible on the terminal 10 (step S279).

Here, in the description of FIG. 36, the case where the information for specifying the conference room to be entered in the entry request start information is the terminal ID of the destination terminal will be supplemented. When the determination unit 59 receives the entrance request start request information via the transmission/reception unit 51, the terminal ID of the request source terminal included in the start request information may be associated with a plurality of conference room IDs. .. At this time, the determination unit 59 transmits, via the transmission/reception unit 51, the conference list information including a plurality of pieces of information (conference name etc.) indicating the conference identified by the conference room ID to the request source terminal, and the transmission/reception unit 51 By further receiving the information indicating the one conference selected from the conference list information, the one conference room into which the request source terminal enters is specified.

As described above, according to the present embodiment, the management system 50 indicates whether or not the destination terminal is associated with the second communication performed using the virtual conference room. The destination terminal state list information including at least one destination terminal state information including the information is transmitted to the terminal 10. Accordingly, the user of the terminal 10 can perform the second communication using the virtual conference room with the user of the destination terminal without specifying the information such as the conference name.

Further, according to the present embodiment, since the destination terminal status information includes the operating status information of the destination terminal, the user of the terminal 10 can determine the destination terminal status information from the image showing the destination terminal status list information displayed on the terminal 10. It is possible to determine whether or not to start communication while referring to the operating state.

<<Supplement to Embodiment>>

Further, the management system 50 and the program providing system 90 in each of the above embodiments may be constructed by a single computer, or may be constructed by a plurality of computers in which each unit (function or means) is divided and arbitrarily assigned. It may have been done. When the program providing system 90 is constructed by a single computer, the program transmitted by the program providing system 90 may be divided into a plurality of modules and may be transmitted. It may be transmitted. Further, when the program providing system 90 is constructed by a plurality of computers, a plurality of modules may be divided and transmitted from each computer.

Further, the recording medium in which the terminal program, the relay device program, and the transmission management program of the present embodiment are stored, the HD 204 in which these programs are stored, and the program providing system 90 including this HD 204 are Both are used as program products when the terminal program, the relay device program, and the transmission management program are provided domestically or internationally to a user or the like.

Further, in the above embodiment, the IP address of the relay device is managed in FIG. 8 and the IP address of the terminal is managed in FIG. 10, but the invention is not limited to this, and the relay device 30 is specified on the communication network 2. The FQDN (Fully Qualified Domain Name) may be managed as long as it is the relay device specifying information of 1. or the terminal specifying information for specifying the terminal 10 on the communication network 2. In this case, the well-known DNS (Domain Name System) server acquires the IP address corresponding to the FQDN. Note that not only "relay device identification information for identifying the relay device 30 in the communication network 2" but also "relay device connection destination information indicating a connection destination to the relay device 30 on the communication network 2" or "communication It may be expressed as “relay device destination information indicating a destination to the relay device 30 on the network 2.” Similarly, not only “terminal identification information for identifying the terminal 10 on the communication network 2” but also “terminal connection destination information indicating a connection destination to the terminal 10 on the communication network 2” or “on the communication network 2” It may also be expressed as "terminal destination information indicating the destination to the terminal 10."

In the present embodiment, “video conference” is used as a term that can be replaced with “video conference”.

Further, in the above-described embodiment, the case of the video conference system has been described as an example of the transmission system 1, but the present invention is not limited to this, and a telephone system such as an IP (Internet Protocol) telephone or an internet telephone may be used. .. Further, the transmission system 1 may be a car navigation system. In this case, for example, one of the terminals 10 corresponds to a car navigation device installed in a car, and the other of the terminals 10 is installed in a management terminal or a management server of a management center that manages car navigation, or in another car. It corresponds to the existing car navigation system. Furthermore, the transmission system 1 may be a voice conference system or a PC (Personal Computer) screen sharing system.

Further, in the above-described embodiment, the case where the video conference is held by the transmission system 1 has been described, but the present invention is not limited to this, and a general conversation such as a meeting, a family or a friend, or information in one direction can be performed. It may be used for presentation.

Further, in the above embodiment, the case where the terminal 10 is a dedicated terminal as shown in FIG. 2 has been described, but the terminal 10 may be a general-purpose terminal such as a PC. That is, the above-mentioned terminal program may be installed and executed in a general-purpose terminal such as a PC.

DESCRIPTION OF SYMBOLS 10 terminal 11 transmission/reception unit 12 operation input reception unit 13 login request unit 14 imaging unit 15a voice input unit 15b voice output unit 16 display control unit 17 storage/readout processing unit 18 destination list creation unit 30 relay device 31 transmission/reception unit 32 state detection unit 33 storage/read processing unit 50 management system 51 transmission/reception unit 52 terminal authentication unit 53 state management unit 54 terminal extraction unit 55 terminal state acquisition unit 56 relay device selection unit 57 session management unit 58 conference management unit 59 determination unit 60 storage/read processing Unit 1000 Non-volatile storage unit 1100 Volatile storage unit 3000 Non-volatile storage unit 5000 Non-volatile storage unit 5001 Relay device management DB
5002 Terminal authentication management DB
5003 Terminal management DB
5004 Destination list management DB
5005 Session management DB
5006 Relay device selection DB
5007 Entry management DB
5008 Conference room management DB
5100 Volatile storage

JP, 2005-167903, A

Claims (8)

A management system for managing a communication end end you send and receive content data,
And identification information of the first terminal, and the destination terminal information management unit for managing in association with identification information of the first second terminal one or more candidates for the destination of the communication terminal,
1 or more terminals that are specified with identification information of the destination terminal information managing the one or more second associated with the identification information of the first terminal that is managed by the unit terminal, the operation accepted in the terminal and There among conference identification information for identifying the possible participation conference, transmitting unit that transmits said conference identification information associated with one of the end the one or more second end to said first terminal,
Equipped with
From the first terminal,
Of identification information of the one or more second terminal that is displayed on the display screen, when receiving a start request for the first communication in which the identification information of the second terminal that is selected destined executes connection control for establishing a communication in which a plurality of terminals including a terminal identified by the identification information of the second terminal said selected transmits the content data can participate,
The conference identified by the conference identification information transmitted by the transmission unit, and when the second communication start request associated with the conference selected on the display screen is received, the selected conference is said one or more second terminal associated to execute connection control for establishing the communication for transmitting the content data can participate,
Management system characterized by. When receiving a start request of the second communication, the first two of the conference identification information included in the start request of the communication, identification of the first terminal included in the start request of the second communication A determination unit that determines whether information is associated,
The conference identification information included in the start request of the second communication, if the identification information of the first terminal included in the start request of the second communication is associated, by the conference identification information A session management unit that permits the first terminal to start the identified second communication;
The management system according to claim 1, further comprising: The transmitter is
Further transmitting operating state information indicating an operating state of the second terminal to the first terminal,
The communication method confirmation request including identification information of the second terminal in the operating state the call, when receiving from said first terminal,
The session management unit,
If the communication identified by the previous Ki識 specific information of the second terminal included in the communication process confirmation request is the first communication, the the start request of the second communication can be received The first terminal is notified, and when it is not the first communication, the first terminal is notified that the request for starting the first communication is receivable. Management system. The management system according to any one of claims 1 to 3, wherein the management system is constructed by one or more computers. The management system according to any one of claims 1 to 4, wherein the content data is image data and audio data. And end late you send and receive content data, a transmission system and a management system for managing communication of pre Symbol edge end,
The management system is,
And identification information of the first terminal, and the destination terminal information management unit for managing in association with identification information of the first second terminal one or more candidates for the destination of the communication terminal,
1 or more terminals that are specified with identification information of the destination terminal information managing the one or more second associated with the identification information of the first terminal that is managed by the unit terminal, the operation accepted in the terminal and There among conference identification information for identifying the possible participation conference, transmitting unit that transmits said conference identification information associated with one of the end the one or more second end to said first terminal,
Equipped with
The management system is
From the first terminal,
Of identification information of the one or more second terminal that is displayed on the display screen, when receiving a start request for the first communication in which the identification information of the second terminal that is selected destined executes connection control for establishing a communication in which a plurality of terminals including a terminal identified by the identification information of the second terminal said selected transmits the content data can participate,
The conference identified by the conference identification information transmitted by the transmission unit, and when the second communication start request associated with the conference selected on the display screen is received, the selected conference is said one or more second terminal associated to execute connection control for establishing the communication for transmitting the content data can participate,
Transmission system characterized by. A transmission management method for managing system that manages the communication end end you send and receive content data,
Management system, the step of managing in association with identification information of the first terminal, and identification information of the first one or more second terminal which is the destination candidate communication terminal,
Management system, and identification information of said first of said one or more second devices associated with identification information of the terminal, one or more terminals can join the conference specified by the operation received at the terminal of conference identification information for identifying, and sending said conference identification information associated with one of the end the one or more second end to said first terminal,
Management system, from said first terminal, among the identification information of the one or more second terminal that is displayed on the display screen, the was identification information of the second terminal that is selected as the destination 1 of when receiving a start request of communication is for establishing a communication in which a plurality of terminals including a terminal identified by the identification information of the second terminal said selected transmits the content data can participate Performing connection control,
When the management system receives the request for starting the second communication associated with the conference selected on the display screen, which is the conference identified by the conference identification information transmitted in the transmitting step, executing a connection control for the one or more second terminal associated with the selected conference to establish communication for transmitting the content data can participate,
Transmission management method including. A computer that manages the communication of multiple terminals that send and receive content data,
Managing the identification information of the first terminal and the identification information of one or more second terminals that are candidates for the destination of communication of the first terminal in association with each other;
A management system identifies the identification information of the one or more second terminals associated with the identification information of the first terminal and the conference in which the one or more terminals designated by the operation accepted by the terminal can participate. Of the conference identification information, transmitting the conference identification information associated with any one of the one or more second terminals to the first terminal;
A first communication start request is received from the first terminal, which is addressed to the identification information of the selected second terminal among the identification information of the one or more second terminals displayed on the display screen. In that case, a step of executing connection control for establishing communication for transmitting the content data in which a plurality of terminals including a terminal identified by the identification information of the selected second terminal can participate,
The conference identified by the conference identification information transmitted in the transmitting step, and if the second communication start request associated with the conference selected on the display screen is received, the selected conference is received. Performing connection control for establishing communication for transmitting the content data in which the one or more second terminals associated with
A program to execute.

Images