EP2599290B1 - Transmission management system and transmission system - Google Patents

Transmission management system and transmission system Download PDF

Info

Publication number
EP2599290B1
EP2599290B1 EP11812414.8A EP11812414A EP2599290B1 EP 2599290 B1 EP2599290 B1 EP 2599290B1 EP 11812414 A EP11812414 A EP 11812414A EP 2599290 B1 EP2599290 B1 EP 2599290B1
Authority
EP
European Patent Office
Prior art keywords
terminal
status
transmission
terminals
alteration
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP11812414.8A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2599290A4 (en
EP2599290A1 (en
Inventor
Naoki Umehara
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ricoh Co Ltd
Original Assignee
Ricoh Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ricoh Co Ltd filed Critical Ricoh Co Ltd
Publication of EP2599290A1 publication Critical patent/EP2599290A1/en
Publication of EP2599290A4 publication Critical patent/EP2599290A4/en
Application granted granted Critical
Publication of EP2599290B1 publication Critical patent/EP2599290B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
    • H04M3/42374—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity where the information is provided to a monitoring entity such as a potential calling party or a call processing server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/15—Conference systems
    • H04N7/152—Multipoint control units therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
    • H04M3/567—Multimedia conference systems

Definitions

  • the disclosures herein generally relate to a transmission system to transmit content data and a transmission management system to manage a status of a transmission terminal to transmit the content data.
  • a videoconferencing system is a technology to conduct videoconferences via communication networks such as the Internet. Owing to recent demand for reducing time and expenses for business trips, such a videoconferencing system is becoming increasingly popular.
  • the videoconference may be implemented by transmitting and receiving telecommunication data such as image data and audio data between two or more terminals at different locations.
  • the Session Initiation Protocol is generally utilized as a communication protocol to establish a session between the terminals at two different locations.
  • IP Internet Protocol
  • SIP Session Initiation Protocol
  • the SIP server controls a call between the communication terminals (i.e., a call is established between the terminals by exchanging call information between them).
  • the SIP is designed as the communication protocol specifically to control a call or a communication session between the two locations (i.e., two terminals)
  • the SIP may not control calls among more than two locations (i.e., two or more communication terminals).
  • Patent Document 1 discloses an example of a related art technology for initiating a videoconference among terminals at more than two locations.
  • This technology utilizes an allocator that determines conference information indicating a conference attribute.
  • two or more clients receive the conference information determined by the allocator.
  • These clients are each connected to a multipoint conference unit (MCU) that relays communication data including audio data and image data based on the received conference information.
  • MCU multipoint conference unit
  • the MCU relays the communication data received from the clients to the other clients.
  • a videoconference may be initiated among the clients (terminals) located at more than two locations.
  • a management system utilized for controlling communications among videoconferencing terminals may not manage communication statuses of the videoconferencing terminals. Accordingly, when the management system transmits information desirable for initiating the communications to destination videoconferencing terminals, connections between the videoconferencing terminals may not be established due to engagement of the destination videoconferencing terminals with other videoconference terminals. That is, in the related art technology, the management system does not detect communication statuses of the destination videoconference terminals before transmitting the information desirable for initiating the communications to destination videoconference terminals, and therefore, the management system may not effectively control the connections among the videoconference terminals.
  • US 7,103,806 B1 relates to a system for performing context-sensitive decisions about ideal communication modalities considering information about channel reliability.
  • a channel manager analyzing deterministic and inferred data.
  • the deterministic data can include deterministic data associated with a first communicating party and deterministic data associated with a second communicating party.
  • a contactor data store and a contactee data store may hold, for example, current state information, predictions concerning future states and costs associated with delaying a communication to points in time associated with the predictions concerning future states.
  • the invention is defined by the subject-matter of the independent claims.
  • the dependent claims are directed to advantageous embodiments.
  • FIG. 1 is a schematic diagram illustrating a transmission system 1 according to an embodiment. Initially, an outline of the transmission system 1 according to the embodiment is described with reference to FIG. 1 .
  • transmission systems There are various types of transmission systems.
  • One example may be a data providing system.
  • content data are transmitted from one terminal to another terminal via a transmission management system in one-way direction.
  • Another example may be a communication system.
  • information or emotional expressions are mutually communicated among two or more transmission terminals via the transmission management system.
  • the communication system is utilized for mutually exchanging information or emotional expressions among the two or more communication terminals (i.e., the transmission terminals) via a communication management system (i.e., the transmission management system).
  • Examples of the communications system include a videoconference system, a videophone system, an audio conference system, a voice-call system, and a personal computer screen sharing system.
  • the following embodiments describe the transmission system, the transmission management system, and the transmission terminal by conceptualizing the videoconference system as an example of the communications system, the videoconference management system as an example of the communication management system, and the videoconference terminal as an example of the communication terminal. That is, the transmission management terminal and the transmission management system utilized in this embodiment may be applied not only to the videoconference system, but may also be applied to the communication system or the transmission system.
  • the transmission system 1 includes two or more transmission terminals (10aa, 10ab, ...), displays (120aa, 120ab, ...) for the transmission terminals (10aa, 10ab, ...), two or more relay devices (30a, 30b, 30c, 30d, and 30e), a transmission management system 50, a program providing system 90, and a maintenance system 100.
  • any one of the transmission terminals (10aa, 10ab, ...) may be referred to as a "transmission terminal 10"
  • any one of the displays (120aa, 120ab, ...) for the transmission terminals (10aa, 10ab, ...) may be referred to as a "display 120”
  • any one of the relay devices (30a, 30b, 30c, 30d, and 30e) may be referred to as a "relay device 30".
  • the transmission terminal 10 is configured to transmit and receive image data and audio data as examples of content data.
  • the "transmission terminal” and the “transmission management system” may be simply called as the “terminal” and the “management system”, respectively.
  • the communications in this embodiment not only include transmission and reception of audio data but also include transmission and reception of image data. That is, the transmission terminal 10 transmits and receives image data and audio data. However, the transmission terminal 10 may transmit and receive the audio data alone without transmitting or receiving the image data.
  • dynamic image data i.e., video data
  • the image data may also be static image data.
  • the image data may include both the dynamic and the static image data.
  • the relay device 30 is configured to relay the image data and the audio data among the terminals 10.
  • the management system 50 is configured to manage the terminal 10 and the relay device 30 in an integrated fashion.
  • Routers (70a, 70b, 70c, 70d, 70d, 70ab, and 70cd) depicted in FIG. 1 are configured to select optimal paths for the image data and the audio data. Note that in this embodiment, any one of the routers (70a, 70b, 70c, 70d, 70d, 70ab, and 70cd) may be simply called a "router 70".
  • the program providing system 90 includes a not-illustrated hard disk (HD) configured to store programs for a terminal, with which the terminal 10 may implement various functions or various methods. Accordingly, the program providing system 90 may transmit such programs for the terminal to the terminal 10.
  • the HD of the program providing system 90 further stores programs for a relay device, with which the relay device 30 may implement various functions or various methods. Accordingly, the program providing system 90 may also transmit such programs for the relay device to the relay device 30.
  • the HD of the program providing system 90 further stores transmission management programs, with which the management system 50 may implement various functions or various methods. Accordingly, the program providing system 90 may also transmit such transmission management programs to the management system 50.
  • the maintenance system 100 is a computer configured to maintain or manage at least one of the terminal 10, the relay device 30, the management system 50, and the program providing system 90. For example, if the maintenance system 100 is domestically located while the terminal 10, the relay device 30, the management system 50 or the program providing system 90 is located abroad, the maintenance system 100 remotely maintains or manages at least one of the terminal 10, the relay device 30, the management system 50, and the program providing system 90 via a communication network 2. Further, the maintenance system 100 performs maintenance, such as the management of a model number, a manufacturer's serial number, a sales destination, a maintenance inspection, and a failure history, on at least one of the terminal 10, the relay device 30, the management system 50, and the program providing system 90 without utilizing the communication network 2.
  • maintenance such as the management of a model number, a manufacturer's serial number, a sales destination, a maintenance inspection, and a failure history
  • the terminals (10aa, 10ab, 10ac, 10a%), the relay device 30a and the router 70a are connected via a LAN 2a so that they may communicate with one another.
  • the terminals (10ba, 10bb, 10bc, 10b...), the relay device 30b and the router 70b are connected via a LAN 2b so that they may communicate with one another.
  • the LAN 2a and LAN 2b are set up in a predetermined region A.
  • the LAN 2a and LAN 2b are connected via a dedicated line 2ab including the router 70ab so that they may communicate with one another.
  • the region A may be Japan
  • the LAN 2a may be set up in the Tokyo Office
  • the LAN 2b may be set up in the Osaka Office.
  • the terminals (10ca, 10cb, 10cc, 10c...), the relay device 30c and the router 70c are connected via a LAN 2c so that they may communicate with one another.
  • the terminals (10da, 10db, 10dc, 10d...), the relay device 30d and the router 70d are connected via a LAN 2d so that they may communicate with one another.
  • the LAN 2c and LAN 2d are set up in a predetermined region B. In the region B, the LAN 2c and LAN 2d are connected via a dedicated line 2cd including the router 70cd so that they may communicate with one another.
  • the region B may be USA, and the LAN 2c may be set up in the New York Office, whereas the LAN 2d may be set up in the Washington, D. C. Office.
  • the region A and the region B are connected from the respective routers 70ab and 70cd via the Internet 2i so that the region A and the region B are mutually in communication via the Internet 2i.
  • management system 50 and the program providing system 90 are connected to the terminal 10 and the relay device 30 via the Internet 2i so that they may communicate with one another.
  • the management system 50 and the program providing system 90 may be located in the region A or the region B, or may be a region other than the regions A and B.
  • the relay device 30e is connected to the terminal 10 via the communication network 2.
  • the relay device 30e is configured to be operating constantly, and may be located in a region other than the regions A and B for not being affected by the communications in the local areas of the regions A and B.
  • the relay device 30e is utilized for relaying the communication data between the two terminal at different local areas.
  • the relay device 30e may also be utilized as an emergency relay device when the terminals located within the same local area desire to communicate with one another but the relay devices located in this local area are not operating.
  • the communication network 2 is made up of the LAN 2a, the LAN 2b, the dedicated line 2ab, the Internet 2i, the dedicated line 2cd, the LAN 2c and the LAN 2d.
  • the communications are typically carried out via the wires, but may partially carried out wirelessly.
  • the set of four numerals attached beneath each of the terminal 10, the relay deice 30, the management system 50, the router 70, the program providing system 90, and the maintenance system 100 simply indicates the IP address of the typical IPv4.
  • the IP address for the terminal 10aa is "1.2.1.3", as illustrated in FIG. 1 .
  • the IP addresses may be the IPv6; however, in this embodiment, the Ipv4 is used for simplifying the illustration.
  • the hardware configuration of the transmission system 1 is described.
  • the resolution of the image data may be altered by the relay device 30 and then the altered image data may be transmitted to the terminal 10 that is utilized as a relay destination.
  • FIG. 37 is an external diagram illustrating the terminal 10 according to the embodiment.
  • an X-axis direction represents a longitudinal direction of the terminal 10
  • a Y-axis direction represents a direction perpendicular to the X-axis direction in a horizontal plane
  • a Z-axis direction represents a direction perpendicular to the X-axis direction and the Y-axis direction (i.e., vertical direction).
  • the terminal 10 includes a case 1120, an arm 1200 and a camera housing 1300.
  • a front-wall face 1120a of the case 1120 includes a not-illustrated air-intake face formed of air-intake holes and a rear-wall face 1120b of the case 1120 includes an exhaust face 1121 formed of exhaust holes. Accordingly, the terminal 10 may take in external air behind the terminal 10 via the air-intake face and exhaust the air inside the terminal 10 via the exhaust face 1121 by driving a cooling fan arranged inside the case 1120.
  • a right-wall face 1130 of the case 1120 includes a sound collecting hole 1131, via which a build-in microphone 114 (see FIG. 2 ) is capable of picking up audio sound such as voice, sound, or noise.
  • the right-wall face 1130 of the case 1120 includes an operations panel 1150.
  • the operations panel 1150 includes operations buttons (108a to 108e), a later-described power switch 109, a later-described alarm lamp 119, and a sound output face 1151 formed of sound output holes for outputting sound from a later-described built-in speaker 115.
  • a left-wall face 1140 of the case 1120 includes a recessed seating unit 1160 for accommodating an arm 1200 and an operations panel 1200.
  • the right-wall face 1130 of the case 1120 further includes connecting ports (1132a to 1132c) for electrically connecting cables to a later-described external device connecting IF 118.
  • the left-wall face 1140 of the case 1120 further includes a not-illustrated connecting port for electrically connecting a display cable 120c cable to the later-described external device connecting IF 118.
  • any one of the operations buttons (108a to 108e) may be called an “operations button 108" and any one of the connecting ports (1132a to 1132c) may be called a “connecting port 1132".
  • the arm 1200 is attached to the case 1120 via a torque hinge 1210 such that the arm 1200 moves in upward and downward directions within a tilt-angle ⁇ 1 range of 135 degrees with respect to the case 1120.
  • the arm 1200 illustrated in FIG. 37 is arranged at a tilt-angle ⁇ 1 of 90 degrees.
  • the camera housing 1300 includes a later-described camera 112 configured to take images of a user, documents, a room, and the like.
  • the camera housing 1300 further includes a torque hinge 1310.
  • the camera housing 1300 is attached to the arm 1200 via the torque hinge 1310.
  • the camera housing 1300 is rotationally attached to the arm 1200 in the upward and downward directions via the torque hinge 1310 such that the camera housing 1300 moves in a pan-angle ⁇ 2 range of ⁇ 180 degrees and a tilt-angle ⁇ 3 range of ⁇ 45 degrees based on the pan and tilt angles illustrated in FIG. 37 are both 0.
  • FIG. 2 is a hardware configuration diagram illustrating the terminal (i.e., transmission terminal) 10 according to an embodiment.
  • the terminal 10 includes a central processing unit (CPU) 101 configured to control overall operations of the terminal 10, a read only memory (ROM) 102 storing programs for the terminal, a random access memory (RAM) 103 utilized as a work area of the CPU 101, a flash memory 104 configured to store various data such as image data or audio data, a solid state drive (SDD) 105 configured to control retrieval and writing (storing) of the various data in the flash memory 104 and the like based on the control of the CPU 101, a media drive 107 configured to control retrieval and writing (storing) of data into a recording medium 106 such as a flash memory, the operations button 108 operated by a user for selecting an address of the terminal 10, the power switch 109 for switching ON/OFF of the power of the terminal 10, and a network interface (IF) for transmitting data utilizing the communication network 2.
  • CPU central processing unit
  • ROM read only memory
  • the terminal 10 further includes the built-in camera 112 configured to image a subject based on the control of the CPU 101, an imaging device IF 113 configured to control driving of the camera 112, a display IF configured to transmit image data to the external display 120 based on the control of the CPU 101, the external device connecting IF 118 configured to connect various external devices to the connecting ports (1132a to 1132c) illustrated in FIG. 37 , the alarm lamp 119 configured to inform the user of various functional problems of the terminal 10, and a bus line 110 such as an address bus or a data bus for electrically connecting the elements and devices with one another illustrated in FIG. 2 via the bus line 110.
  • a bus line 110 such as an address bus or a data bus for electrically connecting the elements and devices with one another illustrated in FIG. 2 via the bus line 110.
  • the display 120 is a display unit formed of liquid crystal or an organic EL material configured to display images of the subject or icons for operating the terminal 10. Further, the display 120 is connected to the display IF 117 via the cable 120c (see FIG. 37 ).
  • the cable 120c may be an analog RGB (VGA) cable, a component video cable, a high-definition multimedia interface (HDMI) cable or a digital video interface (DVI) cable.
  • the camera 112 includes lenses and a solid-state image sensor configured to convert light into electric charges to produce digital images (videos) of the subject.
  • CMOS complementary metal oxide semiconductor
  • CCD charge coupled device
  • the external device connecting IF 118 may be connected via a universal serial bus (USB) with external devices such as the external camera, the external microphone, and the external speaker.
  • USB universal serial bus
  • the external camera On connecting the external camera to the external device connecting IF 118 via the USB, the external camera is driven in priority to the built-in camera 112.
  • the external microphone or external speaker On connecting the external microphone or external speaker to the external device connecting IF 118 via the USB, the external microphone or external speaker is driven in priority to the built-in microphone 114 or the built-in speaker 115.
  • the recording medium 106 is removable from the terminal 10.
  • the recording medium 106 is a non-volatile memory configured to retrieve or write data based on the control of the CPU 101, the recording medium 106 is not limited to the flash memory 104, and may be an electrically erasable and programmable ROM (EEPROM).
  • EEPROM electrically erasable and programmable ROM
  • the aforementioned programs for the terminal may be recorded in an installable format or in an executable format on a computer-readable recording medium such as the recording medium 106 to distribute such a recording medium.
  • FIG. 3 is a hardware configuration diagram illustrating the management system 50 according to an embodiment.
  • the management system 50 includes a central processing unit (CPU) 201 configured to control overall operations of the management system 50, a read only memory (ROM) 202 storing programs for the transmission management, a random access memory (RAM) 203 utilized as a work area of the CPU 201, a hard disk (HD) 204 configured to store various data, a hard disk drive (HDD) 205 configured to control retrieval and writing (storing) of the various data in the HD 204 based on the control of the CPU 201, a media drive 207 configured to control retrieval and writing (storing) of data into a recording medium 206 such as a flash memory, a display 208 configured to display various information such as a cursor, menus, windows, characters and images, a network IF 209 for transmitting data utilizing the later-described communication network 2, a keyboard 211 including plural keys for inputting the characters, numerals, and various instructions, a mouse 212 for selecting or
  • the aforementioned programs for the transmission management may be recorded in an installable format or in an executable format on a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 to distribute such a recording medium.
  • the relay device 30 includes a hardware configuration similar to that of the management system 50, and the description of the hardware configuration of the relay device 30 is therefore omitted.
  • the ROM 202 stores programs for controlling the relay device 30.
  • the programs for the relay device may also be recorded in an installable format or in an executable format on a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 to distribute such a recording medium.
  • the program providing system 90 includes a hardware configuration similar to that of the management system 50, and the description of the hardware configuration of the program providing system 90 is therefore omitted.
  • the ROM 202 stores programs for controlling the program providing system 90.
  • the programs for the program providing system 90 may also be recorded in an installable format or in an executable format on a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 to distribute such a recording medium.
  • the maintenance system 100 includes a hardware configuration similar to that of the management system 50, and the description of the hardware configuration of the maintenance system 100 is therefore omitted.
  • the ROM 202 stores programs for controlling the maintenance system 100.
  • the programs for the maintenance system 100 may also be recorded in an installable format or in an executable format on a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 to distribute such a recording medium.
  • the removable recording medium examples include a compact disc recordable (CD-R), a digital versatile disk (DVD), and a Blu-ray Disc (BD).
  • CD-R compact disc recordable
  • DVD digital versatile disk
  • BD Blu-ray Disc
  • FIG. 4 is a functional block diagram illustrating the transmission terminal 10, the relay device 30, and the manager system 50 that constitute the transmission system 1 according to the embodiment.
  • the terminal 10, the relay device 30, and the management system 50 are connected via the communication network 2 such that they carry out data communications with one another via the communication network 2.
  • the program providing system 90 and the maintenance system 100 are not directly associated with videoconferencing communications, and their illustrations are therefore omitted from FIG. 4 .
  • the terminal 10 includes a transmitter-receiver unit 11, an operation-inputs receiver unit 12, a login request unit 13, an imaging unit 14, a sound input unit 15a, a voice output unit 15b, a display control unit 16, a delay detector unit 18, a storing-reading processing unit 19, and an address list creating unit 20.
  • the above units represent functions and units implemented by any of the elements and devices illustrated in FIG. 2 , which are activated by instructions from the CPU 201 based on the programs stored in the ROM 102.
  • the terminal 10 further includes a volatile storage unit 1100 formed of the RAM 103 illustrated in FIG. 2 , and a nonvolatile storage unit 1000 formed of the flash memory 104 illustrated in FIG. 2 .
  • the transmitter-receiver unit 11 of the terminal 10 is configured to transmit various data (information) to and receive such data from other terminals, relay devices, and systems.
  • the function of the transmitter-receiver unit 11 may be implemented by the network IF 111 illustrated in FIG. 2 .
  • the transmitter-receiver unit 11 starts receiving status information of each of destination candidate terminals from the management system 50 before initiating communication with desired destination terminals. Note that the status information not only includes an operating status (online or offline status), but also includes a detailed status such as engaging or waiting status during the terminal 10 being online.
  • the status information further includes various statuses in addition to the operating status of the terminal 10, examples of which include a status of disconnected cables from the terminal 10, a status of incapability of outputting images while outputting sound, and a mute status of incapability of outputting sound.
  • the following example illustrates a case where the status information is the operating status of the terminal 10.
  • the operation-inputs receiver unit 12 is configured to receive various inputs from the user, and such a function of the operation-inputs receiver unit 12 is implemented by the operations button 108 and the power switch 109 illustrated in FIG. 2 .
  • the operation-inputs receiver unit 12 illustrated in FIG. 4 receives a power-ON signal to switches ON the power of the terminal 10.
  • the login request unit 13 is configured to automatically transmit login request information indicating that the user desires to login, and a current IP address of the terminal 10 as an IP address of a request source terminal from the transmitter-receiver unit 11 to the management system 50 via the communication network 2 when the power-ON signal is received by the operation-inputs receiver unit 12 as a trigger.
  • Such a function of the login request unit 13 is implemented by instructions received from the CPU 101 illustrated in FIG. 2 .
  • the transmitter-receiver unit 11 transmits power off status information to the management system 50, and the operation-inputs receiver unit 12 subsequently turns OFF the power of the terminal 10 completely. Accordingly, the management system 50 may detect a power status of the terminal 10 as an OFF status.
  • the imaging unit 14 is configured to take an image of a subject and output image data of the subject, and such a function of the imaging unit 14 is implemented by instructions received from the CPU 101 illustrated in FIG. 2 , and also by the camera 112 and the imaging device IF 113 also illustrated in FIG. 2 .
  • the sound input unit 15a is configured to input audio data of the audio signal obtained by the microphone 114 that converts voice of the user into the audio signal, and such a function of the sound input unit 15a is implemented by the audio input/output IF 116 illustrated in FIG. 2 .
  • the imaging unit 14 is configured to take an image of a subject and output image data of the subject, and such a function of the imaging unit 15 is implemented by instructions received from the CPU 101 illustrated in FIG. 2 , and also by the camera 116 and the imaging device IF 113 also illustrated in FIG. 2 .
  • the display control unit 16 is configured to control transmission of the image data to the external display 120, and such a function of the display control unit 16 may be implemented by the network IF 117 illustrated in FIG. 2 .
  • the display control unit 16 controls the display 120 such that the display 120 displays the address list containing names of destination terminals to which corresponding status information items of the destination terminals received by the transmitter-receiver unit 11 are reflected before the terminal 10 as the source terminal initiates videoconferencing communications with the desired destination terminals.
  • the display 120 displays an address list frame 11-1 illustrated in FIG. 22 .
  • the address list frame 11-1 includes names of the destination terminals such as "AB TERMINAL TOKYO OFFICE JAPAN" 11-2, and icons (11-3a, 11-3b, 11-3c, and 11-3d) of status information items for corresponding destination terminal names.
  • the icon 11-3a represents a status where one of destination candidate terminals is in an online and standby status, which indicates that this destination candidate terminal is ready to receive a call.
  • the icon 11-3b represents a status where one of destination candidate terminals is in an offline status, which indicates that this destination candidate terminal is unable to receive a call.
  • the icon 11-3c represents a status where one of destination candidate terminals is already talking to another terminal and is in an engaged status, which indicates that this destination candidate terminal is ready to receive another call in addition to the call already received (i.e., ready to accept a three-party call) .
  • the icon 11-3d represents a status where one of destination candidate terminals is calling another terminal or is being called from another terminal, which indicates that this destination candidate terminal is unable to receive a call from other terminals.
  • the icon 11-3d further represents a status where this destination candidate terminal is unable to receive a call from the other terminals since the destination candidate terminal has authorized the call from another terminal or being authorized by another terminal.
  • the address list frame 11-1 includes a scroll bar 11-4 on its right-hand side, and undisplayed address (destination) names and their statuses of the destination candidate terminals in FIG. 22 will appear by selecting an upward-pointing triangle icon or a downward-pointing triangle icon.
  • the delay detector unit 18 is configured to detect a delayed time (ms) of the image data or the audio data transmitted from another terminal 10 via the relay device 30, and such a function of the delay detector unit 18 may be implemented by instructions received from the CPU 101 illustrated in FIG. 2 .
  • the storing-reading processing unit 19 is configured to store various data in a nonvolatile storage unit 1000 or retrieve various data from the nonvolatile storage unit 1000, and such a function of the storing-reading processing unit 19 may be implemented by instructions received from the CPU 101 and also by the SSD 105 illustrated as an example in FIG. 2 .
  • the nonvolatile storage unit 1000 stores a terminal identification (ID), and a password, and the like for identifying the terminal 10.
  • the storing-reading processing unit 19 is configured to further store various data in the volatile storage unit 1100 and retrieve various data from the volatile storage unit 1100.
  • the storing-reading processing unit 19 overwrites the image data and the audio data in the volatile storage unit 1100 with new ones received from the destination terminal every time the terminal 10 talks to the destination terminals. Note that the display 120 displays previous image data before being overwritten with the new image data and the speaker 115 outputs previous audio data before being overwritten with the new audio data.
  • the address list creating unit 20 is configured to create and update an address list illustrated in FIG. 22 which display statuses of the destination candidates with icons based on the later-described address list information and the status information of the terminal 10 as a destination candidate.
  • terminal ID and the later-described relay device ID individually indicate identification information formed of language, characters, and various symbols that uniquely identify the terminal and the relay device.
  • the terminal ID and the relay device ID may be the identification information formed of a combination of two or more of the languages, characters, and various symbols.
  • the relay device 30 includes a transmitter-receiver unit 31, a status detector unit 32, a data quality checker unit 33, a alteration quality management unit 34, a data quality alteration unit 35, and a storing-reading processing unit 39.
  • the above units represent functions and units implemented by any of the elements and devices illustrated in FIG. 3 , which are activated by instructions from the CPU 201 based on the programs stored in the ROM 202.
  • the relay device 30 further includes a nonvolatile storage unit 3000 formed of the HD 204 illustrated in FIG. 3 , which is capable of maintaining the various data or information even when the power of the relay device 30 is turned off.
  • the nonvolatile storage unit 3000 includes an alteration quality management DB 3001 formed of an alteration quality management table illustrated in FIG. 7 .
  • the alteration quality management table includes IP addresses of the terminals 10 utilized as relay destination terminals in relation to image quality of the image data relayed by the respective terminals 10.
  • FIG. 8A represents a base image used as a low-resolution image formed of 160 * 120 pixels
  • FIG. 8B represents a medium-resolution image formed of 320 * 240 pixels
  • FIG. 8C represents a high-resolution image formed of 640 * 480 pixels.
  • the relay device 30 relays the image data addressed to the destination terminal having an IP address "1.3.2.4", the quality of the image data relayed is "high image quality".
  • the functional configuration of the relay device 30 is described. Note that in the following description, the functions of the relay device 30 are illustrated in association with the main elements and devices for implementing the units of the relay device 30 illustrated in FIG. 3 .
  • the transmitter-receiver unit 31 of the relay device 30 is configured to transmit various data (information) to and receive such data from other terminals, relay devices and systems.
  • the function of the transmitter-receiver unit 31 may be implemented by the network IF 209 illustrated in FIG. 3 .
  • the status detector unit 32 is configured to detect an operating status of the relay device 30 having the status detector unit 32.
  • the function of the status detector unit 32 may be implemented by instructions from the CPU 201 illustrated in FIG. 3 .
  • the operating status may be "ONLINE", "OFFLINE” or "FAILED".
  • the data quality checker unit 33 is configured to search the alteration quality management table (see FIG. 7 ) by the IP address of the destination terminal as a search key, and check image quality of the relayed image data by extracting the image quality for the corresponding image data to be relayed.
  • the function of the data quality checker unit 33 may be implemented by instructions from the CPU 201 illustrated in FIG. 3 .
  • the alteration quality management unit 34 is configured to alter content of the alteration quality management table of the status alteration management DB 3001 based on the later-described quality information transmitted from the management system 50.
  • the function of the alteration quality management unit 34 may be implemented by instructions from the CPU 201 illustrated in FIG. 3 .
  • the data quality alteration unit 35 is configured to alter the image quality of the image data transmitted from the transmission source terminal 10 based on the altered content of the alteration quality management table of the status alteration management DB 3001.
  • the function of the data quality alteration unit 35 may be implemented by instructions from the CPU 201 illustrated in FIG. 3 .
  • the storing-reading processing unit 39 is configured to store various data in the nonvolatile storage unit 3000 and retrieve various data from the nonvolatile storage unit 3000.
  • the function of the storing-reading processing unit 39 may be implemented by the HDD 205 illustrated in FIG. 3 .
  • the management system 50 includes a transmitter-receiver unit 51 (an example of a receiver unit; an example of a transmitter request), a terminal authentication unit 52, a status management unit 53, a terminal extraction unit 54, a terminal status acquisition unit 55, a relay device selector unit 56, a session management unit 57, a quality determination unit 58, a storing-reading processing unit 59, a delay time management unit 60, a determination unit 61, and an assessment unit 62.
  • the above units represent functions and units implemented by any of the elements and devices illustrated in FIG. 3 , which are activated by instructions from the CPU 201 based on the programs stored in the ROM 202.
  • the management system 50 further includes a nonvolatile storage unit 5000 formed of the HD 204 illustrated in FIG. 3 , which is capable of maintaining the various data or information even when the power of the management system 50 is turned off.
  • the nonvolatile storage unit 5000 stores an address list frame 11-1 illustrated in FIG. 22 .
  • the management system 50 may include a volatile storage unit 5100 formed of the RAM 203 illustrated in FIG. 3 .
  • the nonvolatile storage unit 5000 includes a relay device management DB 5001 formed of a relay device management table illustrated in FIG. 9 .
  • the relay device IDs of the relay devices 30 are associated with the operating statuses of the relay devices 30, receipt time and dates at which the status information indicating the operating statuses of the relay devices 30 are received by the management system 50, the IP addresses of the relay devices 30, and the maximum data transmission speeds (Mbps) of the relay devices 30.
  • Mbps maximum data transmission speeds
  • the relay device 30a having the relay device ID "111a” is associated with the operating status "ONLINE", the receipt time and date "13:00 November 10, 2009" at which status information of the relay device 30a is received by the management system 50, the IP address "1.2.1.2” of the relay device 30a, and the maximum data transmission speed 100 Mbps of the relay device 30a.
  • the nonvolatile storage unit 5000 includes a terminal authentication management DB 5002 formed of a terminal authentication management table illustrated in FIG. 10 .
  • the terminal authentication management table passwords are individually associated with the terminal IDs of all the terminals managed by the management system 50.
  • the terminal ID "Olaa" of the terminal 10aa is associated with the password "aaaa”.
  • the nonvolatile storage unit 5000 includes a terminal management DB 5003 (an example of a terminal management unit) formed of a terminal management table illustrated in FIG. 11 .
  • terminal IDs of the terminals 10 as destination terminals are associated with terminal names of the destination terminals 10, operating statuses of the destination terminals 10, communication statuses of the destination terminals 10 with other terminals, receipt time and dates at which the later-described login request information of the destination terminals 10 is received by the management system 50, and IP addresses of the destination terminals 10.
  • the terminal 10aa having the terminal ID "Olaa” is associated with the terminal name "AA TERMINAL TOKYO OFFICE JAPAN” of the terminal 10aa, the operating status "ONLINE” of the terminal 10aa, the communication status "NONE” indicating that the terminal 10aa is in a waiting status and not communicating with other terminals, the receipt time and date "13:40 November 10, 2009" at which the login request information of the terminal 10aa is received by the management system 50, and the IP address "1.2.1.3” of the terminal 10aa.
  • the communication status includes "CALLING” indicating a status where the terminal is calling another terminal, "RINGING” indicating a status where the terminal is being called, "ACCEPTED” indicating a status where the terminal has authorized a communication request from another terminal to or communication request of the terminal has been authorized, and a “BUSY” indicating a status where the terminal is engaged with communicating with another terminal.
  • the nonvolatile storage unit 5000 includes an address list management DB 5004 formed of an address list management table illustrated in FIG. 12 .
  • terminal IDs of registered destination candidate terminals are associated with the terminal IDs of the request source terminals that request initiation of a videoconference communication.
  • the terminal ID "Olaa" of the request source terminal 10aa is associated with a destination candidate terminal 10ab having a terminal ID "01ab", a destination candidate terminal 10ba having a terminal ID "01ba”, a destination candidate terminal 10bb having a terminal ID "01bb” and the like, which the request source terminal requests to initiate the videoconference.
  • the destination candidate terminals may be added or deleted based on instructions from the request source terminal to the management system 50.
  • the nonvolatile storage unit 5000 includes a session management DB 5005 formed of a session management table illustrated in FIG. 13 .
  • session IDs that identify sessions in which the communication data are transmitted and received between the terminals are associated with the relay device IDs of the relay devices 30 utilized for relaying the image data and the audio data, the terminal ID of the request source terminal 10, the terminal IDs of the destination terminals 10, delay time (ms) in receiving the image data by the destination terminals 10, and receipt time and dates at which the delay information indicating the delay time transmitted from each of the destination terminals is received by the management system 50.
  • the relay device 30a (having the relay device ID "111a") selected for executing the session having the session ID "se1" is associated with the request source terminal 10aa having the terminal ID "Olaa” that has a videoconference with the destination terminal 10bb having the terminal ID "01bb", the destination terminal 10cb having the terminal ID "01cb", and the destination terminal 10db having the terminal ID "01db”.
  • the session management table indicates that the relay device 30a relays the image data and the audio data between the request source terminal 10aa and the destination terminals 10bb, 10cb, and 10db, and delay time 200 ms in receiving the image data by the destination terminal 10db at the receipt time and date "14:00 November 10, 2009".
  • the receipt time and date of the delay information may be managed not based on the destination terminals but based on the delay information transmitted from the request source terminal. However, if the videoconference is conducted between three or more terminals 10, the receipt time and date of the delay information may be managed based on the delay information transmitted from the image data and the audio data reception side terminals 10.
  • the nonvolatile storage unit 5000 further includes a quality management DB 5007 formed of a quality management table illustrated in FIG. 14 .
  • the delay time (ms) in the request source terminal or the destination terminal is associated with the image quality (quality of image) of the image data relayed by the relay device 30.
  • the nonvolatile storage unit 5000 further includes a relay device selection management DB 5008 formed of a relay device selection management table illustrated in FIG. 15 .
  • relay device IDs of the relay devices utilized for relaying the image data and the audio data are individually associated with the terminal IDs of all the terminals managed by the management system 50.
  • the nonvolatile storage unit 5000 includes a status alteration management DB 5009 (an example of a status alteration management unit) formed of status alteration management tables illustrated in FIGS. 16 , 17 and 18 .
  • a status alteration management table illustrated in FIG. 16 alteration request information (an example of alteration information) indicating a request for altering a communication status between the terminals is associated with pre-alteration status information indicating a communication status before the communication status is altered by a status alteration unit 53c (an example of an alteration unit), and alteration information indicating a altered status altered by the status alteration unit 53c.
  • alteration request information an example of alteration information
  • indicating a request for altering a communication status between the terminals is associated with pre-alteration status information indicating a communication status before the communication status is altered by a status alteration unit 53c (an example of an alteration unit), and alteration information indicating a altered status altered by the status alteration unit 53c.
  • the alteration request information is associated with terminal information for identifying the request source terminal and the destination terminal, the pre-alteration status information, and the alteration information.
  • the alteration request information is associated with the terminal information, assessment information indicating an assessment result as to whether the alteration request information "REJECT” indicating the rejecting the initiation of the communication is received from all the terminals that have received the alteration request information "INVITE” indicating a request for initiating the communication when the alteration request information "REJECT" is received from any one of the terminals that have received the alteration request information "INVITE", the pre-alteration information, and the alteration information.
  • the alteration request information further includes "ACCEPT” indicating the authorization of the communication initiation, "CANCEL” indicating the cancellation of the communication initiation, "JOIN” indicating the initiation of relaying communication data, "CALL” indicating the participation in the established session between the terminals, and "LEAVE” indicating that the end of the communication.
  • the transmitter-receiver unit 51 of the management system 50 is configured to transmit various data (information) to and receive such data from other terminals, relay devices, and systems.
  • the function of the transmitter-receiver unit 51 may be implemented by the network IF 209 illustrated in FIG. 3 .
  • the terminal authentication unit 52 is configured to search the terminal authentication management table (see FIG. 10 ) of the nonvolatile storage unit 5000 by the terminal ID and a password contained in the login request information as search keys, and authenticate the corresponding terminal based on whether the terminal ID and the password contained in the login request are identical to those managed in the terminal authentication management table.
  • the status management unit 53 is configured to manage the terminal management table (see FIG. 11 ) by associating the terminal ID the request source terminal that has requested for login with the operating status, time and date in receiving login request information by the management system 50 and the IP address of the request source terminal.
  • the status management unit 53 may implement a status setting unit 53a (an example of a setting unit), a status acquisition unit 53b (an example of an acquisition unit), and a status alteration unit 53c based on instructions from the CPU 201 illustrated in FIG. 3 .
  • the status setting unit 53a is configured to set the operating status of the terminal from OFFLINE to ONLINE in the terminal management status (see FIG. 11 ) based on the status information indicating turning on the power of the terminal instructed by the user who has switched ON the power switch 109 from OFF.
  • the status setting unit 53a sets the operating status of the terminal from ONLINE to OFFLINE in the terminal management status (see FIG. 11 ) based on the status information indicating turning off the power of the terminal instructed by the user who has switched OFF the power switch 109 from ON.
  • the status acquisition unit 53b is configured to acquire the status information of at least one of the request source terminal and the destination terminal from the terminal management table (see FIG. 11 ) when the status alteration information transmitted from the request source terminal or the destination terminal is received by the transmitter-receiver unit 51.
  • the status alteration unit 53c is configured to alter one of or both of the status information of the request source terminal and the status information of the destination terminal managed by the terminal management table (see FIG. 11 ) based on the alteration request information received by the transmitter-receiver unit 51.
  • the terminal extraction unit 54 is configured to search the address list management table (see FIG. 12 ) by the terminal ID of the request source terminal that has requested for the login as a key, and retrieve the terminal IDs of the destination candidate terminals capable of communicating with the request source terminal. As a result, the terminal extraction unit 54 extracts the terminal IDs of the destination candidate terminals capable of communicating with the request source terminal. Further, the terminal extraction unit 54 is configured to search the address list management table (see FIG. 12 ) by the terminal ID of the request source terminal that has requested for the login as a key, and extract terminal IDs of other request source terminals that have registered the above terminal ID of the request source terminal as a destination candidate terminal.
  • the terminal status acquisition unit 55 is configured to search the terminal management table (see FIG. 11 ) by the terminal IDs of the destination candidate terminals extracted by the terminal extraction unit 54 as search keys, and retrieve the operating statuses of the extracted destination candidate terminals by the terminal IDs of the extracted destination candidate terminals. Thus, the terminal status acquisition unit 55 acquires the operating statuses of the destination candidate terminals capable of communicating with the request source terminal that has requested for the login. Further, the terminal status acquisition unit 55 is configured to search the terminal management table by the terminal IDs of the terminals extracted by the terminal extraction unit 54 as search keys and acquire the operating status of the request source terminal that has requested for the login.
  • the relay device selector unit 56 is configured to carry out a process of eventually selecting one of the relay devices 30.
  • the relay device selector unit 56 may implement a session ID generator unit 56a (see FIG. 6 ), a relay device extraction unit 56b, and a selector unit 56c based on instructions from the CPU 201 illustrated in FIG. 3 .
  • the session ID generator unit 56a is configured to generate session IDs for identifying sessions in which the communication data are transmitted and received between the terminals.
  • the relay device extraction unit 56b is configured to search a relay device selection management table (see FIG. 15 ) based on the terminal ID of the request source terminal and the terminal ID of the destination terminal contained in the initiation request information transmitted from the request source terminal, and extract the relay device IDs corresponding to the request source terminal and the destination terminal.
  • the selector unit 56c is configured to select the relay devices having the operating status "ONLINE" from the relay device management table (see FIG. 9 ).
  • the session management unit 57 is configured to store and manage the session IDs generated by the session ID generator unit 56a in association with the terminal ID of the request source terminal and the terminal ID of the destination terminal. Further, the session management unit 57 is configured to store and manage in the session management table the relay device ID of the finally selected one of the relay devices 30 in association with a corresponding one of session IDs.
  • the quality determination unit 58 is configured to search the quality management table (see FIG. 14 ) by the delay time as a search key, extract the image quality of the corresponding image data, and determine the image quality of the image data relayed by the relay device 30.
  • the storing-reading processing unit 59 is configured to store various data in the nonvolatile storage unit 5000 and retrieve various data from the nonvolatile storage unit 5000. The function of the storing-reading processing unit 59 may be implemented by the HDD 205 illustrated in FIG. 3 .
  • the delay time management unit 60 is configured to search the terminal management table (see FIG. 11 ) by the IP address of the destination terminal as a search key to extract the corresponding terminal ID. Further, the delay time management unit 60 is configured to store the delay time indicated by the delay information in a delay time field of the record corresponding to the extracted terminal ID in the session management table (see FIG. 13 ).
  • the determination unit 61 is configured to determine an appropriate process to alter the communication status between the terminals based on the alteration request information received form the transmitter-receiver unit 51.
  • the assessment unit 62 is configured to determine whether the alteration request information "REJECT” indicating the rejection of the initiation of the communication is received from all the terminals that have received the alteration request information "INVITE" indicating a request for initiating the communication when the alteration request information "REJECT” indicating the rejection of the initiation of the communication is received from any of the terminals that have received the alteration request information "INVITE".
  • An alteration request information determination unit 63 (an example of an alteration information determination unit) is configured to determine whether the alteration request information received by the transmitter-receiver unit 51 is specific alteration request information.
  • the specific alteration request information not only indicates altering the communication status of one of the request source terminal and the destination terminal, but also indicates altering the communication statuses of both the request source terminal and the destination terminal.
  • the alteration request information "INVITE” may not only alter the communication status of the request source terminal into "CALLING" but also alter the communication status of the destination terminal into "RINGING".
  • the alteration request information determination unit 63 determines the alteration request information "INVITE" as the specific alteration request information.
  • alteration request information determination unit 63 determines the alteration request information "ACCEPT" indicating the authorization of the communication initiation, "REJECT” indication the rejection of the communication initiation, and "CANCEL” indicating the cancellation of the communication initiation as the specific alteration request information in addition to the alteration request information "INVITE".
  • FIG. 19 is a sequence diagram illustrating a process in which status information indicating operating statuses of the relay devices are managed.
  • FIG. 20 is a conceptual diagram illustrating transmitting and receiving statuses of image data, audio data and various management information in the transmission system.
  • FIG. 21 is a sequence diagram illustrating a preparatory process for initiating communication among the transmission terminals.
  • FIG. 22 is a conceptual diagram illustrating an address list according to the embodiment.
  • FIG. 23 is a sequence diagram illustrating a process in which initiation of communication is requested.
  • FIG. 19 is a sequence diagram illustrating a process in which status information indicating operating statuses of the relay devices are managed.
  • FIG. 20 is a conceptual diagram illustrating transmitting and receiving statuses of image data, audio data and various management information in the transmission system.
  • FIG. 21 is a sequence diagram illustrating a preparatory process for initiating communication among the transmission terminals.
  • FIG. 22 is a conceptual diagram illustrating an address list according to the embodiment.
  • FIG. 24 is a flowchart illustrating a process in which a communication status is altered.
  • FIG. 25 is a sequence diagram illustrating a process in which the request for initiating the communication is authorized.
  • FIG. 26 is a sequence diagram illustrating a process in which the request for initiating the communication is rejected.
  • FIG. 27 is a flowchart illustrating a process in which a communication status is altered.
  • FIG. 28 is a sequence diagram illustrating a process in which the request for initiating the communication is cancelled.
  • FIG. 29 is a sequence diagram illustrating a process in which relaying of communication data is requested.
  • FIG. 30 is a flowchart illustrating a process in which a communication status is altered.
  • FIG. 25 is a sequence diagram illustrating a process in which the request for initiating the communication is authorized.
  • FIG. 26 is a sequence diagram illustrating a process in which the request for initiating the communication is rejected.
  • FIG. 27 is a flowchart illustrating a process in which a communication
  • FIG. 31 is a sequence diagram illustrating a process in which image data and audio data are transmitted and received among the transmission terminals.
  • FIG. 32 is a sequence diagram illustrating a process in which participation in a communication data session is requested.
  • FIG. 33 is a flowchart illustrating a process in which a communication status is altered.
  • FIG. 34 is a sequence diagram illustrating a process in which leaving of the communication data session is requested.
  • FIG. 35 is a conceptual diagram illustrating an address list according to another embodiment.
  • FIG. 36 is a communication status transition diagram illustrating communications status transitions.
  • FIG. 37 is an external diagram illustrating the transmission terminal according to the embodiment.
  • Each of the relay devices 30 includes a status detector unit 32 illustrated in FIG. 4 that regularly detects the operating status of its own device (i.e., own relay device 30) (steps S1-1 to S1-4).
  • the transmitter-receiver units 31 of the rely devices 30 regularly transmit a corresponding status information of its own device to the management system 50 via the communication network 2 so that the management system 50 side may manage the operating statuses of the relay devices 30 in real time (steps S2-1 to S2-4) .
  • the status information includes the relay device ID of its own relay device 30 and the operating status detected by the status detector unit 32 of its own relay device 30 associated with the relay device ID.
  • this embodiment illustrates a case where the relay devices (30a, 30b, 30d) are running normally and in the "ONLINE" status; however, the relay device 30c is operating but is in the OFFLINE status due to some kind of defects in the programs executing the relay device 30c.
  • the transmitter-receiver unit 51 receives the status information transmitted from each of the relay devices 30 and the storing-reading processing unit 59 stores each of the status information received by the transmitter-receiver unit 51 in association with the corresponding relay device ID in the relay device management table (see FIG. 9 ) in the nonvolatile storage unit 5000 (steps S3-1 to S3-4). Accordingly, the "ONLINE", “OFFLINE”, or “FAILED” is stored in the operating status field of the relay device management table illustrated in FIG. 9 in association with the relay device ID for each of the relay devices 30. Simultaneously, the receipt time and date of the status information received by the management system 50 is also stored in association with the corresponding relay device ID in the relay device management table. Note that when the status information is not transmitted from the relay device 30, the operating status field and the receipt time and date field of the record in the relay device management table illustrated in FIG. 9 may be blank, or may present the previous operating status or previous receipt time and date.
  • management information sessions sei are established between the terminals 10A, 10B, and 10C via the management system 50 for transmitting and receiving various management information items.
  • image-audio data sessions sed are established between the terminals 10A, 10B, and 10C via the relay device 30 for transmitting and receiving high resolution image data, medium resolution image data, low resolution image data and audio data. Note that the four sessions are illustrated as the image and audio data session sed.
  • FIG. 21 illustrates a process in which various management information items are all transmitted and received in the management information sessions sei.
  • the operation-inputs receiver unit 12 illustrated in FIG. 4 receives a power-ON signal to switches ON the power of the terminal 10aa (step S21).
  • the login request unit 13 automatically transmits the login request information indicating the login request from the transmitter-receiver unit 11 to the management system 50 via the communication network 2 (step S22).
  • the login request information includes a terminal ID and a password for identifying the terminal 10aa indicating an own terminal as the request source terminal.
  • the terminal ID and password are data that are retrieved from the nonvolatile storage unit 1000 via the storing-reading processing unit 19 and then transmitted to the transmitter-receiver unit 11.
  • the receiver side management system 50 may detect the IP address of the transmitter side terminal 10aa.
  • the terminal authentication unit 52 of the management system 50 authenticates the terminal 10aa based on whether the ID and password identical to those in the login request information are managed in the terminal authentication management DB 5002 of the nonvolatile storage unit 5000 by searching for the ID and password as search keys in the terminal authentication management table (see FIG. 10 ) (step S23).
  • the terminal authentication unit 52 manages identical terminal IDs and passwords. Accordingly, when the terminal authentication unit 52 determines that the received login request comes from the terminal 10 having a valid access authorization, the status management unit 53 stores the receipt time and date of the received login information and the IP address of the terminal 10aa in association with the record presented by the terminal ID and the destination name of the terminal 10aa in the terminal management table (see FIG. 11 ) (step S24-1). Thus, the receipt time and date "2009.11.10.13:40" and the terminal IP address "1.2.1.3" are managed in association with the terminal ID "01aa" in the terminal management table illustrated in FIG. 11 .
  • the status setting unit 53a of the status management unit 53 sets the operating status "ONLINE” and the communication status "NONE” of the terminal 10aa and stores the set operating status and communication status in association with the record presented by the terminal ID and the destination name of the terminal 10aa in the terminal management table (see FIG. 11 ) (step S24-2).
  • the operating status "ONLINE” and the communication status "NONE” are managed in association with the terminal ID "01aa” in the terminal management table illustrated in FIG. 11 .
  • the transmitter-receiver unit 51 of the management system 50 transmits authentication result information indicating authentication result acquired by the terminal authentication unit 52 via the communication network 2 to the request source terminal (i.e., terminal 10aa) that has requested the login request (step S25).
  • the request source terminal i.e., terminal 10aa
  • the terminal authentication unit 52 has determined that the terminal (e.g., terminal 10aa in this case) has the valid access authorization is further described.
  • the transmitter-receiver unit 11 of the terminal 10aa transmits address list request information indicating an address list request to the management system 50 via the communication network 2 (step S26).
  • the transmitter-receiver unit 51 of the management system 50 then receives the address list request information.
  • the terminal extraction unit 54 searches the address list management table (see FIG. 12 ) by the terminal ID (01aa) of the request source terminal (i.e., terminal 10aa) that has requested for the login as a search key, and retrieves the terminal IDs of the destination candidate terminals capable of communicating with the request source terminal (i.e., terminal 10aa). As a result, the terminal extraction unit 54 extracts the terminal IDs of the destination candidate terminals capable of communicating with the request source terminal (step S27). In addition, the terminal status acquisition unit 54 searches the terminal management table (see FIG. 11 ) by the terminal IDs of the destination candidate terminals extracted by the terminal extraction unit 54 as search keys, and retrieves the destination names corresponding to the terminal IDs of the destination candidate terminals.
  • the transmitter-receiver unit 51 of the management system 50 retrieves data indicated by an address list frame (i.e., data indicated by the address list frame 11-1 in FIG. 22 ) from the nonvolatile storage unit 5000 (step S28), and transmits the address list information (address list frame, terminal IDs, address names) including the address list frame, the terminal IDs and the destination names extracted by the terminal extraction unit 54 to the request source terminal (i.e., terminal 10aa) (step S29). Accordingly, in the request source terminal (terminal 10aa), the transmitter-receiver unit 11 receives the address list information and the storing-reading processing unit 19 stores the address list information in the volatile storage unit 1100 (step S30).
  • the address list information is not managed by the terminal 10 but is managed by the management system 50.
  • the management system 50 uniformly manages the address list information of all the terminals in the transmission system 1. Thus, even if a new terminal 10 is added to the transmission system 1, a new model terminal 10 is replaced with the terminal 10 in the transmission system 1, or the appearance of the address list frame is altered, the management system 50 side may handle all the processes concerning these alternations at once so that the terminal 10 side may not need to carry out the process of changing the address list information.
  • the terminal status acquisition unit 55 of the management system 50 searches the terminal management table (see FIG. 11 ) by the terminal IDs (01ab, 01ba, ..., 01db, ...) of the destination candidate terminals (10ab, 10ba, ..., 10db, ...) extracted by the terminal extraction unit 54 as search keys, and retrieves the operating statuses of the extracted destination candidate terminals (10ab, 10ba, ..., 10db, ...) based on the terminal IDs extracted by the terminal extraction unit 54 (step S31).
  • the transmitter-receiver unit 51 transmits terminal status information containing the terminal ID "01ab” used as a search key in step S27 and the operating status "OFFLINE" of the destination terminal (i.e., terminal 10ab) corresponding to the terminal ID "01ab” to the request source terminal (i.e., terminal 10aa) via the communication terminal 2 (step S32).
  • the transmitter-receiver unit 51 separately transmits the remaining terminal status information containing the terminal ID "01ba” and the operating status "ONLINE (CALLING) " of the destination terminal (i.e., terminal 10ba) corresponding to the terminal ID "01ba” to the request source terminal (i.e., terminal 10aa) via the communication terminal 2 as a part of the process in step S32.
  • the storing-reading processing unit 19 of the request source terminal i.e., terminal 10aa sequentially stores the status information of the terminals received from the management system 50 (step S33). Accordingly, the request source terminal (terminal 10aa) may acquire the current operating status information of the destination candidate terminals such as the terminal 10ab and the like capable of communicating with the request source terminal (terminal 10aa).
  • the address list creating unit 20 of the request source terminal creates an address list to which the statuses of the destination candidate terminals 10 are reflected based on the address list information and the terminal status information stored in the volatile storage unit 1100 and the display control unit 16 controls address list display time of the display 120 illustrated in FIG. 2 (step S34).
  • the display 120aa may display the address list containing the destination names 11-2, status information icons 11-3a reflecting the status information and the like presented in the address list frame 11-1 as illustrated in FIG. 22 .
  • the terminal extraction unit 54 of the management system 50 searches the address list management table (see FIG. 12 ) by the terminal ID (01aa) of the request source terminal (i.e., terminal 10aa) that has requested for the login as a search key, and extracts terminal IDs of other request source terminals that have been registered as the destination candidate terminals for the terminal ID "01aa" of the request source terminal (terminal 10aa).
  • the terminal extraction unit 54 extracts the terminal IDs of other request source terminals that have been registered as the destination candidate terminals for the terminal ID "01aa” of the request source terminal (terminal 10aa) (step S35).
  • the extracted terminal IDs of the other request source terminals that have been registered as the destination terminals for the terminal ID "Olaa" of the request source terminal (terminal 10aa) are "01ab", "01ba", and "01db".
  • the terminal status acquisition unit 55 of the terminal extraction unit 50 searches the terminal management table (see FIG. 11 ) by the terminal ID (01aa) of the request source terminal (i.e., terminal 10aa) that has requested for the login as a search key, and acquires the operating status of the request source terminal (i.e., terminal 10aa)(step S36).
  • the transmitter-receiver unit 51 transmits the terminal status information containing the terminal ID "01aa” and the operating status "ONLINE" of the request source terminal (terminal 10aa) acquired in step S36 to the terminals (terminals 10ba, 10db) the operating statuses of which are presented as "ONLINE" in the terminal management table (see FIG. 11 ) (steps S37-1, S37-2).
  • the transmitter-receiver unit 51 refers to the IP address of the terminals managed in the terminal management table illustrated in FIG.
  • the terminal ID "01aa” and the operating status "ONLINE" of the request source terminal (terminal 10aa) may be transmitted to each of the other destination terminals (10ba, 10db) capable of communicating with the request source terminal (terminal 10aa) that has requested the login as the destination terminal.
  • step S21 when the user switches ON the power switch 109 illustrated in FIG. 2 , the operation-inputs receiver unit 12 illustrated in FIG. 4 receives a power-ON signal to switch ON the power of another terminal 10, and processes similar to those carried out in steps S22 through S38-1, S38-2 are subsequently performed.
  • steps S22 through S38-1, S38-2 are omitted.
  • FIG. 23 illustrates a process in which various management information items are transmitted and received in the management information sessions sei.
  • the request source terminal may communicate with at least one of the terminals (10bb, 10cb, 10db) having the operating status "ONLINE" and the communication status "NONE" that are indicated by the terminal status information received in step S32. Accordingly, in the following, a case where the user of the request source terminal (terminal 10aa) selects the destination terminals (terminals 10bb, 10cb, 10db) to initiate communication is described.
  • the operation-inputs receiver unit 12 illustrated in FIG. 4 receives the respective requests for initiating communication with the destination terminals (terminals 10bb, 10cb, 10db) (step S41).
  • the transmitter-receiver unit 11 of the terminal 10aa transmits initiation request information containing the terminal ID "01aa" of the request source terminal 10aa, the terminal IDs (01bb, 01cb, 01db) of the terminals (terminals 10bb, 10cb, 10db) and alteration request information "INVITE" indicating the request for initiating communication to the management system 50 (step S42). Accordingly, the transmitter-receiver unit 51 of the management system 50 receives the initiation request information while detecting the IP address "1.2.1.3" of the request source terminal 10aa that is a transmission source terminal.
  • the status management unit 53 alters the communication status fields of the records associated with the terminal IDs "01aa”, “01bb”, “01cb”, “01db” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa, the terminal IDs (01bb, 01cb, 01db) of the terminals (terminals 10bb, 10cb, 10db) contained in the initiation request information (step S43).
  • the status management unit 53 alters the communication status of the terminal 10 based on communication status alteration rules illustrated by a status transition diagram in FIG. 36 . For example, when the status management unit 53 receives the alteration request "CANCEL" and the communication status of the terminal is "RINGING” or “CALLING", the status management unit 53 alters the communication status from "RINGING” or "CALLING" to "NONE". When the communication status of the terminal is "ACCEPTED”, the status management unit 53 allows the communication status to remain “ACCEPTED". In this embodiment, an example in which the status alteration management table (see FIGS.
  • management system programs may be defined such that the status management unit 53 alters the communication status of the terminal 53 based on communication status alteration rules illustrated by the status transition diagram in FIG. 36 .
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management DB 5003 (step S43-1).
  • the alteration request information "INVITE" received by the transmitter-receiver unit 51 is determined in advance by the alteration request information determination unit 63 as the specific alteration request information.
  • the status management unit 53 thus not only acquires the communication status of the request source terminal (terminal 10aa) but also acquires the communication statuses of the destination terminals (terminals 10bb, 10cb, 10db). In this case, the status acquisition unit 53b searches the terminal management table (see FIG.
  • the status acquisition unit 53b also acquires the communication statuses "NONE" of the destination terminals 10bb and 10db.
  • the status alteration unit 53c of the status management unit 53 acquires respective pre-alteration status information items of the request source terminal and the destination terminals corresponding to the alteration request information "INVITE" (step S43-2).
  • the status alteration unit 53c searches the status alteration management table (see FIG. 17 ) by the alteration request information "INVITE” and the terminal information "request source” as search keys, and acquires the pre-alteration status information "NONE" of the request source terminal.
  • the status alteration unit 53c searches the status alteration management table (see FIG. 17 ) by the alteration request information "INVITE" and the terminal information "destination” as search keys, and acquires the pre-alteration status information "NONE" of the destination terminals.
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c for each terminal and determines whether the communication status matches the pre-alteration status information (step S43-3). In this case, the status alteration unit 53c compares the communication status "NONE" of the request source terminal (terminal 10aa) acquired by the status acquisition unit 53b and the pre-alteration status information "NONE" of the request source terminal acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information.
  • the status alteration unit 53c compares the communication status of the destination terminal (terminal 10bb, 10cb, or 10db) acquired by the status acquisition unit 53b and the pre-alteration status information of the destination terminals (terminal 10bb, 10cb, or 10db) acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information for each destination terminal.
  • the status alteration unit 53c acquires alteration information of the request source terminal and those of the destination terminals corresponding to the alteration request information "INVITE" (step S43-4).
  • the status alteration unit 53c searches the status alteration management table (see FIG. 17 ) by the alteration request information "INVITE" and the terminal information "request source” as search keys, and acquires the alteration information "CALLING" of the request source terminal. Similarly, the status alteration unit 53c searches the status alteration management table (see FIG. 17 ) by the alteration request information "INVITE” and the terminal information "destination” as search keys, and acquires the alteration information "RINGING" of the destination terminals.
  • the status alteration unit 53c alters the communication status fields of the respective records associated with the terminal IDs "01aa”, “01bb”, “01cb”, “01db” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa, the terminal IDs (01bb, 01cb, 01db) of the terminals (terminals 10bb, 10cb, 10db) contained in the initiation request information (step S43-5).
  • the communication status field of the record associated with the terminal ID "01aa” in the terminal management table is altered to "CALLING" based on the acquired alteration information of the request source terminal.
  • the communication status fields of the records associated with the terminal IDs "01bb”, “01cb”, and “01db” in the terminal management table are altered to "RINGING" based on the acquired alteration information of the destination terminals.
  • the determination unit 61 determines appropriate processes (see steps S48-1, S48-2, and S48-3) for transmitting the communication initiation request information to the destination terminals (terminals 10bb, 10cb, 10db) in order to perform call-control on the communications between the request source terminal (terminal 10aa) and the destination terminals (terminals 10bb, 10cb, 10db).
  • the status alteration unit 53c does not alter the communication status field of the record associated with a corresponding one of the terminal IDs "01aa”, "01bb", "01cb", and "01db" in the terminal management table (see FIG. 11 ). This is because any one of the request source terminal (terminal 10aa) and the destination terminals (terminals 10bb, 10cb, 10db) is not ready to initiate communications.
  • the determination unit 61 determines an appropriate process for creating a predetermined error message and transmitting it to the request source terminal (terminal 10aa). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the request source terminal (terminal 10aa), thereby completing the process.
  • the session ID generator unit 56a generates a session ID "se1" for identifying a session (i.e., communication data session sed) that executes the communication requested by the request source terminal (terminal 10aa) between the request source terminal and each of the destination terminals (step S44).
  • the session ID generator unit 56a generates the session ID "se1”
  • the generated session ID "se1” and the number of destination terminals "3" are stored in the volatile storage unit 5100.
  • the number of destination terminals (“3" in this case) is utilized for determining whether the alteration request information "REJECT" is received from all the destination terminals when the alteration request information "REJECT” indicating the rejecting the initiation of the communication is received.
  • the relay device selector unit 56 of the status management unit 50 selects the relay device 30 for relaying the communications between the request source terminal (terminal 10aa) and the destination terminals (terminals 10bb, 10cb, 10db) based on the relay device management DB 5001 and a relay device selection management DB 5008 (see FIG. 4 ) (step S45).
  • the relay device selector unit 56 searches a relay device selection management table (see FIG.
  • step S43 by the terminal IDs "01aa”, “01bb”, “01cb”, and “01db” contained in the communication initiation request information (step S43) as search keys and extracts the relay device IDs "111a”, “111b”, “111c”, and "111d” associated with the terminals (10aa, 10bb, 10cb, and 10db).
  • the selector unit 56c refers to the operating status of the relay device 30 in the relay device management table (see FIG. 9 ) corresponding to the extracted relay device ID. If the operating status corresponding to the extracted relay device ID is the "ONLINE" status, the selector unit 56c selects the relay device corresponding to the extracted relay device ID as the relay device utilized for relaying the communication. However, if the extracted relay device IDs are not identical, or the operating status is the "OFFLINE" as a result of referring to the operating status of the relay device corresponding to the extracted relay device ID, the selector unit 56c selects a relay device 30e corresponding to the extracted relay device ID "111e" as the relay device utilized for relaying the communication. In the following, the case where the selector unit 56c selects the relay device 30e as the relay device utilized for relaying the communication is described.
  • the session management unit 57 stores the terminal ID "01aa" of the request source terminal 10aa in the request source terminal ID field, the terminal IDs (01bb, 01cb, 01db) of the terminals (terminals 10bb, 10cb, 10db) in the destination terminal field, and the relay device ID (111e) of the selected relay device in the relay device field of the record associated with the session ID "se1" in the session management table (see FIG. 13 ) (step S46).
  • the transmitter-receiver unit 51 illustrated in FIG. 4 transmits the session ID generated by the session ID generator unit 56a and relay device connecting information utilized for connecting the relay device 30e selected by the selector unit 56c to the request source terminal (terminal 10aa) via the communication network 2 (step S47).
  • the relay device connecting information may contain an IP address "1.1.1.3" of the relay device 30e, authentication information, and a port number and the like. Accordingly, the terminal 10aa may detect the relay device connecting information utilized for connecting to the relay device 30e that relays the communication data by execution of the session corresponding to the session ID "se1".
  • the transmitter-receiver unit 51 transmits the terminal ID "01aa” of the request source terminal 10aa, the alteration request information "INVITE" indicating the request for initiating communication with the destination terminals, the communication initiation request information containing the session ID "se1", the relay device connecting information utilized for connecting to the relay device 30e, and the IP address of the management system 50 to all the destination terminals (terminals 10bb, 10cb, 10db) (steps S48-1, S48-2, and S48-3).
  • the transmitter-receiver units 11 of the destination terminals may receive the communication initiation request information and detect the relay device connecting information utilized for connecting to the relay device 30e that relays the communication data, and the IP address "1.1.1.2" of the management system 50 as a transmission source device.
  • the destination terminal (terminal 10db) receives the response indicating the permission to initiate the communication with the request source terminal (terminal 10aa) when the user of the destination terminal (terminal 10db) presses the operations button 108 (step S49).
  • the transmitter-receiver unit 11 of the destination terminal 10db transmits initiation response information containing the terminal ID "01db" of the destination terminal 10db, the terminal ID "01aa” of the request source terminal 10aa, alteration request information "ACCEPT” indicating the permission to initiate the communication, and the session ID "se1" to the management system 50 (step S50).
  • the status management unit 53 alters the communication status fields of the respective records associated with the terminal IDs "01aa” and "01db" in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa and the terminal ID (01db) of the terminal (terminal 10db) (step S51).
  • step S51 the process in step S51 is described further in detail with reference to FIG. 24 .
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management table (see FIG. 11 ) in a similar manner as the process in step S43-1 (step S51-1).
  • the alteration request information "ACCEPT" received by the transmitter-receiver unit 51 is determined in advance by the alteration request information determination unit 63 as the specific alteration request information.
  • the status management unit 53 thus not only acquires the communication status "RINGING" of the destination terminal (terminal 10db) but also acquires the communication status "CALLING" of the request source terminal (terminal 10aa).
  • the status alteration unit 53c of the status management unit 53 acquires the pre-alteration status information "CALLING” and “ACCEPTED” of the request source terminal 10aa associated with the alteration request information "ACCEPT” managed in the status alteration management table (see FIG. 17 ) in a similar manner as the process in step S43-2. Likewise, the status alteration unit 53c of the status management unit 53 acquires the pre-alteration status information "RINGING" of the destination terminal associated with the alteration request information "ACCEPT" managed in the status alteration management table (see FIG. 17 ) (step S51-2).
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c for each terminal and determines whether the communication status matches the pre-alteration status information (step S51-3).
  • the status alteration unit 53c compares the communication status "CALLING" of the request source terminal (terminal 10aa) acquired by the status acquisition unit 53b and the pre-alteration status information "CALLING" of the request source terminal acquired by the status alteration unit 53c and determines whether the communication status "CALLING" of the request source terminal (terminal 10aa) matches one of the pre-alteration status information items "CALLING" and "ACCEPTED".
  • the status alteration unit 53c determines whether the communication status "RINGING" of the destination terminal (terminal 10db) acquired by the status acquisition unit 53b matches the pre-alteration status information "RINGING" of the destination terminal acquired by the status alteration unit 53c.
  • the status alteration unit 53c acquires alteration information of the request source terminal and that of the destination terminal corresponding to the initiation response information "ACCEPT" (step S51-4). In this case, the status alteration unit 53c searches the status alteration management table (see FIG.
  • the status alteration unit 53c searches the status alteration management table (see FIG. 17 ) by the initiation response information "ACCEPT", the terminal information “DESTINATION” indicating the destination terminal, and the pre-alteration status information "RINGING” indicating the previous communication status of the destination terminal as search keys, and acquires the alteration information "ACCEPTED” of the destination terminal.
  • the status alteration unit 53c alters the communication status fields of the respective records associated with the terminal IDs "01aa” and "01db" contained in the initiation response information in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa and the terminal ID (01db) of the destination terminal (terminal 10db) (step S51-5).
  • the communication status field of the record associated with the terminal ID "01aa” in the terminal management table is altered to "ACCEPTED" based on the acquired alteration information of the request source terminal.
  • the communication status field of the record associated with the terminal ID "01db" in the terminal management table is altered to "ACCEPTED" based on the acquired alteration information of the destination terminal. Further, the determination unit 61 determines an appropriate process (see step S52) for transmitting the initiation response information to the request source terminal (terminal 10aa) in order to perform call-control on the communications between the request source terminal (terminal 10aa) and the destination terminal (terminal 10db).
  • the status alteration unit 53c does not alter the communication status field of the record associated with a corresponding one of the terminal IDs "01aa" and "01db" in the terminal management table (see FIG. 11 ).
  • the determination unit 61 determines an appropriate process for creating a predetermined error message and transmitting it to the destination terminal (terminal 10db). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the destination terminal (terminal 10db), thereby completing the process.
  • the transmitter-receiver unit 51 transmits initiation response information containing the terminal ID "01db" of the destination terminal 10db, alteration request information "ACCEPT" indicating the permission to initiate the communication with the destination terminal, and the session ID "se1" to the request source terminal (step S52).
  • the transmitter-receiver unit 11 of the request source terminal (terminal 10aa) transmits the session ID "se1" and the relay device connecting information acquired in step S47 to the relay device 30e, thereby connecting the request source terminal (terminal 10aa) and the relay device 30e (step S53).
  • the transmitter-receiver unit 11 of the destination terminal (terminal 10db) transmits the session ID "se1" and the relay device connecting information acquired in step S48-1 to the relay device 30e, thereby connecting the destination terminal (terminal 10db) and the relay device 30e (step S54).
  • the transmitter-receiver unit 11 of the terminal 10bb transmits initiation response information containing the terminal ID "01bb" of the request source terminal 10bb, alteration request information "REJECT” indicating the rejection in initiating the communication, and the session ID "se1" to the management system 50 (step S56).
  • the status management unit 53 alters the communication status fields of the respective records associated with the terminal IDs "01aa” and "01bb" in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa and the terminal ID "01db” of the terminal 10bb (step S57).
  • step S57 the process in step S57 is described further in detail with reference to FIG. 27 .
  • the assessment unit 62 stores the number of the initiation response information "REJECT" received by the transmitter-receiver unit 51 (the number of received responses) in the session indicated by the session ID "se1" in the volatile storage unit 5100 (step S57-1).
  • the assessment unit 62 since the initiation response information "REJECT" received from the destination terminal (terminal 10bb) is the first one of the initiation response information "REJECT" in the session indicated by the session ID "se1", the assessment unit 62 stores the number of received responses "1" in association with the session ID "se1" in the volatile storage unit 5100.
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management table (see FIG. 11 ) in a similar manner as the process in step S43-1 (step S57-2).
  • the alteration request information determination unit 63 determines the alteration request information "REJECT" received by the transmitter-receiver unit 51 as the specific alteration request information.
  • the status management unit 53 not only acquires the communication status "RINGING" of the destination terminal (terminal 10bb) but also acquires the communication status "ACCEPTED" of the request source terminal (terminal 10aa) (step S57-2).
  • the status alteration unit 53c of the status management unit 53 acquires the pre-alteration status information "CALLING" and "ACCEPTED” of the request source terminal associated with the initiation response information "REJECT" managed in the status alteration management table (see FIG. 18 ) in a similar manner as the process in step S43-2 (step S57-3).
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information for each terminal (stepS57-4).
  • the status alteration unit 53c compares the communication status "ACCEPTED" of the request source terminal (terminal 10aa) acquired by the status acquisition unit 53b and one of the pre-alteration status information items "CALLING" and "ACCEPTED" of the request source terminal acquired by the status alteration unit 53c and determines whether the communication status "ACCEPTED" of the request source terminal (terminal 10aa) matches one of the pre-alteration status information items "CALLING" and "ACCEPTED".
  • the status alteration unit 53c determines whether the communication status "RINGING" of the destination terminal (terminal 10bb) acquired by the status acquisition unit 53b matches the pre-alteration status information "RINGING" of the destination terminal (terminal 10bb) acquired by the status alteration unit 53c.
  • the assessment unit 62 determines whether all the destination terminals have rejected the request from the request source terminal (terminal 10aa), or part of the destination terminals has rejected the request from the request source terminal (terminal 10aa) (step S57-5). In this process, the assessment unit 62 acquires the number of destination terminals "3" of the destination to which the request information is transmitted by the request source terminal (i.e., terminal 10aa) from the volatile storage unit 5100 (see step S44).
  • the assessment unit 62 acquires the number of received initiation response information items "REJECT" (the number of received responses) "1" measured by a measuring unit from the volatile storage unit 5100 (see step S57-1). Thus, the assessment unit 62 determines that part of the destination terminals has rejected the request from the request source terminal (terminal 10aa).
  • the status alteration unit 53c acquires respective alteration information of the request source terminal and the destination terminals associated with the response information "REJECT" (step S57-6).
  • the status alteration unit 53c searches the status alteration management table (see FIG. 18 ) by the response information "reject", the terminal information "request source” indicating the request source terminal, the determination information "PART” indicating the result determined by the assessment unit 62, and the pre-alteration status information "ACCEPTED” indicating the previous communication status of the request source terminal as search keys, and acquires the alteration information "ACCEPTED” of the request source terminal.
  • the status alteration unit 53c searches the status alteration management table (see FIG. 18 ) by the response information "REJECT” and the terminal information "destination” as search keys, and acquires the alteration information "NONE" of the destination terminals.
  • the status alteration unit 53c alters the communication status fields of the respective records associated with the terminal IDs "01aa” and "01bb” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa and the terminal ID (01bb) of the terminal (terminal 10bb) (step S57-7).
  • the communication status field of the record associated with the terminal ID "01aa” in the terminal management table is altered to "ACCEPTED" based on the acquired alteration information of the request source terminal.
  • the communication status field of the record associated with the terminal ID "01bb” in the terminal management table is altered to "NONE" based on the acquired alteration information of the destination terminal.
  • the determination unit 61 determines an appropriate process (see step S59) for transmitting the initiation response information to the request source terminal (terminal 10aa) in order to perform call-control on the communications between the request source terminal (terminal 10aa) and the destination terminal (terminal 10bb).
  • the status alteration unit 53c does not alter the communication status field of the record associated with a corresponding one of the terminal IDs "01aa" and "01bb" in the terminal management table (see FIG. 11 ).
  • the determination unit 61 determines an appropriate process for creating a predetermined error message and transmitting it to the destination terminal (terminal 10bb). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the destination terminal (terminal 10bb), thereby completing the process.
  • the session management unit 57 deletes the terminal ID "01bb" of the destination terminal (terminal 10bb) from the destination terminal ID field of the record associated with the session ID "se1" in the session management table of the nonvolatile storage unit 5000 (see FIG. 13 ) (step S58).
  • the transmitter-receiver unit 51 transmits initiation response information containing the terminal ID "01bb" of the destination terminal 10bb, response information "REJECT” indicating the rejection in initiating the communication, and the session ID "se1" to the request source terminal (terminal 10aa) (step S59). Accordingly, the request source terminal (terminal 10aa) detects the indication that initiating the communication with the destination terminal (terminal 10bb) has been rejected.
  • the request source terminal (terminal 10aa) receives the response indicating cancelling of the communication initiation request (hereinafter called “cancellation request information") by the user pressing the operations button 108 of the request source terminal (terminal 10aa) (step S61), the transmitter-receiver unit 11 of the terminal 10aa transmits cancellation request information containing the terminal ID "01aa" of the request source terminal (terminal 10aa), alteration request information "CANCEL” indicating the cancellation of the communication initiation request, and the session ID "se1" to the management system 50 (step S62).
  • the status management unit 53 alters the communication status field of the record associated with the terminal ID "01aa” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa (step S63).
  • step S63 the process in step S63 is described further in detail with reference to FIG. 24 .
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management table (see FIG. 11 ) (step S63-1).
  • the alteration request information determination unit 63 determines the alteration request information "CANCEL" received by the transmitter-receiver unit 51 as the specific alteration request information.
  • the status management unit 53 not only acquires the communication status of the request source terminal (terminal 10aa) but also acquires the communication statuses of the destination terminals (step S63-1).
  • the status acquisition unit 53b searches the terminal management table (see FIG. 11 ) by the terminal ID "01aa" of the request source terminal (terminal 10aa) as a search key, and acquires the communication status "ACCEPTED" of the request source terminal (terminal 10aa) that has requested the initiation of the communication.
  • the status acquisition unit 53b searches the session management table (see FIG. 13 ) by the session ID "se1" as a search key, and acquires the terminal IDs "01db" and "01cb" of the destination terminals.
  • the status acquisition unit 53b searches the status alteration management table (see FIG. 11 ) by the terminal ID "01db" of the destination terminal (terminal 10db) and the terminal ID "01cd” of the destination terminal (terminal 10cb) as search keys, and acquires the respective communication statuses "ACCEPTED” and "RINGING" of the destination terminals (terminals 10db and 10cd in this case).
  • the status alteration unit 53c of the status management unit 53 acquires the pre-alteration status information "CALLING” and “ACCEPTED” of the request source terminal and the pre-alteration status information "RINGING" of the destination terminal associated with the initiation response information "CANCEL” managed in the status alteration management table (see FIG. 17 ) in a similar manner as the process in step S43-2 (step 63-2).
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c for each terminal and determines whether the communication status matches the pre-alteration status information (step S63-3).
  • the status alteration unit 53c compares the communication status "ACCEPTED" of the request source terminal (terminal 10aa) acquired by the status acquisition unit 53b and one of the pre-alteration status information "CALLING" and “ACCEPTED” of the request source terminal acquired by the status alteration unit 53c and determines whether the communication status "ACCEPTED" of the request source terminal (terminal 10aa) matches one of the pre-alteration status information "CALLING" and "ACCEPTED” of the corresponding destination terminal.
  • the status alteration unit 53c determines whether the communication status "ACCEPTED" of the destination terminal (terminal 10db) and the communication status "RINGING" of the destination terminal (terminal 10cb) acquired by the status acquisition unit 53b matches the pre-alteration status information "RINGING" of the corresponding destination terminal acquired by the status alteration unit 53c.
  • the status alteration unit 53c acquires alteration information of the request source terminal and those of the destination terminals corresponding to the alteration request information "CANCEL" (step S63-4). In this case, the status alteration unit 53c searches the status alteration management table (see FIG.
  • the status alteration unit 53c searches the status alteration management table (see FIG. 17 ) by the alteration request information "CANCEL” and the terminal information "destination” as search keys, and acquires the alteration information "NONE" of the destination terminal.
  • the status alteration unit 53c alters the communication status fields of the respective records associated with the terminal IDs "01aa” and "01cb” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa and the terminal ID (01cb) of the terminal (terminal 10cb) (step S63-5).
  • the communication status field of the record associated with the terminal ID "Olaa” in the terminal management table is altered to "ACCEPTED" based on the acquired alteration information of the request source terminal.
  • the communication status field of the record associated with the terminal ID "01cb” in the terminal management table is altered to "NONE" based on the acquired alteration information of the destination terminal.
  • the determination unit 61 determines appropriate processes (see steps S65-1 and S65-2) for transmitting the cancellation request information to the request source terminal (terminal 10aa) and the destination terminal (terminal 10cb) in order to perform call-control on the communications between the request source terminal (terminal 10aa) and the destination terminal (terminal 10cb).
  • the status alteration unit 53c does not alter the communication status field of the record associated with a corresponding one of the terminal IDs of the request source terminal and destination terminal in the terminal management table (see FIG. 11 ).
  • the communication status "ACCEPTED" of the destination terminal (terminal 10db) differs from the pre-alteration status "RINGING" of the destination terminal (terminal 10db)
  • the communication status field of the record associated with the terminal ID "01db" is not altered in the terminal management table (see FIG. 11 .
  • the determination unit 61 determines an appropriate process for creating a predetermined error message indicating that the communication with the destination terminal (terminal 10db) may not be cancelled and transmitting it to the request source terminal (terminal 10aa). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the request source terminal (terminal 10aa), thereby completing the process.
  • the session management unit 57 deletes the terminal ID "01cb" of the destination terminal (terminal 10cb) from the destination terminal ID field of the record associated with the session ID "se1" in the session management table of the nonvolatile storage unit 5000 (see FIG. 13 ) (step S64).
  • the transmitter-receiver unit 51 transmits the cancellation information containing the session ID "se1" and the information indicating that the communication with the destination terminal (terminal 10cb) has been cancelled to the request source terminal (terminal 10aa) and the destination terminal (terminal 10cb) (steps S65-1 and S65-2). Accordingly, the request source terminal (terminal 10aa) and the destination terminal (terminal 10cb) detect the indication that the communication between the request source terminal (terminal 10aa) and the destination terminal (terminal 10cb) has been cancelled.
  • FIG. 29 illustrates a process in which various management information items are transmitted and received via the management information sessions sei.
  • the transmitter-receiver unit 11 of the request source terminal (10aa) transmits relay request information containing the terminal ID "01aa” of the request source terminal (terminal 10aa), the session ID "se1", and alteration request information "JOIN” indicating a request for initiating relaying of the communication data (hereinafter called a "relay initiation request”) to the management system 50 at a predetermined timing (step S71-1).
  • the status management unit 53 alters the communication status field of the record associated with the terminal ID "01aa” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa (step S72-1).
  • step S72-1 the process in step S72-1 is described further in detail with reference to FIG. 30 .
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management DB 5003 (step S72-1-1).
  • the alteration request information "JOIN" received by the transmitter-receiver unit 51 is determined in advance by the alteration request information determination unit 63 as non-specific alteration request information.
  • the status management unit 53 thus only acquires the communication status of the request source terminal (terminal 10aa).
  • the status acquisition unit 53b searches the terminal management table (see FIG.
  • the status alteration unit 53c of the status management unit 53 acquires pre-alteration status information of the request source terminal (terminal 10aa) corresponding to the alteration request information "JOIN” (step S72-1-2).
  • the status alteration unit 53c searches the status alteration management table (see FIG. 16 ) by the alteration request information "JOIN” as a search key, and acquires the pre-alteration status information "ACCEPTED" of the request source terminal (terminal 10aa).
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c for the terminal 10aa and determines whether the communication status matches the pre-alteration status information (step S72-1-3). In this case, the status alteration unit 53c compares the communication status "ACCEPTED" of the request source terminal (terminal 10aa) acquired by the status acquisition unit 53b and the pre-alteration status information "ACCEPTED" of the request source terminal (terminal 10aa) acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information.
  • the status alteration unit 53c acquires alteration information of the request source terminal associated with the alteration request information "JOIN" (step S72-1-4). In this case, the status alteration unit 53c searches the status alteration management table (see FIG. 16 ) by the alteration request information "JOIN" as a search key, and acquires the alteration information "BUSY".
  • the status alteration unit 53c alters the communication status field of the record associated with the terminal ID "01aa” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa (step S72-1-5).
  • the communication status field of the record associated with the terminal ID "01aa” in the terminal management table is altered to "BUSY” based on the acquired alteration information.
  • the determination unit 61 determines an appropriate process (see step S73-1) for transmitting the relay initiation request to the relay device 30e in order to perform call-control on the communications.
  • the status alteration unit 53c does not alter the communication status field of the record associated with the terminal ID "01aa" in the terminal management table (see FIG. 11 ).
  • the determination unit 61 determines an appropriate process for creating a predetermined error message and transmitting it to the request source terminal (terminal 10aa). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the request source terminal (terminal 10aa), thereby completing the process.
  • the management system 50 transmits the relay initiation request containing the terminal ID "01aa" of the request source terminal 10aa and the session ID "se1" to the relay device 30e (step S73-1).
  • the relay device 30e receives the relay initiation request, the relay device 30e transmits relay initiation permission information containing report information "OK" indicating the permission to initiate the relaying of the communication data to the management system 50 (step S74-1).
  • the transmitter-receiver unit 51 of the management system 50 On receiving the relay initiation permission information as a response, the transmitter-receiver unit 51 of the management system 50 transmits the received relay initiation permission information to the request source terminal (terminal 10aa) (step S75-1). Accordingly, a communication data session sed is established between the request source terminal (terminal 10aa) and the relay device 30e (step S76-1).
  • the transmitter-receiver unit 11 of the destination terminal (10db) transmits relay request information containing the terminal ID "01db" of the destination terminal (terminal 10db), the session ID "se1", and alteration request information "JOIN” indicating a request for initiating relaying of the communication data to the management system 50 at a predetermined timing (step S71-2).
  • the management system 50 and the relay device 30e execute processes similar to those in steps S72-1, S73-1, S74-1, and S75-1, so that a communication data session sed is established between the destination terminal (terminal 10db) and the relay device 30e (steps 72-2, S73-2, S74-2, S75-2 and S76-2).
  • the relay device 30e may relay three levels of image data, that is, low resolution, medium resolution and high resolution image data, and audio data between the terminals (terminals 10aa and 10db). Accordingly, a videoconference may be initiated between the terminals (10aa and 10db).
  • the process of transmitting and receiving the image data and audio data and the later described delay time detecting process are described based on the one-way process of transmitting the image data and audio data from the terminal 10aa to the terminal 10db alone and the descriptions of those for the reverse process are omitted.
  • the transmitter-receiver unit 11 of the request source terminal transmits the image data of a subject captured by the imaging unit 14 and the audio data input by the voice input unit 15a in the image and audio data session sed to the relay device 30e via the communication network 2 (step S81).
  • high quality image data formed of three levels of image data, that is, low resolution, medium resolution and high resolution image data illustrated in FIG. 20 and the audio data are transmitted.
  • the transmitter-receiver unit 31 of the relay device 30e may receive the three resolution levels of the image data and the audio data.
  • the data quality checker unit 33 searches the alteration quality management table (see FIG. 7 ) by the IP address of the destination terminal (terminal 10db) as a search key, and checks quality of the image data to be relayed by extracting image quality of the corresponding image data to be relayed (step S82).
  • the image quality of the image data checked by the data quality checker unit 33 is "high image quality" that is the same image quality as that of the image data receives by the transmitter-receiver unit 31. Accordingly, the relay device 30a transfers the image data and audio data in the image and audio data session sed to the destination terminal (terminal 10db) without any change (step S83).
  • the transmitter-receiver unit 11 received the image data and audio data
  • the display control unit 16 displays the images on the display 120 based on the above image data
  • the voice output unit 15b outputs sounds based on the above audio data.
  • the delay detector unit 18 of the destination terminal detects delay time of the image data received by the transmitter-receiver unit 11 per a predetermined time (e.g., per second) (step S84). Note that in the following, a case where the delay time is determined as 200 ms is described.
  • the transmitter-receiver unit 11 of the destination terminal transmits delay information indicating the delay time "200 ms" in the management information session sei to the management system 50 via the communication network 2 (step S85). Accordingly, the management system 50 may detect the delay time and the IP address "1.3.2.4" of the destination terminal 10db that is a transmission source terminal for transmitting the delay information.
  • the delay time management unit 60 of the management system 50 searches the terminal management table (see FIG. 11 ) by the IP address "1.3.2.4" of the destination terminal (terminal 10db) as a search key to extract the corresponding terminal ID "01db". Further, the delay time management unit 60 manages the delay time by storing the delay time "200 ms" indicated by the delay information in a delay time field of the record corresponding to the extracted terminal ID "01db" in the session management table (see FIG. 13 ) (step S86).
  • the quality determination unit 58 searches the quality management table (see FIG. 14 ) by the delay time "200 ms" as a search key, and extracts the "medium image quality” for the corresponding image data to determine the image quality of the image data as the "medium image quality” (step S87).
  • the quality determination unit 51 searches the relay device management table (see FIG. 9 ) by the relay device ID "111e" associated with the terminal ID "01db” in the session management table (see FIG. 13 ) as a search key, and extracts the corresponding IP address "1.1.1.3" of the relay device 30e (step S88).
  • the transmitter-receiver unit 51 then transmits quality information indicating the image quality "medium” of the image data determined in step S87 to the relay device 30e via the communication network 2 (step S89).
  • the quality information contains the IP address "1.3.2.4" of the destination terminal (terminal 10db) utilized as the search key in step S86.
  • the alteration quality management unit 34 stores the IP address "1.3.2.4" of the transmission source terminal 10 (terminal 10db in this case) and the image quality "medium image quality” of the image data to be relayed by associating the transmission source terminal 10 (terminal 10db in this case) with the IP address "1.3.2.4” and the image quality "medium image quality” of the image data to be relayed in the alteration quality management table (see FIG. 7 ) (step S90).
  • the terminal 10aa continuously transmits three levels of low, medium and high image quality image data and audio data in the image and audio data session sed to the relay device 30e in a similar manner as the process in step S81 (step S91).
  • the data quality checker unit 33 searches the alteration quality management table (see FIG. 7 ) by the IP address "1.3.2.4" of the destination terminal (terminal 10db) as a search key, and checks the quality of the image data to be relayed by extracting the "medium image quality" for the corresponding image data to be relayed in a similar manner as the process in step S82 (step S92).
  • the image quality of the image data checked by the data quality checker unit 33 is "medium image quality" the level of which is lower than the image quality of the image data received by the transmitter-receiver unit 31.
  • the data quality alteration unit 35 alters the image quality of the image data by degrading the high image quality image data to the medium image quality image data (step S93).
  • the transmitter-receiver unit 31 transmits the image data having the "medium” image quality and the audio data without alteration of sound quality in the image and audio data session sed to the terminal 10db via the communication network 2 (step S94).
  • the relay device alters the image quality such that participants in the videoconference may not feel unnatuaral.
  • FIG. 32 illustrates a process in which various management information items are transmitted and received via the management information sessions sei.
  • the user of the request source terminal presses an operations button 108 illustrated in FIG. 2 to receive information on a request for reporting the session ID to the destination terminal 10cb in order for the destination terminal 10cb to participate in the communication session sed (step S101).
  • the transmitter-receiver unit 11 of the request source terminal transmits session ID report request information containing the terminal ID "01aa" of the request source terminal (terminal 10aa), the terminal ID "01cb" of the destination terminal (terminal 10cb) and the session ID "se1" to the management system 50 (step S102).
  • the transmitter-receiver unit 51 of the management system 50 On receiving the session ID report request information, the transmitter-receiver unit 51 of the management system 50 transmits session ID report information containing the terminal ID "01aa" of the request source terminal (terminal 10aa) and the session ID "se1" to the terminal 10cb (step S103).
  • the destination terminal (terminal 10cb) On receiving the session ID report information, the destination terminal (terminal 10cb) receives a participation request in the communication data session sed (step S104). In this case, the user of the destination terminal (terminal 10cb) presses an operations button 108 illustrated in FIG. 2 to receive the participation request in the communication data session sed. Accordingly, the transmitter-receiver unit 11 of the destination terminal (terminal 10cb) transmits session participating request information containing the terminal ID "01cb" of the destination terminal (terminal 10cb), alteration request information "CALL" indicating a request for participating in the communication data session and the session ID "se1" to the management system 50 (step S105).
  • the status management unit 53 of the management system 50 alters the communication status field of the record associated with the terminal ID "01cb" in the terminal management table (see FIG. 11 ) based on the terminal ID "01cb" of the request source terminal (terminal 10cb) contained in the session participating request information (step S106).
  • step S106 the process in step S106 is described further in detail with reference to FIG. 33 .
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management DB 5003 (step S106-1).
  • the alteration request information "CALL" received by the transmitter-receiver unit 51 is determined in advance by the alteration request information determination unit 63 as non-specific alteration request information.
  • the status management unit 53 thus only acquires the communication status of the destination terminal (terminal 10cb).
  • the status acquisition unit 53b searches the terminal management table (see FIG. 11 ) by the terminal ID "Olcb" of the destination terminal (terminal 10cb) as a search key, and acquires the communication status "NONE" of the destination terminal (terminal 10cb) that has requested the participation in the communication data session.
  • the status alteration unit 53c of the status management unit 53 acquires pre-alteration status information of the destination terminal corresponding to the alteration request information "CALL" (step S106-2).
  • the status alteration unit 53c searches the status alteration management table (see FIG. 16 ) by the alteration request information "CALL" as a search key, and acquires the pre-alteration status information "NONE" of the destination terminal (terminal 10cb).
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information (step S106-3). In this case, the status alteration unit 53c compares the communication status "NONE" of the destination terminal (terminal 10cb) acquired by the status acquisition unit 53b and the pre-alteration status information "NONE" of the destination terminal (terminal 10cb) acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information.
  • the status alteration unit 53c acquires alteration information of the destination terminal associated with the alteration request information "CALL" (step S106-4). In this case, the status alteration unit 53c searches the status alteration management table (see FIG. 16 ) by the alteration request information "CALL" as a search key, and acquires the alteration information "ACCEPTED" of the destination terminal (terminal 10cb).
  • the status alteration unit 53c alters the communication status field of the record associated with the terminal ID "01cb” in the terminal management table (see FIG. 11 ) based on the terminal ID "01cb" of the destination terminal (terminal 10cb) (step S106-5).
  • the communication status field of the record associated with the terminal ID "01cb” in the terminal management table is altered to "ACCEPTED" based on the acquired alteration information of the destination terminal.
  • the determination unit 61 determines appropriate processes (see steps S107-1, S107-2, and S107-3) for transmitting information indicating that the participation request has been authorized to the request source terminal (terminal 10aa) and the destination terminals (terminals 10cb, 10db) for performing call-control on the communications between the request source terminal (terminal 10aa) and the destination terminals (terminals 10cb, 10db).
  • the status alteration unit 53c does not alter the communication status field of the record associated with the terminal ID "01cb" in the terminal management table (see FIG. 11 ).
  • the determination unit 61 determines an appropriate process for creating a predetermined error message and transmitting it to the destination terminal (terminal 10cb). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the destination terminal (terminal 10cb), thereby completing the process.
  • the session management unit 57 inserts the terminal ID "01cb" of the destination terminal (terminal 10cb) that has requested for the participation in the communication data session into the destination terminal ID field of the record associated with the session ID "se1" in the session management table of the nonvolatile storage unit 5000 (see FIG. 13 ).
  • the transmitter-receiver unit 51 of the management system 50 transmits the participation report containing the terminal ID of the terminal (terminal 10cb) for participating in the communication data session sed and the session ID "se1" to the request source terminal (terminal 10aa) and the terminal ID "01db" of the destination terminal (terminal 10db) that have already participated in the communication data session sed (steps S107-1, S107-2). Accordingly, the request source terminal (terminal 10aa) and the destination terminal (terminal 10db) may detect the indication that the destination terminal (terminal 10cb) may participate in the communication data session sed.
  • the transmitter-receiver unit 51 of the management system 50 transmits a participation permission report containing the session ID "se1" for participating in the communication data session sed and relay device connecting information utilized for connecting the relay device to the destination terminal (terminal 10cb) that will participate in the communication data session sed (steps S107-3) .
  • the transmitter-receiver unit 11 of the destination terminal On receiving the participation permission report, the transmitter-receiver unit 11 of the destination terminal (terminal 10cb) transmits the session ID "se1" and the relay device connecting information contained in the participation permission report to the relay device 30e, thereby connecting the destination terminal (terminal 10cb) and the relay device 30e (step S108). Further, when the destination terminal (terminal 10db) has connected to the relay device 30e, the transmitter-receiver unit 11 of the destination terminal (10cb) transmits relay request information containing the terminal ID "Olcb" of the destination terminal (terminal 10cb), the session ID "se1", and alteration request information "JOIN” indicating a request for initiating relaying of the communication data to the management system 50 at a predetermined timing.
  • the management system 50 and the relay device 30e execute processes similar to those in steps S72-1, S73-1, S74-1, and S75-1, so that a communication data session sed is established between the destination terminal (terminal cb) and the relay device 30e.
  • the relay device 30e may relay low resolution, medium resolution and high resolution image data and audio data between the terminals (terminals 10aa, 10cb and 10db). Accordingly, videoconference may be initiated between the terminals (10aa, 10cb and 10db).
  • FIG. 20 illustrates a process in which various management information items are transmitted and received via the management information session sei.
  • the user of the request source terminal presses an operations button 108 illustrated in FIG. 2 to receive a leaving request for leaving the communication data session sed (step S111).
  • the transmitter-receiver unit 11 of the request source terminal transmits session leaving request information containing the terminal ID "Olaa” of the request source terminal (terminal 10aa), alteration request information "LEAVE” indicating a request for leaving the communication data session and the session ID "se1" to the management system 50 (step S112) .
  • the status management unit 53 of the management system 50 alters the communication status field of the record associated with the terminal ID "Olaa" in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa contained in the session leaving request (step S113).
  • step S113 the process in step S113 is described further in detail with reference to FIG. 30 .
  • the status acquisition unit 53b of the status management unit 53 illustrated in FIG. 5 acquires the communication statuses of the terminals managed by the terminal management DB 5003 (step S113-1).
  • the alteration request information "LEAVE" received by the transmitter-receiver unit 51 is determined in advance by the alteration request information determination unit 63 as non-specific alteration request information.
  • the status management unit 53 thus only acquires the communication status of the request source terminal (terminal 10aa).
  • the status acquisition unit 53b searches the terminal management table (see FIG. 11 ) by the terminal ID "01aa" of the request source terminal (terminal 10aa) as a search key, and acquires the communication status "BUSY" of the request source terminal (terminal 10aa).
  • the status alteration unit 53c of the status management unit 53 acquires pre-alteration status information of the request source terminal (terminal 10aa) corresponding to the alteration request information "LEAVE” (step S113-2).
  • the status alteration unit 53c searches the status alteration management table (see FIG. 16 ) by the alteration request information "LEAVE” as a search key, and acquires the pre-alteration status information "BUSY" of the request source terminal (terminal 10aa).
  • the status alteration unit 53c compares the communication status acquired by the status acquisition unit 53b and the pre-alteration status information acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information (step S113-3). In this case, the status alteration unit 53c compares the communication status "BUSY" of the request source terminal (terminal 10aa) acquired by the status acquisition unit 53b and the pre-alteration status information "BUSY" of the request source terminal (terminal 10aa) acquired by the status alteration unit 53c and determines whether the communication status matches the pre-alteration status information.
  • the status alteration unit 53c acquires alteration information of the terminal associated with the alteration request information "LEAVE" (step S113-4). In this case, the status alteration unit 53c searches the status alteration management table (see FIG. 16 ) by the alteration request information "LEAVE" as a search key, and acquires the pre-alteration status information "NONE".
  • the status alteration unit 53c alters the communication status field of the record associated with the terminal ID "01aa” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa (step S113-5).
  • the communication status field of the record associated with the terminal ID "01aa” in the terminal management table is altered to "NONE" based on the acquired alteration information of the request source terminal.
  • the determination unit 61 determines an appropriate process for transmitting information indicating that the leaving from the communication data session has been authorized to the destination terminals in order to perform call-control on the communications between the request source terminal (terminal 10aa) and the destination terminals (terminals 10cb, 10db).
  • the status alteration unit 53c does not alter the communication status field of the record associated with the terminal IDs "01aa" in the terminal management table (see FIG. 11 ).
  • the determination unit 61 determines an appropriate process for creating a predetermined error message and transmitting it to the request source terminal (terminal 10aa). Subsequently, the transmitter-receiver unit 51 creates the predetermined error message and transmits it to the request source terminal (terminal 10aa), thereby completing the process.
  • the session management unit 57 deletes the terminal ID "01aa” of the request source terminal (terminal 10aa) from the request source terminal ID field of the record associated with the session ID "se1" in the session management table of the nonvolatile storage unit 5000 (see FIG. 13 ) (step S114).
  • the management system 50 transmits a report indicating a request for leaving from the communication data session containing the terminal ID "01aa” of the request source terminal 10aa and the session ID "se1" to the relay device 30e (step S115).
  • the communication data session is terminated between the request source terminal (terminal 10aa) and the relay device 30e, and the request source terminal (terminal 10aa) is disconnected from the relay device 30e.
  • the relay device 30e transmits the report indicating the permission for the request for leaving from the communication data session containing the terminal ID "01aa" of the request source terminal 10aa and the session ID "se1" to the management system 50 (step S116).
  • the management system 50 On receiving the report indicating the permission for the request for leaving from the communication data session, the management system 50 transmits session leaving permission information containing the terminal ID "01aa" of the request source terminal 10aa, the alteration request information "LEAVE", reporting information "OK” indicating the permission for leaving from the communication data session and the session ID "se1" to the request source terminal (terminal 10aa) (step S117).
  • the user of the request source terminal (terminal 10aa) presses a power switch 109 illustrated in FIG. 2 to receive a power off request (step S118).
  • the transmitter-receiver unit 11 of the terminal 10aa On receiving the power off request, the transmitter-receiver unit 11 of the terminal 10aa transmits disconnection request information containing the terminal ID "01aa" of the terminal 10aa, report information indicating disconnecting of the terminal 10aa from the management system 50 to management system 50 (step S119).
  • the status management unit 53 deletes a record of the communication status field associated with the terminal ID "01aa” in the terminal management table (see FIG. 11 ) based on the terminal ID "01aa” of the request source terminal 10aa contained in the disconnection request information (step S120) . Subsequently, the transmitter-receiver unit 51 transmits disconnection permission information indicating that the disconnection request has been authorized to the request source terminal (terminal 10aa) (step S121). Accordingly, the management data session is terminated between the request source terminal (terminal 10aa) and the management system 50, and the request source terminal (terminal 10aa) is disconnected from the management system 50.
  • the request source terminal (terminal 10aa) executes switching off the power, thereby completing the process (step S122) .
  • the terminals 10cb and 10db may also leave the communication data session sed in a similar manner as the processes carried out by the request source terminal 10aa in steps S111 to S121 to complete (terminate) the communications between the terminals.
  • the management system 50 manages the communication status of the terminal 10 that communicates with another terminal.
  • the management system 50 may alter the communication status of the terminal 10 based on the received alteration request information and the communication status of the terminal 10 managed by the management system 50. Accordingly, since the management system 50 may detect the communication status of the terminal 10, the management system 50 may effectively control the connection between the terminals.
  • the management system 50 further manages the communication status of another terminal.
  • the management system 50 may alter the communication status of another terminal based on the received alteration request information and the communication statuses of the terminals managed by the management system 50. Accordingly, since the management system 50 manages the communication status of another terminal, the management system 50 may effectively control the connection between the terminals.
  • the management system 50 may acquire the communication statuses of another terminal. Accordingly, the management system 50 may be able to effectively alter one or both of the communication statuses of the terminals that initiate the communication based on various alteration request information.
  • the management system 50 includes the status alteration management DB 5009 formed of the status alteration management table having the alteration request information, the pre-alteration status information and the post-alteration management information that are associated with one another. Accordingly, the management system 50 may be able to effectively alter the communication statuses of the terminals based on the alteration request information received by the transmitter-receiver unit 51 and the communication status acquired by the status acquisition unit 53b.
  • the management system 50 when the communication status of the terminal 10 does not match the predetermined communication status corresponding to the predetermined alteration request information, the management system 50 does not alter the status information of the terminal 10, and when the communication status of another terminal does not match the predetermined communication status corresponding to the predetermined alteration request information, the management system 50 does not alter the status information of another terminal. Accordingly, the management system 50 may be able to accurately manage the communication statuses of the terminal 10 and another terminal.
  • the management system 50 transmits the predetermined information utilized for altering the communication statuses based on the predetermined alteration request information to at least one of the terminal 10 and another terminal. Accordingly, the management system 50 may be able to effectively control the connection between the terminal 10 and another terminal.
  • the management system 50 transmits the predetermined information indicating the request for initiating the communication to the plural destination terminals. Accordingly, the management system 50 may be able to effectively control the connections between the request source terminal and the destination terminals when the communications between the request source terminal and the destination terminals are initiated in another area.
  • the management system 50 determines whether the predetermined alteration request information indicating the rejection of the initiation of the communication with the request source terminal is received from all the destination terminals, and alters the status information of the request source terminal based on the determined result. Accordingly, the management system 50 may be able to accurately manage the communication statuses of the request source terminal when the management system 50 receives the alteration request information indicating the rejection of the initiation of the communication with the request source terminal from the destination terminals.
  • the management system 50 alters the status of the terminal 10 managed by the management system 50 into the status indicating the connection or the disconnection when the management system 50 receives information based on the connection or the disconnection between the terminal 10 and the management system 50. Accordingly, the management system 50 may be able to accurately manage the communication status of the terminal 10 when the terminal 10 and the management system are connected or disconnected.
  • the above embodiment has described a case where the user of the request source terminal (terminal 10aa) selects the destination terminals (terminals 10bb, 10cb, 10db) to initiate communications; however, the embodiment is not limited to the aforementioned case.
  • the user of the request source terminal (terminal 10aa) may select the own terminal (i.e., terminal 10aa) as the destination terminal.
  • the own terminal (terminal 10aa) is selected as the destination terminal, the communication data session sed is initially established between the request source terminal (terminal 10aa) and the relay device 30.
  • the request source terminal (terminal 10aa) specifies a desired destination terminal, receives information indicating a request for reporting the session ID required for participating in the communication data session sed to the specified destination terminal (step S101), and initiates communications by executing the process of requesting participation in the communication data session sed.
  • the request source terminal (terminal 10aa) selects own terminal as a destination terminal and transmits the alteration request information "INVITE" to the own terminal (terminal 10aa)
  • the management system 50 searches the status alteration management table (see FIG. 17 ) by the terminal information "own terminal selection" as a search key, and alters the status of the request source terminal (terminal 10aa).
  • the address list frame 11-1 including the destination names 11-2, icons 11-3a and the like is displayed as illustrated in FIG. 22 ; however, the destination names 11-2, icons 11-3a and the like may be displayed without the address list frame 11-1.
  • the management system 50 and the program providing system 90 may be integrated in a single computer, or various functions and units of the management system 50 and the program providing system 90 may be separately arranged in two or more computers. Moreover, if the program providing system 90 is formed in a single computer, programs transmitted via the program providing system 90 may be grouped into two or modules or may not be grouped. Further, if the program providing system 90 is formed of two or more computers, the programs grouped into modules may be transmitted from the separate computers.
  • recording media storing a terminal program, a relay device program and a transmission management program, and the program providing system 90 including the HD 204 storing such programs may be distributed to users domestically and abroad as a program product.
  • the image data relayed by the relay device 30 are managed based mainly focused on the resolutions of the images as an example of quality of the images by utilizing the alteration quality management table illustrated in FIG. 7 and the quality management table illustrated in FIG. 14 .
  • the quality of the images is not limited to this example.
  • the quality of images may be managed based on the depth of the image data, the sampling frequency of the audio data, or the bit length of the audio data.
  • the receipt time and dates are managed by the relay device management table, the terminal management table and the session management table illustrated in FIGS. 9 , 11 and 13 .
  • at least the receipt time may be managed by the relay device management table, the terminal management table and the session management table.
  • the IP addresses of the relay devices are managed by the relay device management table, and the IP addresses of the terminals are managed by the terminal management table as illustrated in FIGS. 9 and 11 .
  • respective fully qualified domain names (FQDNs) of the relay devices 30 and the terminals 10 may be managed instead of the respective IP addresses as relay device specifying information for specifying the relay devices 30 over the communication network 2 and terminal specifying information for specifying the terminals 10 over the communication network 2.
  • DNS domain name system
  • the "relay device specifying information for specifying the relay devices 30 over the communication network 2" may also be expressed as “relay device access point information indicating access points of the relay devices 30 over the communication network 2" or “relay device destination information indicating destinations of the relay devices 30 over the communication network 2".
  • the "terminal specifying information for specifying the terminals 10 over the communication network 2" may also be expressed as “terminal access point information indicating access points of the terminals 10 over the communication network 2" or “terminal destination information indicating destinations of the terminals 10 over the communication network 2".
  • videoconference and “teleconference” may be interchangeably used.
  • the video conference system is described as an example of the transmission system 1; however, the transmission system 1 may not be limited to the video conference system.
  • the transmission system 1 may be a telephone system such as an Internet protocol (IP) phone or an Internet phone.
  • IP Internet protocol
  • the transmission system 1 may be a car navigation system.
  • one of the terminals 10 may be a car navigation device mounted on a vehicle and the other terminal 10 may be a management terminal or a management server configured to manage the car navigation, or another car navigation device mounted on another vehicle.
  • the transmission system 1 may be an audio conferencing system or a personal computer (PC) screen shared system.
  • PC personal computer
  • the transmission system 1 may be a mobile phone communication system.
  • the terminal 10 may be a mobile phone terminal.
  • FIG. 35 illustrates an example of an address list displayed on the mobile phone terminal.
  • the mobile phone terminal as the terminal 10 includes a main body 10-1, a menu screen display button 10-2 arranged on the main body 10-1, a display unit 10-3 arranged on the main body 10-1, a microphone provided in a lower part of the main body 10-1 and a speaker provided in a surface of the main body 10-1.
  • the "menu screen display button" 10-2 is utilized for displaying a menu screen on which icons of various applications are displayed.
  • the display unit 10-3 is formed of a touch panel on which the user touches with a finger or hand to select a desired address name to communicate with a person of the desired address name.
  • the image data and the audio data are described as an example of the content data; however, the content data may not be limited to the image data or the audio data.
  • the content data may be touch data (tactile data). In this case, a tactile sense obtained by the user who has touched one terminal may be transmitted to the other terminal.
  • the content data may be smell (olfactory sense) data. In this case, the smell (odor) obtained by one terminal may be transmitted to the other terminal.
  • the content data may be at least one of the image data, the audio data, the touch data and the smell data.
  • the video conference system implemented by the transmission system 1 is described; however, the transmission system 1 may not be limited to the video conference system.
  • the transmission system 1 may be utilized for a preliminary meeting, a general conversation between family members or friends, or one-way presentation of information.
  • a transmission management system manages a communication status of a first transmission terminal that communicates with a second transmission terminal.
  • the transmission management system receives alteration information for altering the communication status of the first transmission terminal from the first transmission terminal
  • the transmission management system alters the communication status of the first transmission terminal based on the received alteration information and the communication status of the first transmission terminal managed by the transmission management system. Accordingly, since the transmission management system detects the communication status of the first transmission terminal, the transmission management system may effectively control connection between the first and second transmission terminal.
EP11812414.8A 2010-07-28 2011-07-15 Transmission management system and transmission system Active EP2599290B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2010169434 2010-07-28
JP2011107320A JP5998383B2 (ja) 2010-07-28 2011-05-12 伝送管理システム、伝送システム、伝送管理方法、及びプログラム
PCT/JP2011/066776 WO2012014824A1 (en) 2010-07-28 2011-07-15 Transmission management system and transmission system

Publications (3)

Publication Number Publication Date
EP2599290A1 EP2599290A1 (en) 2013-06-05
EP2599290A4 EP2599290A4 (en) 2014-11-12
EP2599290B1 true EP2599290B1 (en) 2019-11-20

Family

ID=45530032

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11812414.8A Active EP2599290B1 (en) 2010-07-28 2011-07-15 Transmission management system and transmission system

Country Status (8)

Country Link
US (3) US9043399B2 (ja)
EP (1) EP2599290B1 (ja)
JP (1) JP5998383B2 (ja)
CN (1) CN103155531B (ja)
CA (1) CA2805006C (ja)
RU (1) RU2536801C2 (ja)
SG (1) SG187023A1 (ja)
WO (1) WO2012014824A1 (ja)

Families Citing this family (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5998383B2 (ja) 2010-07-28 2016-09-28 株式会社リコー 伝送管理システム、伝送システム、伝送管理方法、及びプログラム
JP5821433B2 (ja) 2010-11-30 2015-11-24 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
US9294546B2 (en) * 2011-06-03 2016-03-22 Apple Inc. Sending files from one device to another device over a network
WO2013098688A1 (en) * 2011-12-29 2013-07-04 Turkcell Teknoloji Arastirma Ve Gelistirme Anonim Sirketi A status-sensitive power observing system
JP6019707B2 (ja) 2012-04-25 2016-11-02 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP6260101B2 (ja) 2012-05-01 2018-01-17 株式会社リコー 通信端末、起動方法及びプログラム
JP5924119B2 (ja) * 2012-05-18 2016-05-25 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP5953932B2 (ja) * 2012-05-18 2016-07-20 株式会社リコー 中継装置選択装置、伝送システム、及び中継装置選択装置用プログラム
JP6064367B2 (ja) * 2012-05-18 2017-01-25 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP6074915B2 (ja) * 2012-05-18 2017-02-08 株式会社リコー 伝送管理システム、伝送システム、伝送管理方法、及び伝送管理システム用プログラム
JP5928148B2 (ja) * 2012-05-18 2016-06-01 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP6003274B2 (ja) 2012-06-18 2016-10-05 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP5942626B2 (ja) 2012-06-18 2016-06-29 株式会社リコー 伝送管理システム、伝送端末、伝送システム、及び、伝送管理システム用プログラム
JP5949272B2 (ja) * 2012-07-25 2016-07-06 株式会社リコー 通信システムおよびプログラム
JP6003360B2 (ja) 2012-08-01 2016-10-05 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP6019920B2 (ja) * 2012-08-17 2016-11-02 株式会社リコー 管理システムおよびプログラム
US9379783B2 (en) 2012-09-14 2016-06-28 Ricoh Company, Ltd. Transmission system
JP6201299B2 (ja) * 2012-11-15 2017-09-27 株式会社リコー 通信システム、通信方法およびプログラム
JP6171319B2 (ja) 2012-12-10 2017-08-02 株式会社リコー 情報処理装置、情報処理方法、情報処理システム及びプログラム
JP6115153B2 (ja) * 2013-01-30 2017-04-19 株式会社リコー 情報処理端末、情報処理方法及びプログラム
JP6107196B2 (ja) * 2013-02-12 2017-04-05 株式会社リコー 管理システム、管理方法及びプログラム
WO2014186757A2 (en) * 2013-05-17 2014-11-20 Huawei Technologies Co., Ltd. Multi-tier push hybrid service control architecture for large scale conferencing over icn
JP6236962B2 (ja) * 2013-07-26 2017-11-29 株式会社リコー 通信システム、方法、通信装置およびプログラム
SG11201600650YA (en) 2013-08-08 2016-02-26 Ricoh Co Ltd Program, communication quality estimation method, information processing apparatus, communication quality estimation system, and storage medium
CN105453529B (zh) * 2013-08-09 2018-12-28 株式会社理光 管理系统、传输系统、管理方法和存储介质
JP6221489B2 (ja) 2013-08-09 2017-11-01 株式会社リコー 通信システム、管理装置、通信方法およびプログラム
JP6252740B2 (ja) * 2013-09-13 2017-12-27 株式会社リコー 伝送管理システム、管理方法、及びプログラム
JP6503654B2 (ja) * 2013-09-30 2019-04-24 株式会社リコー 通信管理システム、通信システム、及び通信方法
JP6291802B2 (ja) 2013-11-18 2018-03-14 株式会社リコー 制御システム、通信システム、プログラム、及び制御方法
JP2015119472A (ja) 2013-11-18 2015-06-25 株式会社リコー 選択システム、通信管理システム、通信システム、プログラム、及び選択方法
JP2015099954A (ja) 2013-11-18 2015-05-28 株式会社リコー 制御システム、通信システム、プログラム、及び制御方法
TWI565295B (zh) * 2013-11-18 2017-01-01 技嘉科技股份有限公司 可進行三方通話的行動裝置及其方法
JP6372156B2 (ja) * 2014-05-13 2018-08-15 株式会社リコー 接続制御システム、通信端末、通信システム、プログラム、及び接続制御方法
JP6269835B2 (ja) 2014-07-22 2018-01-31 株式会社リコー 制御システム、通信端末、通信システム、制御方法、及びプログラム
JP2016062272A (ja) 2014-09-17 2016-04-25 株式会社リコー 伝送システム、伝送管理システム、伝送方法およびプログラム
JP6405936B2 (ja) 2014-11-26 2018-10-17 株式会社リコー 管理システム、管理装置、通信システム、情報送信方法、及びプログラム
JP6458464B2 (ja) 2014-11-26 2019-01-30 株式会社リコー 制御システム、制御装置、通信システム、中継装置の選択方法、及びプログラム
JP6464696B2 (ja) 2014-11-26 2019-02-06 株式会社リコー 制御システム、通信システム、制御方法、及びプログラム
EP3226525B1 (en) * 2014-11-26 2020-04-29 Ricoh Company, Ltd. Control system, communication terminal, control device, communication system, control method, and program
JP6451276B2 (ja) 2014-12-10 2019-01-16 株式会社リコー 画像管理システム、通信端末、通信システム、画像管理方法、及びプログラム
WO2016114270A1 (ja) 2015-01-15 2016-07-21 株式会社リコー 制御システム、通信端末、通信システム、制御方法、及びプログラム
JP6536068B2 (ja) 2015-02-19 2019-07-03 株式会社リコー 制御システム、通信システム、制御方法、及びプログラム
JP2017050603A (ja) 2015-08-31 2017-03-09 株式会社リコー 管理システム、制御装置、管理方法、及びプログラム
JP6586909B2 (ja) * 2016-03-09 2019-10-09 富士通株式会社 データ管理方法及びデータ管理システム
JP6229756B2 (ja) * 2016-04-28 2017-11-15 株式会社リコー システム、管理システム、及び管理方法
JP6825342B2 (ja) * 2016-12-13 2021-02-03 株式会社リコー 通信端末、通信システム、通信方法及びプログラム
CN107332756A (zh) * 2017-06-15 2017-11-07 百度在线网络技术（北京）有限公司 一种视频社交中用户状态处理方法及装置
TWI653623B (zh) * 2018-01-24 2019-03-11 宏碁股份有限公司 顯示裝置控制系統、控制裝置、控制方法及顯示裝置

Family Cites Families (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7103806B1 (en) 1999-06-04 2006-09-05 Microsoft Corporation System for performing context-sensitive decisions about ideal communication modalities considering information about channel reliability
US7606864B2 (en) * 2000-11-10 2009-10-20 At&T Intellectual Property I, L.P. Setting and display of communication receipt preferences by users of multiple communication devices
US7631039B2 (en) 2000-12-01 2009-12-08 Radvision Ltd. Initiation and support of video conferencing using instant messaging
EP1237329B1 (en) * 2001-01-17 2007-08-29 Canon Kabushiki Kaisha Method and device for network device status notification
JP2003069563A (ja) * 2001-08-22 2003-03-07 Nippon Telegr & Teleph Corp <Ntt> 多地点間会議方法及びシステム
JP3967589B2 (ja) * 2001-12-28 2007-08-29 富士通株式会社 広告配信方法及び広告配信装置
DE10309815A1 (de) * 2003-03-05 2004-09-23 Francotyp-Postalia Ag & Co. Kg Verfahren zum Datenaustausch zwischen Datenverarbeitungseinheiten
KR100964679B1 (ko) * 2003-08-19 2010-06-22 엘지전자 주식회사 멀티미디어 방송 멀티 캐스트서비스에서 무선자원제어연결 모드 단말을 집계하는 방법
US7287076B2 (en) * 2003-12-29 2007-10-23 Microsoft Corporation Performing threshold based connection status responses
JP4655190B2 (ja) 2004-08-06 2011-03-23 ソニー株式会社 情報処理装置および方法、記録媒体、並びにプログラム
US20060173997A1 (en) * 2005-01-10 2006-08-03 Axis Ab. Method and apparatus for remote management of a monitoring system over the internet
JP4619177B2 (ja) * 2005-03-31 2011-01-26 沖電気工業株式会社 プレゼンス情報提示システム
CN1794708A (zh) 2005-07-29 2006-06-28 华为技术有限公司 呈现业务系统及发布呈现信息的方法
US7570752B2 (en) * 2005-09-23 2009-08-04 Alcatel Lucent Telephony/conference activity presence state
CN1859320A (zh) * 2005-10-26 2006-11-08 华为技术有限公司 一种提供呈现信息的方法及装置
JP4037432B2 (ja) * 2005-11-29 2008-01-23 エヌ・ティ・ティ・コムウェア株式会社 電話交換システム及び電話交換方法及び電話交換プログラム
JP5009524B2 (ja) 2005-11-30 2012-08-22 株式会社リコー 画像読取ユニット、画像読取装置、画像形成装置
RU2321183C2 (ru) * 2005-12-23 2008-03-27 Григорий Гемфриевич Дмитриев Способ и система осуществления видеоконференций
JP2007243727A (ja) 2006-03-09 2007-09-20 Ntt Communications Kk 代理応答制御方法及び統合呼制御システム
JP4859578B2 (ja) * 2006-04-20 2012-01-25 富士通株式会社 Ｉｐ電話機に関連する情報処理機器を接続するためのシステム
JP4679483B2 (ja) 2006-10-06 2011-04-27 Ｎｅｃインフロンティア株式会社 Ｉｐ通話端末切り替え装置及び方法
JP2008253694A (ja) 2007-04-04 2008-10-23 Takeshi Sano 商品陳列フック
JP4957420B2 (ja) * 2007-07-11 2012-06-20 パナソニック株式会社 電話システム及び、電話システムの自動転送規制方法
GB0713786D0 (en) * 2007-07-16 2007-08-22 Cellfire Security Technologies Call processing system
JP5003556B2 (ja) * 2008-03-28 2012-08-15 富士通株式会社 通信検知装置、通信検知方法、及び通信検知プログラム
JP2009246687A (ja) 2008-03-31 2009-10-22 Nippon Telegraph & Telephone West Corp 通信システム、通信解析装置および通信解析方法
JP2008283694A (ja) * 2008-06-06 2008-11-20 Hitachi Ltd セッション制御装置、当該セッション制御装置に適用されるソフトウェア、セッション制御方法、およびネットワークシステム
CN101686210B (zh) * 2008-09-26 2012-11-21 华为技术有限公司 一种处理即时消息报告或即时消息的方法和装置
JP5332544B2 (ja) 2008-11-21 2013-11-06 富士通株式会社 呼制御装置、呼制御システム、呼制御方法及びコンピュータプログラム
JP2010130389A (ja) * 2008-11-28 2010-06-10 Hitachi Ltd 通信システム、管理装置
JP5691396B2 (ja) 2009-12-25 2015-04-01 株式会社リコー 伝送端末、伝送端末用プログラム、プログラム提供システム、及びメンテナンスシステム
JP5655499B2 (ja) 2009-12-25 2015-01-21 株式会社リコー 伝送管理システム、伝送システム、伝送管理用プログラム、プログラム提供システム、及びメンテナンスシステム
CA2753528C (en) 2009-12-25 2014-06-17 Ricoh Company, Limited Transmission management system, transmission system, computer program product, program providing system, and maintenance system
JP5998383B2 (ja) 2010-07-28 2016-09-28 株式会社リコー 伝送管理システム、伝送システム、伝送管理方法、及びプログラム
JP5687561B2 (ja) 2010-09-06 2015-03-18 株式会社日立製作所 水処理装置
JP5048140B2 (ja) 2010-09-08 2012-10-17 シャープ株式会社 浄水器
JP5928148B2 (ja) 2012-05-18 2016-06-01 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム
JP6064367B2 (ja) 2012-05-18 2017-01-25 株式会社リコー 伝送管理システム、伝送システム、及び伝送管理システム用プログラム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
RU2013108792A (ru) 2014-09-10
US20140129641A1 (en) 2014-05-08
US20150256998A1 (en) 2015-09-10
US8782229B2 (en) 2014-07-15
WO2012014824A1 (en) 2012-02-02
US20130117373A1 (en) 2013-05-09
EP2599290A4 (en) 2014-11-12
EP2599290A1 (en) 2013-06-05
SG187023A1 (en) 2013-02-28
JP5998383B2 (ja) 2016-09-28
US9043399B2 (en) 2015-05-26
US9578491B2 (en) 2017-02-21
CA2805006A1 (en) 2012-02-02
CA2805006C (en) 2015-11-17
JP2012050063A (ja) 2012-03-08
CN103155531B (zh) 2016-05-18
CN103155531A (zh) 2013-06-12
RU2536801C2 (ru) 2014-12-27

Similar Documents

Publication Publication Date Title
EP2599290B1 (en) Transmission management system and transmission system
EP2879364B1 (en) Communication system, communication method, and computer-readable recording medium
JP5919695B2 (ja) セッション制御システム、伝送システム、及びプログラム
JP6019920B2 (ja) 管理システムおよびプログラム
JP6379496B2 (ja) 管理装置、通信システム及びプログラム
EP2850826B1 (en) Transmission management system, transmission system, and program for transmission management system
CA2871719A1 (en) Transmission management system, transmission system, and transmission management system program
EP2850817B1 (en) Relay device selection device, transmission system, and program for relay device selection device
JP6365541B2 (ja) 管理システム、プログラム、伝送システム、管理方法及び記憶媒体
JP6128177B2 (ja) 伝送システム、伝送方法、及びプログラム
JP5392431B2 (ja) 接続制御システム、伝送システム、接続制御システム用プログラム、及び、接続制御方法
JP2015154196A (ja) 伝送システム、伝送管理装置およびプログラム
JP2017059925A (ja) 管理装置、管理システム及び管理方法
JP2016178563A (ja) 伝送システム及び出力方法

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130110

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20141009

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/06 20060101ALI20141003BHEP

Ipc: H04N 7/15 20060101ALI20141003BHEP

Ipc: H04M 3/56 20060101AFI20141003BHEP

Ipc: H04M 3/42 20060101ALI20141003BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20181112

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602011063534

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04M0003560000

Ipc: H04W0008220000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/42 20060101ALI20190605BHEP

Ipc: H04W 8/22 20090101AFI20190605BHEP

Ipc: H04M 3/56 20060101ALI20190605BHEP

Ipc: H04W 76/14 20180101ALI20190605BHEP

Ipc: H04L 29/06 20060101ALI20190605BHEP

Ipc: H04N 7/15 20060101ALI20190605BHEP

INTG Intention to grant announced

Effective date: 20190627

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: RICOH COMPANY, LTD.

RIN1 Information on inventor provided before grant (corrected)

Inventor name: UMEHARA, NAOKI

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAL Information related to payment of fee for publishing/printing deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR3

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAR Information related to intention to grant a patent recorded

Free format text: ORIGINAL CODE: EPIDOSNIGR71

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

INTC Intention to grant announced (deleted)
AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

INTG Intention to grant announced

Effective date: 20191015

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011063534

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1205573

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191215

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20191120

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200220

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200221

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200220

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200320

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200412

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1205573

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191120

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011063534

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20200821

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200731

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200731

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200715

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191120

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230522

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230720

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230725

Year of fee payment: 13

Ref country code: DE

Payment date: 20230719

Year of fee payment: 13