EP2798827B1 - Communication management system, communication system, communication management method and computer-readable recording medium - Google Patents

Communication management system, communication system, communication management method and computer-readable recording medium Download PDF

Info

Publication number
EP2798827B1
EP2798827B1 EP12862181.0A EP12862181A EP2798827B1 EP 2798827 B1 EP2798827 B1 EP 2798827B1 EP 12862181 A EP12862181 A EP 12862181A EP 2798827 B1 EP2798827 B1 EP 2798827B1
Authority
EP
European Patent Office
Prior art keywords
terminal
communication
information
communication terminal
session
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
EP12862181.0A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP2798827A1 (en
EP2798827A4 (en
Inventor
Takahiro Asai
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 EP2798827A1 publication Critical patent/EP2798827A1/en
Publication of EP2798827A4 publication Critical patent/EP2798827A4/en
Application granted granted Critical
Publication of EP2798827B1 publication Critical patent/EP2798827B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/141—Systems for two-way working between two video terminals, e.g. videophone
    • H04N7/147—Communication arrangements, e.g. identifying the communication as a video-communication, intermediate storage of the signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
    • 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/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/765—Media network packet handling intermediate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/14—Systems for two-way working
    • H04N7/141—Systems for two-way working between two video terminals, e.g. videophone
    • H04N7/142—Constructional details of the terminal equipment, e.g. arrangements of the camera and the display
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H04M7/0072—Speech codec negotiation
    • 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

Definitions

  • the present invention relates to management of first and second communication terminals that transmit and receive predetermined call data.
  • WO 2011/105621 A1 describes a transmission system that transmits and receives base data, which is necessary for reproducing image and audio, and extended data, which is used for improving quality of the image and the audio, via a communication network between transmission terminals.
  • the transmission system includes: a base-data relay system that includes: a plurality of base-data relaying units for relaying the base data transmitted from a source transmission terminal among the transmission terminals to a destination transmission terminal among the transmission terminals; and a selecting unit that selects one base-data relaying unit from among the base-data relaying units for each communication between transmission terminals; and an extended-data relay system that includes: an extended-data relaying unit for relaying the extended-data transmitted from the source transmission terminal to the destination transmission terminal.
  • WO 2008/084424 A1 relates to a system and method for providing and using predetermined signaling of interoperability points for transcoded media streams.
  • a system and method for identifying when an indicated or predetermined media transcoding process results in a media stream that is compliant with an indicated interoperability point Various embodiments allow for the encoding, storage, transcoding, and transmission of a media stream, for which a transcoding process is identified and the resulting media stream of the transcoding process is associated with at least one property.
  • the signaling of the property or properties, and an identification of the transcoding process in one embodiment may be included in the media bitstream, in a file format container containing the media bitstream, or in a transmission or control protocol for transmission or control of the media bitstream.
  • the invention is defined by the subject-matter of the independent claims.
  • the dependent claims are directed to advantageous embodiments.
  • FIGS. 1 to 25 embodiments of the present invention will be described with reference to FIGS. 1 to 25 .
  • FIG. 1 is a schematic diagram of a call system according to an embodiment of the present invention.
  • a call system 1 is constructed by a plurality of call terminals (10aa, 10ab, ...), displays (120aa, 120ab, ...) of the respective call terminals (10aa, 10ab, ...), a plurality of relay devices (30a, 30b, and 30c), a call management system 50, a conversion system 80, a program providing system 90, and a maintenance system 100.
  • a plurality of routers (70a, 70b, 70c, 70d, 70ab, and 70cd) select an optimal path of call data.
  • the call terminals (10aa, 10ab, 10ac, ...), the relay device 30a, and the router 70a are connected to perform communication with one another via a local area network (LAN) 2a.
  • the call terminals (10ba, 10bb, 10bc, ...), the relay device 30b, and the router 70b are connected to perform communication with one another via a LAN 2b.
  • the LAN 2a and the LAN 2b are connected to perform communication with each other via a dedicated line 2ab including the router 70ab.
  • the LAN 2a, the LAN 2b, and the dedicated line 2ab are constructed in a predetermined region X.
  • the region X is Japan
  • the LAN 2a is constructed in a business office in Tokyo
  • the LAN 2b is constructed in a business office in Osaka.
  • the call terminals (10ca, 10cb, 10cc, ...), the relay device 30c, and the router 70c are connected to perform communication with one another via a LAN 2c.
  • the call terminals (10da, 10db, 10dc, ...), the conversion system 80, and the router 70d are connected to perform communication with one another via a LAN 2d.
  • the LAN 2c and the LAN 2d are connected to perform communication with each other via a dedicated line 2cd including the router 70cd.
  • the LAN 2c, the LAN 2d, and the dedicated line 2cd are constructed in a predetermined region Y.
  • the region Y is the USA
  • the LAN 2c is constructed in a business office in New York
  • the LAN 2d is constructed in a business office in Washington D.C.
  • the region X and the region Y are connected to perform communication with each other via the Internet 2i from the routers (70ab, 70cd).
  • a "call terminal” is referred to simply as a "terminal”
  • a "call management system” is referred to simply as a “management system”.
  • An arbitrary one of a plurality of terminals (10aa, 10ab, ...) is referred to as a “terminal 10”
  • an arbitrary one of a plurality of displays (120aa, 120ab, ...) is referred to as a “display 120”
  • an arbitrary one of a plurality of relay devices (30a, 30b, 30c) is referred to as a "relay device 30".
  • a terminal serving as a request source that requests a start of a video conference is referred to as a "request source terminal”
  • a terminal serving as a destination (a relay destination) that is a request destination is referred to as a "destination terminal”.
  • an arbitrary one of the routers (70a, 70b, 70c, 70d, 70ab, 70cd) is referred to as a "router 70".
  • the call management system 50, the program providing system 90, and the maintenance system 100 are connected to the Internet 2i.
  • the conversion system 80 is connected to the router 70d in the LAN 2d in the region Y.
  • the call management system 50, the program providing system 90, and the maintenance system 100 may be installed in the region X or the region Y or may be installed in any other region.
  • a communication network 2 of the present embodiment is constructed by 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 communication network 2 there may be a place in which communication is performed in a wireless manner such as WiFi (Wireless Fidelity) or Bluetooth (registered trademark) as well as a wired manner.
  • each terminal 10 4-set digits illustrated below each terminal 10, each relay device 30, the call management system 50, each router 70, the conversion system 80, the program providing system 90, and the maintenance system 100 simply represent an IP address in typical IPv4.
  • IPv4 may be used rather than IPv4, but the description will proceed with IPv4 for the sake of simplification of description.
  • Each terminal 10 may be used not only for a call between a plurality of business offices or a call between different rooms in the same business office but also for a call within the same room, a call between an indoor place and an outdoor place, or a call between outdoor places.
  • communication is performed by a wireless manner such as a cellular telecommunication network.
  • Each terminal 10 illustrated in FIG. 1 is a terminal that implements a user's call by transmitting and receiving call data, and is a terminal for a video conference, for example. Further, the terminal 10 performs transmission and reception of call data using a predetermined communication scheme (a call control scheme for establishing or disconnecting a connection with a destination of a call and a coding scheme for converting call data into IP packets).
  • a predetermined communication scheme a call control scheme for establishing or disconnecting a connection with a destination of a call and a coding scheme for converting call data into IP packets.
  • the examples of the call control scheme includes (1) a session initiation protocol (SIP), (2) a H.323, (3) a protocol extended from the SIP, (4) a protocol of an instant messenger, (5) a protocol using a MESSAGE method of the SIP, (6) a protocol of Internet Relay Chat (IRC), and (7) a protocol extended from a protocol of an instant messenger.
  • SIP session initiation protocol
  • IRC Internet Relay Chat
  • a protocol extended from a protocol of an instant messenger is a protocol used for (4-1) an extensible messaging and presence protocol (XMPP) or (4-2) a protocol used in ICQ (registered trademark), AIM (registered trademark), Skype (registered trademark), or the like.
  • (7) the protocol extended from the protocol of the instant messenger is jingle.
  • a terminal 10 that uses a communication scheme in which a call control scheme is a protocol of an instant messenger (or a protocol extended from a protocol of an instant messenger), and a coding scheme is a scalable video coding (SVC) is referred to as a "dedicated terminal A".
  • a terminal 10 that has an IP address that is not managed by the call management system 50 and uses a communication scheme in which at least one of the call control scheme and the coding scheme is different from one of the dedicated terminal A is referred to as a "non-dedicated terminal D".
  • dedicated terminal A is described as a terminal which is manufactured, sold, or managed by a specific company
  • non-dedicated terminal D is described as a terminal which is manufactured, sold, or managed by a company other than the specific company.
  • terminals which are manufactured, sold, or managed by different companies are likely to differ in communication scheme from each other, the description will proceed with this example.
  • a terminal which is new in a manufacturing or selling time is referred to as a "dedicated terminal A”
  • an old terminal is referred to as a "non-dedicated terminal D".
  • Each relay device 30 is a computer system that relays call data between the plurality of terminals 10.
  • the call management system 50 is a computer system that performs login authentication from the terminal 10, management of a call status of the terminal 10, management of a destination list, and management of a communication status of the relay device 30 in an integrated fashion.
  • An image of image data may be either or both of a moving image and a still image.
  • the conversion system 80 undertakes a signaling gateway that performs conversion of a call control signal and a video/audio gateway that performs encoding of call data.
  • the conversion system 80 is a gateway that performs mutual conversion of a communication scheme of call data transmitted from a request source terminal and a communication scheme (a call control scheme and a coding scheme) of call data transmitted from a destination terminal, and converts at least one of a call control scheme and a coding scheme.
  • the program providing system 90 is a computer system that provides programs to be used to the terminal 10, the relay device 30, the call management system 50, the conversion system 80, and the maintenance system 100 via the communication network 2, respectively.
  • the maintenance system 100 is a computer system that performs maintenance, management, or repair of at least one of the terminal 10, the relay device 30, the call management system 50, the conversion system 80, and the program providing system 90.
  • the maintenance system 100 remotely performs maintenance, that is, maintenance, management, or repair of at least one of the terminal 10, the relay device 30, the call management system 50, the conversion system 80, and the program providing system 90 via the communication network 2.
  • the maintenance system 100 performs maintenance such as management of a model number, a manufacturing number, a sales destination, a repair check, or a failure history of at least one of the terminal 10, the relay device 30, the call management system 50, the conversion system 80, and the program providing system 90 without the communication network 2.
  • FIG. 2 is a conceptual diagram illustrating a communication status when a call is implemented between call terminals having the same communication scheme.
  • the call system 1 performs communication of call data using a video coding standard of H.264/SVC. Specifically, in the call system 1, a management communication session sei to transmit and receive various kinds of management information is established between a request source terminal of a dedicated terminal A and a destination terminal of a dedicated terminal A through the call management system 50 as illustrated in FIG. 2 . Further, four communication sessions to transmit and receive four pieces of data, that is, high-resolution image data, moderate-resolution image data, low-resolution image data, and audio data through the relay device 30 are established between the request source terminal and the destination terminal.
  • a management communication session sei to transmit and receive various kinds of management information is established between a request source terminal of a dedicated terminal A and a destination terminal of a dedicated terminal A through the call management system 50 as illustrated in FIG. 2 .
  • four communication sessions to transmit and receive four pieces of data that is, high-resolution image data, moderate-resolution image data, low-resolution image data, and audio data through the relay device 30 are established between the request source terminal and
  • FIG. 2 four communication sessions established between the request source terminal and the relay device 30 are represented as a first communication session sed1 for call data. Further, four communication sessions established between the relay device 30 and the destination terminal are represented as a second communication session sed2 for call data.
  • FIG. 3 is a conceptual diagram illustrating an image quality of image data transmitted and received according to the SVC standard in FIG. 2 .
  • low-resolution image including 160 ⁇ 120 pixels as illustrated in (a) of FIG. 3 as a base image
  • moderate-resolution image including 320 ⁇ 240 pixels as illustrated in (b) of FIG. 3
  • high-resolution image including 640 ⁇ 480 pixels as illustrated in (c) of FIG. 3 .
  • low-quality image data including low-resolution image data as a base image is relayed by the relay device 30.
  • moderate-quality image data including low-resolution image data serving as a base image and moderate-resolution image data is relayed by the relay device 30.
  • high-quality image data including low-resolution image data serving as a base image, moderate-resolution image data, and high-resolution image data is relayed by the relay device 30.
  • FIG. 4 is a conceptual diagram illustrating a communication status when a call is implemented between call terminals having different communication schemes.
  • the call system 1 performs communication of call data using a video coding standard of H.264/SVC and a video coding standard of H.264/AVC (Advanced Video Coding). Specifically, in the call system 1, a management communication session sei to transmit and receive various kinds of management information is established between a request source terminal of a dedicated terminal A and a destination terminal of a non-dedicated terminal D through the call management system 50 as illustrated in FIG. 4 .
  • a management communication session sei to transmit and receive various kinds of management information is established between a request source terminal of a dedicated terminal A and a destination terminal of a non-dedicated terminal D through the call management system 50 as illustrated in FIG. 4 .
  • four communication sessions to transmit and receive four pieces of data that is, high-resolution image data, moderate-resolution image data, low-resolution image data, and audio data based on H.264/SVC through the relay device 30 are established between the request source terminal (an example of a first communication terminal) and the conversion system 80.
  • the request source terminal an example of a first communication terminal
  • the conversion system 80 four communication sessions established between the request source terminal and the relay device 30 are represented as a first communication session sedll for call data.
  • four communication sessions established between the relay device 30 and the conversion system 80 are represented as a second communication session sed12 for call data.
  • two communication sessions to transmit and receive two pieces of data that is, moderate-resolution image data and audio data based on H.264/AVC are established between the conversion system 80 and the destination terminal (an example of a second communication terminal).
  • two communication sessions established between the conversion system 80 and the destination terminal are represented as a third communication session sed13 for call data.
  • FIG. 5 is a conceptual diagram illustrating an image quality of image data transmitted and received according to the AVC standard in FIG. 4 .
  • image data of three resolutions illustrated in (a) to (c) of FIG. 3 are transmitted and received as in the first communication session sed1 and the second communication session sed2 illustrated in FIG. 2 .
  • moderate-resolution image data illustrated in FIG. 5 is transmitted and received.
  • FIG. 6 is an external appearance diagram of a call terminal according to the present embodiment.
  • the terminal 10 includes a housing 1100, an arm 1200, and a camera housing 1300.
  • a front sidewall surface 1110 of the housing 1100 is provided with an air intake surface (not illustrated) formed by a plurality of air intake holes
  • a rear sidewall surface 1120 of the housing 1100 is provided with an exhaust surface 1121 formed by a plurality of exhaust holes.
  • a sound pick-up hole 1131 is formed on a right sidewall surface 1130 of the housing 1100, and a voice, a sound, a noise, or the like are picked up by a built-in microphone 114 which will be described later.
  • An operation panel 1150 is formed on the right sidewall surface 1130 of the housing 1100, and the operation panel 1150 is provided with a plurality of operation buttons 108a to 108e, a power supply switch 109, and an alarm lamp 119, which will be described later, and also provided with an output surface 1151 formed by a plurality of audio output holes through which a sound from a built-in speaker 115, which will be described later, is output.
  • An accommodating unit 1160 serving as a concave portion that accommodate the arm 1200 and the camera housing 1300 is formed on a left sidewall surface 1140 side of the housing 1100.
  • the right sidewall surface 1130 of the housing 1100 is provided with a plurality of connection ports 1132a to 1132c used to electrically connect a cable with a display I/F 117 which will be described later.
  • the left sidewall surface 1140 of the housing 1100 is provided with a connection port (not illustrated) used to eclectically connect a cable 120c for the display 120 to an external device connection I/F 118 which will be described later.
  • connection port 1132 an arbitrary one of the operation buttons 108a to 108e is referred to as an "operation button 108"
  • connection port 1132 an arbitrary one of the connection ports 1132a to 1132c is referred to as a "connection port 1132”.
  • the arm 1200 is attached to the housing 1100 through a torque hinge 1210, and the arm 1200 is configured to be vertically rotatable with a range of a tilt angle ⁇ 1 of 135° with respect to the housing 1100.
  • FIG. 6 illustrates a state in which the tilt angle ⁇ 1 is 90°.
  • a built-in camera 112 is disposed in the camera housing 1300, and can image the user, a document, a room, or the like.
  • the camera housing 1300 is provided with a torque hinge 1310.
  • the camera housing 1300 is attached to the arm 1200 through the torque hinge 1310.
  • the camera housing 1300 is configured to be horizontally rotatable in a range of a pan angle of ⁇ 2 of ⁇ 180° with respect to the arm 1200 and vertically rotatable in a range of a tilt angle ⁇ 3 of ⁇ 45° with respect to the arm 1200 when the state illustrated in FIG. 6 is 0°.
  • Each of the relay device 30, the call management system 50, the conversion system 80, the program providing system 90, and the maintenance system 100 has the same external appearance as a general server computer, and thus a description thereof will not be made.
  • FIG. 7 is a hardware configuration diagram of a terminal according to the present embodiment.
  • the terminal 10 includes a central processing unit (CPU) 101 that controls an operation of the terminal 10 in general, a read only memory (ROM) 102 that stores a program used to drive the CPU 101 such as an initial program loader (IPL), a random access memory (RAM) 103 used as a work area of the CPU 101, a flash memory 104 that stores various kinds of data such as a program for the terminal 10, image data, and audio data, a solid state drive (SSD) 105 that controls reading or writing of various kinds of data on the flash memory 104 according to control of the CPU 101, a media drive 107 that controls reading or writing (storing) of data on a recording medium 106 such as a flash memory, the operation button 108 operated to select a destination of the terminal 10, the power supply switch 109 used to power on or off the terminal 10, and a network I/F 111 used to transmit data using the communication network 2.
  • CPU central processing unit
  • ROM read only memory
  • the terminal 10 includes the built-in camera 112 that images a subject according to control of the CPU 101 and obtains image data, an imaging element I/F 113 that controls driving of the camera 112, the built-in microphone 114 that receives a sound, the built-in speaker 115 that outputs a sound, an audio input output I/F 116 that processes an input and an output of an audio signal between the microphone 114 and the speaker 115 according to control of the CPU 101, the display I/F 117 that transmits image data to the external display 120 according to control of the CPU 101, the external device connection I/F 118 used to connect various kinds of external devices, the alarm lamp 119 that notifies of abnormality of various kinds of functions of the terminal 10, and a bus line 110 such as an address bus or a data bus used to electrically connect the above-mentioned components as illustrated in FIG. 5 .
  • a bus line 110 such as an address bus or a data bus used to electrically connect the above-mentioned components as illustrated in FIG. 5 .
  • the display 120 is a display unit configured with a liquid crystal display (LCD) device or an organic EL device that displays a subject image, an operation icon, or the like.
  • the display 120 is connected to the display I/F 117 through the cable 120c.
  • the cable 120c may be a cable for an analog RGB (VGA) signal, a cable for a component video, or a cable for high-definition multimedia interface (HDMI) or digital video interface (DVI).
  • the camera 112 includes a lens and a solid-state imaging element that converts light into electric charges and digitizes a subject image (video), and a complementary metal oxide semiconductor (CMOS), a charge coupled device (CCD), or the like is used as the solid-state imaging element.
  • CMOS complementary metal oxide semiconductor
  • CCD charge coupled device
  • An external device such as an external camera, an external microphone, and an external speaker may be electrically connected to the external device connection I/F 118 through a universal serial bus (USB) cable inserted into the connection port 1132 of the housing 1100 illustrated in FIG. 6 .
  • USB universal serial bus
  • the external camera takes priority over the built-in camera 112 and is driven according to control of the CPU 101.
  • the external microphone or the external speaker takes priority over the built-in microphone 114 or the built-in speaker 115 and is driven according to control of the CPU 101.
  • the recording medium 106 is configured to be removably attached to the terminal 10. As long as non-volatile memory that performs reading or writing of data according to control of the CPU 101, the recording medium 106 is not limited to the flash memory 104 and may include electrically erasable and programmable ROM (EEPROM) or the like.
  • EEPROM electrically erasable and programmable ROM
  • FIG. 8 is a hardware configuration diagram of a management system according to the present embodiment of the present invention.
  • the call management system 50 includes a CPU 201 that controls an operation of the call management system 50 in general, a ROM 202 that stores a program used for driving of the CPU 201 such as an IPL, a RAM 203 used as a work area of the CPU 201, and a hard disk (HD) 204 that stores various kinds of data such as a program for the call management system 50, a hard disk drive (HDD) 205 that controls reading or writing of various kinds of data on the HD 204 according to control of the CPU 201, a media drive 207 that controls reading or writing (storing) of data on a recording medium 206 such as a flash memory, a display 208 that displays various kinds of information such as a cursor, a menu, a window, a text, or an image, a network I/F 209 that performs data communication via the communication network 2, a keyboard 211 including a plurality of keys used to input a
  • each HD 204 stores various kinds of data such as a program that controls each of the relay device 30, the conversion system 80, the program providing system 90, and the maintenance system 100.
  • the programs for the terminal 10, the relay device 30, the conversion system 80, the program providing system 90, and the maintenance system 100 may be recorded in a computer readable recording medium (the recording medium 106 or the like) as a file of an installable format or an executable form, and distributed.
  • a computer readable recording medium there are a compact disc recordable (CD-R), a digital versatile disk (DVD), a Blu-ray disc, and the like.
  • FIG. 9 is a functional block diagram of the terminal 10, the relay device 30, the call management system 50, and the conversion system 80 that configure a part of the call system 1 according to the present embodiment.
  • the terminal 10, the relay device 30, the call management system 50, and the conversion system 80 are connected to perform data communication with one another via the communication network 2.
  • the terminal 10 includes a transceiving unit 11, an operation input receiving unit 12, a login requesting unit 13, an imaging unit 14, an audio input unit 15a, an audio output unit 15b, a display control unit 16, a delay detecting unit 17, and a storing/reading processing unit 19.
  • Each unit is any one of the components illustrated in FIG. 7 and is a function or a device that is operated and implemented according to an instruction from the CPU 101 that follows a program for the terminal 10 developed from the flash memory 104 onto the RAM 103.
  • the terminal 10 includes a storage unit 1000 that is constructed by the RAM 103 illustrated in FIG. 7 and the flash memory 104 illustrated in FIG. 7 .
  • each functional configuration of the terminal 10 will be described in detail with reference to FIGS. 7 and 9 .
  • a relation with a main component for implementing each functional configuration of the terminal 10 among the components illustrated in FIG. 7 will be also described.
  • the transceiving unit 11 of the terminal 10 illustrated in FIG. 9 is implemented by the network I/F 111 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 , and transmits or receives various kinds of data (or information) to or from another terminal, device, or system via the communication network 2.
  • the transceiving unit 11 starts to receive each piece of status information representing a status of each terminal serving a destination candidate through the call management system 50 before starting a call with a desired destination terminal.
  • the status information represents not only an operation status (an online status or an offline status) of each terminal 10 but also a detailed status representing whether each terminal 10 is available or busy, or whether or not the user has left his/her seat even though each terminal 10 is online.
  • the status information represents not only the operation status of each terminal 10 but also various statuses such as a status representing that the cable 120c is removed from the terminal 10, a status in which a sound is output but an image is not output, and a status (MUTE) in which a sound is not output.
  • a status representing that the cable 120c is removed from the terminal 10 a status in which a sound is output but an image is not output
  • a status (MUTE) in which a sound is not output a sound is not output.
  • the operation input receiving unit 12 is implemented by the operation button 108 and the power supply switch 109 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 , and receives various kinds of inputs made by the user. For example, when the user turned on the power supply switch 109 illustrated in FIG. 7 , the operation input receiving unit 12 illustrated in FIG. 9 receives a power-on input and turns on power.
  • the login requesting unit 13 is implemented according to an instruction from the CPU 101 illustrated in FIG. 7 , and automatically transmits login request information to request a login and a current IP address of the request source terminal from the transceiving unit 11 to the call management system 50 via the communication network 2 when the power-on input is received. Further, when the user turned off the power supply switch 109 that is in an on state, the transceiving unit 11 transmits status information representing power off to the call management system 50, and then the operation input receiving unit 12 completely turned off the power. Thus, the call management system 50 side can detect that the terminal 10 has transitioned from the power-on state to the power-off state.
  • the imaging unit 14 is implemented by the camera 112 and the imaging element I/F 113 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 , and images a subject and outputs obtained image data.
  • the audio input unit 15a is implemented by the audio input output I/F 116 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 , and converts the user's sound into an audio signal through the microphone 114 and receives audio data related to the audio signal.
  • the audio output unit 15b is implemented by the audio input output I/F 116 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 , and outputs an audio signal related to audio data to the speaker 115 and outputs a sound from the speaker 115.
  • the display control unit 16 is implemented by the display I/F 117 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 , and performs control such that received image data having different resolutions are combined and combined image data will be transmitted to the display 120 as will be described later.
  • the display control unit 16 can cause the destination list to be displayed on the display 120 by transmitting information of the list received from the call management system 50 to the display 120.
  • the delay detecting unit 17 is implemented according to an instruction from the CPU 101 illustrated in FIG. 7 , and detects a delay time (ms) of image data or audio data transmitted from another terminal 10 through the relay device 30.
  • the storing/reading processing unit 19 is implemented by the SSD 105 illustrated in FIG. 7 according to an instruction from the CPU 101 illustrated in FIG. 7 or is implemented according to an instruction from the CPU 101, and performs a process of storing various kinds of data in the storage unit 1000 or reading various kinds of data stored in the storage unit 1000.
  • the storage unit 1000 stores terminal identification (ID) used to identify the terminal 10, a password, and the like. Further, image data and audio data received when a call with the destination terminal is performed are overwritten and stored in the storage unit 1000 each time image data and audio data are received. Of these, an image is displayed on the display 120 based on image data which is not overwritten, and a sound is output from the speaker 115 based on audio data that is not overwritten.
  • the terminal ID and a relay device ID (which will be described later) of the present embodiment represent identification information, such as a language, a text, a symbol, or a sign, which is used to uniquely identify the terminal 10 and the relay device 30, respectively.
  • the terminal ID and the relay device ID may be identification information in which at least two of a language, a text, a symbol, and a sign are combined.
  • the relay device 30 includes a transceiving unit 31, a status detecting unit 32, a data quality verifying unit 33, a changed quality managing unit 34, a data quality changing unit 35, and a storing/reading processing unit 39.
  • Each unit is any one of the components illustrated in FIG. 8 and is a function or a device that is operated and implemented according to an instruction from the CPU 201 that follows a program for the relay device 30 developed from the HD 204 onto the RAM 203.
  • the relay device 30 includes a storage unit 3000 that is constructed by the RAM 203 illustrated in FIG. 8 and the HD 204 illustrated in FIG. 8 .
  • FIG. 10 is a conceptual diagram illustrating a changed quality management table.
  • a changed quality management database (DB) 3001 configured with a changed quality management table illustrated in FIG. 10 is constructed.
  • DB changed quality management database
  • an IP address of the terminal 10 serving as a relay destination (destination) of image data is managed in association with an image quality of image data which is relayed to this relay destination by the relay device 30.
  • each functional configuration of the relay device 30 will be described in detail.
  • a relation with a main component for implementing each functional configuration of the relay device 30 among the components illustrated in FIG. 8 will be also described.
  • the transceiving unit 31 of the relay device 30 illustrated in FIG. 9 is implemented by the network I/F 209 illustrated in FIG. 8 according to an instruction from the CPU 201 illustrated in FIG. 8 , and transmits or receives various kinds of data (or information) to or from another terminal, device, or system via the communication network 2.
  • the transceiving unit 31 performs initialization of a communication session in an own device.
  • the transceiving unit 31 transmits session start instruction information to instruct a start of a communication session (a first communication session) to a destination represented by an IP address of the request source terminal among IP addresses received by the transceiving unit 31. Further, the transceiving unit 31 transmits session start instruction information to instruct a start of a communication session (a second communication session) and an IP address of the destination terminal to a destination represented by an IP address of the conversion system 80 among IP addresses received by the transceiving unit 31.
  • the status detecting unit 32 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and detects the operation status of the relay device 30 having the status detecting unit 32. As the operation status, there are an "online” state, an "offline” state, a “busy” state, and a “temporary stop” state.
  • the data quality verifying unit 33 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and verifies an image quality of image data to be relayed by searching the changed quality management table (see FIG. 10 ) using the IP address of the destination terminal as a search key and extracting an image quality of corresponding image data to be relayed.
  • the changed quality managing unit 34 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and changes content of the changed quality management table (see FIG. 10 ) based on quality information (which will be described later) transmitted from the call management system 50. For example, while a video conference is being performed such that high-quality image data is transmitted and received between the request source terminal (the terminal 10aa) having the terminal ID of "Olaa” and the destination terminal (the terminal 10ba) having the terminal ID of "Olba", when the request source terminal (the terminal 10bb) and the destination terminal (the terminal 10ca), which perform another video conference, start a video conference via the communication network 2 and thus image data is received with a delay by the destination terminal (the terminal 10ba), the relay device 30 lowers an image quality of image data received until now from a high image quality to a moderate image quality.
  • content of the changed quality management table (see FIG. 10 ) is changed based on the quality information represented by the moderate image quality such that an image quality of image data to be relayed by the relay device 30 is lowered from the high image quality to the moderate image quality.
  • the data quality changing unit 35 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , an image quality of image data transmitted from a transmission source terminal is changed based on the changed content of the changed quality management table (see FIG. 10 ).
  • the storing/reading processing unit 39 is implemented by the HDD 205 illustrated in FIG. 8 according to an instruction from the CPU 201 illustrated in FIG. 8 , and performs a process of storing various kinds of data in the storage unit 3000 or reading various kinds of data stored in the storage unit 3000.
  • the call management system 50 includes a transceiving unit 51, a terminal authenticating unit 52, a status managing unit 53, an extracting unit 54, a determining unit 55, a session managing unit 56, a quality deciding unit 57, a delay time managing unit 58, and a storing/reading processing unit 59.
  • Each unit is any one of the components illustrated in FIG. 8 and is a function or a device that is operated and implemented according to an instruction from the CPU 201 that follows a program for the call management system 50 developed from the HD 204 onto the RAM 203.
  • the call management system 50 includes a storage unit 5000 that is constructed by the HD 204 illustrated in FIG. 8 .
  • FIG. 11 is a conceptual diagram illustrating a relay device management table.
  • a relay device management DB 5001 configured with a relay device management table illustrated in FIG. 11 is constructed.
  • an operation status of each relay device 30, a reception date and time in which status information represented by the operation status is received by the call management system 50, an IP address of the relay device 30, and a maximum data call rate (Mbps) in the relay device 30 are managed in association with the relay device ID of each relay device 30.
  • 11 represents that the operation status of a relay device 30a having the relay device ID of "111a” is "online”, a date and time in which the status information is received by the call management system 50 is "13:00, November 10, 2011”, the IP address of the relay device 30a is "1.2.1.2”, and the maximum data call rate in the relay device 30a is 100 Mbps.
  • FIG. 12 is a conceptual diagram illustrating a terminal information management table.
  • a terminal information management DB 5002 configured with a terminal information management table illustrated in FIG. 12 is constructed.
  • a password for authentication, a model number of the terminal 10, a serial number of the terminal 10, and a communication scheme of the terminal 10 are managed in association with each terminal ID of each of all terminals 10 managed by the call management system 50.
  • the terminal information management table illustrated in FIG. 12 represents that a terminal ID of a terminal 10aa is "01aa”, a password is "aaaa”, a model number is "9001", a serial number is "2001”, and a communication scheme is "dedicated”.
  • a communication scheme represented as "dedicated” is a communication scheme used by the dedicated terminal A illustrated in FIGS. 2 and 4 .
  • a communication scheme represented as "non-dedicated 1" is a communication scheme used by the non-dedicated terminal D illustrated in FIG. 4 .
  • a communication scheme represented as "non-dedicated 2" is a communication scheme other than communication schemes which are respectively used by the dedicated terminal A and the non-dedicated terminal D.
  • FIG. 13 is a conceptual diagram illustrating a terminal status management table.
  • a terminal status management DB 5003 configured with a terminal status management table illustrated in FIG. 13 is constructed.
  • the terminal status management table a terminal name of each terminal 10 set as a destination, an operation status of each terminal 10, a reception date and time in which login request information (which will be described later) is received by the call management system 50, and an IP address of the terminal 10 are managed in association with the terminal ID of each terminal 10.
  • the IP address of the terminal 10 other than the dedicated terminal A that is, the IP address of the non-dedicated terminal D or the like is not a management target and thus not managed.
  • FIG. 14 is a conceptual diagram illustrating a destination list management table.
  • a destination list management DB 5004 configured with a destination list management table illustrated in FIG. 14 is constructed.
  • terminals ID of destination terminals that are registered as a destination terminal candidate are managed in association with a terminal ID of a request source terminal that requests a start of a call.
  • the destination list management table illustrated in FIG. 14 illustrates the destination list management table illustrated in FIG.
  • destination terminal candidates that can request a start of a call from a request source terminal (a terminal 10aa) having the terminal ID of "Olaa” are a terminal 10ab having the terminal ID of "01ab", a terminal 10ba having the terminal ID of "Olba”, and a terminal 10bb having the terminal ID of "01bb”.
  • a request source terminal requests the call management system 50 to add or delete, the destination terminal candidate is added or deleted and updated.
  • the IP address of the terminal 10 other than the dedicated terminal A is a management target, but in the destination list management table (see FIG. 14 ), the terminal ID of the terminal 10 other than the dedicated terminal A is a management target.
  • FIG. 15 is a conceptual diagram illustrating a session management table.
  • a session management DB 5005 configured with a session management table illustrated in FIG. 15 , is constructed.
  • the relay device ID of the relay device 30 used to relay image data and audio data the terminal ID of the request source terminal, the terminal ID of the destination terminal, a reception delay time (ms) when image data is received in the destination terminal, and a reception date and time in which delay time information representing the delay time is transmitted from the destination terminal and received by the call management system 50 are managed in association with one another.
  • the relay device 30a (the relay device ID "111a") relays image data and audio data between the request source terminal (a terminal 10aa) having the terminal ID "Olaa” and the destination terminal (a terminal 10ca) having the terminal ID of "01ca", and the delay time of image data at "14:00, November 10, 2011" in the destination terminal (the terminal 10ca) is 200 (ms).
  • the reception date and time of the delay time information may be managed based on the delay time information transmitted from the request source terminal other than the destination terminal.
  • the reception date and time of the delay time information is managed based on the delay time information transmitted from the terminal 10 at the reception side of image data and audio data.
  • FIG. 16 is a conceptual diagram illustrating a conversion management table.
  • a conversion management DB 5006 configured with a conversion management table illustrated in FIG. 16 is constructed.
  • the terminal ID of the non-dedicated terminal including terminals of non-dedicated 1 and non-dedicated 2
  • the IP address of the conversion system 80 and the IP address of the non-dedicated terminal are managed in association with one another.
  • FIG. 17 is a conceptual diagram illustrating a quality management table.
  • a quality management DB 5007 configured with a quality management table illustrated in FIG. 17 is constructed.
  • the delay time information representing the delay time of image data and image quality information representing an image quality of image data are managed in association with each other such that as the delay time (ms) of image data the request source terminal or the destination terminal increases, an image quality of image data to be relayed by the relay device 30 decreases.
  • each functional configuration of the call management system 50 will be described in detail.
  • a relation with a main component for implementing each functional configuration of the call management system 50 among the components illustrated in FIG. 8 will be also described.
  • the transceiving unit 51 is implemented by the network I/F 209 illustrated in FIG. 8 according to an instruction from the CPU 201 illustrated in FIG. 8 , and transmits or receives various kinds of data (or information) to or from another terminal, device, or system via the communication network 2.
  • the terminal authenticating unit 52 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , searches the terminal information management table (see FIG. 12 ) using the terminal ID and the password included in the login request information received through the transceiving unit 51 as the search key, and performs terminal authentication by determining whether or not the same terminal ID and password are managed in the terminal information management table.
  • the status managing unit 53 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and manages the terminal ID of the request source terminal, the operation status of the request source terminal, the reception date and time in which login request information is received by the call management system 50, and the IP address of the request source terminal to be stored in the terminal status management table (see FIG. 13 ) in association with one another in order to manage the operation status of the request source terminal that has made the login request. Further, when the user switches the power supply switch 109 of the terminal 10 from an on state to an off state, the status managing unit 53 changes the operation status of the terminal status management table (see FIG. 13 ) representing the online state to the offline state based on the status information representing the power off transmitted from the terminal 10.
  • the extracting unit 54 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and searches each management DB constructed in the storage unit 5000 using various kinds of search keys and extracts data (information) corresponding to the search keys as a search result.
  • the extracting unit 54 searches the destination list management table (see FIG. 14 ) using the terminal ID of the request source terminal that has made the login request as a key, and extracts the terminal ID of the destination terminal candidate that can perform a call with the request source terminal. Further, the extracting unit 54 searches the terminal status management table (see FIG. 13 ) using the terminal ID of the destination terminal candidate as the search key and extracts the operation status for each terminal ID. Thus, the extracting unit 54 can acquire the operation status of the destination terminal candidate that can perform a call with the request source terminal that has made the login request.
  • the extracting unit 54 searches the destination list management table (see FIG. 14 ) using the terminal ID of the request source terminal that has made the login request as a key, and extracts the terminal ID of another request source terminal in which the terminal ID of the request source terminal is registered as the destination terminal candidate. Further, the extracting unit 54 searches the terminal status management table (see FIG. 13 ) using the terminal ID as the search key, and acquires the operation status of the request source terminal that has made the login request.
  • the extracting unit 54 searches the terminal status management table (see FIG. 13 ) using the terminal ID of the terminal 10 received by the transceiving unit 51 as the search key, and extracts the IP address of the corresponding terminal 10. Further, the extracting unit 54 searches the terminal information management table (see FIG. 12 ) using the terminal ID of the terminal 10 received by the transceiving unit 51 as the search key, and extracts corresponding communication scheme information. Further, the extracting unit 54 searches the conversion management table (see FIG. 16 ) using the terminal ID of the terminal 10 received by the transceiving unit 51 as the search key, and extracts the IP address of the corresponding conversion system 80 and the IP address of the terminal 10 related to the received terminal ID.
  • the extracting unit 54 searches the quality management table (see FIG. 17 ) using the delay time information received by the transceiving unit 51 as the search key, and extracts image quality information of corresponding image data.
  • the extracting unit 54 searches the terminal status management table (see FIG. 13 ) using the IP address of the destination terminal as the search key, and extracts the corresponding terminal ID.
  • the determining unit 55 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and determines whether or not the communication scheme used by the terminal 10 is the communication scheme used by the dedicated terminal A.
  • the session managing unit 56 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and manages the relay device ID of the relay device 30 used to relay call data, the terminal ID of the request source terminal, the terminal ID of the destination terminal, the reception delay time (ms) when image data is received by the destination terminal, and a reception date and time in which the delay time information representing the delay time is transmitted from the destination terminal and received by the call management system 50 to be stored in the session management table (see FIG. 15 ) of the storage unit 5000 in association with one another. Further, the session managing unit 56 generates a session ID used to establish a communication session.
  • the quality deciding unit 57 decides an image quality of image data to be relayed by the relay device 30 based on the image quality information of image data extracted by the extracting unit 54.
  • the delay time managing unit 58 is implemented according to an instruction from the CPU 201 illustrated in FIG. 8 , and manages the delay time represented by the delay time information to be stored in a delay time field portion of a record including a terminal ID extracted by the extracting unit 54 in the session management table of the session management DB 5005 (see FIG. 15 ).
  • the storing/reading processing unit 59 is implemented by the HDD 205 illustrated in FIG. 8 according to an instruction from the CPU 201 illustrated in FIG. 8 , and performs a process of storing various kinds of data in the storage unit 5000 or reading various kinds of data stored in the storage unit 5000.
  • the conversion system 80 includes a transceiving unit 81, a communication scheme converting unit 82, and a storing/reading processing unit 89. Each unit is any one of the components illustrated in FIG. 8 and is a function or a device that is operated and implemented according to an instruction from the CPU 201 that follows a program for the conversion system 80 developed from the HD 204 onto the RAM 203. Further, the conversion system 80 includes a storage unit 8000 that is constructed by the RAM 203 illustrated in FIG. 8 and/or the HD 204 illustrated in FIG. 8 . The storage unit 8000 stores conversion rule data used to convert communication data.
  • each functional configuration of the conversion system 80 will be described with reference to FIGS. 8 and 9 .
  • a relation with a main component for implementing each functional configuration of the conversion system 80 among the components illustrated in FIG. 8 will be also described.
  • the transceiving unit 81 of the conversion system 80 illustrated in FIG. 9 is implemented by the network I/F 209 illustrated in FIG. 8 according to an instruction from the CPU 201 illustrated in FIG. 8 , and transmits or receives various kinds of data (or information) to or from another terminal, device, or system via the communication network 2. Further, the transceiving unit 81 transmits session start instruction information to instruct a start of a communication session (a third communication session) to a destination represented by destination information transmitted by the relay device 30. In addition, an IP address, a uniform resource identifier (URI), or the like may be used as the destination information.
  • URI uniform resource identifier
  • the communication scheme converting unit 82 mutually converts a communication scheme of call data transmitted from the request source terminal and communication scheme of call data transmitted from the destination terminal based on communication scheme conversion rule data stored in the storage unit 8000.
  • the storing/reading processing unit 89 is implemented by the HDD 205 illustrated in FIG. 8 according to an instruction from the CPU 201 illustrated in FIG. 8 , and performs a process of storing various kinds of data stored in the storage unit 8000 or reading various kinds of data stored in the storage unit 8000.
  • FIG. 18 is a sequence diagram illustrating a process of a preliminary step to start a call between terminals.
  • various kinds of pieces of management information are transmitted and received according to the management communication session sei illustrated in FIG. 2 .
  • the operation input receiving unit 12 illustrated in FIG. 9 receives the power-on input and turns on the power as illustrated in FIG. 18 (step S21). Then, when the power-on input is received, the login requesting unit 13 automatically transmits login request information representing a login request to the call management system 50 via the communication network 2 through the transceiving unit 11 (step S22).
  • the login request information includes a terminal ID used to identify an own device serving as the request source terminal (the terminal 10aa) and a password.
  • the terminal ID and the password are data which is read from the storage unit 1000 through the storing/reading processing unit 19 and transmitted to the transceiving unit 11. Further, when the login request information is transmitted from the request source terminal (the terminal 10aa) to the call management system 50, the call management system 50 at the reception side can detect the IP address of the request source terminal (the terminal 10aa) at the transmission side.
  • the terminal authenticating unit 52 of the call management system 50 searches the terminal information management table (see FIG. 12 ) using the terminal ID and the password included in the login request information received through the transceiving unit 51 as the search key, and performs terminal authentication by determining whether or not the same terminal ID and password are managed in the terminal information management DB 5002 (step S23). Since the same terminal ID and password are managed by the terminal authenticating unit 52, when it is determined that there is a login request from the terminal 10 having an appropriate right of usage, the status managing unit 53 stores the terminal ID of the request source terminal (the terminal 10aa), the operation status, the reception date and time in which login request information is received, and the IP address of the request source terminal (the terminal 10aa) in the terminal status management table (see FIG.
  • the operation status "online”, the reception date and time "2011.11.10.13:40", and the IP address "1.2.1.3" of the request source terminal (the terminal 10aa) are managed in associated with one another using the terminal ID "01aa”.
  • the transceiving unit 51 of the call management system 50 transmits authentication result information representing the authentication result obtained by the terminal authenticating unit 52 to the request source terminal (the terminal 10aa) that has made the login request via the communication network 2 (step S25).
  • the description will proceed with an example in which the terminal authenticating unit 52 determines that the terminal 10 has an appropriate right of usage.
  • the extracting unit 54 of the call management system 50 searches the destination list management table (see FIG. 14 ) using the terminal ID "Olaa" of the request source terminal (the terminal 10aa) that has made the login request as the search key, and extracts the terminal ID of the destination terminal candidate that can perform communication with the request source terminal (the terminal 10aa) (step S26).
  • the terminal IDs (01ab", “Olba”, ...) of the destination terminals (the terminals 10ab, 10ba, ...) corresponding to the terminal ID "Olaa" of the request source terminal (the terminal 10aa) are assumed to be extracted.
  • the extracting unit 54 searches the terminal status management table (see FIG. 13 ) using the terminal IDs ("01ab”, “Olba”, ...) of the destination terminal candidate extracted in step S26 as the search key and acquires the operation statuses of the terminals (10ab, 10ba, %) by reading the operation status ("offline", "online”, ...) of each terminal ID (step S27).
  • the transceiving unit 51 transmits destination status information including the terminal IDs ("Olab”, “Olba”, ...) used in step S27 as the search key and the operation status ("offline”, "online”, %) of the corresponding destination terminals (the terminals 10ab, 10ba, 7) to the request source terminal (the terminal 10aa) via the communication network 2 (step S28).
  • the request source terminal (the terminal 10aa) can detect the current operation statuses ("offline”, "online”, %) of the terminals (10ab, 10ba, ...) serving as the destination terminal candidate that can perform communication with the request source terminal (the terminal 10aa).
  • the extracting unit 54 searches the destination list management table (see FIG. 14 ) using the terminal ID "Olaa" of the request source terminal (the terminal 10aa) that has made the login request as the search key, and extracts the terminal IDs of other request source terminals in which the terminal ID "Olaa" of the request source terminal (the terminal 10aa) is registered as the destination terminal candidate (step S29).
  • the destination list management table illustrated in FIG. 14 "Olba”, “01ca”, and "01da” are extracted as the terminal IDs of other request source terminal.
  • the description will proceed with the example in which "Olba”, “01ca”, and "01da” are extracted as the terminal IDs of other request source terminals.
  • the extracting unit 54 searches the terminal status management table (see FIG. 13 ) using the terminal ID "Olaa" of the request source terminal (the terminal 10aa) that has made the login request as the search key, and acquires the operation status of the request source terminal (the terminal 10aa) that has made the login request (step S30). Then, the transceiving unit 51 transmits the destination status information including the terminal ID "Olaa” of the request source terminal (the terminal 10aa) acquired in step S30 and the operation status "online” to the terminals (10ba and 10ca) whose operation status is set to "online” in the terminal status management table (see FIG.
  • the transceiving unit 51 transmits the destination status information to the terminals (10ba and 10ca
  • the IP address of the terminal managed in the terminal status management table is referred to on the basis of each of the terminal IDs ("01ba" and "01ca").
  • the terminal ID "Olaa" of the request source terminal (the terminal 10aa) that has made the login request and the operation status "online” can be transmitted to each of the other destination terminals (the terminals 10ba and 10ca) that can perform communication with the request source terminal (the terminal 10aa) that has made the login request as the destination.
  • the operation status of the terminal 10da serving as the non-dedicated terminal D is not managed in the terminal status management table (see FIG. 13 ), and thus the terminal ID "Olaa" of the request source terminal (the terminal 10aa) that has made the login request and the operation status "online” are hardly transmitted to the terminal 10da.
  • the non-dedicated terminal D side hardly use a service of acquiring the operation status of the dedicated terminal A.
  • the operation input receiving unit 12 illustrated in FIG. 9 receives the power-on input, and the same process as the process of steps S22 to S31-1, S31-2 is performed, and thus a description thereof will not be made.
  • FIG. 19 is a sequence diagram illustrating a call start request.
  • the operation input receiving unit 12 illustrated in FIG. 9 receives a request to start a call with the destination terminal (the terminal 10ca) (step S41). Then, the transceiving unit 11 of the request source terminal (the terminal 10aa) transmits start request information representing a call start desire to the call management system 50 (step S42).
  • the start request information includes the terminal ID "Olaa" of the request source terminal (the terminal 10aa) and the terminal ID "01ca" of the destination terminal (the terminal 10ca).
  • the status managing unit 53 of the call management system 50 illustrated in FIG. 9 changes all the operation status field portions of the records respectively including the terminal ID "Olaa” and the terminal ID "01ca” in the terminal status management table (see FIG. 13 ) to "online (busy)" based on the terminal ID "Olaa” of the request source terminal (the terminal 10aa) and the terminal ID "01ca” of the destination terminal (the terminal 10ca) included in the start request information (step S43).
  • the request source terminal (the terminal 10aa) and the destination terminal (the terminal 10ca) do not start a call but becomes the busy state, and when another terminal 10 desires to make a call to the request source terminal (the terminal 10aa) or the destination terminal (the terminal 10ca), an alert tone or a display representing a so-called busy state is output.
  • the session managing unit 56 of the call management system 50 generates a session ID used to establish a communication session (step S44). Then, the call management system 50 determines a communication scheme that can be used by the destination terminal (the terminal 10ca) (step S45).
  • FIG. 20 is a flowchart illustrating a determination of a communication scheme.
  • the extracting unit 54 searches the terminal information management table (see FIG. 12 ) based on the terminal ID "01ca" of the destination terminal (the terminal 10ca) received by the transceiving unit 51, and extracts a corresponding communication scheme information (step S45-1).
  • the determining unit 55 determines whether or not a communication scheme represented by the extracted communication scheme information is a communication scheme that can be used by the request source terminal (the terminal 10aa) serving as the dedicated terminal A (step S45-2). Specifically, the determining unit 55 determines whether or not a communication scheme represented by the communication scheme information extracted by the extracting unit 54 is the same as a communication scheme that can be used by the request source terminal (the terminal 10aa).
  • the two communication schemes are determined to be the same as each other when the two communication schemes are the same in both of the call control scheme and the coding scheme, but the two communication schemes are determined to be not the same as each other when the two communication schemes are different in at least one of the call control scheme and the coding scheme.
  • FIG. 21 is a sequence diagram illustrating a process of establishing a communication session before a call is performed between the two dedicated terminals A.
  • the description will proceed with an example in which the relay device 30a connected to the same LAN 2a as in the request source terminal (the terminal 10aa) is used among a plurality of relay devices 30.
  • the call management system 50 transmits session initialization request information to initialize a communication session established by the relay device 30a to the relay device 30a through the transceiving unit 51 (step S61).
  • the session initialization request information includes the session ID generated in step S44 and the IP addresses of the request source terminal (the terminal 10aa) and the destination terminal (the terminal 10ca) managed by the terminal status management table (see FIG. 13 ).
  • the call management system 50 also transmits the IP address of the call management system 50 when transmitting the session initialization request information to the relay device 30a.
  • the transceiving unit 31 of the relay device 30a receives the session initialization request information and the IP address of the call management system 50.
  • the transceiving unit 31 of the relay device 30a initializes the communication session (step S62). Then, the transceiving unit 31 transmits the session start instruction information to instruct a start of the communication session to the request source terminal (the terminal 10aa) (step S63).
  • the session start instruction information includes the session ID transmitted from the call management system 50.
  • the relay device 30a also transmits the IP address of the relay device 30a to the request source terminal (the terminal 10aa) when transmitting the session start instruction information.
  • the transceiving unit 11 of the request source terminal (the terminal 10aa) receives the session start instruction information and the IP address of the relay device 30a.
  • the transceiving unit 31 transmits the session start instruction information to instruct a start of the communication session to the destination terminal (the terminal 10ca) (step S64).
  • the session start instruction information includes the session ID transmitted from the call management system 50.
  • the relay device 30a also transmits the IP address of the relay device 30a to the destination terminal (the terminal 10ca) when transmitting the session start instruction information.
  • the transceiving unit 11 of the destination terminal (the terminal 10ca) receives the session start instruction information and the IP address of the relay device 30a.
  • the communication session (the first communication session sed1 illustrated in FIG. 2 ) to transmit and receive call data is established between the request source terminal (the terminal 10aa) and the relay device 30a based on step S63 (step S65-1). Further, the communication session (the second communication session sed2 illustrated in FIG. 2 ) to transmit and receive call data is established between the relay device 30a and the destination terminal (the terminal lOca) based on step S64 (step S65-2).
  • FIG. 22 is a sequence diagram illustrating a process of transmitting and receiving call data between the two dedicated terminals A.
  • a process of transmitting a call data from the terminal 10aa to the terminal 10ca in one direction and a process of transmitting call data from the terminal 10ca to the terminal 10aa in a reverse direction transmission and reception of call data, detection of the delay time which will be described later, or the like is performed by the same process, and thus the description will proceed with communication in one direction, and a description of communication in the reverse direction will not be made.
  • the request source terminal (the terminal 10aa) transmits subject image data imaged by the imaging unit 14 and audio data of a sound input through the audio input unit 15a to the relay device 30a via the communication network 2 through the transceiving unit 11 using the communication session sed1 (step S81).
  • high-quality image data having the three resolutions that is, the low resolution, the moderate resolution, and the high resolution illustrated in FIG. 3 and audio data are transmitted.
  • the relay device 30a receives the image data having the three resolutions and the audio data through the transceiving unit 31.
  • the data quality verifying unit 33 verifies a quality of an image of image data to be relayed by searching the changed quality management table (see FIG.
  • the relay device 30a transfers the image data with the same image quality and the audio data with the same audio quality to the destination terminal (the terminal 10ca) using the communication session sed2 (step S83).
  • the destination terminal (the terminal 10ca) receives the high-quality image data having the three resolutions, that is, the low resolution, the moderate resolution, the high resolution and the audio data through the transceiving unit 11.
  • the display control unit 16 can cause an image to be displayed on the display 120 based on a combination of the image data having the three image qualities, and the audio output unit 15b can output a sound based on the audio data.
  • the delay detecting unit 17 of the destination terminal detects the reception delay time of the image data received through the transceiving unit 11 at predetermined time intervals (for example, each second (step S84).
  • the delay time is 200 (ms).
  • the transceiving unit 11 of the destination terminal transmits the delay time information representing the delay time "200 (ms)" to the call management system 50 via the communication network 2 through the management communication session sei illustrated in FIG. 2 (step S85).
  • the call management system 50 can detect the delay time and detect the IP address "1.3.1.3" of the terminal 10ca serving as the transmission source of the delay time information.
  • the delay time managing unit 58 of the call management system 50 searches the terminal status management table (see FIG. 13 ) using the IP address "1.3.1.3" of the destination terminal (the terminal 10ca) as the search key and extracts the corresponding terminal ID "01ca", and manages the delay time "200 (ms)" represented by the delay time information to be stored in the delay time field portion in the record of the terminal ID "01ca” in the session management table (see FIG. 15 ) (step S86).
  • the quality deciding unit 57 decides the image quality as the "moderate image quality” by searching the quality management table (see FIG. 17 ) using the delay time "200 (ms)" as the search key and extracting an image quality "moderate image quality” of corresponding image data (step S87).
  • the transceiving unit 51 searches the relay device management table (see FIG. 11 ) using the relay device ID "111a" associated with the terminal ID "01ca” in the session management table (see FIG. 15 ) as the search key, and extracts the IP address "1.2.1.2” of the corresponding relay device 30a (step S88). Then, the transceiving unit 51 transmits the quality information representing the image quality "moderate image quality" of the image data decided in step S87 to the relay device 30a via the communication network 2 through the management communication session sei (step S89).
  • the quality information includes the IP address "1.3.1.3" of the destination terminal (the terminal 10ca) used as the search key in step S86.
  • the changed quality managing unit 34 manages the IP address "1.3.1.3" of the transmission destination terminal 10 (here, the terminal 10ca) and the image quality "moderate image quality" of the image data to be relayed to be stored in the changed quality management table (see FIG. 10 ) in association with each other (step S90).
  • the request source terminal (the terminal 10aa) transmits the high-quality image data having the three resolutions, that is, the low resolution, the moderate resolution, the high resolution and the audio data to the relay device 30a through the first communication session sed1 (step S91).
  • the data quality verifying unit 33 verifies a quality of an image of image data to be relayed by searching the changed quality management table (see FIG. 10 ) using the IP address "1.3.1.3" of the destination terminal (the terminal 10ca) as the search key and extracting an image quality "moderate image quality" of corresponding image data to be relayed (step S92).
  • the data quality changing unit 35 suppresses an image quality of image data from the "high image quality” to the "moderate image quality” and changes the quality of the image of the image data (step S93).
  • the transceiving unit 31 transmits the image data in which an image quality of image data has been changed to the "moderate image quality" and the audio data in which a sound quality of a sound has not been changed to the destination terminal (the terminal 10ca) via the communication network 2 through the second communication session sed2 (step S94).
  • the destination terminal receives image data of a moderate image quality having two resolutions, that is, the low resolution, the moderate resolution and the audio data through the transceiving unit 11.
  • the display control unit 16 can cause an image to be displayed on a display 120ca based on a combination of the image data having the two resolutions, and the audio output unit 15b can output a sound based on the audio data.
  • the relay device 30a changes a quality of an image, and thus that the user who attends a call such as a video conference does not feel uncomfortable. In other words, a service to cope with a reception delay of image data can be provided between the two dedicated terminals A.
  • the second communication pattern in which a call is performed between the dedicated terminal A (an example of a first communication terminal) and the non-dedicated terminal D (and example of a second communication terminal) will be described with reference to FIG. 20 and FIGS. 23 to 25. Specifically, a call is performed between the terminal 10aa serving as the dedicated terminal A and the terminal 10da serving as the non-dedicated terminal D.
  • a call control scheme is a protocol of an instant messenger (or a protocol extended from a protocol of an instant messenger), and a coding scheme is the SVC
  • a call control scheme is the SIP
  • a coding scheme is the AVC
  • the second communication pattern is different from the first communication pattern in that the destination terminal (the terminal 10da) selects the destination in step S41 rather than the destination terminal (the terminal 10ca), and thus the terminal ID of the destination terminal used for transmission and reception or a search is also changed, and thus a description thereof will not be made. Then, the description will proceed from when the determining unit 55 determines that the two communication schemes are not the same in step S45-2 illustrated in FIG. 20 (NO).
  • the extracting unit 54 searches the conversion management table (see FIG. 16 ) based on the terminal ID "01da" of the destination terminal (the terminal 10da) received through the transceiving unit 51, and extracts the corresponding IP address "1.3.2.2" of the conversion system 80 and the IP address "1.3.2.3” of the destination terminal (the terminal 10da) (step S45-3). Then, the process proceeds to step S101 illustrated in FIG. 23 which will be described later.
  • FIG. 23 is a sequence diagram illustrating a process of establishing a communication session before a call is performed between the dedicated terminal A and the non-dedicated terminal D.
  • the call management system 50 transmits session initialization request information to initialize a communication session established by the relay device 30a to the relay device 30a through the transceiving unit 51 (step S101).
  • the session initialization request information includes the session ID and the IP addresses of the request source terminal (the terminal 10aa), the conversion system 80, and the destination terminal (the terminal 10da). Of these, the session ID is the ID generated in step S44.
  • the IP address of the request source terminal (the terminal 10aa) is managed in the terminal status management table (see FIG. 13 ). Further, the IP addresses of the conversion system 80 and the destination terminal (the terminal 10da) are the IP addresses extracted in step S45-3.
  • the call management system 50 also transmits the IP address of the call management system 50 when transmitting the session initialization request information to the relay device 30a.
  • the transceiving unit 31 of the relay device 30a receives the session initialization request information and the IP address of the call management system 50.
  • the transceiving unit 31 of the relay device 30a initializes the communication session (step S102). Then, the transceiving unit 31 transmits the session start instruction information to instruct a start of the communication session to the request source terminal (the terminal 10aa) (step S103).
  • the session start instruction information includes the session ID transmitted from the call management system 50.
  • the relay device 30a also transmits the IP address of the relay device 30a to the request source terminal (the terminal 10aa) when transmitting the session start instruction information.
  • the transceiving unit 11 of the request source terminal (the terminal 10aa) receives the session start instruction information and the IP address of the relay device 30a.
  • the transceiving unit 31 transmits the session start instruction information to instruct a start of the communication session to the conversion system 80 (step S104).
  • the session start instruction information includes the session ID transmitted from the call management system 50 and the IP address of the destination terminal (the terminal 10da).
  • the transceiving unit 31 transmits the session start instruction information and transmits the IP address of the destination terminal (the terminal 10da).
  • the relay device 30a also transmits the IP address of the relay device 30a to the conversion system 80 when transmitting the session start instruction information.
  • the transceiving unit 81 of the conversion system 80 receives the session start instruction information and the IP address of the relay device 30a.
  • the transceiving unit 81 of the conversion system 80 transmits the session start instruction information to instruct a start of the communication session to the destination terminal (the terminal 10da) (step S105).
  • the session start instruction information includes the session ID transmitted from the call management system 50.
  • the conversion system 80 also transmits the IP address of the conversion system 80 to the destination terminal (the terminal 10da) when transmitting the session start instruction information.
  • the transceiving unit 11 of the destination terminal (the terminal 10da) receives the session start instruction information and the IP address of the conversion system 80.
  • the communication session (the first communication session sed11 illustrated in FIG. 4 ) to transmit and receive call data is established between the request source terminal (the terminal 10aa) and the relay device 30a based on step S103 (step S106-1). Further, the communication session (the second communication session sed12 illustrated in FIG. 4 ) to transmit and receive call data is established between the relay device 30a and the conversion system 80 based on step S104 (step S106-2). Further, the communication session (the third communication session sed13 illustrated in FIG. 4 ) to transmit and receive call data is established between the conversion system 80 and the destination terminal (the terminal 10da) based on step S105 (step S106-3).
  • FIG. 24 is a sequence diagram illustrating a process of transmitting and receiving call data between the dedicated terminal A and the non-dedicated terminal D.
  • the request source terminal (the terminal 10aa) transmits subject image data imaged by the imaging unit 14 and audio data of a sound input through the audio input unit 15a to the relay device 30a via the communication network 2 through the transceiving unit 11 using the communication session sed11 (step S121).
  • the second communication pattern similarly to the first communication pattern, high-quality image data having the three resolutions, that is, the low resolution, the moderate resolution, and the high resolution illustrated in FIG. 3 and audio data are transmitted.
  • the relay device 30a receives the image data having the three resolutions and the audio data through the transceiving unit 31.
  • the relay device 30a transmits the high-quality image data having the three resolutions and the audio data to the conversion system 80 via the communication network 2 through the transceiving unit 31 using the communication session sed12 (step S122).
  • the conversion system 80 receives the image data having the three resolutions and the audio data through the transceiving unit 81.
  • the communication scheme converting unit 82 of the conversion system 80 converts the communication scheme of the image data having the three resolutions from the communication scheme used by the request source terminal (the terminal 10aa) to the communication scheme used by the destination terminal (the terminal 10da) based on the conversion rule data stored in the storage unit 8000 in advance (step S123).
  • the image data having the three resolutions (the high resolution, the moderate resolution, and the low resolution) illustrated FIG. 3 is converted into the image data having one resolution (the moderate resolution) illustrated in FIG. 5 .
  • the conversion system 80 transmits the audio data and the moderate-resolution image data to the terminal 10da via the communication network 2 through the transceiving unit 81 using the communication session sed13 (step S124).
  • the destination terminal receives the audio data and the moderate-resolution image data through the transceiving unit 11.
  • the destination terminal transmits the audio data and the moderate-resolution image data to the conversion system 80 via the communication network 2 through the transceiving unit 11 using the communication session sedl3 as illustrated in FIG. 24 (step S125).
  • the conversion system 80 receives the audio data and the moderate-resolution image data through the transceiving unit 81.
  • the communication scheme converting unit 82 of the conversion system 80 converts the communication scheme of the audio data and the moderate-resolution image data from the communication scheme used by the destination terminal (the terminal 10da) to the communication scheme used by the request source terminal (the terminal 10aa) based on the conversion rule data stored in the storage unit 8000 in advance (step S126).
  • FIG. 25 is a conceptual diagram illustrating an image quality of image data converted by the conversion system.
  • the image data having one resolution (the moderate resolution) illustrated in FIG. 5 is converted into low-resolution image data illustrated in (a) of FIG. 25 , moderate-resolution image data illustrated in (c) of FIG. 25 , and image data with a low moderate resolution which is a moderate resolution between the moderate resolution and the low resolution as illustrated in (b) of FIG. 25 .
  • the conversion system 80 does not convert the moderate-resolution image data into the high-resolution image data transmitted in step S122, and the moderate-resolution image data transmitted from the destination terminal (the terminal 10da) has the maximum resolution and is converted into image data having the three resolutions, that is, the moderate resolution, the moderate resolution between the moderate resolution and the low resolution, and the low resolution.
  • the conversion system 80 transmits the audio data and the image data having the three resolutions to the relay device 30a via the communication network 2 through the transceiving unit 81 using the communication session sedl2 (step S127).
  • the relay device 30a receives the audio data and the image data having the three resolutions through the transceiving unit 31.
  • the relay device 30a transmits the audio data and the image data having the three resolutions to the request source terminal (the terminal 10aa) via the communication network 2 through the transceiving unit 31 using the communication session sed11 (step S128).
  • the request source terminal receives the audio data and the image data having the three resolutions through the transceiving unit 11.
  • the session initialization request information to be transmitted from the call management system 50 to the relay device 30a includes the IP addresses of the request source terminal, the conversion system 80, and the destination terminal.
  • the relay device 30a can transmit the session start instruction information to the IP address of the request source terminal and transmit the session start instruction information including the IP address of the destination terminal to the IP address of the conversion system 80.
  • the conversion system 80 can transmit the session start instruction information to the IP address of the destination terminal.
  • the first communication session sed11 can be established between the relay device 30 and the request source terminal
  • the second communication session sed12 can be established between the relay device 30 and the conversion system 80
  • the third communication session sed13 can be established between the conversion system 80 and the destination terminal.
  • the request source terminal or the dedicated terminal A is used as an example of the first communication terminal
  • the destination terminal or the non-dedicated terminal D is used as an example of the second communication terminal.
  • the present invention is not limited to this example, and the destination terminal or the non-dedicated terminal D may be used as an example of the first communication terminal, and the request source terminal or the dedicated terminal A may be used as an example of the second communication terminal.
  • the call data is an example of communication data.
  • the communication data includes a text or image file data.
  • the terminal 10 is an example of the communication terminal.
  • an information processing terminal that transmits and receives the file data as well as a terminal that performs a call may be used as the communication terminal.
  • the call management system 50 is an example of the communication management system.
  • a file management system that manages processing of the file data as well as a system that manages a call may be used as the communication management system.
  • the call system 1 is an example of the communication system.
  • the communication system is constructed by the communication terminal and the communication management system.
  • the call management system 50 manages communication scheme information through the terminal information management table (see FIG. 12 ).
  • the present invention is not limited to this example, and the request source terminal may manage communication scheme information of the destination terminal.
  • the request source terminal (the terminal 10aa) can transmit the start request information including the terminal ID of the request source terminal and the terminal ID of the destination terminal and the communication scheme information to the call management system 50.
  • the display control unit 16 may cause a selection screen used to select the non-dedicated terminal as the destination of a call to be displayed on the display 120 and encourages the user to make a selection.
  • step S42 of FIG. 19 the request source terminal (the terminal 10aa) transmits the start request information including information (communication scheme information) representing that the destination terminal ID is the non-dedicated terminal to the call management system.
  • the call management system 50 needs not execute step S45-1 of FIG. 20 , determines that the communication scheme of the destination terminal is not "dedicated” based on the communication scheme information included in the start request information (NO in step S45-2 of FIG. 20 ), and causes the process to proceed to step S45-3 of FIG. 20 .
  • the operation input receiving unit 12 may receive an input of the destination information (the IP address or the like) of the destination terminal from the user.
  • the request source terminal transmits the start request information including the destination information of the destination terminal and the information (the communication scheme information) representing that the destination terminal is "non-dedicated" rather than the terminal ID of the destination terminal to the call management system 50.
  • the determining unit 55 determines that the destination terminal represented by the destination information is not "dedicated", and then causes the process to proceed to step S45-3.
  • the extracting unit 54 extracts the destination information of the conversion system 80 based on the destination information of the non-dedicated terminal, and causes the process to proceed to step S101.
  • the terminal ID may be stored in the terminal 10 in advance at the time of factory shipment or may be input by the user.
  • the relay device 30, the call management system 50, the conversion system 80, the program providing system 90, and the maintenance system 100 may be constructed by a single computer or may be constructed by a plurality of computers in which respective portions (functions or devices) are divided and arbitrarily allocated.
  • a program transmitted by the program providing system 90 may be divided into a plurality of modules and then transmitted or may be transmitted without any division.
  • transmission from each computer may be performed in a state in which the program is divided into a plurality of modules.
  • a protocol of an instant messenger or a protocol extended from a protocol of an instant messenger
  • the SIP have been described, but the present invention is not limited to this combination as long as call control schemes of terminals are different from each other.
  • a combination of a protocol of an instant messenger (or a protocol extended from a protocol of an instant messenger) and H.323 may be used.
  • a combination of a protocol of an instant messenger and a protocol extended from a protocol of an instant messenger may be used.
  • all a recording medium such as a CD-ROM storing each program of the above-described embodiment, the HD 204 storing the program, and the program providing system 90 including the HD 204 may be provided inside or outside the country as a program product.
  • a quality of an image is managed by the changed quality management table illustrated in FIG. 10 and the quality management table illustrated in FIG. 17 , focusing on the resolution of an image of image data as an example of a quality of an image of image data to be relayed by the relay device 30, and the present invention is not limited to this example.
  • a quality may be managed focusing on the depth of an image quality of image data, a sampling frequency in a sound of audio data, or a bit length in a sound of audio data.
  • the audio data may be divided into three kinds of resolutions (the high resolution, the moderate resolution, and the low resolution) and then transmitted and received.
  • the reception date and time is managed, but the present invention is not limited to this example, and it is preferable that at least a reception time of the reception date and time be managed.
  • the IP address of the relay device 30 is managed in FIG. 11
  • the IP address of the terminal 10 is managed in FIG. 13
  • the present invention is not limited to this example.
  • destination information specifies the relay device 30 on the communication network 2 or destination information specifies the terminal 10 on the communication network 2
  • each fully qualified domain name may be managed.
  • an IP address corresponding to the FQDN is acquired by a known domain name system (DNS) server.
  • DNS domain name system
  • the video conference system has been described as an example of the call system 1, but the present invention is not limited to this example, and the call system 1 may be a telephone system such as an internet protocol (IP) telephone or an Internet telephone.
  • the call system 1 may be a car navigation system.
  • one terminal 10 corresponds to a car navigation device mounted in a vehicle
  • the other terminal 10 corresponds to a management terminal or a management server of a management center that manages a car navigation device, or a car navigation device mounted in another device.
  • the call system 1 may be a communication system of a mobile telephone.
  • the terminal 10 corresponds to a mobile phone.
  • call data may be haptic (touch) data.
  • the call data may be smell data. In this case, smelling (bad smelling) at one terminal is transmitted to the other terminal side.
  • the call data is preferably at least one of image data, audio data, haptic data, and smell data.
  • the above-described embodiment has been described in connection with the example in which a video conference is performed by the call system 1, but the present invention is not limited to this example, and the call system 1 may be used for a meeting, an ordinary conversation between family members or friends, or provision of information in one direction.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP12862181.0A 2011-12-27 2012-12-26 Communication management system, communication system, communication management method and computer-readable recording medium Active EP2798827B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2011285768 2011-12-27
JP2012262456A JP6079174B2 (ja) 2011-12-27 2012-11-30 通信管理システム、通信システム、プログラム、及びメンテナンスシステム
PCT/JP2012/084288 WO2013100184A1 (en) 2011-12-27 2012-12-26 Communication management system, communication system, computer-readable recording medium, and maintenance system

Publications (3)

Publication Number Publication Date
EP2798827A1 EP2798827A1 (en) 2014-11-05
EP2798827A4 EP2798827A4 (en) 2015-06-17
EP2798827B1 true EP2798827B1 (en) 2020-04-08

Family

ID=48697647

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12862181.0A Active EP2798827B1 (en) 2011-12-27 2012-12-26 Communication management system, communication system, communication management method and computer-readable recording medium

Country Status (8)

Country Link
US (6) US9350947B2 (ja)
EP (1) EP2798827B1 (ja)
JP (1) JP6079174B2 (ja)
CN (1) CN104137522B (ja)
AU (1) AU2012360696B2 (ja)
CA (1) CA2861239C (ja)
SG (1) SG11201403576UA (ja)
WO (1) WO2013100184A1 (ja)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6260101B2 (ja) 2012-05-01 2018-01-17 株式会社リコー 通信端末、起動方法及びプログラム
US9923950B1 (en) 2012-07-24 2018-03-20 Ports America Group, Inc. Systems and methods involving features of terminal operation including TOS-agnostic and/or other features
CA2919151A1 (en) * 2012-07-24 2014-01-30 Ports America Group, Inc. Systems and methods involving features of terminal operation including user interface and/or other features
JP6330354B2 (ja) 2013-02-25 2018-05-30 株式会社リコー 通信管理システム、通信管理方法、及びプログラム
JP6263843B2 (ja) 2013-02-28 2018-01-24 株式会社リコー 通信管理システム、通信管理方法、及びプログラム
JP6347115B2 (ja) 2013-02-28 2018-06-27 株式会社リコー 通信管理システム、通信管理方法、及びプログラム
JP6182935B2 (ja) 2013-03-29 2017-08-23 株式会社リコー 通信管理システム、通信管理方法、プログラム、及び通信システム
RU2640643C2 (ru) * 2013-05-13 2018-01-10 Хуавэй Текнолоджиз Ко., Лтд. Способ управления перегрузкой и устройство
JP6252740B2 (ja) 2013-09-13 2017-12-27 株式会社リコー 伝送管理システム、管理方法、及びプログラム
JP6375682B2 (ja) 2014-04-30 2018-08-22 株式会社リコー 通信管理システム、通信管理方法、及びプログラム
EP3062260B1 (en) * 2015-02-27 2017-05-31 Sap Se A method for controlling access to electronic documents using locks
JP6582562B2 (ja) * 2015-05-29 2019-10-02 株式会社リコー 通信端末、通信システム、通信方法、及びプログラム
JP2017041831A (ja) 2015-08-21 2017-02-23 株式会社リコー 通信システム、通信管理システム、通信管理方法、及びプログラム
CN106488169B (zh) * 2015-08-28 2019-09-13 腾讯科技（深圳）有限公司 一种数据传输的方法、系统以及相关设备
JP5907304B2 (ja) * 2015-09-04 2016-04-26 株式会社リコー 通信管理システム、通信システム、通信管理方法、及びプログラム
CN108780474B (zh) 2016-03-14 2022-07-19 株式会社理光 服务提供系统、服务递送系统、服务提供方法和记录介质
JP6620883B2 (ja) 2016-03-29 2019-12-18 株式会社リコー サービス提供システム、サービス授受システム、サービス提供方法、及びプログラム
EP3438838A4 (en) 2016-03-29 2019-03-13 Ricoh Company, Ltd. SERVICE DELIVERY SYSTEM, SERVICE PACKING SYSTEM, SERVICE PROCESSING AND PROGRAM
JP6638808B2 (ja) 2016-03-29 2020-01-29 株式会社リコー サービス提供システム、サービス授受システム、サービス提供方法、及びプログラム
JP6688485B2 (ja) * 2016-07-15 2020-04-28 株式会社リコー サービス提供システム、サービス授受システム、サービス提供方法、及びプログラム
EP3641235B1 (en) * 2017-06-12 2022-11-09 Audio-Technica Corporation Data transmission device and data transmission system
JP7355996B2 (ja) * 2019-05-17 2023-10-04 アイコム株式会社 中継装置および音声通信の録音方法
JP7334482B2 (ja) * 2019-06-05 2023-08-29 富士フイルムビジネスイノベーション株式会社 情報管理装置、端末装置、情報処理システム、情報管理プログラム及び情報処理プログラム

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7383341B1 (en) * 1996-10-15 2008-06-03 Kabushiki Kaisha Toshiba Data transfer control device, relay device and control device suitable for home network environment
US7079495B1 (en) * 2000-01-04 2006-07-18 Cisco Technology, Inc. System and method for enabling multicast telecommunications
JP4098977B2 (ja) 2001-11-02 2008-06-11 ソフトバンク株式会社 構内通信システム、構内通信方法及び構内回線交換機
JP4133512B2 (ja) 2003-03-28 2008-08-13 エヌ・ティ・ティ・コムウェア株式会社 プレゼンス表示制御装置、プレゼンス表示制御方法、プレゼンス表示制御プログラム及びプレゼンス表示制御プログラムを格納した記録媒体
KR100735274B1 (ko) * 2004-11-18 2007-07-03 삼성전자주식회사 트랜스코더를 구비한 분산형 멀티미디어 전송 네트워크의트랜스코딩 방법 및 장치
JP2009508454A (ja) * 2005-09-07 2009-02-26 ヴィドヨ，インコーポレーテッド スケーラブルなビデオ符号化を用いたスケーラブルで低遅延のテレビ会議用システムおよび方法
CN101507267B (zh) 2005-09-07 2011-09-14 维德约股份有限公司 用于使用可缩放视频编码进行可缩放和低延迟视频会议的系统和方法
CN102318202B (zh) 2006-03-29 2014-06-04 维德约股份有限公司 用于可缩放与非可缩放视频编解码器之间的译码的系统和方法
JP2008035476A (ja) 2006-06-26 2008-02-14 Nec Infrontia Corp 呼制御方法、コンピュータプログラム及び構内交換機
US8311197B2 (en) * 2006-11-10 2012-11-13 Cisco Technology, Inc. Method and system for allocating, revoking and transferring resources in a conference system
CN101578884B (zh) * 2007-01-08 2015-03-04 诺基亚公司 提供和使用译码的媒体流的互操作点的预定信令的系统和方法
WO2008086423A2 (en) 2007-01-09 2008-07-17 Vidyo, Inc. Improved systems and methods for error resilience in video communication systems
JP2008227577A (ja) 2007-03-08 2008-09-25 Konica Minolta Holdings Inc テレビ会議システム
JP2009194661A (ja) 2008-02-14 2009-08-27 Nippon Telegr & Teleph Corp <Ntt> 会議端末装置
CA2727569C (en) 2008-06-09 2017-09-26 Vidyo, Inc. Improved view layout management in scalable video and audio communication systems
JP5311460B2 (ja) * 2008-09-03 2013-10-09 日本電気株式会社 接続制御装置
KR101630283B1 (ko) 2009-06-25 2016-06-14 한화테크윈 주식회사 영상 보안 시스템에서 부호화 장치
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
JP4947160B2 (ja) * 2010-02-02 2012-06-06 沖電気工業株式会社 コーデック変換装置
US8949593B2 (en) 2010-02-12 2015-02-03 Ricoh Company, Limited Authentication system for terminal identification information
JP5999873B2 (ja) 2010-02-24 2016-09-28 株式会社リコー 伝送システム、伝送方法、及びプログラム
JP5793869B2 (ja) 2010-03-05 2015-10-14 株式会社リコー 伝送管理システム、伝送管理方法、及び伝送管理プログラム
US8731331B2 (en) 2010-11-30 2014-05-20 Ricoh Company, Ltd. Apparatus, system, and method of communication, and recording medium storing communication control program
JP5919695B2 (ja) 2011-02-25 2016-05-18 株式会社リコー セッション制御システム、伝送システム、及びプログラム
JP2013009304A (ja) 2011-05-20 2013-01-10 Ricoh Co Ltd 画像入力装置、会議装置、画像処理制御プログラム、記録媒体
JP5811334B2 (ja) 2011-09-01 2015-11-11 株式会社リコー 伝送管理システム、伝送管理方法、プログラム、及び伝送システム
JP6136217B2 (ja) 2011-12-27 2017-05-31 株式会社リコー 通信管理システム、通信システム、プログラム、及びメンテナンスシステム

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP2798827A1 (en) 2014-11-05
US20150189237A1 (en) 2015-07-02
AU2012360696A1 (en) 2014-07-24
US9912906B2 (en) 2018-03-06
CN104137522B (zh) 2018-02-06
WO2013100184A1 (en) 2013-07-04
JP2013153419A (ja) 2013-08-08
US10904480B2 (en) 2021-01-26
EP2798827A4 (en) 2015-06-17
US10225517B2 (en) 2019-03-05
JP6079174B2 (ja) 2017-02-15
US9350947B2 (en) 2016-05-24
US20190158785A1 (en) 2019-05-23
CA2861239C (en) 2017-10-17
US20140375757A1 (en) 2014-12-25
US9270942B2 (en) 2016-02-23
CN104137522A (zh) 2014-11-05
US20210092324A1 (en) 2021-03-25
US20160234460A1 (en) 2016-08-11
CA2861239A1 (en) 2013-07-04
US20180139411A1 (en) 2018-05-17
US11539914B2 (en) 2022-12-27
SG11201403576UA (en) 2014-07-30
AU2012360696B2 (en) 2016-02-18

Similar Documents

Publication Publication Date Title
EP2798827B1 (en) Communication management system, communication system, communication management method and computer-readable recording medium
JP6263843B2 (ja) 通信管理システム、通信管理方法、及びプログラム
JP6136217B2 (ja) 通信管理システム、通信システム、プログラム、及びメンテナンスシステム
JP6330354B2 (ja) 通信管理システム、通信管理方法、及びプログラム
JP6347115B2 (ja) 通信管理システム、通信管理方法、及びプログラム
EP2845375B1 (en) Communication terminal, communication function starting method, and computer-readable recording medium
JP6638768B2 (ja) 通信システムおよび通信方法
JP2020025293A (ja) 通信管理システム、通信システム、プログラム、及びメンテナンスシステム
JP6182935B2 (ja) 通信管理システム、通信管理方法、プログラム、及び通信システム
JP2018191301A5 (ja)
JP2017126985A5 (ja)
JP5907304B2 (ja) 通信管理システム、通信システム、通信管理方法、及びプログラム
JP6443532B2 (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: 20140626

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)
RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20150519

RIC1 Information provided on ipc code assigned before grant

Ipc: H04M 3/00 20060101AFI20150512BHEP

Ipc: H04L 12/18 20060101ALI20150512BHEP

Ipc: H04M 3/56 20060101ALI20150512BHEP

Ipc: H04L 29/06 20060101ALI20150512BHEP

Ipc: H04N 7/15 20060101ALI20150512BHEP

17Q First examination report despatched

Effective date: 20160503

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602012069206

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04M0003000000

Ipc: H04L0012180000

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: H04L 12/18 20060101AFI20191008BHEP

Ipc: H04M 3/56 20060101ALI20191008BHEP

Ipc: H04N 7/15 20060101ALI20191008BHEP

Ipc: H04M 7/00 20060101ALI20191008BHEP

INTG Intention to grant announced

Effective date: 20191108

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

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

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

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1255824

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200415

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: 602012069206

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: NL

Ref legal event code: MP

Effective date: 20200408

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: 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: 20200408

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: 20200708

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: 20200408

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: 20200408

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: 20200408

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: 20200709

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: 20200817

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: 20200808

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1255824

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200408

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: 20200408

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: 20200408

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: 20200408

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: 20200708

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: 20200408

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012069206

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: 20200408

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: 20200408

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: 20200408

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: 20200408

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: 20200408

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: 20200408

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: 20200408

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: 20200408

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

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

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: 20200408

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: 20200408

26N No opposition filed

Effective date: 20210112

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

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: 20200408

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

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: 20200408

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201231

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: 20201226

Ref country code: LU

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

Effective date: 20201226

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

Ref country code: CH

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

Effective date: 20201231

Ref country code: LI

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

Effective date: 20201231

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: 20200408

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: 20200408

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: 20200408

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: 20200408

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: 20201231

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: 20231220

Year of fee payment: 12

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

Ref country code: FR

Payment date: 20231221

Year of fee payment: 12

Ref country code: DE

Payment date: 20231214

Year of fee payment: 12