Source: https://patents.google.com/patent/JP2012191598A/en
Timestamp: 2020-02-22 23:54:14
Document Index: 141424657

Matched Legal Cases: ['art 51', 'art 12', 'art 13', 'art 14', 'art 15', 'art 15', 'art 16', 'art 18', 'art 19', 'art 20', 'art 31', 'art 32', 'art)\n63']

JP2012191598A - Connection control system, transmission system, and program for connection control system - Google Patents
Connection control system, transmission system, and program for connection control system Download PDF
JP2012191598A
JP2012191598A JP2011199212A JP2011199212A JP2012191598A JP 2012191598 A JP2012191598 A JP 2012191598A JP 2011199212 A JP2011199212 A JP 2011199212A JP 2011199212 A JP2011199212 A JP 2011199212A JP 2012191598 A JP2012191598 A JP 2012191598A
JP2011199212A
JP5919695B2 (en
2011-02-25 Priority to JP2011039920 priority Critical
2011-02-25 Priority to JP2011039920 priority
2011-09-13 Application filed by Ricoh Co Ltd, 株式会社リコー filed Critical Ricoh Co Ltd
2011-09-13 Priority to JP2011199212A priority patent/JP5919695B2/en
2012-10-04 Publication of JP2012191598A publication Critical patent/JP2012191598A/en
2016-05-18 Publication of JP5919695B2 publication Critical patent/JP5919695B2/en
According to a conventional video conference system, there is a problem that a video conference terminal that is not reserved cannot participate in a video conference when performing a video conference between multiple sites.
A terminal extraction unit 54 of a transmission management system 50 receives destination terminal identification information associated with transmission terminal identification information of each transmission terminal 10 of a first transmission terminal and a second transmission terminal from a destination list management DB 5004. Extract. Further, the destination determination unit 62 determines whether the extracted destination terminal identification information includes destination terminal identification information for identifying the third transmission terminal. Thereby, the transmission management system 50 can perform control for connecting the first transmission terminal, the second transmission terminal, and the third transmission terminal based on a predetermined determination. That is, when a session between multiple sites is performed, it is possible to realize that the transmission terminal 10 that has not reserved participates in this session.
The present invention relates to a connection control system that controls connection between transmission terminals based on a predetermined determination.
2. Description of the Related Art In recent years, video conferencing systems that conduct video conferences via a communication network such as the Internet have become widespread in response to requests for reducing business trip expenses and business trip times. In this video conference system, when a call is started between transmission terminals such as a plurality of video conferences, call data such as image data and audio data is transmitted and received, thereby realizing a video conference. With the recent enhancement of broadband environment, it has become possible to send and receive high-quality image data and high-quality audio data, making it easier to understand the status of the other party and improving the level of communication through the call. Can now.
In addition to the video conference between the two video conference terminals, the video conference system realizes the video conference between the multiple sites by transmitting and receiving call data between the video conference terminals at three or more sites (multiple sites). I was able to do that. When starting a video conference between multiple locations, the management system knows that it will accept conference start information by e-mail to identify the conference start time, conference terminal, etc. sent by the groupware with conference reservation function. (See Patent Document 1). Thereby, the management system can perform control and management associated with holding a conference on the video conference terminal based on the conference holding information extracted from the e-mail.
In addition, when another video conference terminal participates in an ongoing video conference and conducts a video conference between multiple locations, the list of users allowed to participate in the electronic conference is added to the list of permitted participants held by the conference manager. It is known to register an identifier (see Patent Document 2). Accordingly, the conference manager that has received the participation request can register the conference terminal as a conference participant when the transmitted user identifier is included in the participation permitter list.
However, according to the conventional video conference system, when starting a video conference between multiple bases, or when performing a video conference between multiple bases by mid-participation, a reservation is made by designating a terminal that participates in the video conference in advance. There was a need. That is, when performing a video conference between multiple locations, there is a problem that a video conference terminal that has not been reserved cannot participate in the video conference.
The invention according to claim 1 is a connection control system for controlling connection between transmission terminals based on a predetermined judgment, and transmission terminal identification information for identifying the transmission terminal, and content data transmitted from the transmission terminal A destination terminal management unit that associates and manages destination terminal identification information for identifying a destination transmission terminal, and a session that transmits content data between the first transmission terminal and the second transmission terminal. A reception unit that receives a request for participation in the session from a third transmission terminal, and the first transmission terminal and the second transmission when the request for participation is received by the reception unit. A destination terminal extraction unit that extracts destination terminal identification information associated with transmission terminal identification information for identifying each transmission terminal of the terminal from the destination terminal management unit; and the destination terminal A connection unit comprising: a determination unit configured to determine whether the destination terminal identification information for identifying the third transmission terminal is included in the destination terminal identification information extracted by the output unit; Control system.
As described above, according to the present invention, the destination terminal extraction unit of the connection control system uses the destination terminal identification information associated with the transmission terminal identification information of each transmission terminal of the first transmission terminal and the second transmission terminal. Extract. The determination unit makes a predetermined determination as to whether the extracted destination terminal identification information includes destination terminal identification information for identifying the third transmission terminal. Thereby, the connection control system can perform control for connecting the first transmission terminal, the second transmission terminal, and the third transmission terminal based on the predetermined determination. That is, when a session between multiple sites is performed, it is possible to realize that a third transmission terminal that has not reserved participates in this session.
1 is a schematic diagram of a transmission system according to an embodiment of the present invention. It is a hardware block diagram of the transmission terminal which concerns on one Embodiment of this invention. 1 is a hardware configuration diagram of a transmission management system, a relay device, a program providing system, or a maintenance system according to an embodiment of the present invention. 1 is an external view of a transmission terminal according to an embodiment of the present invention. It is a functional block diagram of each terminal, apparatus, and system which comprise the transmission system which concerns on one Embodiment of this invention. FIG. 6 is a functional block diagram illustrating in detail a state management unit 53 in FIG. 5. FIG. 6 is a functional block diagram illustrating the relay device selection unit 56 of FIG. 5 in detail. It is a conceptual diagram which shows a change quality management table. It is a conceptual diagram explaining the image quality of image data. It is a conceptual diagram which shows a relay apparatus management table. It is a conceptual diagram which shows a terminal authentication management table. It is a conceptual diagram which shows a terminal management table. It is a conceptual diagram which shows a destination list management table. It is a conceptual diagram which shows a session management table. It is a conceptual diagram which shows a quality management table. It is a conceptual diagram which shows a relay apparatus selection management table. It is a conceptual diagram which shows a state change management table. It is a conceptual diagram which shows a state change management table. It is the sequence figure which showed the process which manages the status information which shows the operating state of each relay apparatus. It is the conceptual diagram which showed the transmission / reception state of the image data in the transmission system, audio | voice data, and various management information. It is the sequence diagram which showed the process of the preparation stage which starts a telephone call between transmission terminals. It is a conceptual diagram which shows the destination list of this embodiment. It is the sequence diagram which showed the process which requests | requires the start of communication. It is a processing flowchart which showed the process which changes the state of communication. It is the sequence diagram which showed the process which permits the request | requirement of a communication start. It is the sequence diagram which showed the process which requests | requires relay of content data. It is a processing flowchart which showed the process which changes the state of communication. It is the sequence diagram which showed the process which transmits / receives content data between transmission terminals. It is the sequence diagram which showed the process which requests | requires participation in the session for content data. FIG. 10 is a process flow diagram illustrating participation determination processing using a destination list. It is the conceptual diagram which showed the distance between terminals. It is a processing flowchart which showed the process which changes the state of communication. It is the sequence diagram which showed the process which requests | requires withdrawal from the session for content data. It is a conceptual diagram which shows the destination list of other embodiment. It is a state transition diagram which shows the transition of the state of communication.
Hereinafter, an embodiment of the present invention will be described with reference to FIGS. 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 with reference to FIG.
1 includes a plurality of transmission terminals (10aa, 10ab,...), A display (120aa, 120ab,...) For each transmission terminal (10aa, 10ab,...), And a plurality of relay devices (30a, 30b). , 30c, 30d, 30e), the transmission management system 50, the program providing system 90, and the maintenance system 100.
In the present embodiment, “transmission terminal 10” is used to indicate any transmission terminal among the transmission terminals (10aa, 10ab,...), And any display among the displays (120aa, 120ab,...) Is illustrated. In this case, “display 120” is used, and “relay device 30” is used when an arbitrary relay device among relay devices (30a, 30b, 30c, 30d, 30e) is indicated.
The transmission terminal 10 transmits and receives image data and audio data as an example of content data. In the following, “transmission terminal” is simply represented as “terminal”, and “transmission management system” is simply represented as “management system”. That is, the call in the present embodiment includes not only audio data transmission but also image data transmission. That is, the terminal 10 in the present embodiment transmits image data and audio data. However, the terminal 10 may transmit audio data without transmitting image data. Hereinafter, “image data and audio data” is represented as “content 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 a moving image and a still image. The relay device 30 relays content data among a plurality of terminals 10. The management system 50 manages the terminal 10 and the relay device 30 in an integrated manner.
In addition, the plurality of routers (70a, 70b, 70c, 70d, 70ab, 70cd) shown in FIG. 1 select an optimum route for content data. In the present embodiment, “router 70” is used to indicate an arbitrary router among the routers (70a, 70b, 70c, 70d, 70ab, 70cd).
The program providing system 90 includes an HD (Hard Disk) (not shown) that stores a terminal program for realizing various functions or various means in the terminal 10, 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 can transmit the relay device program to the relay device 30. . Further, the HD of the program providing system 90 also stores a transmission management program for causing the management system 50 to realize various functions or various means, and can transmit the transmission management program to the management system 50. .
Further, the terminals (10aa, 10ab, 10ac, 10a...), The relay device 30a, and the router 70a are communicably connected via the LAN 2a. The terminals (10ba, 10bb, 10bc, 10b...), The relay device 30b, and the router 70b are communicably connected via the 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 region A is Japan, the LAN 2a is constructed in a Tokyo office, and the LAN 2b is constructed in an Osaka office.
On the other hand, the terminals (10ca, 10cb, 10cc, 10c...), The relay device 30c, and the router 70c are communicably connected via the LAN 2c. The terminals (10da, 10db, 10dc, 10d...), The relay device 30d, and the router 70d are communicably connected via a LAN 2d. The LAN 2c and the LAN 2d are communicably connected via a dedicated line 2cd including the router 70cd, and are constructed in a predetermined area B. For example, region B is the United States, LAN 2c is built in a New York office, and LAN 2d is Washington D.C. C. Is built in the office. Area A and area B are connected to each other via routers (70ab, 70cd) via the Internet 2i.
The relay device 30e is connected to the terminal 10 through the communication network 2 so as to be communicable. This relay device 30e is always in operation, and is installed in a region other than these in order to be less affected by the traffic in the local area of region A or region B. Thereby, 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 content 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 if the relay device installed in the local area is not operating.
In FIG. 1, the four sets of numbers shown under each terminal 10, each relay device 30, management system 50, each router 70, program providing system 90, and maintenance system 100 are in general IPv4. An IP address is simply shown. For example, the IP address of the terminal 10aa is “1.2.1.3”. In addition, IPv6 may be used instead of IPv4, but IPv4 will be used for the sake of simplicity.
Next, the hardware configuration of this embodiment will be described. FIG. 4 is an external view of the terminal 10 according to an embodiment of the present invention. 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 as the Y-axis direction, and the direction orthogonal to the X-axis direction and the Y-axis direction (vertical direction) as the Z-axis direction.
FIG. 2 is a hardware configuration diagram of the terminal 10 according to an embodiment of the present invention. As shown in FIG. 2, the terminal 10 of this 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 that stores various data such as image data and audio data, and an SSD (SSD) that controls reading or writing of various data to the flash memory 104 under the control of the CPU 101 Solid State Drive) 105, a media drive 107 that controls reading or writing (storage) of data to a recording medium 106 such as a flash memory, an operation button 108 that is operated when a destination of the terminal 10 is selected, and a power source of the terminal 10 To switch ON / OFF A source switch 109 and a network I / F (Interface) 111 for data transmission using the communication network 2 described later are provided.
The terminal 10 also includes a built-in camera 112 that captures an image of a subject under the control of the CPU 101 to obtain image data, an image sensor I / F 113 that controls driving of the camera 112, a built-in microphone 114 that inputs sound, and sound. The built-in speaker 115 for outputting the sound, the sound input / output I / F 116 for processing the input / output of the sound signal between the microphone 114 and the speaker 115 according to the control of the CPU 101, and the image data on the external display 120 according to the control of the CPU 101. As shown in FIG. 2, a display I / F 117 for transmission, an external device connection I / F 118 for connecting various external devices, an alarm lamp 119 for notifying abnormality of various functions of the terminal 10, and the above-described components are shown. A bus line 110 such as an address bus or a data bus is provided for electrical connection. To have.
FIG. 3 is a hardware configuration diagram of the management system according to the embodiment of the present invention. The management system 50 includes 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 for the CPU 201, an HD (Hard Disk) 204 that stores various data, and a control of the CPU 201. , A HDD (Hard Disk Drive) 205 that controls reading or writing of various data with respect to the HD 204, a media drive 207 that controls reading or writing (storage) of data with respect 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 transmitting data using a communication network 2 to be described later, and a plurality of keys for inputting characters, numerical values, various instructions, etc. Reading data from a keyboard 211 provided, a mouse 212 for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like, and a CD-ROM (Compact Disc Read Only Memory) 213 as an example of a removable recording medium Alternatively, a CD-ROM drive 214 for controlling writing and a bus line 210 such as an address bus and a data bus for electrically connecting the above-described components as shown in FIG.
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 the present embodiment. In FIG. 5, the terminal 10, the relay device 30, and the management system 50 are connected so that data communication can be performed 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 video conference communication.
The terminal 10 includes a transmission / reception unit 11, an operation input reception unit 12, a login request unit 13, an imaging unit 14, an audio input unit 15a, an audio output unit 15b, a display control unit 16, a delay detection unit 18, a storage / read processing unit 19, And a destination list creation unit 20. Each of these units is a function or means realized by any one of the constituent elements shown in FIG. 2 operating according to a command from the CPU 101 according to a program stored in the ROM 102. Further, the terminal 10 includes a volatile storage unit 1100 constructed by the RAM 103 shown in FIG. 2 and a volatile storage unit 1100 constructed by the flash memory 104 shown in FIG.
Next, each part of the terminal will be described in detail. The transmission / reception unit 11 of the terminal 10 is realized by the network I / F 111 illustrated in FIG. 2, and transmits / receives various data (or information) to / from other terminals, devices, or systems via the communication network 2. The transmission / reception unit 11 starts receiving state information indicating the state of each terminal as a destination candidate from the management system 50 before starting a call with the terminal 10 (destination terminal) as a desired destination. This status information includes not only the operating status of each terminal 10 (the status of ON line or OFF line) but also the detailed status such as whether a call is in progress or waiting even if it is an ON line. Indicates. In addition, the status information is not limited to the operating status of each terminal 10, but the cable is disconnected from the terminal 10 at the terminal 10, audio is output but no image is output, or audio is not output ( Various states such as MUTE) are shown. Below, the case where status information shows an operation state is demonstrated as an example.
The operation input receiving unit 12 is realized by the operation button 108 and the power switch 109 shown in FIG. 2 and receives various inputs by the user. For example, when the user turns on the power switch 109 shown in FIG. 2, the operation input receiving unit 12 shown in FIG. 5 receives the power ON and turns on the power.
The login request unit 13 is realized by a command from the CPU 101 shown in FIG. 2, and requests that the login is made from the transmission / reception unit 11 to the management system 50 via the communication network 2 when the power-on is accepted. And the current IP address of the terminal 10 (request source terminal) as the request source is automatically transmitted. When the user turns the power switch 109 from the ON state to the OFF state, the transmission / reception unit 11 transmits state information indicating that the power supply is turned off to the management system 50, and then the operation input reception unit 12 completely turns the power supply. Set to OFF. As a result, the management system 50 side can grasp that the terminal 10 has been turned off from being turned on.
The imaging unit 14 is realized by the instruction from the CPU 101 illustrated in FIG. 2 and the camera 112 and the image sensor I / F 113 illustrated in FIG. 2. Output image data. The voice input unit 15a is realized by the voice input / output I / F 116 shown in FIG. 2, and after the user's voice is converted into a voice signal by the microphone 114, voice data related to the voice signal is input. The audio output unit 15b is realized by the instruction from the CPU 101 shown in FIG. 2 and the audio input / output I / F 116 shown in FIG. 2, and outputs an audio signal related to the audio data to the speaker. To output sound.
The display control unit 16 is realized by the display I / F 117 illustrated in FIG. 2, and performs control for transmitting image data to the external display 120. The display control unit 16 reflects the state information received after the start of reception by the transmission / reception unit 11 before the terminal 10 as the request source starts a video conference call with the terminal 10 as the desired destination. The destination list including the name is displayed on the display 120.
For example, a destination list frame 1100-1 as shown in FIG. 22 is displayed on the display 120 by the display execution unit 16a. Each destination name such as a destination name “Japan Tokyo Office AB terminal” 1100-2 is displayed in the destination list frame 1100-1, and an icon (1100-) indicating a state relating to the state information for each destination name. 3a, 1100-3b, 1100-3c, 1100-3d) are displayed. Among these, the icon 1100-3a indicates that one terminal as a destination candidate is in an on-line state and can communicate with this terminal. The icon 1100-3b indicates that one terminal as a destination candidate is in an OFF line state and cannot communicate with this terminal. The icon 1100-3c indicates a state in which three-party communication or the like is possible in addition to this call while one of the destination candidates is in a call with another terminal. The icon 1100-3d indicates that one terminal as a destination candidate is requesting a call with another terminal or a call is requested from another terminal. Show. In addition to the above state, the icon 1100-3d permits a request for a call with another terminal or a request for a call with another terminal. Indicates an impossible state. Further, in the destination list frame 1100-1, a scroll bar 1100-4 is displayed on the right side, and when an upward or downward triangle icon is selected, destination names and states of destination candidates not displayed in FIG. Will be displayed.
The delay detection unit 18 is realized by a command from the CPU 101 shown in FIG. 2, and detects a delay time (ms) of image data or audio data sent from another terminal 10 via the relay device 30. .
Further, the storage / read processing unit 19 is executed by the instruction from the CPU 101 shown in FIG. 2 and the SSD 105 shown in FIG. 2 as an example, and stores various data in the nonvolatile storage unit 1000 or nonvolatile storage. Processing for reading various data stored in the unit 1000 is performed. The nonvolatile storage unit 1000 stores a terminal ID (Identification) for identifying the terminal 10, a password, and the like. Further, the storage / reading processing unit 19 stores various data in the volatile storage unit 1100 and also performs processing for reading out various data stored in the volatile storage unit 1100. The volatile storage unit 1100 overwrites and stores content data received when a call with the destination terminal is made. Among these, an image is displayed on the display 120 by the image data before being overwritten, and sound is output from the speaker 115 by the audio data before being overwritten.
Based on destination list information described later and the status information of the terminal 10 as each destination candidate received from the management system 50, the destination list creation unit 20 uses icons to indicate the status of destination candidates as shown in FIG. Create and update the indicated destination list.
Next, functions 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, a data quality confirmation unit 33, a change quality management unit 34, a data quality change unit 35, and a storage / read processing unit 39. Each of these units is a function or means realized by any one of the components shown in FIG. 3 operating according to a command from the CPU 201 according to a program stored in the ROM 202. Further, the relay device 30 is constructed by the HD 204 shown in FIG. 3, and has a non-volatile storage unit 3000 in which storage of various data and information is maintained even when the power of the relay device 30 is turned off.
In the nonvolatile storage unit 3000, a change quality management DB (Data Base) 3001 configured by a change quality management table as shown in FIG. FIG. 8 is a conceptual diagram showing the changed quality management table. In the change quality management table, the IP address of the terminal 10 as the relay destination of the image data and the image quality of the image data relayed by the relay device 30 are managed in association with the relay destination.
Here, the image resolution of the image data handled in the present embodiment will be described with reference to FIG. FIG. 9 is a conceptual diagram illustrating the image quality of image data. As shown in FIG. 9 (a), the horizontal image is composed of 160 pixels and the vertical image is 120 pixels, and the low-resolution image as the base image and the horizontal image as shown in FIG. 9 (b). There are a medium resolution image composed of 320 pixels and 240 pixels vertically, and a high resolution image composed of 640 pixels horizontally and 480 pixels vertically as shown in FIG. 9C. Among these, when passing through a narrow band route, low-quality image data consisting only of low-resolution image data serving as a base image is relayed. When the band is relatively wide, low-resolution image data serving as a base image and medium-quality image data composed of medium-resolution image data are relayed. When the bandwidth is very wide, high-resolution image data composed of low-resolution image data serving as base image quality, intermediate-resolution image data, and high-resolution image data is relayed. For example, in the modified quality management table shown in FIG. 8, when the relay device 30 relays image data to the destination terminal having the IP address “1.3.2.4”, the relay is performed. The image quality (image quality) of the image data is “high quality”.
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. 3, and other terminals, devices, or systems and various data (or the data (or Information). The state detection unit 32 is realized by a command from the CPU 201 illustrated in FIG. 3, 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 “failing” state.
The data quality confirmation unit 33 is realized by an instruction from the CPU 201 shown in FIG. 3, searches the change quality management table (see FIG. 8) using the IP address of the destination terminal as a search key, and relays correspondingly. The image quality of the relayed image data is confirmed by extracting the image quality of the image data. The change quality management unit 34 is realized by a command from the CPU 201 shown in FIG. 3, and the contents of the change quality management table of the change quality management DB 3001 based on quality information to be described later sent from the management system 50. To change. For example, a video conference is performed by transmitting and receiving high-quality image data between a request source terminal (terminal 10aa) whose terminal ID is “01aa” and a destination terminal (terminal 10db) whose terminal ID is “01db”. While the request is being made, the requesting terminal (terminal 10bb) and the destination terminal (terminal 10ca) that conduct another videoconference start the videoconference via the communication network 2, etc., so that the destination terminal (terminal 10db) When a delay in the reception of image data occurs, the relay device 30 needs to reduce the image quality of the image data that has been relayed from the high image quality to the medium image quality. In such a case, the content of the change quality management table of the change quality management DB 3001 is changed so as to lower the image quality of the image data relayed by the relay device 30 from high image quality to medium image quality based on the quality information indicating the medium image quality. Is done.
The data quality changing unit 35 is realized by a command from the CPU 201 shown in FIG. 3 and changes the image quality of the image data sent from the transmission source terminal 10 to the change quality of the changed change quality management DB 3001. Change based on the contents of the management table. The storage / reading processing unit 39 is realized by the HDD 205 shown in FIG. 3, and stores various data in the nonvolatile storage unit 3000 and reads various data stored in the nonvolatile storage unit 3000.
Next, functions or means of the management system 50 will be described. The management system 50 includes a transmission / reception unit 51, a terminal authentication unit 52, a state management unit 53, a terminal extraction unit 54, a terminal state acquisition unit 55, a relay device selection unit 56, a session management unit 57, a quality determination unit 58, and storage / read processing. Unit 59, delay time management unit 60, change request information determination unit 61, destination determination unit 62, and calculation unit 63. Each of these units is a function or means realized by any one of the components shown in FIG. 3 operating according to a command from the CPU 201 according to a program stored in the ROM 202. In addition, the management system 50 includes a non-volatile storage unit 5000 that is constructed by the HD 204 shown in FIG. 3 and maintains various data and information even when the management system 50 is turned off. The nonvolatile storage unit 5000 stores a destination list frame 1100-1 shown in FIG. Furthermore, the management system 50 has a volatile storage unit 5100 constructed by the RAM 203 shown in FIG.
In the nonvolatile storage unit 5000, a relay device management DB 5001 configured by a relay device management table as shown in FIG. 10 is constructed. FIG. 10 is a conceptual diagram showing the relay device management table. 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 status information indicating the operating status is received by the management system 50, and the IP address of the relay device 30 , And the maximum data transmission rate (Mbps) in the relay device 30 is managed in association with each other. For example, in the relay device management table shown in FIG. 10, the relay device 30a with the relay device ID “111a” has an “ON line” operating state and the date and time when the management system 50 received the status information “ "November 10, 2009 13:00" indicates 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.
Further, a terminal authentication management DB 5002 configured by a terminal authentication management table as shown in FIG. 11 is constructed in the nonvolatile storage unit 5000. FIG. 11 is a conceptual diagram showing a terminal authentication management table. In this terminal authentication management table, each password is associated with each terminal ID of all terminals 10 managed by the management system 50 and managed. For example, the terminal authentication management table shown in FIG. 11 indicates that the terminal ID of the terminal 10aa is “01aa” and the password is “aaaa”.
In the nonvolatile storage unit 5000, a terminal management DB 5003 configured by a terminal management table as shown in FIG. 12 is constructed. FIG. 12 is a conceptual diagram showing a terminal management table. In this terminal management table, for each terminal ID of each terminal 10, a destination name when each terminal 10 is a destination, an operating state of each terminal 10, a communication state with other terminals, and login request information described later are managed systems. The reception date and time received at 50 and the IP address of the terminal 10 are associated and managed. For example, in the terminal management table shown in FIG. 12, the terminal 10aa with the terminal ID “01aa” has the terminal name “Japan Tokyo office AA terminal”, the operation state “ON line”, and the communication state. “None” indicating a standby state without communicating with other terminals, and the date and time when the login request information is received by the management system 50 is “13:40 on November 10, 2009”. It is indicated that the IP address of 10aa is “1.2.1.3”. The communication status includes “Calling” indicating that the other terminal is being called, “Ringing” indicating the status being called from the other terminal, whether the request for a call with the other terminal is permitted, “Accepted” indicating that a request for a call with the other terminal is permitted, “Busy” indicating a state during a call with another terminal, and the like are included.
Further, in the nonvolatile storage unit 5000, a destination list management DB 5004 configured by a destination list management table as shown in FIG. 13 is constructed. FIG. 13 is a conceptual diagram showing a destination list management table. In this destination list management table, a terminal that is a candidate for a destination of content data transmitted from the terminal 10 is identified with respect to the terminal ID of the terminal 10 as a call start request source managed by the management system 50. Destination terminal IDs are managed in association with each other. For example, in the destination list management table shown in FIG. 13, a candidate for a destination terminal that can request a start of a video conference call from a terminal (terminal 10aa) whose terminal ID is “01aa” has a terminal ID of It is shown that the terminal 10ab is “01ab”, the terminal 10ba has a terminal ID “01ba”, and the terminal 10db has a terminal ID “01db”. This destination candidate terminal is updated by being added or deleted by a request for addition or deletion from the terminal as a request source to the management system 50.
In the nonvolatile storage unit 5000, a session management DB 5005 configured by a session management table as shown in FIG. 14 is constructed. FIG. 14 is a conceptual diagram showing a session management table. In this session management table, for each session ID for identifying a session in which content data is transmitted between terminals, the relay device ID of the relay device 30 used for relaying content data in this session, the terminal of the request source terminal The management system 50 receives the ID, the terminal ID of the destination terminal, the reception delay time (ms) when image data is received at the destination terminal, and the delay information indicated by this delay time from the destination terminal. The reception date and time received at is associated and managed. For example, in the session management table shown in FIG. 14, the relay device 30e (relay device ID “111e”) selected in the session executed using the session ID “se1” has the terminal ID “01aa”. The content data is relayed between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db) whose terminal ID is “01db”. In the destination terminal (terminal 10db), “November 10, 2009 It is shown that the delay time of the image data at the time “14:00” is 200 (ms). When a video conference is performed between the two terminals 10, the reception date and time of the delay information may be managed based on the delay information transmitted from the request source terminal instead of the destination terminal. However, when a video conference is performed between three or more terminals 10, the reception date and time of delay information is managed based on the delay information transmitted from the terminal 10 on the content data receiving side.
Furthermore, a quality management DB 5007 configured by a quality management table as shown in FIG. 15 is constructed in the nonvolatile storage unit 5000. FIG. 15 is a conceptual diagram showing a quality management table. In this quality management table, the image quality (image quality) of image data relayed by the relay device 30 is associated and managed according to the delay time (ms) of the image data at the request source terminal or the destination terminal.
Further, in the nonvolatile storage unit 5000, a relay device selection management DB 5008 configured by a relay device selection management table as shown in FIG. 16 is constructed. FIG. 16 is a conceptual diagram showing a relay device selection management table. In this quality management table, each terminal ID of all terminals 10 managed by the management system 50 is managed in association with the relay apparatus ID of the relay apparatus 30 used for relaying content data.
Further, in the nonvolatile storage unit 5000, a state change management DB 5009 configured by a state change management table as shown in FIGS. 17 and 18 is constructed. 17 and 18 are conceptual diagrams showing a state change management table. In the state change management table of FIG. 17, change request information indicating a request for changing the state of communication between terminals, state information before change indicating a state of communication before being changed by the state change unit 53c, and a state change unit The change information indicating the state changed by 53c is managed in association with it. In the state change management table of FIG. 18, change request information, terminal information for identifying a request source terminal and a destination terminal, state information before change, and change information are associated and managed.
The state change management table of FIG. 18 indicates that, when the change request information “Invite” is received, the management system 50 changes the communication state “None” before the change of the request source terminal to “Calling”. ing. The change request information includes change request information “Accept” for requesting start of communication, change request information “Accept” for permitting start of communication, and request for start of relay of content data. Change request information “Join”, change request information “Call” requesting participation in this session when a session between terminals is already established, change request information “Leave” requesting termination of communication And the like.
Next, each functional unit of the management system 50 will be described in detail. In the following, in describing each part of the management system 50, a relationship with main constituent elements for realizing each part of the management system 50 among the constituent elements illustrated in FIG. 3 will also be described.
The transmission / reception unit 51 is executed by the network I / F 209 illustrated in FIG. 3, and transmits / receives various data (or information) to / from other terminals, devices, or systems via the communication network 2. The terminal authentication unit 52 searches the terminal authentication management table (see FIG. 11) of the nonvolatile storage unit 5000 using the terminal ID and password included in the login request information received via the transmission / reception unit 51 as search keys. The terminal authentication is performed by determining whether the same terminal ID and password are managed in the terminal authentication management table.
In order to manage the operation state of the request source terminal that has requested the login, the state management unit 53 stores the terminal ID of the request source terminal, the operation state of the request source terminal, and the management system 50 in the terminal management table (see FIG. 12). The reception date and time when the login request information is received and the IP address of the request source terminal are stored and managed in association with each other. Therefore, the state management unit 53 realizes the state setting unit 53a, the state acquisition unit 53b, and the state change unit 53c shown in FIG. 6 according to a command from the CPU 201 shown in FIG. FIG. 6 is a functional block diagram showing the state management unit 53 of FIG. 5 in detail.
Among these, the state setting unit 53a is based on the state information that the user of the terminal 10 turns on the power supplied from the terminal by turning on the power switch 109 of the terminal 10 from the OFF state. The operation state indicating the OFF line of the operation state in the terminal management table (see FIG. 12) is set to the ON line. In addition, when the user turns off the power switch 109 of the terminal 10 from the ON state, the terminal management table (see FIG. 12) of the terminal management table (see FIG. 12) is based on the state information indicating that the power sent from the terminal is turned off. The operation state indicating the ON line is set to the OFF line.
When the change request information transmitted by the request source terminal or the destination terminal is received by the transmission / reception unit 51, the status acquisition unit 53b displays the status information of at least one of the request source terminal and the destination terminal in the terminal management table (see FIG. 12). Get from.
Based on the change request information received by the transmission / reception unit 51, the state change unit 53c displays either or both of the request source terminal state information and the destination terminal state information managed by the terminal management table (see FIG. 12). change.
The terminal extraction unit 54 searches the destination list management table (see FIG. 13) using the terminal ID of the request source terminal that requested the login as a search key, and sets the terminal IDs of candidate destination terminals that can talk to the request source terminal. By reading, the terminal ID is extracted. Also, the terminal extraction unit 54 searches the destination list management table using the terminal ID of the request source terminal that has requested login as a key, and requests other requests that register the terminal ID of the request source terminal as candidates for the destination terminal. The terminal ID of the original terminal is also extracted.
Further, the terminal extraction unit 54 searches the destination list management table (see FIG. 13) using the terminal ID of the request source terminal and the terminal ID of the destination terminal extracted by the session management unit 57 as search keys, and sets the request source terminal. The terminal ID is extracted by reading the corresponding destination terminal and the terminal ID of the destination terminal corresponding to the destination terminal.
The terminal status acquisition unit 55 searches the terminal management table (see FIG. 12) using the terminal ID of the destination terminal candidate extracted by the terminal extraction unit 54 as a search key, and the terminal extracted by the terminal extraction unit 54 Read the operating status for each ID. Thereby, the terminal state acquisition unit 55 can acquire the operating state of the candidate destination terminal that can make a call with the request source terminal that has requested the login. In addition, the terminal state acquisition unit 55 searches the terminal management table using the terminal ID extracted by the terminal extraction unit 54 as a search key, and also acquires the operating state of the request source terminal that requested the login.
The relay device selection unit 56 performs processing for selecting one relay device 30 from the plurality of relay devices 30. Therefore, the relay device selection unit 56 implements the session ID generation unit 56a, the relay device extraction unit 56b, and the selection unit 56c shown in FIG. 7 according to a command from the CPU 201 shown in FIG. FIG. 7 is a functional block diagram showing the relay device selection unit 56 of FIG. 5 in detail.
Among these, the session ID generation unit 56a generates a session ID for identifying a session in which content data is transmitted between terminals. The relay device extraction unit 56b determines the relay device selection management table (see FIG. 16) 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. Is retrieved, the corresponding relay device ID is extracted. The selection unit 56c selects the relay device ID of the relay device 30 whose operation state is “ON line” from among the relay devices 30 managed in the relay device management table (see FIG. 10), thereby relaying. The device 30 is selected.
The session management unit 57 associates 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 with the session management table (see FIG. 14) of the nonvolatile storage unit 5000. Remember and manage. The session management unit 57 stores and manages the relay device ID of the relay device 30 that is finally selected for each session ID in the session management table. Further, the session management unit 57 searches the session management table (see FIG. 14) using the session ID included in the participation request information as a search key, and extracts the terminal ID of the corresponding request source terminal and the terminal ID of the destination terminal. .
The quality determining unit 58 searches the quality management table (see FIG. 15) using the delay time as a search key, and extracts the image quality of the corresponding image data, thereby determining the image quality of the image data to be relayed to the relay device 30. To do. The storage / reading processing unit 59 is executed by the HDD 205 illustrated in FIG. 3, and stores various data in the nonvolatile storage unit 5000 or reads various data stored in the nonvolatile storage unit 5000. Further, the storage / reading processing unit 59 stores various data in the volatile storage unit 5100 and reads out various data stored in the volatile storage unit 5100.
The delay time management unit 60 extracts a corresponding terminal ID by searching the terminal management table (see FIG. 12) using the IP address of the destination terminal as a search key, and further acquires a session management table (see FIG. 14). The delay time indicated by the delay information is stored and managed in the delay time field portion of the record including the extracted terminal ID.
The destination determination unit 62 determines whether or not the destination terminal ID of the terminal 10 requesting participation is included in the destination terminal ID of the terminal 10 participating in the content data session sed extracted by the terminal extraction unit 54. to decide.
When the distance between the request source terminal managed in the destination list management table (see FIG. 13) and the destination terminal associated with the request source terminal is assumed to be a predetermined distance, the calculation unit 63 The distance of the shortest path of the terminal having the longest distance among the terminals participating in the content data session sed is calculated.
The above is the description of the configuration and function (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 is described with reference to FIGS. 19 to 35. . FIG. 19 is a sequence diagram illustrating processing for managing state information indicating the operating state of each relay device. FIG. 20 is a conceptual diagram showing a state of transmission / reception of image data, audio data, and various management information in the transmission system. FIG. 21 is a sequence diagram showing processing in a preparation stage for starting a call between terminals. FIG. 22 is a conceptual diagram showing a destination list of the present embodiment. FIG. 23 is a sequence diagram illustrating processing for requesting the start of communication. FIG. 24 is a process flowchart showing a process for changing the communication state. FIG. 25 is a sequence diagram illustrating processing for permitting a request to start communication. FIG. 26 is a sequence diagram illustrating processing for requesting relay of content data. FIG. 27 is a process flowchart showing a process for changing the communication state. FIG. 28 is a sequence diagram showing processing for transmitting / receiving content data between terminals. FIG. 29 is a sequence diagram showing processing for requesting participation in a content data session. FIG. 30 is a processing flowchart showing participation determination processing using a destination list. FIG. 31 is a conceptual diagram showing the distance between terminals. FIG. 32 is a process flowchart showing a process for changing the communication state. FIG. 33 is a sequence diagram showing processing for requesting exit from the content data session. FIG. 34 is a conceptual diagram showing a destination list according to another embodiment. FIG. 35 is a state transition diagram showing the transition of the communication state.
First, a process for managing 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. First, in each relay device 30, the state detection unit 32 shown in FIG. 5 periodically detects the operating state of the relay device 30 as its own device (steps S1-1 to S1-4). Then, the transmission / reception unit 31 of each relay device 30 periodically transmits each state information to the management system 50 via the communication network 2 so that the operation state of each relay device 30 is managed in real time on the management system 50 side. (Steps S2-1 to S2-4). Each state information includes the relay device ID for each relay device 30 and the 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) operate normally and are “ON line”, while the relay device 30c is in operation, but the relay operation of the relay device 30c. The case where some trouble has occurred in the program for executing the “OFF line” is shown.
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 (FIG. 5) of the nonvolatile storage unit 5000 via the storage / read processing unit 59. 10), state information is stored and managed for each relay device ID (steps S3-1 to S3-4). As a result, the operating status of “ON line”, “OFF line”, or “failing” is stored and managed for each relay device ID in the relay device management table as shown in FIG. The At this time, the reception date and time when the status information is received by the management system 50 is also stored and managed for each relay device ID. If the status information is not sent from the relay device 30, the field portion of the operation state and the field portion of the reception date and time in each record of the relay device management table shown in FIG. The operation status and the reception date and time at the previous reception are shown.
Next, with reference to FIG. 20, the concept indicating the transmission / reception state of content data and various management information in the transmission system 1 will be described. As shown in FIG. 20, in the transmission system 1, management information for transmitting / receiving various types of management information between the request source terminal, the destination terminal A, and the destination terminal B via the management system 50. Session sei is established. Further, between the request source terminal, the destination terminal A, and the destination terminal B, each of the four types of high resolution image data, medium resolution image data, low resolution image data, and audio data is transmitted via the relay device 30. Four sessions are established for sending and receiving data. Here, these four sessions are collectively shown as a content data session sed.
Next, the transmission / reception process of each management information in the preparation stage before the terminal 10aa starts a call will be described with reference to FIG. Note that FIG. 21 illustrates a process in which various types of management information are transmitted and received through the management information session sei.
First, when the user of the terminal 10aa turns on the power switch 109 shown in FIG. 2, the operation input accepting unit 12 shown in FIG. 5 accepts the power ON and turns on the power (step) S21). The login request unit 13 automatically transmits login request information indicating a login request from the transmission / reception unit 11 to the management system 50 via the communication network 2 in response to the reception of the power ON (step S22). This login request information includes a terminal ID and a password for identifying the terminal 10aa which is the own terminal as a request source. These terminal ID and password are data read from the non-volatile storage unit 1000 via the storage / read processing unit 19 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 that is the receiving side can grasp the IP address of the terminal 10aa that is the transmitting 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 the terminal authentication management table (see FIG. 11) and terminal authentication is performed by determining whether the same terminal ID and password are managed in the terminal authentication management DB 5002 (step S23).
Since the same terminal ID and password are managed by the terminal authentication unit 52, if it is determined that the login request is from the terminal 10 having a valid usage right, the state management unit 53 In the table (see FIG. 12), the reception date and time when the login request information is received and the IP address of the terminal 10aa are stored in association with each record indicated by the terminal ID and the destination name of the terminal 10aa (step S24-1). ). Accordingly, the terminal management table shown in FIG. 12 includes the terminal ID “01aa”, the reception date and time “2009.11.10.10:40” and the terminal IP address “1.2.1.3”. It will be managed in association.
Subsequently, the state setting unit 53a of the state management unit 53 sets the operation state “ON line” and the communication state “None” of the terminal 10aa, and the terminal ID and destination of the terminal 10aa are set in the terminal management table (see FIG. 12). For each record indicated by the name, the operating state and the communication state are associated and stored (step S24-2). As a result, the terminal management table shown in FIG. 12 manages the terminal ID “01aa” in association with the operation state “ON line” and the communication state “None”.
When the terminal 10aa receives the authentication result information indicating the result determined to be a terminal having a valid use authority, the transmission / reception unit 11 requests the management system 50 via the communication network 2 for a destination list. Is sent to the destination list request information (step S26). Thereby, 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. 13) using the terminal ID “01aa” of the request source terminal (terminal 10aa) that requested the login as a search key, and requests the request source terminal (terminal 10aa). It extracts by reading the terminal IDs of candidate destination terminals that can make a call (step S27). The terminal extraction unit 54 searches the terminal management table (see FIG. 12) using the extracted terminal ID as a search key, and extracts the destination name corresponding to the terminal ID by reading it. Here, the terminal IDs (“01ab”, “01ba”, “01db”) of the destination terminals (terminals (10ab, 10ba, 10db)) corresponding to the terminal ID “01aa” of the request source terminal (terminal 10aa) and Terminal names corresponding to these ("Japan Tokyo Office AB Terminal", "Japan Osaka Office BA Terminal", "America Washington Office DB Terminal") are extracted.
Next, the transmission / reception unit 51 of the management system 50 receives data of the destination list frame (data of the destination list frame 1100-1 part shown in FIG. 22) from the nonvolatile storage unit 5000 via the storage / read processing unit 59. (Step S28), and “destination list information (destination list frame, terminal ID, destination name)” including the destination list frame and the terminal ID and destination name extracted by the terminal extraction unit 54, the request source It transmits to the terminal (terminal 10aa) (step S29). Thereby, in the request source terminal (terminal 10aa), the transmission / reception unit 11 receives the destination list information, and the storage / reading processing unit 19 stores the destination list information in the volatile storage unit 1100 (step S30).
Further, the terminal status acquisition unit 55 of the management system 50 uses the terminal IDs of the destination terminal candidates (“01ab”, “01ba”, “01db”) extracted by the terminal extraction unit 54 as a search key, as a terminal management table. (See FIG. 12), and for each terminal ID extracted by the terminal extraction unit 54, the corresponding operating state is read to obtain each operating state of the terminal (10ab, 10ba, 10db) as a destination candidate (Step S31).
Next, the transmission / reception unit 51 includes “terminal state” including the terminal ID “01ab” as the search key used in step S31 and the operation state “OFF line” of the corresponding destination terminal (terminal 10ab). Information "is transmitted to the request source terminal (terminal 10aa) via the communication network 2 (step S32). Similarly, as part of step S32, the transmitting / receiving unit 51 includes “terminal state information” including the terminal ID “01ba” and the operating state “ON line (Calling)” of the corresponding destination terminal (terminal 10ba). The remaining “terminal status information” is also individually transmitted to the request source terminal (terminal 10aa).
Next, the storage / read processing unit 19 of the request source terminal (terminal 10aa) sequentially stores the terminal status information received from the management system 50 in the volatile storage unit 1100 (step S33). Therefore, the request source terminal (terminal 10aa) receives the status information of each of the terminals, so that each of the current times of the terminal 10ab and the like that are candidates for the destination terminal that can talk to the request source terminal (terminal 10aa) is obtained. The operating state can be acquired.
Next, the destination list creation unit 20 of the request source terminal (terminal 10aa) determines the status of the terminal 10 as a destination candidate based on the destination list information stored in the volatile storage unit 1100 and the status information of the terminal. While creating the reflected destination list, the display control unit 16 controls the timing for displaying the destination list on the display 120 shown in FIG. 2 (step S34).
As described above, as shown in FIG. 22, a destination list in a state where each destination name 1100-2 etc. and icons 1100-3a reflecting each state information are displayed in the destination list frame 1100-1 is displayed. 120aa will be displayed.
On the other hand, returning to FIG. 21, the terminal extraction unit 54 of the management system 50 uses the terminal ID “01aa” of the request source terminal (terminal 10aa) that requested the login as a search key, and uses the destination list management table (see FIG. 13). The terminal ID “01aa” of the request source terminal (terminal 10aa) is searched and the terminal IDs of other request source terminals registered as destination terminal candidates are extracted (step S35). In the destination list management table shown in FIG. 13, the terminal IDs of the other request source terminals to be extracted are “01ab”, “01ba”, and “01db”.
Next, the terminal status acquisition unit 55 of the management system 50 searches the terminal management table (see FIG. 12) using the terminal ID “01aa” of the request source terminal (terminal 10aa) that requested the login as a search key. Then, the operating state of the request source terminal (terminal 10aa) that has requested the login is acquired (step S36).
Then, the transmission / reception unit 51 includes a terminal management table (see FIG. 12) among the terminals (10ab, 10ba, 10db) associated with the terminal IDs (“01ab”, “01ba”, and “01db”) extracted in step S35. ) Includes the terminal ID “01aa” and the operation state “ON line” of the request source terminal (terminal 10aa) acquired in step S36 in the terminals (10ba, 10db) whose operation state is “ON line”. "Terminal status information" is transmitted (steps S37-1, S37-2). When the transmission / reception unit 51 transmits the terminal status information to the terminals (10ba, 10db), the terminal management table shown in FIG. 12 is used based on each terminal ID (“01ba”, “01db”). Refers to the IP address of the managed terminal. As a result, the request source terminal (terminal 10aa) that requested the login is sent to each of the other destination terminals (terminals (10db, 10ba)) that can communicate with the request source terminal (terminal 10aa) that requested the login. ) Terminal ID “01aa” and the operation state “ON line”.
On the other hand, in the other terminals 10 as well, when the user turns on the power switch 109 shown in FIG. 3, the operation input receiving unit 12 shown in FIG. Since the same processes as those in steps S22 to S38-1 and S38-2 are performed, the description thereof is omitted.
Next, processing when a terminal requests the start of communication with another terminal will be described with reference to FIG. Note that FIG. 23 illustrates a process in which various types of management information are transmitted and received through the management information session sei. Further, in the present embodiment, the request source terminal (terminal 10aa) determines that the operating state is ON line and the communication state is None based on the terminal state information received in step S32 among the terminals 10 as destination candidates. It is possible to make a call with at least one of the terminals (10aa, 10bb, 10cb, 10db). Therefore, hereinafter, a case where the user of the request source terminal (terminal 10aa) has selected to start a call with the destination terminal (terminal 10db) will be described.
First, when the user of the request source terminal (terminal 10aa) presses the operation button 108 shown in FIG. 2 and selects the destination terminal (terminal 10db), the operation input receiving unit 12 shown in FIG. Accepts a request to start a call with the terminal 10db (step S41). Then, the transmission / reception unit 11 of the terminal 10aa changes the request ID (01aa) of the request source terminal (terminal 10aa), the terminal ID “01db” of the destination terminal (terminal 10db), and change request information indicating that a call start is requested. The start request information including “Invite” is transmitted to the management system 50 (step S42). Thereby, 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. .
Then, based on the terminal ID “01aa” of the request source terminal (terminal 10aa) and the terminal ID “01db” of the destination terminal (terminal 10db) included in the start request information, the state management unit 53 determines the terminal management DB 5003 (FIG. 12). In the terminal management table of the reference), the field portion of the communication state of the record including the terminal ID “01aa” and the terminal ID “01db” is changed (step S43).
Here, the processing in step S43 will be described in detail with reference to FIG. In the present embodiment, the state management unit 53 changes the communication state of the terminal 10 in accordance with the communication state change rule shown by the state transition diagram of FIG. For example, when the change request information “Accept” is received, if the communication state of the terminal 10 is “Ringing” or “Calling”, the communication state is changed to “Accepted”, and the communication state of the terminal 10 is “Accepted”. ", The communication state remains" Accepted ". In the present embodiment, an example in which a state change management table (see FIGS. 17 and 18) is used to realize a state change by the state management unit 53 will be described, but the present invention is not limited to such a form. In this case, it is only necessary to be defined by the management system program so that the state management unit 53 can change the communication state in accordance with the communication state transition rules shown in the state transition diagram of FIG.
First, the state acquisition unit 53b of the state management unit 53 illustrated in FIG. 6 acquires the communication state of the terminal managed by the terminal management DB (step S43-1). In this case, the change request information “Invite” received by the transmission / reception unit 51 is determined in advance by the change request information determination unit 61 as specific change request information. Based on this, the status acquisition unit 53b acquires not only the request source terminal (terminal 10aa) but also the communication status of the destination terminal (terminal 10db). In this case, the status acquisition unit 53b searches the terminal management table (see FIG. 12) using the terminal ID “01aa” of the request source terminal (terminal 10aa) as a search key, and makes a request to start a call. The communication state “None” of (terminal 10aa) is acquired. Similarly, the communication state “None” of the destination terminal (terminal 10db) is acquired.
Next, the state change unit 53c of the state management unit 53 acquires the pre-change state information of the request source terminal and the destination terminal corresponding to the change request information “Invite” (step S43-2). In this case, the state change unit 53c searches the state change management table (see FIG. 18) using the change request information “Invite” and the terminal information “request source” as search keys, and the state information “None before change” of the request source terminal. Is obtained. Similarly, the state change unit 53c searches the state change management table (see FIG. 18) using the change request information “Invite” and the terminal information “destination” as search keys, and the state information “None” before the change of the destination terminal. To get.
Next, the state change unit 53c compares the communication state acquired by the state acquisition unit 53b with the pre-change state information acquired by the state change unit 53c, and determines whether or not they are the same ( Step S43-3). In this case, the state change unit 53c includes the communication state “None” of the request source terminal (terminal 10aa) acquired by the state acquisition unit 53b and the pre-change state information “None” of the request source end acquired by the state change unit 53c. To determine whether or not they are the same. Similarly, the state change unit 53c compares each of the communication states of the destination terminal (terminal 10db) acquired by the state acquisition unit 53b with the pre-change state information of the destination terminal acquired by the state change unit 53c, It is determined whether or not they are the same.
If it is determined in step S43-3 that the communication state of the request source terminal is the same as the state information before change, and the communication state of the destination terminal is the same as the state information before change (step S43). -3), the state change unit 53c acquires the change information of the request source terminal and the destination terminal corresponding to the change request information “Invite” (step S43-4). In this case, the state change unit 53c searches the state change management table (see FIG. 18) using the change request information “Invite” and the terminal information “request source” as search keys, and stores the change information “Calling” of the request source terminal. get. Similarly, the state changing unit 53c searches the state change management table (see FIG. 18) using the request information “Invite” and the terminal information “destination” as search keys, and acquires the destination terminal change information “Ringing”. .
Next, based on the terminal ID “01aa” of the request source terminal (terminal 10aa) and the terminal ID “01db” of the destination terminal (terminal 10db), the state change unit 53c performs the above in the terminal management table (see FIG. 12). The field portion of the communication state of the record including the terminal ID “01aa” and the terminal ID “01db” is changed (step S43-5). In this case, the field portion of the communication state of the record including the terminal ID “01aa” of the terminal management table is changed to “Calling” based on the acquired change information of the request source terminal. Similarly, the field part of the communication state of the record including the terminal ID “01db” is changed to “Ringing” based on the acquired change information of the destination terminal.
If it is determined in step S43-3 that the communication state of the request source terminal is not the same as the state information before change, or the communication state of the destination terminal is not the same as the state information before change (step S43). −3), the state changing unit 53c does not change the field portion of the communication state of the record including the terminal ID “01aa” and the terminal ID “01db” in the terminal management table (see FIG. 12). This is because either the request source terminal (terminal 10aa) or the destination terminal (terminal 10db) is not in a state in which a call can be started. In this case, the transmission / reception unit 51 creates a predetermined error message and transmits it to the request source terminal (terminal 10aa) to complete the process (step S43-6).
Next, returning to FIG. 23, the subsequent processing will be described for the case where the communication state is changed in step S43-5. First, the session ID generating unit 56a identifies a session (content data session sed) for executing communication with the destination terminal requested by the request source terminal (terminal 10aa). Is generated (step S44). When the session ID is generated, the session management unit 57 stores the session ID “se1” in the volatile storage unit 5100.
Subsequently, the relay device selection unit 56 of the management system 50 selects the relay device 30 for relaying content data in the content data session between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db). Is performed (step S45). In this case, first, the relay device extraction unit 56b receives the terminal ID “01aa” of the request source terminal (terminal 10aa) and the destination terminal (terminal 10db) included in the start communication information transmitted from the request source terminal (10aa). ), The relay device ID (“111a”, “111d”) corresponding to the terminal (10aa, 10db) is extracted by searching the relay device selection management table (see FIG. 16) based on the terminal ID “01db”. To do.
If the extracted relay device IDs are the same, the selection unit 56c operates among the operating states of the relay device 30 managed in the relay device management table (see FIG. 10). Refer to Here, when the operation state of the relay device ID is “ON line”, the selection unit 56c selects the extracted relay device as a relay device for relaying content data. If the extracted relay device IDs are not the same, or if the operation status of the relay device ID is “OFF line” as a result of the above reference, the relay device 30e with the relay device ID “111e” Select as a relay device to relay data. In the present embodiment, the case where the relay device 30e is selected by the selection unit 56c will be described below.
When the selection processing of the relay device 30 is completed, the session management unit 57, in the session management table (see FIG. 14) of the nonvolatile storage unit 5000, the relay device ID and request source terminal ID of the record including the session ID “se1”. And the field ID of the destination terminal ID include the relay device ID “111e” of the selected relay device, the terminal ID “01aa” of the request source terminal (terminal 10aa), and the terminal ID “01db” of the destination terminal (terminal 10db). Store and manage (step S46).
Next, the transmission / reception unit 51 illustrated in FIG. 5 is selected by the selection unit 56c and the session ID generated by the session ID generation unit 56a 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 S47). The relay device connection information can include the IP address “1.1.1.3” of the relay device 30e, authentication information, a port number, and the like. Accordingly, the terminal 10aa can grasp the relay device connection information used for connecting to the relay device 30e used for relaying the content 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 the start of a call with the destination terminal is requested, 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 the destination terminal (terminal 10db) (step S48). Thereby, the transmission / reception unit 51 of the destination terminal (terminal 10db) receives the start request information, and at the transmission device connection information and the transmission source used to connect to the relay device 30e used for relaying the content data. The IP address “1.1.1.2” of a certain management system 50 is grasped.
Subsequently, using FIG. 25 and FIG. 24, the user of the destination terminal (terminal 10db) that has received the start request information presses the operation button 108 shown in FIG. Processing in a case where a response to permit the start of communication with (terminal 10aa) is accepted will be described. First, a response to permit the start of communication with the request source terminal (terminal 10aa) is accepted by the operation button 108 of the destination terminal (terminal 10db) (step S49). Next, the transmission / reception unit 11 of the destination terminal (terminal 10db) permits the terminal ID “01db” of the destination terminal (terminal 10db), the terminal ID “01aa” of the request source terminal (terminal 10aa), and permission to start communication. The start response information including the change request information “Accept” and the session ID “se1” is transmitted to the management system 50 (step S50).
When the transmission / reception unit 51 of the management system 50 receives the start response information, the state management unit 53 is based on 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. 12), the field portion of the communication state of the record including the terminal ID “01aa” and the terminal ID “01db” is changed (step S51).
Here, the processing in step S51 will be described in detail with reference to FIG. First, when the transmission / reception unit 51 of the management system 50 receives this start response information, the state acquisition unit 53b of the state management unit 53 shown in FIG. 6 performs the terminal management table ( The communication status of the terminal managed in (see FIG. 12) is acquired (step S51-1). In this case, the change request information “Accept” received by the transmission / reception unit 51 is determined in advance by the change request information determination unit 61 as specific change request information. Based on this, the state acquisition unit 53b acquires not only the communication state “Ringing” of the destination terminal (terminal 10db) but also the communication state “Calling” of the request source terminal (terminal 10aa).
Subsequently, the state change unit 53c of the state management unit 53 performs a request of the request source terminal corresponding to the change request information “Accept” managed in the state change management table (see FIG. 18) in the same manner as the process of step S43-2. The pre-change state information “Calling” and “Accepted” are acquired. Similarly, the state change unit 53c acquires the pre-change state information “Ringing” of the destination terminal corresponding to the change request information “Accept” managed by the state change management table (see FIG. 18) (step S51-). 2).
Next, the state change unit 53c compares the communication state acquired by the state acquisition unit 53b with the pre-change state information acquired by the state change unit 53c, and determines whether or not they are the same ( Step S51-3). In this case, the state change unit 53c determines that the communication state “Calling” of the request source terminal (terminal 10aa) acquired by the state acquisition unit 53b is the status information “Calling before change” of the request source end acquired by the state change unit 53c. ”And“ Accepted ”. Similarly, the state change unit 53c indicates that the communication state “Ringing” of the destination terminal (terminal 10db) acquired by the state acquisition unit 53b is the state information “Ringing” before change of the destination terminal acquired by the state change unit 53c. It is determined whether or not the same.
If it is determined in step S51-3 that the communication state of the request source terminal is the same as the state information before change and the communication state of the destination terminal is the same as the state information before change (step S51- 3), the state changing unit 53c acquires the change information of the request source terminal and the destination terminal corresponding to the response information “Accept” (step S51-4). In this case, the state change unit 53c uses the response information “Accept”, the terminal information “request source” indicating the request source terminal, and the pre-change state “Calling” indicating the communication status before the change of the request source terminal as search keys. The state change management table (see FIG. 18) is searched, and change information “Accepted” of the request source terminal is acquired. Similarly, the state change unit 53c changes the state using the response information “Accept”, the terminal information “destination” indicating the destination terminal, and the pre-change state “Ringing” indicating the communication state before the change of the destination terminal as search keys. The management table (see FIG. 18) is searched, and change information “Accepted” of the destination terminal is acquired.
Next, the state changing unit 53c determines the terminal management table (see FIG. 12) based on the terminal ID “01aa” of the request source terminal (terminal 10aa) and the terminal ID “01db” of the destination terminal (terminal 10db) included in the start response information. ), The field portion of the communication state of the record including the terminal ID “01aa” and the terminal ID “01db” is changed (step S51-5). In this case, the field portion of the communication state of the record including the terminal ID “01aa” of the terminal management table is changed to “Accepted” based on the acquired change information of the request source terminal. Similarly, the field portion of the communication state of the record including the terminal ID “01db” in the terminal management table is changed to “Accepted” based on the acquired change information of the destination terminal.
In step S51-3, it is determined that the communication state of the request source terminal (10aa) and the state information before change are not the same, or the communication state of the destination terminal (terminal 10db) and the state information before change are not the same. In the case where the terminal ID is “01aa” and the terminal ID “01db” in the terminal management table (see FIG. 12), the state changing unit 53c Do not change the field part. In this case, the transmission / reception unit 51 creates this error message and transmits it to the destination terminal (terminal 10db), thereby completing the process (step S51-6).
Next, returning to FIG. 25, the subsequent processing will be described for the case where the communication state is changed in step S <b> 51-5. The transmission / reception unit 51 includes a start response including a terminal ID “01db” of the destination terminal (terminal 10db), change request information “Accept” indicating that a request to start a call with the destination terminal is permitted, and a session ID “se1”. Information is transmitted to the request source terminal (terminal 10aa) (step S52). When 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 S47 to the relay device 30e by the transmission / reception unit 11, thereby transmitting the relay device. 30e is connected (step S53). On the other hand, the destination terminal (terminal 10db) transmits the session ID “se1” and the relay device connection information acquired in step S48 to the relay device 30e by the transmission / reception unit 11, thereby connecting to the relay device 30e (step S54). ).
Next, a process in which the relay device 30e starts relaying content data transmitted between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db) will be described with reference to FIG. Note that FIG. 26 illustrates a process in which various types of management information are transmitted and received through the management information session sei.
First, the request source terminal (terminal 10aa) is connected to the relay device 30e (see step S53) at a predetermined timing by the transmission / reception unit 11 by the terminal ID “01aa” and the session ID of the request source terminal (terminal 10aa). Relay request information including “se1” and change request information “Join” indicating a request to start relaying is transmitted to the management system 50 (step S71-1).
When the transmission / reception unit 51 of the management system 50 receives the relay request information, the state management unit 53 determines the terminal management table (see FIG. 12) based on the terminal ID “01aa” of the request source terminal (terminal 10aa) included in the relay request information. ), The field portion of the communication state of the record including the terminal ID “01aa” is changed (step S72-1).
Here, the processing in step S72-1 will be described in detail with reference to FIG. First, the state acquisition unit 53b of the state management unit 53 illustrated in FIG. 6 acquires the communication state of the terminal managed by the terminal management DB (step S72-1-1). In this case, the change request information “Join” received by the transmission / reception unit 51 is determined in advance by the change request information determination unit 61 as not being specific change request information. Based on this, the state acquisition unit 53b acquires only the communication state of the request source terminal (terminal 10aa). In this case, the state acquisition unit 53b searches the terminal management table (see FIG. 12) using the terminal ID “01aa” of the request source terminal (terminal 10aa) as a search key, and makes a request to start relaying. The communication state “Accepted” of (terminal 10aa) is acquired.
Next, the state change unit 53c of the state management unit 53 acquires pre-change state information corresponding to the change request information “Join” (step S72-1-2). In this case, the state change unit 53c searches the state change management table (see FIG. 17) using the change request information “Join” as a search key, and acquires the pre-change state information “Accepted”.
Next, the state change unit 53c compares the communication state acquired by the state acquisition unit 53b with the pre-change state information acquired by the state change unit 53c, and determines whether or not they are the same ( Step S72-1-3). In this case, the state change unit 53c compares the communication state “Accepted” of the request source terminal (terminal 10aa) acquired by the state acquisition unit 53b with the pre-change state information “Accepted” acquired by the state change unit 53c. Whether these are the same is determined.
When it is determined in step S72-1-3 that the communication state of the request source terminal is the same as the pre-change state information (YES in step S72-1-3), the state change unit 53c changes the change request information “ Change information corresponding to “Join” is acquired (step S72-1-4). In this case, the state change unit 53c searches the state change management table (see FIG. 17) using the change request information “Join” as a search key, and acquires the change information “Busy”.
Next, based on the terminal ID “01aa” of the request source terminal (terminal 10aa), the state changing unit 53c includes a communication status field of the record including the terminal ID “01aa” in the terminal management table (see FIG. 12). The part is changed (step S72-1-5). In this case, the field portion of the communication state of the record including the terminal ID “01aa” in the terminal management table is changed to “Busy” based on the acquired change information.
If it is determined in step S72-1-3 that the communication state of the request source terminal and the pre-change state information are not the same (NO in step S72-1-3), the state change unit 53c determines the terminal management. In the table (see FIG. 12), the field portion of the communication state of the record including the terminal ID “01aa” is not changed. In this case, the transmission / reception unit 51 completes the process by transmitting this error message to the request source terminal (terminal 10aa) (step S72-1-6).
Next, returning to FIG. 26, the subsequent processing will be described for the case where the communication state is changed in step S72-1-5. First, the management system 50 transmits 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 S73-1). When the relay start request information is received, the relay device 30e transmits relay start permission information including notification information “OK” indicating that the start of relay is permitted to the management system 50 (step S74-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 S75-1). Thereby, the content data session sed between the request source terminal (terminal 10aa) and the relay device 30a is established (step S76-1).
On the other hand, the destination terminal (terminal 10db) is connected to the relay device 30e (see step S54), and the transmission / reception unit 11 causes the terminal ID “01db” and session ID “se1” of the destination terminal (terminal 10db) to be transmitted and received. "And the relay request information including the change request information" Join "indicating that the start of relay is requested is transmitted to the management system 50 (step S71-2).
Subsequently, the management system 50 and the relay device 30e perform the same processing as that of Steps S72-1, S73-1, S74-1, and S75-1, so that the destination terminal (terminal 10db) and the relay device 30a are connected. The content data session sed is established (steps S72-2, S73-2, S74-2, S75-2, S76-2). When the content data session sed between the request source terminal (terminal 10aa) and the relay device 30e and the content data session sed between the destination terminal (terminal 10aa) and the relay device 30e are established, the relay device 30e The three image data of low resolution, medium resolution, and high resolution, and audio data can be relayed between the terminals (10aa, 10db). Accordingly, the terminals (10aa, 10db) can start a video conference.
Next, a process of transmitting and receiving content data to perform a video conference call between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db) will be described with reference to FIGS. In addition, transmission / reception of content data, detection of a delay time described later, and the like are performed by one-way processing for transmitting content data from the terminal 10aa to the terminal 10db and reverse processing for transmitting content data from the terminal 10db to the terminal 10aa. Since the processing is the same, the one-way communication will be described, and the reverse communication will be omitted.
First, the request source terminal (terminal 10aa) communicates the subject image data captured by the imaging unit 14 and the audio data of the audio input by the audio input unit 15a from the transmission / reception unit 11 through the content data session sed. The data is transmitted to the relay device 30e via the network 2 (step S81). In the present embodiment, high-quality image data composed of the low resolution, medium resolution, and high resolution shown in FIG. 20 and audio data are transmitted. Thereby, in the relay device 30e, the transmission / reception unit 31 receives the image data and the audio data of the three resolutions.
Then, the data quality confirmation unit 33 searches the change quality management table (see FIG. 8) using the IP address “1.3.2.4” of the destination terminal (terminal 10db) as a search key, and relays the corresponding image. By extracting the image quality of the data, the image quality of the image data to be relayed is confirmed (step S82). In this embodiment, since the image quality of the confirmed image data is “high quality” and is the same as the image quality of the image data received by the transmission / reception unit 31, the relay device 30a uses the content data session sed. The image data with the same image quality and the sound data with the same sound quality are transferred to the destination terminal (terminal 10db) (step S83). As a result, the destination terminal (terminal 10db) receives the content data at the transmission / reception unit 11, the display control unit 16 displays an image based on the image data on the display 120, and the audio output unit 15b receives the audio based on the audio data. Can be output.
Next, the transmission / reception unit 51 uses the relay device management table (see FIG. 10) using the relay device ID “111e” associated with the terminal ID “01db” in the session management table (see FIG. 14) as a search key. The IP address “1.1.1.3” of the corresponding relay device 30e is extracted by searching (step S88).
Then, the transmission / reception unit 51 transmits the quality information indicating the image quality “medium image quality” of the image data determined in step S87 to the relay device 30e via the communication network 2 through the management information session sei (step S89). ). This quality information includes the IP address “1.3.2.4” of the destination terminal (terminal 10db) used as the search key in step S86. As a result, in the relay device 30e, the change quality management unit 34 stores the IP address “1.3. In the destination terminal 10 (here, the destination terminal (terminal 10db)) in the change quality management table (see FIG. 8). 2.4 ”and the image quality“ medium image quality ”of the image data to be relayed are stored and managed in association with each other (step S90).
Next, similarly to step S81, the terminal 10aa continues to the relay device 30e through the content data session sed, and the high-quality image data including the low image quality, the medium image quality, and the high image quality, and the audio. Data is transmitted (step S91). As a result, in the relay device 30e, as in step S82, the data quality confirmation unit 33 uses the IP address “1.3.2.4” of the destination terminal (terminal 10db) as a search key to change the quality management table ( 8) and the image quality “medium image quality” of the corresponding image data to be relayed is extracted to check the image quality of the image data to be relayed (step S92).
In this embodiment, since the image quality of the confirmed image data is “medium image quality” and lower than the image quality “high image quality” of the image data received by the transmission / reception unit 31, the data quality changing unit 35 The image quality of the image data is changed by suppressing the image quality from “high image quality” to “medium image quality” (step S93). The transmission / reception unit 31 does not change the image data in which the image quality of the image data is changed to “medium image quality” and the sound quality of the sound to the terminal 10db via the communication network 2 by the content data session sed. Audio data is transmitted (step S94). As described above, when a reception delay occurs at the destination terminal (terminal 10db) that receives the image data, the relay device 30e changes the image quality and gives a strange feeling to the person participating in the video conference. Can not be.
Subsequently, with reference to FIG. 29, after the content data session is established between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db), the terminal 10cb participates in the content data session. explain. Note that FIG. 29 illustrates a process in which various types of management information are transmitted and received through the management information session sei.
First, when the user of the request source terminal (terminal 10aa) presses the operation button 108 shown in FIG. 2, the terminal 10cb notifies the terminal 10cb of the session ID so as to participate in the content data session sed. Information indicating that this is requested is accepted (step S101). Next, the transmission / reception unit 11 of the request source terminal (terminal 10aa) includes the terminal ID “01aa” of the request source terminal (terminal 10aa), the terminal ID “01cb” of the terminal 10cb, and the session ID “se1”. ID notification request information (an example of session information) is transmitted to the management system 50 (step S102). When the management system 50 receives the session ID notification request information, the transmission / reception unit 51 transmits the session ID notification information including the terminal ID “01aa” and the session ID “se1” of the request source terminal (terminal 10aa) to the terminal 10cb. (Step S103).
Upon receiving the session ID notification information, the terminal 10cb accepts a request to participate in the content data session sed (step S104). Here, when the user of the terminal 10cb presses the operation button 108 shown in FIG. 2, a request for participation in this content data session is accepted. Thereby, the transmission / reception unit 11 of the participation requesting terminal (terminal 10cb) requesting participation changes the terminal ID “01cb” of the participation requesting terminal (terminal 10cb) and a change request indicating requesting to participate in the content data session. Session participation request information including the information “Call” and the session ID “se1” is transmitted to the management system 50 (step S105).
Upon receiving the session participation request information, the management system 50 uses the destination list management table (FIG. 13) to participate in the participation request terminal (terminal 10cb) and the participating terminals participating in the content data session sed (terminal 10aa, 10db), it is determined whether or not to continue the process for connecting (step S106). Here, the processing in step S106 will be described in detail with reference to FIG. FIG. 30 is a processing flowchart showing participation determination processing using a destination list.
First, the session management unit 57 searches the session management table (see FIG. 14) using the session ID “se1” included in the participation request information as a search key, and the terminal ID of the corresponding request source terminal and the terminal ID of the destination terminal. Is extracted (step S106-1). Thereby, the session management unit 57 acquires the terminal IDs “01aa, 01db” of the participating terminals participating in the content data session sed identified by the session ID “se1”.
Subsequently, the terminal extraction unit 54 searches the destination list management table (see FIG. 13) using each of the terminal IDs “01aa, 01db” of the participating terminals extracted by the session management unit 57 as search keys, and the corresponding destinations. A terminal ID is extracted (step S106-2). Thereby, the terminal extraction unit 54 identifies the terminal ID “01ab, 01ba, 01db” that identifies the destination terminal corresponding to the participating terminal (terminal 10aa) and the terminal ID that identifies the destination terminal corresponding to the participating terminal (terminal 10db). “01aa, 01cb, 01da” is acquired.
Next, the destination determination unit 62 includes the destination terminal ID for identifying the participation request terminal in the destination terminal ID of the destination terminal corresponding to the participation terminal extracted by the terminal extraction unit 54 in step S106-2. It is determined whether or not there is (step S106-3). As a result, the destination determination unit 62 uses the extracted destination terminal IDs “(01ab, 01ba, 01db), (01aa, 01cb, 01da)” to identify the participation request terminal (terminal 10cb). "01cb" is included (YES in step S106-3).
If the destination terminal ID of the destination terminal corresponding to the participating terminal does not include the destination terminal ID for identifying the participation requesting terminal (NO in step S106-3), the destination determining unit 62 creates an error message. To the participation request terminal (step S106-4). In this case, the management system 50 completes the process without continuing the process for connecting the participation requesting terminal and the participating terminal.
Subsequently, when it is determined in step S106 that the extracted destination terminal ID includes the destination terminal ID for identifying the terminal 10cb, the subsequent processing will be described. First, when the distance between the request source terminal managed in the destination list management table (see FIG. 13) and the destination terminal associated with the request source terminal is assumed to be a predetermined distance, the calculation unit 63 requests participation. The distance of the shortest path between the terminal and the terminal having the largest shortest path distance among the participating terminals is calculated (step S106-5).
Here, the distance calculation method will be described in detail with reference to FIG. In the present embodiment, when the participation request terminal (terminal 10cb) is managed as the destination terminal of the participating terminal in the destination list management table (see FIG. 13), the participation requesting terminal and the terminals participating in the session Is set to “1” (see FIG. 31A).
Here, in the destination list management table (see FIG. 13), the terminal ID “01cb” of the participation requesting terminal (terminal 10cb) is registered as the destination terminal ID associated with the terminal ID “01db” of the participating terminal (terminal 10db). Has been. Therefore, the distance between the participation requesting terminal (terminal 10cb) and the participating terminal (terminal 10db) is “1”.
On the other hand, in the destination list management table (see FIG. 13), the terminal ID “01cb” of the participation request terminal (terminal 10cb) is registered as the destination terminal ID associated with the terminal ID “01aa” of the participating terminal (terminal 10aa). Not. For this reason, the distance between the participation requesting terminal (terminal 10cb) and the participating terminal (terminal 10aa) is larger than “1”.
For a terminal where the distance between the participating terminal and the participation requesting terminal is greater than “1”, the distance is calculated according to the following procedure. In the destination list management table (see FIG. 13), when the participating terminal (terminal 10db) whose distance from the participation requesting terminal is “1” is managed as the destination terminal of the other participating terminals, The distance from the participating terminal is “2” (see FIG. 31A).
Here, in the destination list management table (see FIG. 13), the terminal ID “01db” of the terminal (terminal 10db) whose distance from the participation requesting terminal is “1” is the terminal ID “01” of the other participating terminals (terminal 10aa). Is registered as a destination terminal ID associated with “01aa”. For this reason, the distance between the participation requesting terminal (terminal 10cb) and another participating terminal (terminal 10aa) is “2”. Note that the distance is calculated by the same procedure for a terminal whose distance from the participation requesting terminal is larger than “2”.
In this way, the calculation unit 63 calculates the distance of the shortest path between the participation request terminal (terminal 10cb) and the participating terminal (terminal 10aa) having the largest shortest path distance among the participating terminals (terminals (10aa, 10db)). “2” is calculated (step S106-5). The processing of the calculation unit 63 is executed by a command of the CPU 201 based on, for example, a management system program incorporating an algorithm for solving the shortest path problem in Dijkstra graph theory.
When the calculation of the distance of the shortest path is completed, the destination determination unit 62 determines whether or not the calculated distance is smaller than a predetermined threshold (for example, “3”) (step S106-6). The predetermined threshold value is stored in advance in a predetermined storage area of the nonvolatile storage unit 5000 and can be read out by the storage / read processing unit 59. When it is determined that the distance is smaller than the predetermined threshold (YES in step S106-6), the storage / reading processing unit 59 determines the terminal ID “01cb” of the participation requesting terminal (terminal 10cb), the session requesting participation. The session ID “se1” and the shortest path distance “2” are stored in a predetermined storage area of the volatile storage unit 5100 (step S106-7). In this case, the management system 50 determines to continue the process for connecting the participation requesting terminal and the participating terminal, and executes the processes after step S107.
When it is determined that the distance is not smaller than the predetermined threshold (NO in step S106-6), the transmission / reception unit 51 creates an error message and transmits the error message to the terminal 10 requesting participation (step S106-8). . In this case, the management system 50 completes the process without continuing the process for connecting the participation requesting terminal and the participating terminal.
Subsequently, returning to FIG. 29, when it is determined that the process for connecting the participation requesting terminal (terminal 10 cb) and the participating terminal (terminal (10aa, 10db)) is continued, the subsequent processing Will be explained. First, the state management unit 53 of the management system 50 uses the terminal ID “01cb” in the terminal management table (see FIG. 12) based on the terminal ID “01cb” of the participation request terminal (terminal 10cb) included in the session participation request information. "Is changed in the communication state field part of the record including" "(step S107).
Here, the processing in step S107 will be described in detail with reference to FIG. First, the state acquisition unit 53b of the state management unit 53 illustrated in FIG. 6 acquires the communication state of the terminal managed by the terminal management DB (step S107-1). In this case, the change request information “Call” received by the transmission / reception unit 51 is determined in advance by the change request information determination unit 61 as not being specific change request information. Based on this, the state acquisition unit 53b acquires only the communication state of the participation request terminal (terminal 10cb). In this case, the state acquisition unit 53b searches the terminal management table (see FIG. 12) using the terminal ID “01cb” of the participation request terminal (terminal 10cb) as a search key, and the communication state “of the participation request terminal (terminal 10cb)”. “None” is acquired.
Next, the state change unit 53c of the state management unit 53 acquires the pre-change state information of the destination terminal corresponding to the change request information “Call” (step S107-2). In this case, the state change unit 53c searches the state change management table (see FIG. 17) using the change request information “Call” as a search key, and acquires the pre-change state information “None”.
Next, the state change unit 53c compares the communication state acquired by the state acquisition unit 53b with the pre-change state information acquired by the state change unit 53c, and determines whether or not they are the same ( Step S107-3). In this case, the state change unit 53c compares the communication state “None” of the participation request terminal (terminal 10cb) acquired by the state acquisition unit 53b with the pre-change state information “None” acquired by the state change unit 53c. Whether these are the same is determined.
When it is determined in step S107-3 that the communication state of the destination terminal is the same as the state information before change (YES in step S107-3), the state change unit 53c corresponds to the change request information “Call”. Change information is acquired (step S107-4). In this case, the state change unit 53c searches the state change management table (see FIG. 17) using the change request information “Call” as a search key, and acquires the change information “Accepted”.
Next, based on the terminal ID “01cb” of the participation requesting terminal (terminal 10cb), the state changing unit 53c includes a communication state field of the record including the terminal ID “01cb” in the terminal management table (see FIG. 12). The part is changed (step S107-5). In this case, the field portion of the communication state of the record including the terminal ID “01cb” in the terminal management table is changed to “Accepted” based on the acquired change information.
If it is determined in step S107-3 that the communication status of the terminal requesting participation is not the same as the pre-change status information (NO in step S107-3), the status change unit 53c uses the terminal management table ( In FIG. 12), the field portion of the communication state of the record including the terminal ID “01cb” is not changed. In this case, the transmission / reception unit 51 completes the processing by transmitting this error message to the participation request terminal (terminal 10cb) (step S107-6).
Next, returning to FIG. 29, the subsequent processing will be described for the case where the communication state is changed in step S107-5. First, in the session management table (see FIG. 14) of the nonvolatile storage unit 5000, the session management unit 57 adds the terminal ID of the participation request terminal (terminal 10cb) to the field portion of the destination terminal of the record including the session ID “se1”. “01cb” is added (step S108).
Next, when participating in the content data session sed, the transmission / reception unit 51 of the management system 50 sends a participation permission notification including the session ID “se1” and the relay device connection information used to connect to the relay device 30e. Then, it transmits to the participation request terminal (terminal 10cb) (step S109). In addition, the transmission / reception part 51 may transmit the distance (an example of distance information) of the shortest path | route memorize | stored in the predetermined storage area by step S106-7 with participation permission notification. Thereby, the participation request terminal (terminal 10cb) can grasp the risk of participating in the session based on the distance from the participating terminal.
When the terminal 10cb receives the participation permission notification, the terminal 10cb connects 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 S10). S110). Further, the participating terminal (terminal 10cb) requests the terminal ID “01cb”, the session ID “se1” of the terminal 10cb, and the start of relay by the transmission / reception unit 11 at a predetermined timing after connecting to the relay device 30e. Relay request information including change request information “Join” indicating that is transmitted to the management system 50. Subsequently, content data between the terminal 10cb and the relay device 30e is executed by the management system 50 and the relay device 30e executing processes similar to those in steps S72-1, S73-1, S74-1, and S75-1. Session sed is established. When the content data session sed is established, the relay device 30e relays three image data and audio data of low resolution, medium resolution, and high resolution between the terminals (10aa, 10cb, 10db). can do. Accordingly, the terminals (10aa, 10cb, 10db) can start a video conference.
In addition, the transmission / reception unit 51 of the management system 50 notifies the participation notification including the terminal ID “01cb” and the session ID “se1” of the participation request terminal (terminal 10cb), and has already started the content data session sed. It transmits to the terminal (terminal 10aa, terminal 10db) (steps S111-1, S111-2). Thereby, the participating terminals (terminal (10aa, terminal 10db)) can grasp that the participation requesting terminal (terminal 10cb) participates in the content data session.
Further, the terminal extraction unit 54 searches the destination list management table (see FIG. 13) using the terminal ID of the participation request terminal (terminal 10cb) included in the session participation request information as a search key, and the destination corresponding to the participation request terminal. By reading out the terminal ID of the terminal, the terminal ID “01aa, 01bb, 01db” is extracted (step S112). The transmission / reception unit 51 of the management system 50 includes a participation notification in which the terminal ID “01cb” is included in the terminal 10bb that has not transmitted the participation notification among the terminals (10aa, 10bb, 10db) identified by the extracted terminal ID. (An example of participation information) is transmitted (step S113). Accordingly, the terminal 10bb can grasp that the participation request terminal (terminal 10cb) participates in the content data session.
Subsequently, a process in which the terminal 10aa exits from the content data session after the content data session is established with the terminals (10aa, 10cb, 10db) will be described with reference to FIG. Note that FIG. 26 illustrates a process in which various types of management information are transmitted and received through the management information session sei.
First, when the user of the terminal 10aa presses the operation button 108 shown in FIG. 2, a request to exit from the content data session is accepted (step S121). The transmission / reception unit 11 of the terminal 10aa includes the session exit request information including the terminal ID “01aa” of the terminal 10aa, the change request information “Leave” indicating a request to exit from the content data session, and the session ID “se1”. Is transmitted to the management system 50 (step S122).
Upon receiving this session exit request information, the state management unit 53 of the management system 50 uses the terminal ID in the terminal management table (see FIG. 12) based on the terminal ID “01aa” of the terminal 10aa included in the session exit request information. The field portion of the communication state of the record including “01aa” is changed (step S123).
Here, the processing in step S123 will be described in detail with reference to FIG. First, the state acquisition unit 53b of the state management unit 53 illustrated in FIG. 6 acquires the communication state of the terminal managed by the terminal management DB (step S123-1). In this case, the change request information “Leave” received by the transmission / reception unit 51 is determined in advance by the change request information determination unit 61 as not being specific change request information. Based on this, the state acquisition unit 53b acquires only the communication state of the terminal 10aa. In this case, the state acquisition unit 53b searches the terminal management table (see FIG. 12) using the terminal ID “01aa” of the terminal 10aa as a search key, and acquires the communication state “Busy” of the terminal 10aa.
Next, the state change unit 53c of the state management unit 53 acquires the pre-change state information corresponding to the change request information “Leave” (step S123-2). In this case, the state change unit 53c searches the state change management table (see FIG. 17) using the change request information “Leave” as a search key, and acquires the pre-change state information “Busy”.
Next, the state change unit 53c compares the communication state acquired by the state acquisition unit 53b with the pre-change state information acquired by the state change unit 53c, and determines whether or not they are the same ( Step S123-3). In this case, the state change unit 53c compares the communication state “Busy” of the terminal 10aa acquired by the state acquisition unit 53b with the pre-change state information “Busy” acquired by the state change unit 53c. Judge whether there is.
When it is determined in step S123-3 that the communication state of the terminal and the state information before change are the same (YES in step S123-3), the state change unit 53c changes the change request information “Leave”. Information is acquired (step S123-4). In this case, the state change unit 53c searches the state change management table (see FIG. 17) using the change request information “Leave” as a search key, and acquires the change information “None”.
Next, based on the terminal ID “01aa” of the request source terminal (terminal 10aa), the state changing unit 53c includes a communication status field of the record including the terminal ID “01aa” in the terminal management table (see FIG. 12). The part is changed (step S123-5). In this case, the field portion of the communication state of the record including the terminal ID “01aa” in the terminal management table is changed to “None” based on the acquired change information.
When it is determined in step S123-3 that the communication state of the request source terminal is not the same as the pre-change state information (NO in step S113-3), the state change unit 53c displays the terminal management table (FIG. 12). In the reference), the field portion of the communication state of the record including the terminal ID “01aa” is not changed. In this case, the process is completed by transmitting an error message to the request source terminal (terminal 10aa) (step S123-6).
Next, returning to FIG. 33, the subsequent processing will be described for the case where the communication state is changed in step S123-5. First, the session management unit 57 obtains the terminal ID “01aa” of the terminal 10aa from the field part of the request source terminal of the record including the session ID “se1” in the session management table (see FIG. 14) of the nonvolatile storage unit 5000. Delete (step S124). The management system 50 transmits to the relay device 30e a notification to request exit of the session including the terminal ID “01aa” of the terminal 10aa and the session ID “se1” (step S125). Accordingly, the relay device 30e stops the content data session with the terminal 10aa and disconnects the connection with the terminal 10aa. Subsequently, the relay device 30e transmits to the management system 50 a notification that the request for leaving including the terminal ID “01aa” and the session ID “se1” of the terminal 10aa is permitted (step S126).
When the management system 50 receives a notification that the exit request is permitted, the transmission / reception unit 51 permits the terminal ID “01aa”, the change request information “Leave”, the session ID “se1”, and the exit request of the terminal 10aa. Session exit permission information including notification information “OK” to that effect is transmitted to the terminal 10aa (step S127). When the session exit permission information is received, the terminal 10aa accepts a power-off request by pressing the power switch 109 shown in FIG. 2 (step S128). When a request to turn off the power is received, the transmission / reception unit 11 transmits to the management system 50 disconnection request information including notification information for disconnecting the connection between the terminal ID “01aa” of the terminal 10aa and the management system 50 ( Step S129).
When the transmission / reception unit 51 of the management system 50 receives this disconnection request information, the state management unit 53 determines the above in the terminal management table (see FIG. 12) based on the terminal ID “01aa” of the terminal 10aa included in the disconnection request information. The record in the field portion of the communication state of the record including the terminal ID “01aa” is deleted (step S130). Subsequently, the transmission / reception unit 51 transmits disconnection permission information indicating that the disconnection request is permitted to the terminal 10aa (step S131). As a result, the management system 50 stops the management data session with the terminal 10aa and disconnects the connection with the terminal 10aa.
When the cutting permission information is received, the terminal 10aa turns off the power and completes the process (step S132). The terminal 10cb and the terminal 10db can also exit the content data session sed and complete the call between the terminals in the same manner as the processing in steps S121 to S131 of the terminal 10aa.
As described above, according to the present embodiment, the transmission / reception unit 51 of the management system 50 executes a session for transmitting content data between the first terminal (terminal 10aa) and the second terminal (terminal 10db). If so, a request for participation in this session is accepted from the third terminal (terminal 10cb). Further, the terminal extraction unit 54 extracts a destination terminal ID associated with a terminal ID for identifying each of the first terminal and the second terminal from the destination list management table (FIG. 13). Further, the destination determination unit 62 determines whether the destination terminal ID for identifying the third terminal is included in the extracted destination terminal ID. Thereby, the management system 50 can perform control for connecting the first terminal, the second terminal, and the third terminal based on the predetermined determination. That is, when a session between multiple sites is performed, it is possible to realize that the terminal 10 that has not reserved participates in this session.
Moreover, the management system 50 performs control for connecting the first terminal (terminal 10aa), the second terminal (10db), and the third terminal (terminal 10cb) based on a predetermined determination. In this case, the terminal extraction unit 54 extracts the destination terminal ID associated with the terminal ID for identifying the third terminal from the destination list management table (see FIG. 13). In addition, the transmission / reception unit 51 transmits participation information indicating participation in the session of the third terminal to the terminal 10 identified by the extracted destination terminal ID. As a result, the management system 50 can notify the destination terminal of the third terminal that the terminal is participating in the session.
Further, the transmission / reception unit 51 of the management system 50 receives the session ID notification request information from the first terminal (terminal 10aa). In this case, the terminal extraction unit 54 extracts the destination terminal ID associated with the terminal ID for identifying the first terminal from the destination list management table (see FIG. 13). When it is determined that the destination terminal ID extracted by the terminal extraction unit 54 includes the destination terminal ID for identifying the terminal that is notified of the session ID, the transmission / reception unit 51 performs a session with the terminal 10 that is the notification destination. Notify ID. Thus, the terminal 10 that has received this notification can request participation in the session using the session ID.
Further, the calculation unit 63 of the management system 50 determines the distance between the terminal 10 identified by the terminal ID and the terminal 10 identified by the destination terminal ID associated with this terminal ID in the destination list management table (see FIG. 13). Is the predetermined distance, the shortest path distance between the third terminal (terminal 10cb) and the third terminal among the first terminal (terminal 10aa) and the second terminal (terminal 10db) is The distance of the shortest route of the largest terminal is calculated. In addition, the destination determination unit 62 determines whether or not the shortest path distance calculated by the calculation unit is smaller than a predetermined threshold. Thereby, the management system 50 can perform control for connecting the first terminal, the second terminal, and the third terminal based on the predetermined determination.
The transmission / reception unit 51 of the management system 50 transmits distance information indicating the distance of the shortest path calculated by the calculation unit 63 to the third terminal (terminal 10cb). Thereby, the 3rd terminal can grasp the risk of participating in a session based on the distance with the 3rd terminal.
The management system 50 also performs control for connecting the first terminal (terminal 10aa), the second terminal (terminal 10db), and the third terminal (terminal 10cb). In this case, the transmission / reception unit 51 transmits, to the third terminal, relay device connection information for connecting to the relay device 30e that relays the content data transmitted from the first terminal to the second terminal. As a result, the third terminal can connect to the relay device 30e using the relay device connection information.
In the present embodiment, in step S106-5, when the participation request terminal is managed as the destination terminal of the participating terminal in the destination list management table (see FIG. 13), the distance between the participation requesting terminal and the participating terminal is set to “ 1 ”(see FIG. 31A). However, the method for calculating the distance is not limited to this method. In this case, when the participating terminal is managed as the destination terminal of the participation request terminal in the destination list management table (see FIG. 13), the distance between the participation requesting terminal and the participating terminal may be set to “1” (FIG. 13). 31 (b)). In addition, in the destination list management table (see FIG. 13), when the participation request terminal is managed as the destination terminal of the participation terminal and the participation terminal is managed as the destination terminal of the participation request terminal, the participation request The distance between the terminal and the participating terminal may be “1” (see FIG. 31C).
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 arbitrarily assigned by dividing each unit (function or means). May be. In addition, when the program providing system 90 is constructed by a single computer, the program transmitted by the program providing system 90 may be transmitted by dividing it into a plurality of modules. 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 terminal program, the relay device program, and the transmission management program of the present embodiment, the HD 204 storing the program, and the program providing system 90 including the HD 204 are as follows: All of them are used when the terminal program, the relay device program, and the transmission management program are provided to users or the like as program products in Japan or overseas.
Furthermore, in the above-described embodiment, as an example of the image quality of the image data relayed by the relay device 30 using the changed quality management table shown in FIG. 8 and the quality management table shown in FIG. Although it was managed by focusing on the resolution of the image of the data, the present invention is not limited to this. Other examples of the quality include the depth of image quality of the image data, the sampling frequency of the audio data, and the bit length of the audio data. You may manage it paying attention to.
10, 12, and 14 manage the reception date and time, but the present invention is not limited to this, and at least the reception time of the reception date and time may be managed.
Further, in the above embodiment, the IP address of the relay device is managed in FIG. 10 and the IP address of the terminal in FIG. 12, but the present invention is not limited to this, and the relay device 30 is specified on the communication network 2. Each relay device specifying information or terminal specifying information for specifying the terminal 10 on the communication network 2 may manage each FQDN (Fully Qualified Domain Name). In this case, an IP address corresponding to the FQDN is acquired by a known DNS (Domain Name System) server. In addition to “relay device specifying information for specifying the relay device 30 in the communication network 2”, “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 specifying information for specifying the terminal 10 in 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 be expressed as “terminal destination information indicating a destination to the terminal 10”.
In the above-described embodiment, the case of the video conference system has been described as an example of the transmission system 1. . 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 mounted on a car, and the other of the terminals 10 is mounted on a management terminal or management server of a management center that manages car navigation, or another car. This corresponds to a car navigation device. Further, the transmission system 1 may be an audio conference system or a PC (Personal Computer) screen sharing system.
Further, the transmission system 1 may be a mobile phone communication system. In this case, for example, the terminal 10 corresponds to a mobile phone. A display example of the destination list in this case is shown in FIG. FIG. 34 is a conceptual diagram showing a destination list according to another embodiment. That is, the terminal 10 as a mobile phone includes a mobile phone main body 1110-1, a menu screen display button 1110-2 provided on the main body 1110-1, a display unit 1110-3 provided on the main body 1110-1, and a main body. The microphone 1110-4 provided in the lower part of 1110-1 and the speaker 1110-5 provided in the main body 1110-1 are provided. Among these, the “menu screen display button” 1110-2 is a button for displaying a menu screen on which icons indicating various applications are displayed. The display unit 1110-3 is a touch panel, and the user can make a call with the other party's mobile phone by selecting a destination name.
DESCRIPTION OF SYMBOLS 10 Transmission terminal 11 Transmission / reception part 12 Operation input reception part 13 Login request | requirement part 14 Imaging part 15a Audio | voice input part 15b Audio | voice output part 16 Display control part 18 Delay detection part 19 Memory | storage / reading process part 20 Destination list creation part 31 Transmission / reception part 32 State Detection unit 33 Data quality confirmation unit 34 Change quality management unit 35 Data quality change unit 39 Storage / read processing unit 50 Transmission management system (an example of a connection control system)
51 Transmitting / receiving unit (an example of a reception unit, an example of a distance information transmission unit, a participation information transmission unit, a session information transmission unit, a connection information transmission unit, and a transmission unit)
52 terminal authentication unit 53 state management unit 53a state setting unit 53b state acquisition unit 53c state change unit 54 terminal extraction unit (an example of a destination terminal extraction unit)
55 Terminal status acquisition unit 56 Relay device selection unit 56a Session ID generation unit 56b Relay device extraction unit 56c Selection unit 57 Session management unit 58 Quality determination unit 59 Storage / read processing unit 60 Delay time management unit 61 Change request information determination unit 62 Destination Judgment part (an example of a judgment part)
63 Calculation unit 1000 Non-volatile storage unit 1100 Volatile storage unit 3000 Non-volatile storage unit 3001 Change quality management DB
5004 Destination list management DB (an example of a destination terminal management unit)
Japanese Patent No. 4292544 JP-A-8-256145
A connection control system for controlling connection between transmission terminals based on a predetermined judgment,
Destination terminal management unit that associates and manages transmission terminal identification information for identifying the transmission terminal and destination terminal identification information for identifying the transmission terminal that is a destination of content data transmitted from the transmission terminal When,
A reception unit that receives a request for participation in the session from a third transmission terminal when a session for transmitting the content data is being executed between the first transmission terminal and the second transmission terminal;
When the request for participation is received by the reception unit, destination terminal identification information associated with transmission terminal identification information for identifying each transmission terminal of the first transmission terminal and the second transmission terminal is displayed as the destination. A destination terminal extraction unit to extract from the terminal management unit;
A determination unit configured to determine whether the destination terminal identification information for identifying the third transmission terminal is included in the destination terminal identification information extracted by the destination terminal extraction unit;
A connection control system comprising:
When the distance between the transmission terminal identified by the transmission terminal identification information and the transmission terminal identified by the destination terminal identification information associated with the transmission terminal identification information in the destination terminal management unit is assumed to be a predetermined distance The distance of the shortest path between the third transmission terminal and the transmission terminal having the longest shortest path distance from the third transmission terminal among the first transmission terminal and the second transmission terminal. A calculation unit for calculating
The connection control system according to claim 1, wherein the determination unit determines whether a distance of the shortest path calculated by the calculation unit is smaller than a predetermined threshold.
The connection control system according to claim 2, further comprising a distance information transmission unit that transmits distance information indicating the distance of the shortest path calculated by the calculation unit to the third transmission terminal.
When control for connecting the first transmission terminal, the second transmission terminal, and the third transmission terminal is executed based on the predetermined determination,
The destination terminal extraction unit extracts destination terminal identification information associated with transmission terminal identification information for identifying the third transmission terminal from the destination terminal management unit;
A participation information transmitting unit that transmits participation information indicating participation of the third transmission terminal in the session to a transmission terminal identified by the destination terminal identification information extracted by the destination terminal extraction unit, The connection control system according to any one of claims 1 to 3.
Accepting a request from the first transmission terminal to notify the presence of the session to a predetermined transmission terminal;
When the request is received by the reception unit,
The destination terminal extraction unit extracts destination terminal identification information associated with transmission terminal identification information for identifying the first transmission terminal from the destination terminal management unit;
A session for notifying the presence of the session when it is determined that the destination terminal identification information extracted by the destination terminal extraction unit includes the destination terminal identification information for identifying the predetermined transmission terminal The connection control system according to any one of claims 1 to 4, further comprising a session information transmission unit that transmits information to the predetermined transmission terminal.
The first transmission terminal, the second transmission terminal, and the third transmission terminal;
The content data transmitted from at least one of the first transmission terminal, the second transmission terminal, and the third transmission terminal is transferred to the first transmission terminal, the second transmission terminal, and the first transmission terminal. A relay device that relays to at least one of the three transmission terminals;
A connection control system according to any one of claims 1 to 5;
When the connection control system executes control for connecting the first transmission terminal, the second transmission terminal, and the third transmission terminal based on the predetermined determination,
The transmission system according to claim 6, further comprising: a connection information transmission unit configured to transmit relay apparatus connection information for connecting the third transmission terminal to the relay apparatus to the third transmission terminal.
A destination terminal management unit that manages transmission terminal identification information for identifying a transmission terminal and destination terminal identification information for identifying a transmission terminal that is a destination of content data transmitted from the transmission terminal in association with each other; A connection control system program used in a connection control system that controls connection between the transmission terminals based on a predetermined determination,
In the connection control system,
An accepting process for accepting a request for participation in the session from a third transmission terminal when a session for transmitting the content data is being executed between the first transmission terminal and the second transmission terminal;
When the request for participation is accepted by the accepting process, destination terminal identification information associated with transmission terminal identification information for identifying each transmission terminal of the first transmission terminal and the second transmission terminal, Destination terminal extraction processing extracted from the destination terminal management unit;
A determination process for determining whether the destination terminal identification information for identifying the third transmission terminal is included in the destination terminal identification information extracted by the destination terminal extraction process;
A program for a connection control system, characterized in that
JP2011199212A 2011-02-25 2011-09-13 Session control system, transmission system, and program Active JP5919695B2 (en)
JP2011039920 2011-02-25
JP2011199212A JP5919695B2 (en) 2011-02-25 2011-09-13 Session control system, transmission system, and program
US13/368,588 US20120221702A1 (en) 2011-02-25 2012-02-08 Apparatus, system, and method of controlling connection among terminals and recording medium storing connection control program
EP12155564.3A EP2493143B1 (en) 2011-02-25 2012-02-15 Apparatus, system, and method of controlling connection among terminals and recording medium storing connection control program
CN201210033497.8A CN102651773B (en) 2011-02-25 2012-02-15 Terminal connection control system, transmission terminal, transfer system and terminal connection control method
US13/974,867 US8850033B2 (en) 2011-02-25 2013-08-23 Apparatus, system, and method of controlling connection among terminals and recording medium storing connection control program
JP2012191598A true JP2012191598A (en) 2012-10-04
JP5919695B2 JP5919695B2 (en) 2016-05-18
ID=45581785
JP2011199212A Active JP5919695B2 (en) 2011-02-25 2011-09-13 Session control system, transmission system, and program
US (2) US20120221702A1 (en)
EP (1) EP2493143B1 (en)
JP (1) JP5919695B2 (en)
CN (1) CN102651773B (en)
WO2014069650A1 (en) * 2012-10-31 2014-05-08 Ricoh Company, Ltd. Transmission system, relay apparatus, transmission terminal, and transmission terminal control program
EP2770691A1 (en) 2013-02-25 2014-08-27 Ricoh Company, Ltd. Communication Management System, Communication Method, and Communication Control Carrier Means
US9401936B2 (en) 2013-02-28 2016-07-26 Ricoh Company, Ltd. Communication management system, communication management method, and computer program product
JP2016181899A (en) * 2011-02-25 2016-10-13 株式会社リコー Control system and control method
US9596434B2 (en) 2015-07-07 2017-03-14 Ricoh Company, Ltd. Communication management system, communication system, communication terminal, communication management method, and recording medium
US10298880B2 (en) 2015-07-23 2019-05-21 Ricoh Company, Ltd. Communication management system, communication system, communication management method, and medium
AU2015272608A1 (en) * 2014-06-10 2016-12-15 Ricoh Company, Ltd. Control system, communication system, control method, and program
CN110235425A (en) * 2017-01-23 2019-09-13 阿尔卡特朗讯企业通信国际公司 Utilize the conference system of terminal diversity
JP2006254328A (en) * 2005-03-14 2006-09-21 Nippon Telegr & Teleph Corp <Ntt> Audio/video communications system
JP3748952B2 (en) 1996-08-08 2006-02-22 株式会社リコー Multipoint connection network construction method and multipoint connection network system
JP3910580B2 (en) 2003-12-26 2007-04-25 株式会社エヌ・ティ・ティ・ドコモ Communication control device, terminal device, communication system, and communication method
JP3910581B2 (en) 2003-12-26 2007-04-25 株式会社エヌ・ティ・ティ・ドコモ Communication control device, terminal device, communication system, and communication method
JPWO2007013614A1 (en) * 2005-07-28 2009-02-12 京セラ株式会社 Communication method, communication system, and communication terminal
JP5188160B2 (en) 2007-11-28 2013-04-24 キヤノン株式会社 Conference apparatus and connection control method
JP2011007713A (en) * 2009-06-29 2011-01-13 Internatl Business Mach Corp <Ibm> Multi-pairs shortest path finding method and system
2011-09-13 JP JP2011199212A patent/JP5919695B2/en active Active
2012-02-08 US US13/368,588 patent/US20120221702A1/en not_active Abandoned
2012-02-15 EP EP12155564.3A patent/EP2493143B1/en active Active
2012-02-15 CN CN201210033497.8A patent/CN102651773B/en active IP Right Grant
2013-08-23 US US13/974,867 patent/US8850033B2/en active Active
JP2014090364A (en) * 2012-10-31 2014-05-15 Ricoh Co Ltd Transmission system, repeating device, transmission terminal, and transmission terminal control program
US9674487B2 (en) 2012-10-31 2017-06-06 Ricoh Company, Ltd. Transmission system, relay apparatus, transmission terminal, and transmission terminal control program
US9401939B2 (en) 2013-02-25 2016-07-26 Ricoh Company, Ltd. Communication management system, communication method, and recording medium storing communication control program
JP2014187689A (en) * 2013-02-25 2014-10-02 Ricoh Co Ltd Communication management system, communication management method, and program
US9392040B2 (en) 2013-02-28 2016-07-12 Ricoh Company, Ltd. Communication management system, communication method, and recording medium storing communication control program
US9438644B2 (en) 2013-02-28 2016-09-06 Ricoh Company, Ltd. Communication management system, communication management method, and computer program product
EP2493143A1 (en) 2012-08-29
CN102651773B (en) 2015-08-19
CN102651773A (en) 2012-08-29
JP5919695B2 (en) 2016-05-18
EP2493143B1 (en) 2017-12-27
US8850033B2 (en) 2014-09-30
US20120221702A1 (en) 2012-08-30
US20130335514A1 (en) 2013-12-19
AU2011337652A1 (en) 2013-05-30 Transmission management system, transmission system, program for transmission management system and computer readable information recording medium