JP6183072B2 - Transmission management system, management method and program - Google Patents

Description

  The present invention relates to an invention for managing destination candidates for a predetermined transmission terminal.

  Communication systems that communicate with remote locations via communication networks such as the Internet have become widespread. Examples of the communication system include a conference system that performs a remote conference. In a general conference system, a terminal used by one of parties involved in a remote conference converts an image or sound of a subject in a conference room into digital data and transmits the digital data to a terminal used by the other party. Next, the terminal used by the other party displays an image on the display and outputs a sound from the speaker. Thereby, a conference between remote locations can be performed in a state close to an actual conference.

  In such a conference system, a technique for registering a destination candidate in a destination list or the like is known in order to easily call a terminal as a destination candidate. For example, Patent Document 1 discloses an invention in which identification information of each terminal is stored at the first meeting so that the identification information can be called at the second and subsequent meetings. ing.

  However, if a destination candidate is registered without any limitation, a security problem occurs. Conversely, if security is tightened by applying various restrictions, there arises a problem that destination candidates cannot be registered smoothly.

  The invention according to claim 1 is a transmission management system for managing destination candidates of a predetermined transmission terminal, comprising administrator identification information for identifying an administrator who manages the predetermined transmission terminal, the predetermined transmission terminal Storage means for storing predetermined terminal identification information for identification and related information associated with attribute information indicating the attribute of the administrator, and for identifying a transmission terminal as a destination candidate of the predetermined transmission terminal Receiving means for receiving specific terminal identification information and first administrator identification information for identifying the first administrator, the specific terminal identification information received by the receiving means, and the first If the administrator identification information is not associated in the related information, the first attribute information associated with the first administrator identification information in the related information and the related information Determining means for determining whether or not the second attribute information associated with the specific terminal identification information is the same, and the determining means determines that the first attribute information and the second attribute information are the same. And a registration unit configured to register the specific terminal identification information as a destination candidate of the predetermined transmission terminal when it is determined to be present.

  As described above, according to the present invention, it is possible to more smoothly register destination candidates while maintaining a certain level of security.

FIG. 1 is a schematic diagram of a transmission system according to the first embodiment of the present invention. FIG. 2 is a conceptual diagram showing a state of transmission / reception of image data, sound data, and various management information in the transmission system. FIG. 3 is a conceptual diagram illustrating the image quality of image data. FIG. 4 is an external view of the transmission terminal. FIG. 5 is a hardware configuration diagram of the transmission terminal. FIG. 6 is a hardware configuration diagram of the relay device, the terminal management system, the destination registration system, the program providing system, and the maintenance system. FIG. 7 is a functional block diagram of the terminal management system and the destination registration system that constitute the transmission management system. FIG. 8 is a conceptual diagram of the terminal authentication management DB. FIG. 9 is a conceptual diagram of the terminal management DB. FIG. 10 is a conceptual diagram of the destination list management DB. FIG. 11 is a conceptual diagram of the request management DB. FIG. 12 is a conceptual diagram of the administrator DB. FIG. 13 is a conceptual diagram illustrating an example of destination candidate registration processing. FIG. 14 is a conceptual diagram illustrating an example of destination candidate registration processing. FIG. 15 is a conceptual diagram illustrating an example of destination candidate registration processing. FIG. 16 is a flowchart showing a management method by the transmission management system. FIG. 17 is a conceptual diagram of an authentication screen. FIG. 18 is a diagram showing a conceptual diagram of the administrator registration screen. FIG. 19 is a conceptual diagram of the management terminal list screen. FIG. 20 is a conceptual diagram of the management terminal registration screen. FIG. 21 is a conceptual diagram of a management terminal deletion confirmation screen. FIG. 22 is a conceptual diagram of a destination candidate registration screen. FIG. 23 is a conceptual diagram of a destination candidate deletion screen. FIG. 24 is a flowchart showing management terminal registration and deletion processing. FIG. 25 is a flowchart showing destination candidate registration and deletion processing. FIG. 26 is a conceptual diagram of an administrator DB according to the second embodiment.

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

[First Embodiment]
First, a first embodiment of the present invention will be described with reference to FIGS.

<Overall Configuration of Embodiment>
FIG. 1 is a schematic diagram of a transmission system according to the first embodiment of the present invention. FIG. 2 is a conceptual diagram showing a state of transmission / reception of image data, sound data, and various management information in the transmission system. FIG. 3 is a conceptual diagram illustrating the image quality of image data.

  The transmission system 1 includes a communication system that transmits information, emotions, and the like between a plurality of terminals. This communication system is a system for mutually transmitting information, emotions, etc. between a plurality of communication terminals (corresponding to “transmission terminals”) via a communication management system (corresponding to “transmission management system” in the present embodiment). An example is a TV (video) conference system.

  First, the transmission system 1 shown in FIG. 1 includes a plurality of transmission terminals (10aa, 10ab,...), A display (120aa, 120ab,...) For each transmission terminal (10aa, 10ab,. The user terminal (20a, 20b, 20c, 20d), a plurality of relay devices (30a, 30b, 30c, 30d), the transmission management system 40, the program providing system 90, and the maintenance system 100 are constructed. Furthermore, the transmission management system 40 is constructed by a terminal management system 50 and a destination registration system 80.

  The plurality of transmission terminals 10 perform transmission by transmission / reception of image data and sound data as an example of content data. Note that text data is another example of content data. The content data only needs to include at least one of image data, sound data, and text data.

  In the following, an arbitrary transmission terminal among a plurality of transmission terminals (10aa, 10ab,...) Is represented as “transmission terminal 10”, and an arbitrary display among a plurality of displays (120aa, 120ab,. An arbitrary relay device among the plurality of relay devices (30a, 30b, 30c, 30d) is represented as “relay device 30”.

  In addition, the transmission terminal 10 that is a request source that requests the start of communication for communication such as a video conference is represented as “start terminal”, and the transmission terminal 10 that is the request destination (relay destination) is “destination terminal”. It expresses. Further, the transmission terminal 10 that makes a request for registering the counterpart transmission terminal 10 in its destination list is represented as “request source terminal”, and the counterpart transmission terminal 10 in this case is represented as “request destination terminal”. .

  As shown in FIG. 2, in the transmission system 1, a management information session sei for transmitting and receiving various types of management information is transmitted between the start terminal and the destination terminal via the terminal management system 50. Established. In addition, between the start terminal and the destination terminal, the relay device 30 is used to transmit and receive each of the four data: high-resolution image data, medium-resolution image data, low-resolution image data, and sound data. Four sessions are established. Here, these four sessions are collectively shown as an image / sound data session sed. Note that the start terminal and the destination terminal do not necessarily have to pass through the relay device 30, and the image / sound data session sed may be established directly between the start terminal and the destination terminal.

  Here, the resolution of the image data handled in the present embodiment will be described. As shown in FIG. 3 (a), the horizontal image is composed of 160 pixels and the vertical image is 120 pixels, and a low-resolution image serving as a base image and a horizontal image as illustrated in FIG. 3 (b). There are a medium-resolution image composed of 320 pixels and 240 pixels vertically, and a high-resolution image composed of 640 pixels horizontally and 480 pixels vertically as shown in FIG. Among these, when passing through a narrow band route, low-quality image data consisting only of low-resolution image data serving as a base image is relayed. When the band is relatively wide, low-resolution image data serving as a base image and medium-quality image data composed of medium-resolution image data are relayed. When the bandwidth is very wide, high-resolution image data composed of low-resolution image data serving as base image quality, intermediate-resolution image data, and high-resolution image data is relayed.

  The relay device 30 shown in FIG. 1 relays content data among a plurality of transmission terminals 10. The terminal management system 50 centrally manages login authentication from the transmission terminal 10, management of the call status of the transmission terminal 10, management of the destination list, and the communication status of the relay device 30. The image of the image data may be a moving image or a still image, or both a moving image and a still image.

  A plurality of routers (70a, 70b, 70c, 70d, 70ab, 70cd) select an optimum route for image data and sound data. In the following, an arbitrary router among the routers (70a, 70b, 70c, 70d, 70ab, 70cd) is represented as “router 70”.

  The program providing system 90 includes an HD (Hard Disk) 204, which will be described later, and stores a transmission terminal program for causing the transmission terminal 10 to realize various functions (or to cause the transmission terminal 10 to function as various means). The transmission terminal program can be transmitted to the transmission terminal 10. The HD 204 of the program providing system 90 also stores a relay device program for causing the relay device 30 to realize various functions (or to cause the relay device 30 to function as various means). The relay device program can be transmitted.

  Furthermore, the HD 204 of the program providing system 90 also stores a transmission management program for realizing various functions in the terminal management system 50 (or causing the terminal management system 50 to function as various means). 50, a transmission management program can be transmitted. The HD 204 of the program providing system 90 also stores a destination registration program for causing the destination registration system 80 to realize various functions (or causing the destination registration system 80 to function as various means). 80, the destination registration program can be transmitted. Note that the terminal management program and the destination registration program are collectively handled as a transmission management program.

  The maintenance system 100 is a computer for performing maintenance, management, or maintenance of at least one of the transmission terminal 10, the relay device 30, the terminal management system 50, the destination registration system 80, and the program providing system 90. For example, when the maintenance system 100 is installed in the country and the transmission terminal 10, the relay device 30, the terminal management system 50, the destination registration system 80, or the program providing system 90 is installed outside the country, the maintenance system 100 is connected to the communication network 2 The remote terminal performs maintenance such as maintenance, management, and maintenance of at least one of the transmission terminal 10, the relay device 30, the terminal management system 50, the destination registration system 80, and the program providing system 90. In addition, the maintenance system 100 includes a model number and a manufacturing number in at least one of the transmission terminal 10, the relay device 30, the terminal management system 50, the destination registration system 80, and the program providing system 90 without using the communication network 2. Carry out maintenance such as sales destination, maintenance inspection, or management of failure history.

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

  On the other hand, the transmission terminals (10ca, 10cb, 10cc,...), The relay device 30c, and the router 70c are communicably connected via a LAN 2c. The transmission terminals (10da, 10db, 10dc,...), The relay device 30d, and the router 70d are communicably connected via a LAN 2d. The LAN 2c and the LAN 2d are communicably connected via a dedicated line 2cd including the router 70cd, and are constructed in a predetermined area B. For example, the region B is an office in Osaka, the LAN 2c is built in the development part, and the LAN 2d is built in the development part 2. Area A and area B are connected to each other via routers (70ab, 70cd) via the Internet 2i.

  The terminal management system 50, the destination registration system 80, and the program providing system 90 are connected to the transmission terminal 10 and the relay device 30 through the Internet 2i so as to be communicable. The terminal management system 50, the destination registration system 80, and the program providing system 90 may be installed in the region A or the region B, or may be installed in a region other than these.

  In the present embodiment, the 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 may have a place where wireless communication such as WiFi (Wireless Fidelity) or Bluetooth (registered trademark) is performed in addition to wired communication.

  Also, in FIG. 1, four sets of numbers shown under each transmission terminal 10, each relay device 30, terminal management system 50, each router 70, destination registration system 80, and program providing system 90 are general The IP address in IPv4 is simply shown. For example, the IP address of the transmission terminal 10aa is “1.2.1.3”. In addition, IPv6 may be used instead of IPv4, but IPv4 will be used for the sake of simplicity.

  In addition, each transmission terminal 10 is not only a call between a plurality of offices, a call between different rooms in the same office, a call within the same room, a telephone call outdoors and indoors or outdoors and outdoors. May be used in When each transmission terminal 10 is used outdoors, wireless communication such as a cellular phone communication network is performed.

<Hardware Configuration of Embodiment>
Subsequently, the hardware configuration of the present embodiment will be described with reference to FIGS. 4 to 6. FIG. 4 is an external view of the transmission terminal. Hereinafter, the longitudinal direction of the transmission terminal 10 will be described as the X-axis direction, the direction orthogonal to the X-axis direction in the horizontal plane as the Y-axis direction, and the direction orthogonal to the X-axis direction and the Y-axis direction (vertical direction) as the Z-axis direction. .

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

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

  In the following description, “operation button 108” is used when an arbitrary operation button is indicated among the operation buttons (108a to 108e), and “an arbitrary connection port is indicated among the connection ports (1132a to 1132c)”. This will be described using the connection port 1132 ”.

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

  The camera housing 1300 is provided with a built-in camera 112 described later, and can capture images of users, documents, rooms, and the like. A torque hinge 1310 is formed in the camera housing 1300. The camera housing 1300 is attached to the arm 1200 via a torque hinge 1310. The camera housing 1300 is attached to the arm 1200 via a torque hinge 1310. The pan angle θ2 of ± 180 degrees is assumed with respect to the arm 1200, with the state shown in FIG. And a tilt angle θ3 of ± 45 degrees can be rotated in the vertical and horizontal directions.

  Note that the relay device 30, the terminal management system 50, the destination registration system 80, the program providing system 90, and the maintenance system 100 have the same external appearance as a general server computer, and thus the description of the external appearance is omitted.

  FIG. 5 is a hardware configuration diagram of the transmission terminal. As shown in FIG. 5, the transmission terminal 10 of this embodiment is used to drive a CPU 101 such as a CPU (Central Processing Unit) 101 that controls the operation of the entire transmission terminal 10 and an IPL (Initial Program Loader). ROM (Read Only Memory) 102 storing a program, RAM (Random Access Memory) 103 used as a work area of the CPU 101, a flash memory 104 storing various data such as a transmission terminal program, image data, and sound data, An SSD (Solid State Drive) 105 that controls reading or writing of various data to the flash memory 104 according to the control of the CPU 101, a media drive 107 that controls reading or writing (storage) of data to the recording medium 106 such as a flash memory, and transmission When selecting the destination of the terminal 10 An operation button 108 that is operated by the user, a power switch 109 for switching on / off the power of the transmission terminal 10, and a network I / F (Interface) 111 for data transmission using the communication network 2. .

  The transmission terminal 10 also includes a built-in camera 112 that captures an image of a subject under the control of the CPU 101 to obtain image data, an image sensor I / F 113 that controls driving of the camera 112, a built-in microphone 114 that inputs sound, The built-in speaker 115 that outputs sound, the sound input / output I / F 116 that processes input / output of sound signals between the microphone 114 and the speaker 115 according to the control of the CPU 101, and the image data on the external display 120 according to the control of the CPU 101 A display I / F 117 that transmits a signal, an external device connection I / F 118 that is attached to the connection port 1021g shown in FIG. 4 and connects various external devices, and an alarm lamp 119 that notifies abnormality of various functions of the transmission terminal 10 And an electrical connection for electrically connecting the above components as shown in FIG. And a Resubasu, a data bus, and the like bus line 110.

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

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

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

  Note that the camera 112, the microphone 114, and the speaker 115 are not necessarily built in, and may be configured such that only an external camera, an external microphone, and an external speaker can be connected. The recording medium 106 is detachable from the terminal 10. Further, as long as it is a non-volatile memory that reads or writes data according to the control of the CPU 101, not only the flash memory 104 but also an EEPROM (Electrically Erasable and Programmable ROM) or the like may be used.

  Further, the transmission terminal program may be installed in an installable or executable format, recorded on a computer-readable recording medium such as the recording medium 106, and distributed. The transmission terminal program may be stored in the ROM 102 instead of the flash memory 104.

  FIG. 6 is a hardware configuration diagram of the relay device, the terminal management system, the destination registration system, the program providing system, and the maintenance system. The terminal management system 50 includes a CPU 201 that controls the overall operation of the terminal management system 50, a ROM 202 that stores a program used to drive the CPU 201 such as an IPL, a RAM 203 that is used as a work area for the CPU 201, and various types of programs such as a terminal management program. HD 204 for storing data, HDD (Hard Disk Drive) 205 for controlling reading or writing of various data to the HD 204 according to control of the CPU 201, media for controlling reading or writing (storage) of data to a recording medium 206 such as a flash memory Drive 207, display 208 for displaying various information such as a cursor, menu, window, character, or image, network I / F 209 for data transmission using communication network 2, character A keyboard 211 having a plurality of keys for inputting numerical values and various instructions, a mouse 212 for selecting and executing various instructions, selecting a processing target, moving a cursor, etc., and a CD as an example of a removable recording medium A CD-ROM drive 214 for controlling reading or writing of various data with respect to a ROM (Compact Disc Read Only Memory) 213, and a bus line 210 such as an address bus or a data bus for electrically connecting the above components. It has.

  The terminal management program is a file in an installable or executable format, and may be recorded and distributed on a computer-readable recording medium such as the recording medium 206 or CD-ROM 213. . The terminal management program may be stored in the ROM 202 instead of the HD 204.

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

  Furthermore, since the destination registration system 80 has the same hardware configuration as the terminal management system 50, description thereof is omitted. However, a destination registration program for controlling the destination registration system 80 is recorded in the HD 204. Also in this case, the destination registration program is a file in an installable or executable format, and may be recorded and distributed on a computer-readable recording medium such as the recording medium 206 or CD-ROM 213. Good. Further, the destination registration program may be stored in the ROM 202 instead of the HD 204.

  Moreover, since the program providing system 90 and the maintenance system 100 have the same hardware configuration as the terminal management system 50, the description thereof is omitted. However, a program providing program for controlling the program providing system 90 is recorded in the HD 204. Also in this case, the program providing program is a file in an installable or executable format, and may be recorded and distributed on a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213. Good. The program providing system program may be stored in the ROM 202 instead of the HD 204. The same applies to the maintenance system 100 and the maintenance program.

  As another example of the detachable recording medium, the recording medium is provided by being recorded on a computer-readable recording medium such as a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), or a Blu-ray Disc. May be.

<Functional Configuration of Embodiment>
The functional configurations of the terminal management system 50 and the destination registration system 80 will be described below with reference to FIGS. FIG. 7 is a functional block diagram of the terminal management system and the destination registration system that constitute the transmission management system.

(Functional configuration of terminal management system)
First, the terminal management system 50 will be described. The terminal management system 50 includes a second communication unit 51, a second authentication unit 52, a storage control unit 53, and a storage unit 60 according to the hardware configuration and the terminal management program shown in FIG. The storage control unit 53 includes a storage / read processing unit 54, a second extraction unit 55, a terminal management unit 56, a destination list management unit 57, a request management unit 58, and a second determination unit 59. The storage unit 60 includes a terminal authentication management DB 61, a terminal management DB 62, a destination list management DB 63, a request management DB 64, and an administrator DB 65.

  FIG. 8 is a conceptual diagram of the terminal authentication management DB 61. In the terminal authentication management DB 61, information indicating a terminal ID and a password is managed as related information associated with each other. This terminal ID is identification information for identifying the transmission terminal 10. The terminal ID (an example of terminal identification information) may be identification information stored in the transmission terminal 10 in advance, or may be identification information input to the transmission terminal 10 by a user of the transmission terminal 10. Good. The password is a password for the transmission terminal 10 to log in to the transmission management system 40 with the terminal ID. The record of the terminal authentication management DB 61 may have a column (field) other than the above.

  FIG. 9 is a conceptual diagram of the terminal management DB 62. In the terminal management DB 62, each piece of information indicating a terminal ID, a name, an operating state, a reception date and time, and an IP address of the terminal is managed as related information associated with each other. This terminal ID is identification information for identifying the transmission terminal 10. The name is the name of the transmission terminal 10. However, the name of the user of the transmission terminal 10 or the name of a department may be used. The operating state is the latest operating state of the transmission terminal 10. The reception date and time is the date and time when a login request from the transmission terminal 10 to the transmission management system 40 is received. The IP address is the IP address of the transmission terminal 10. Note that the record of the terminal management DB 62 may have columns other than those described above.

  FIG. 10 is a conceptual diagram of the destination list management DB 63. In the destination list management DB 63, the terminal ID of the start terminal and the destination candidate terminal ID that can be the destination terminal are managed as related information associated with each other. Note that the record in the destination list management DB 63 may have columns other than those described above.

  FIG. 11 is a conceptual diagram of the request management DB 64. In the request management DB, the terminal ID of the request source terminal and the terminal ID of the request destination terminal are managed as related information associated with each other. The terminal ID of the request source terminal is identification information for identifying the transmission terminal 10 that has requested registration of the destination candidate. The terminal ID of the request destination terminal is identification information for identifying the transmission terminal 10 requested by the transmission terminal 10 identified by the request source terminal ID as a registration target of the destination candidate. Note that the record of the request management DB 64 may have columns other than those described above.

  FIG. 12 is a conceptual diagram of the administrator DB 65. In the administrator DB 65, the administrator ID, password, terminal ID of the management terminal, administrator email address, and administrator attribute information are associated and managed as related information. Note that as related information, at least the manager ID, the terminal ID of the management terminal, and the attribute information of the manager need only be associated.

  Among these, the manager ID is identification information for identifying the manager of the transmission terminal 10. The administrator ID may be the name of the administrator. The password is a password for logging in to the transmission management system 40 with the administrator ID. The terminal ID of the management terminal is identification information for identifying the management terminal (transmission terminal 10) managed by the administrator. The administrator email address is an administrator email address. The attribute information is affiliation information indicating the department to which an administrator belongs in an organization such as a company, position information indicating a position, and authority information indicating authority. The attribute information may be any one of these pieces of information (affiliation information, post information, authority information), or may be information combining at least two of these pieces of information. . Note that the record of the administrator DB 65 may have columns other than those described above.

  In this embodiment, in FIG. 1, the administrator A uses the administrator terminal 20a and manages a plurality of transmission terminals (10aa, 10ab,...) Connected to the LAN 2a as his management terminal. doing. The manager B uses the manager terminal 20b and manages a plurality of transmission terminals (10ba, 10bb,...) Connected to the LAN 2b as his management terminal. The administrator C uses the administrator terminal 20c, and manages a plurality of transmission terminals (10ca, 10cb,...) Connected to the LAN 2c as its own management terminal. The manager D uses the manager terminal 20d and manages a plurality of transmission terminals (10da, 10db,...) Connected to the LAN 2d as his management terminal.

  Returning to FIG. 7, the second communication unit 51 communicates with the transmission terminal 10 and other systems via the communication network 2.

  The second authentication unit 52 performs authentication when the transmission terminal 10 logs in to the terminal management system 50 (transmission management system 40) in order to start communication with the other transmission terminals 10. Specifically, the second authentication unit 52 uses the terminal ID and password included in the login information received by the second communication unit 51 as search keys and the terminal authentication management DB 61 of the storage unit 60. Search for. The second authentication unit 52 authenticates whether or not to permit login to the terminal management system 50 by determining whether or not the search key matches the information in the terminal authentication management DB 61.

  The terminal management unit 56 manages the operating state of the transmission terminal 10 that has made a login request to the transmission management system 40. The terminal management unit 56 updates the record in the terminal management DB 62 corresponding to the terminal ID of the transmission terminal 10 that has made a login request to the transmission management system 40. Specifically, when the login is successful, the “operation state” is changed from offline to online (transmittable), and “reception date” and “IP address” are updated.

  For example, the second extraction unit 55 searches the destination list management DB 63 using the terminal ID of the transmission terminal 10 that has made a login request to the transmission management system 40 as a search key, and is registered as a destination candidate of the transmission terminal 10 that has requested the login. Read the terminal ID. In addition, the second extraction unit 55 searches the terminal management DB 62 using the extracted terminal ID as a search key, and reads the operating state of the transmission terminal 10 for each extracted terminal ID. The read terminal ID and the operating state are transmitted to the transmission terminal 10 that has made a login request to the transmission management system 40 via the second communication unit 51. By this processing, the destination list showing the destination candidates is displayed on the display 120 of the requested transmission terminal 10, and the user of the transmission terminal 10 designates a desired destination from the destination list, whereby the transmission terminal 10. Session sed can be established between the transmission terminals 10 and communication between the transmission terminals 10 can be realized.

  Note that the session sed between the transmission terminals 10 may be established via the transmission management system 40 or may be directly exchanged without going through the transmission management system 40. Further, the transmission terminal 10 can exchange content data through the session sed.

  In addition, the second extraction unit 55 searches the destination list management DB 63 using the terminal ID of the transmission terminal 10 requested to log in to the transmission management system 40 as a search key, and the terminal ID of the transmission terminal 10 requested to log in is the destination candidate terminal. The terminal ID of the start terminal can also be extracted from the record registered as the ID. Accordingly, the second extraction unit 55 extracts the corresponding operating state by searching the terminal management DB 62 using the terminal ID of the start terminal that has registered the transmission terminal 10 that requested the login as a destination candidate as a search key. Can do.

  The request management unit 58 adds, changes, and deletes records in the request management DB 64.

  The destination list management unit 57 adds, changes, and deletes records in the destination list management DB 63. For example, the destination list management unit 57 extracts a record in the destination list management DB 63 in which the terminal ID of the request source terminal managed in the request management DB 64 matches the terminal ID of the start terminal in the destination list management DB 63. Then, the destination list management unit 57 adds the ID of the request destination terminal to the column of the destination candidate terminal ID in the extracted record.

  The storage / reading processing unit 54 performs processing for storing data in the storage unit 60. In addition, the storage / reading processing unit 54 performs processing for reading data stored in the storage unit 60.

  The second determination unit 59 determines whether the terminal ID and the administrator ID (first administrator ID) received by the second communication unit 51 are associated in the related information (first determination). In addition, when the second determination unit 59 determines that the terminal ID is not associated by the first determination, another administrator ID (second administrator ID) associated with the terminal ID in the related information is determined. Judgment is made (second judgment). Further, when the second determination unit 59 determines that there is the second administrator ID by the second determination, the attribute information (first attribute) associated with the first administrator ID in the related information Information) and the attribute information (second attribute information) associated with the second administrator ID in the related information is determined (third determination).

(Functional configuration of the destination registration system)
Next, the destination registration system 80 will be described. The destination registration system 80 includes a first communication unit 81, a first authentication unit 82, and a display control unit 83 according to the hardware configuration and the terminal management program shown in FIG. Further, the display control unit 83 includes a storage / read processing unit 84, a first extraction unit 85, a screen creation unit 86, and a first determination unit 87.

  Among them, the first communication unit 81, the storage / read processing unit 84, and the first extraction unit 85 have the same functions as the second communication unit 51, the storage / read processing unit 54, and the second extraction unit 55, respectively. The description is omitted. The destination registration system 80 does not include a storage unit, but by accessing the storage unit 60 of the terminal management system 50 via the communication network 2, the storage / read processing unit 84 and the first extraction unit 85 The same functions as those of the storage / read processing unit 54 and the second extraction unit 55 can be realized.

  The first authentication unit 82 performs authentication when the transmission terminal 10 or the administrator terminal 20 logs into the destination registration system 80 (transmission management system 40) in order to add or delete destination candidates. That is, a request for adding or deleting destination candidates can be made not only from the transmission terminal 10 but also from the administrator terminal 20.

  Further, the first authentication unit 82 uses the terminal ID (or administrator ID) and password included in the login information received by the first communication unit 81 as search keys, and the terminal authentication management DB 61 (or administrator DB 65) in the storage unit 60. ) The first authentication unit 82 permits login to the destination registration system 80 (transmission management system 40) by determining whether or not the search key and information in the terminal authentication management DB 61 (or administrator DB 65) match. Authentication of whether or not.

  The screen creation unit 86 includes an authentication screen (see FIG. 17), an administrator registration screen (see FIG. 18), a management terminal list screen (see FIG. 19), a management terminal registration screen (see FIG. 20), and a destination candidate registration screen (see FIG. 22) and the like. The screen creation unit 86 creates a screen by, for example, HTML (HyperText Markup Language).

  Next, a plurality of patterns will be described with reference to FIGS. 13 to 15 regarding destination candidate registration processing managed in the destination list.

(First pattern)
The first pattern is shown in FIG. 13, and the user of the transmission terminal 10aa wants to register the transmission terminal 10da of a different organization (for example, different “office”) as a destination candidate in his / her destination list. The registration process is shown. FIG. 13 is a conceptual diagram illustrating an example of destination candidate registration processing.

  First, the transmission terminal 10aa transmits to the transmission management system 40 a destination candidate registration request indicating that the transmission terminal 10da is requested to be registered as a destination candidate of the transmission terminal 10aa (ST11). Next, the transmission management system 40 transmits to the transmission terminal 10da an approval request indicating that an approval for registration as a destination candidate of the transmission terminal 10aa is requested (ST12). In response to this, the transmission terminal 10da transmits a response indicating approval or denial to the transmission management system 40 (ST13). When the transmission management system 40 receives a response indicating approval, the transmission management system 40 registers the transmission terminal 10da in the destination list management DB 63 as a destination candidate in the transmission terminal 10aa, and the registration of the destination is completed in the transmission terminal 10aa and the transmission terminal 10da. A registration completion notification indicating is transmitted (ST14).

(Second pattern)
The second pattern is shown in FIG. 14, and the user of the transmission terminal 10aa (first user aa) transmits the same organization (for example, the same “department”) as a destination candidate to his / her destination list. A registration process for registering the terminal 10ab is shown. FIG. 14 is a conceptual diagram illustrating an example of destination candidate registration processing.

  First, the transmission terminal 10aa transmits a destination candidate registration request indicating that the transmission terminal 10ab is requested to be registered as a destination candidate of the transmission terminal 10aa to the transmission management system 40 (ST21). Next, in the transmission management system 40, the transmission terminal 10aa that is the request source terminal and the transmission terminal 10ab that is the request destination terminal are the same management terminal of the manager A (transmission terminal under the management of the manager A). Is determined (ST22). Thereby, when the transmission terminal 10aa and the transmission terminal 10ab are the same management terminal of the administrator A, the transmission management system 40 does not bother to request the approval of the transmission terminal 10ab as in ST12. 10ab is registered in the destination list management DB 63 as a destination candidate in the transmission terminal 10aa, and a registration completion notification indicating that the registration of the destination is completed is transmitted to the transmission terminal 10aa and the transmission terminal 10ab (ST23).

  Note that the destination candidate registration request shown in ST21 may be made by the administrator A from the administrator terminal 20a to the transmission management system 40. When the administrator A makes a destination candidate registration request, the destination candidate registration requests of a plurality of transmission terminals 10 can be collectively requested.

(Third pattern)
The third pattern is shown in FIG. 15, and the user (first user aa) of the transmission terminal 10aa has different organizations (for example, different “departments”) as destination candidates in his / her destination list. The registration process is shown when it is desired to register the transmission terminal 10da of the user (second user ba) of the same “office”. In this case, the administrator of the transmission terminal 10aa (first administrator A) and the administrator of the transmission terminal 10ba (second administrator B) belong to different “sections”, but both belong to the same “department”. doing. FIG. 15 is a conceptual diagram illustrating an example of destination candidate registration processing.

  First, the transmission terminal 10aa transmits to the transmission management system 40 a destination candidate registration request indicating that the transmission terminal 10ba is requested to be registered as a destination candidate of the transmission terminal 10aa (ST31). Next, the transmission management system 40 includes an administrator (first administrator A) of the transmission terminal 10aa that is the request source terminal, and an administrator (second administrator B) of the transmission terminal 10ab that is the request destination terminal. Are determined to belong to the same attribute (for example, the same “department”) (ST32). Thereby, even if the transmission terminal 10ab is not under the control of the first administrator, if the first administrator A and the second administrator B have the same attribute, the transmission management system 40 determines that the above ST12 As described above, the transmission terminal 10ba is registered in the destination list management DB 63 as a destination candidate in the transmission terminal 10aa without making a request for approval to the transmission terminal 10ba, and the registration of the destination is completed in the transmission terminal 10aa and the transmission terminal 10ba. A registration completion notification indicating this is transmitted (ST33).

  Note that the destination candidate registration request shown in ST31 may be sent from the administrator terminal 20a to the transmission management system 40 by the administrator A. When the administrator A makes a destination candidate registration request, the destination candidate registration requests of a plurality of transmission terminals 10 can be collectively requested.

<Operation or Processing of Embodiment>
Subsequently, the operation or processing of this embodiment will be described with reference to FIGS. FIG. 16 is a flowchart showing a management method by the transmission management system 40.

  First, the first authentication unit 82 of the destination registration system 80 determines whether or not a login request is received from the administrator terminal 20 operated by the administrator via the communication network 2 using the administrator ID (step S101). When the login request is accepted with the administrator ID (step S101, Yes), the process proceeds to step S102. If the login request is not received by the administrator ID (the login request is received by the user by the terminal ID) (No in step S101), login processing by the terminal ID is performed (step S199). The transmission terminal 10 can only process the destination candidates in its own destination list, but the administrator registers the destination candidates in all the destination lists of the management terminal (the transmission terminal 10 under management). Can do.

  FIG. 17 is a conceptual diagram of an authentication screen of the transmission management system 40. Before the login request in step S101, the screen creation unit 86 displays, for example, the authentication screen shown in FIG. 17 on the administrator terminal 20 operated by the administrator via the first communication unit 81. Let

  Each screen data of FIG. 17 thru | or FIG. 23 is hold | maintained by the screen preparation part 86 itself. The screen data of FIGS. 17 to 23 are stored in the storage unit 60, and the storage / reading processing unit 84 reads out the screen data from the storage unit 60 in accordance with an instruction from the screen creation unit 86. Also good.

  Returning to FIG. 16, when it is determined in step S101 that a login request is made with an administrator ID (Yes in step S101), the first authentication unit 82 manages administrator information such as an administrator ID and a password. It is determined whether it is registered in the user DB 65 (step S102). When the administrator information is registered in the administrator DB 65 (No at Step S102), the first authentication unit 82 allows login (Step S104). On the other hand, when the administrator information is not registered in the administrator DB 65 (step S102, Yes), the screen creation unit 86 is connected to the administrator terminal 20 operated by the administrator via the first communication unit 81. After displaying the registration screen and registering the administrator information input to the registration screen in the administrator DB 65, the user logs in to the destination registration system 80 (step S103). An example of the case where the administrator information is not registered in the administrator DB 65 is, for example, the case where the administrator ID is used for the first time using the initial setting password.

  FIG. 18 is a conceptual diagram of an administrator registration screen. In step S103, for example, the administrator registration screen of FIG. 18 is displayed on the administrator terminal 20.

  Returning to FIG. 16, the screen creation unit 86 creates the management terminal list screen shown in FIG. 19, and the first communication unit 81 displays the screen by transmitting the data of the management terminal list screen to the administrator terminal 20. (Step S105). FIG. 19 is a conceptual diagram of the management terminal list screen. This management terminal list screen shows a list of transmission terminals managed by the administrator. The management terminal list screen is created by the terminal ID and name in the terminal management DB 62, the terminal ID of the start terminal in the destination list management DB 63 (same as the terminal ID in the terminal management DB 62), and the terminal ID of the destination candidate. Specifically, the first extraction unit 85 searches the administrator DB 65 using the administrator ID received by the destination registration system 80 as a search key, and acquires the terminal ID of the administrator terminal associated with the administrator ID. Thereby, the transmission terminal 10 managed by a specific administrator can be specified. Further, the first extraction unit 85 searches the terminal ID of the start terminal in the destination list management DB 63 using each acquired terminal ID as a search key, and acquires the terminal ID of the destination candidate associated with each terminal ID. The first extraction unit 85 searches the terminal management DB 62 using the terminal ID acquired in the same manner as described above as a search key, and acquires the name associated with each terminal ID. Based on the information acquired by the first extraction unit 85 in this manner, the screen creation unit 86 can create a management terminal list screen.

  On the management terminal list screen, a “management terminal registration” button for newly registering the transmission terminal 10 as a management terminal, and “management terminal deletion” for deleting the transmission terminal 10 already registered as the management terminal from the management terminal ”Button, a“ destination candidate registration ”button for newly registering the transmission terminal 10 as a destination candidate, and a“ destination candidate deletion ”button for deleting the transmission terminal 10 already registered as a destination candidate from the destination candidate Is displayed. A “logout” button for logging out is also displayed. Each of these buttons is selected by being pressed by the administrator.

  Next, the screen creation unit 86 determines whether the “management terminal registration” button or the “management terminal deletion” button has been selected on the administrator terminal 20 side (step S106). When the “management terminal registration” button or the “management terminal deletion” button is selected (step S106, Yes), the following (management terminal registration and deletion processing) is performed (step S107). On the other hand, if neither the “register management terminal” button nor the “delete management terminal” button is selected (No at Step S106), the process proceeds to Step S108.

  Next, the screen creation unit 86 determines whether the “destination candidate registration” button or the “destination candidate deletion” button has been selected on the administrator terminal 20 side (step S108). When the “destination candidate registration” button or the “destination candidate deletion” button is selected (step S108, Yes), the following (destination candidate registration and deletion processing) is performed (step S109). On the other hand, when neither the “register destination candidate” button nor the “delete destination candidate” button is selected (No at Step S108), the process proceeds to Step S110.

  Next, the screen creation unit 86 determines whether or not the administrator's operation is finished depending on whether the “logout” button is selected (step S110). When the “logout” button is selected (step S110, Yes), the destination registration system 40 logs out to the administrator terminal 20 (step S111). When the “logout” button is not selected (step S110, No), the process returns to step S106.

(Management terminal registration and deletion processing)
Next, the registration and deletion processing of the management terminal in step S107 will be described with reference to FIGS. FIG. 20 is a conceptual diagram of the management terminal registration screen. FIG. 21 is a conceptual diagram of a management terminal deletion confirmation screen. FIG. 24 is a flowchart showing management terminal registration and deletion processing.

  First, the first determination unit 87 determines whether to register the management terminal by determining whether the administrator selects the “management terminal registration” button or the “management terminal deletion” button (step S201). . When the “register management terminal” button is selected (step S201, Yes), the screen creation unit 86 uses the first communication unit 81 to display the administrator terminal 20 as shown in FIG. Send the management terminal registration screen data.

  On the other hand, the administrator terminal 20 displays a management terminal registration screen as shown in FIG. In this management terminal registration screen, a plurality of input fields for inputting the terminal ID (registration terminal ID) of the transmission terminal 10 that the administrator wishes to newly register as his / her management terminal are displayed. When the administrator inputs the terminal ID of the transmission terminal 10 in the input field and presses the “Register” button, the administrator terminal 20 displays the terminal ID input in the input field and the administrator ID of the input administrator. Is sent to the destination registration system 80. Thereby, the first communication unit 81 of the destination registration system 80 receives the registration request. Then, the storage / reading processing unit 84 stores the registered terminal ID in the terminal ID column in the record including the administrator ID used for the login process in step S101 in the administrator DB 65 of the terminal management system 50. Is added as a terminal ID (step S202).

  On the other hand, when it is not registration of a management terminal (step S201, No), the 1st judgment part 87 judges whether it is deletion of the transmission terminal 10 (step S203). When the management terminal is to be deleted (step S203, Yes), the screen creation unit 86, via the first communication unit 81, the terminal ID checked (selected) in the check box in FIG. By transmitting a deletion request including the administrator ID to the terminal management system 50, the storage / reading processing unit 54 of the terminal management system 50 stores the administrator ID used in the login process in the administrator DB 65. The terminal ID requested to be deleted is deleted from the record (step S204). If the transmission terminal 10 is not deleted (No at Step S203), the process ends. Further, in the process of step S203, the screen creation unit 86 causes the administrator terminal 20 to display the management terminal deletion confirmation screen shown in FIG. 21 via the first communication unit 81. FIG. 21 is a management terminal deletion confirmation screen. In this case, when the “OK” button is pressed by the administrator, the process of step S204 is executed, and when the “cancel” button is pressed, the process of step S204 is not executed.

  In addition, although FIG. 20 demonstrated the example in which an administrator inputs terminal ID, it is not restricted to this, For example, the file in which terminal ID was described is designated (it is necessary for the screen creation part 86 to refer to the said file) The terminal ID may be input by specifying a path).

(Destination candidate registration and deletion processing)
Next, destination candidate registration and deletion processing will be described with reference to FIGS. 22, 23, and 25. FIG. 22 is a conceptual diagram of a destination candidate registration screen. FIG. 23 is a conceptual diagram of a destination candidate deletion screen. FIG. 25 is a flowchart showing destination candidate registration and deletion processing. Here, an example of (pattern 3) shown in FIG. 15 will be described. However, here, a case is shown in which the administrator A makes a destination candidate registration request to the transmission management system 40 from the administrator terminal 20a instead of the user aa.

  First, the first determination unit 87 receives a request from the administrator terminal 20a by the administrator A by receiving a request source terminal that desires registration or deletion of the request destination terminal among the management terminals under the management of the administrator A. An original terminal is specified (step S301). Specifically, when the administrator A checks the check box of the transmission terminal (terminal ID) to be a request source terminal on the management terminal list screen shown in FIG. 19 and presses the “register destination candidate” button, A request source terminal that desires registration of a destination candidate is specified. In addition, when the administrator A checks the check box of the transmission terminal to be the request source terminal on the management terminal list screen shown in FIG. 19 and presses the “delete destination candidate” button, he / she wants to delete the destination candidate. The requesting terminal is identified.

  Next, the first determination unit 87 determines whether an operation such as pressing received from the administrator terminal 20a is an operation indicating registration of a destination candidate (step S302). For example, the first determination unit 87 determines whether or not the “destination candidate registration” button on the management terminal list screen illustrated in FIG. 19 has been pressed. If the operation is not an operation indicating registration of a destination candidate (step S302, No), the process proceeds to step S312. In the case of an operation indicating registration of a destination candidate (step S302, Yes), the display control unit 83 causes the management terminal 20a to display a destination candidate registration screen as illustrated in FIG. 22 via the first communication unit 81. The destination candidate registration screen is displayed on the management terminal 20a (step S303).

  As shown in FIG. 22, the destination candidate registration screen displays a plurality of input fields for inputting the terminal ID (registered terminal ID) of the transmission terminal 10 that is newly registered as a destination candidate. . Further, for each registered terminal ID, as shown in ST12 of FIG. 13, an approval for asking the request destination terminal whether the request destination terminal may be registered as a destination candidate in the destination list of the request source terminal. A check box is displayed as an item for selecting whether or not to omit the request.

  Next, returning to FIG. 25, the administrator A inputs a desired terminal ID in the input field of the destination candidate registration screen shown in FIG. 22 and presses the “Register” button. The designation of the transmission terminal 10 requested to be registered as a candidate is accepted (step S304). The terminal ID of the transmission terminal 10 requested to be registered is transmitted from the destination registration system 80 to the terminal management system 50. More specifically, the first communication unit 81 of the destination registration system 80 transmits a destination candidate registration request to the second communication unit 51 of the terminal management system 50. In this registration request, the terminal ID of the request source terminal (request source terminal specified in step S301) requesting registration of the destination candidate and the request destination terminal requested to register as the destination candidate (input on the screen of FIG. 22) are input. Terminal ID of the request destination terminal indicated by the terminal ID) and the logged-in administrator ID. If the check box for omitting approval in each registration terminal ID on the destination candidate registration screen shown in FIG. 22 is checked, the request for registration is requested to be omitted from the registration request. Approval request omission request information indicating that is included.

  Next, the second determination unit 59 of the terminal management system 50 determines whether or not omission of the approval process is requested for each request destination terminal that may be registered as a destination candidate based on the received registration request. Judgment is made (step S305). Specifically, if the received registration request includes the approval request omission request information, the second determination unit 59 sets the request destination terminal in which the check box illustrated in FIG. 22 is checked. On the other hand, it is determined that an approval request is not required, and it is determined that an approval request is required for a request destination terminal whose check box is not checked.

  When the check box is checked in FIG. 22, the second determination unit 59 refers to the administrator DB 65 to refer to the terminal ID (specific terminal) of the request destination terminal requested to register as a destination candidate. ID) and an administrator ID (first administrator ID) are determined (step S306). If it is associated (step S306, YES), the approval process is not required, and the process proceeds to step S307. If not associated (step S306, NO), the process proceeds to step S308 for further determination.

  Next, in step S308, the second determination unit 59 determines whether there is another administrator ID (second administrator ID) associated with the specific terminal ID in the administrator DB 65, thereby registering it. It is determined whether the destination candidate to be managed is also managed by another administrator. If there is another associated administrator ID (step S308, YES), the second determination unit 59 further uses the first administrator ID associated with the first administrator ID in the administrator DB 65. It is determined whether the attribute information of the second and the second attribute information associated with the second administrator ID are the same (step S309). If the first attribute information and the second attribute information are the same (step S309, YES), the process proceeds to step S307. In step S308, when there is no other associated administrator ID (step S308, NO), and in step S309, the first attribute information and the second attribute information are not the same (step S309). , NO), the process proceeds to step S310.

  Next, in step S310, the first communication unit 81 of the destination registration system 80 transmits a destination registration approval request to the transmission terminal 10 requested to register as a destination candidate. More specifically, it can be realized by the following processing, for example.

  That is, if it is selected in step S305 that the approval is not omitted, the request management unit 58 of the terminal management system 50 creates a new association that associates the request source terminal ID and the request destination terminal ID included in the received registration request. Records are additionally stored in the request management DB 64. Then, the second extraction unit 55 of the terminal management system 50 extracts the corresponding operating state information by searching the terminal management DB 62 using the terminal ID of the request destination terminal in the request management DB 64 as a search key. When the operating state is communicable (for example, online (transmittable) or the like), the second communication unit 51 transmits a destination registration approval request to the communicable transmission terminal 10. Note that an approval request is transmitted to the transmission terminal 10 whose operation state is not communicable (for example, offline) when the operation state is updated to be communicable.

  Next, after step S310, the second determination unit 59 of the transmission management system 40 determines whether an approval response has been received from the request destination terminal that has received the approval request (step S311). And when the 2nd communication part 51 receives the response of approval (step S311, Yes), it progresses to step S307. In step S307, the destination list management unit 57 registers the terminal ID of the request destination terminal as a destination candidate when the request source terminal is the start terminal in the destination list management DB 63, and the request destination terminal is the start terminal. As a destination candidate in this case, the terminal ID of the request source terminal is registered (step S308). That is, the request source terminal and the request destination terminal are registered as destination candidates.

  In step S307, the request source terminal and the request destination terminal may not be registered as destination candidates, but the terminal ID of the request destination terminal may be registered in the destination candidate of the request source terminal.

  When the registration is completed, the second communication unit 51 transmits a registration completion notification to the request source terminal and the request destination terminal. When the above processing is completed, the request management unit 58 of the terminal management system 50 deletes the registered record from the request management DB 64. When the omission of approval is not requested in step S305 (NO), no new record is added to the request management DB 64 for the set of the terminal ID of the request source terminal and the terminal ID of the request destination terminal. Therefore, there is no need for deletion.

  Note that step S306 may be executed even if NO in step S305. In this case, step S307 can be executed regardless of whether or not there is a response to the approval request for registering the destination candidate, and whether or not the response indicates approval.

  Next, a process for deleting a destination candidate will be described.

  In the case of NO in step S302, the first determination unit 87 determines whether the operation is an operation indicating deletion of a destination candidate (step S312). For example, the first determination unit 87 determines whether or not the “delete destination candidate” button on the management terminal list screen in FIG. 19 has been pressed. In this case, the destination candidate of the transmission terminal 10 whose check box is checked on the management terminal list screen is a deletion target.

  If the operation is not an operation indicating deletion of the destination candidate (No in step S312), the process illustrated in FIG. 25 ends. If the operation is an operation indicating deletion of the destination candidate (step S312, Yes), the screen creation unit 86 sends the destination candidate as shown in FIG. 23 to the administrator terminal 20 via the first communication unit 81. A deletion screen is displayed, and a destination candidate to be deleted is specified based on the terminal ID input by the administrator (step S313). FIG. 21 is a confirmation screen for deleting the management terminal. In this case, when the administrator inputs the terminal ID of the destination candidate to be deleted from the destination list and presses the “delete” button, the process of step S313 is executed.

  Then, the storage / reading processing unit 84 deletes the identified destination candidate terminal ID from the destination list management DB 63 (step S314).

<Main effects of the embodiment>
As described above, according to the present embodiment, as shown in FIG. 15, even when the transmission terminal 10 not managed by the administrator is requested to register as a destination candidate, the administrator If an administrator with the same attribute (affiliation department, etc.) manages the transmission terminal 10 (ensures security), the user of the transmission terminal 10 does not bother to perform an approval process (smooth registration). Can be registered as destination candidates. Thereby, there is an effect that registration of destination candidates can be made smoother while maintaining a certain level of security.

[Second Embodiment]
Subsequently, a second embodiment of the present embodiment will be described with reference to FIG. Here, another example of the administrator DB 65 shown in the first embodiment will be described. FIGS. 26A and 26B are conceptual diagrams of the administrator DB according to the second embodiment. As shown in FIG. 26, the administrator DB 65 ′ of this embodiment is constructed by two tables. That is, as shown in FIG. 26A, as the first table, an administrator ID, a password, an administrator email address, and attribute information are managed in association with each other. Further, as shown in FIG. 26B, as the second table, the manager ID and the terminal ID are managed in association with each other. As described above, the information shown in FIGS. 26A and 26B corresponds to the “related information” shown in the first embodiment. Note that the administrator ID, password, terminal ID, administrator e-mail address, and attribute information are the same as those in the first embodiment, and thus description thereof is omitted.

  In this case, the same effect as that of the first embodiment can be obtained.

[Other Embodiments]
In the above embodiment, at least one of the processing in step S306 and the processing in step S308 may be omitted.

  Further, the transmission management system 40 can be applied to any system as long as it is a communication system capable of communicating between the transmission terminals 10. For example, the present invention can be applied to a TV (video) conference system, a sound conference system, a sound phone system (including a mobile phone system), a text chat system, or a whiteboard sharing system. The transmission terminal 10 may be a dedicated terminal for the communication system described above or a dedicated terminal for a game, or may be a general-purpose terminal such as a personal computer, a smartphone, a mobile phone terminal, or a tablet terminal. Further, the terminal management system 50 and the destination registration system 80 may be any information processing apparatus including the functional blocks illustrated in FIG. 7, and may be a dedicated server apparatus or a general-purpose terminal apparatus.

DESCRIPTION OF SYMBOLS 1 Transmission system 10 Transmission terminal 20 Administrator terminal 40 Transmission management system 50 Terminal management system 51 2nd communication part (an example of a receiving means)
52 Second Authentication Unit 54 Storage / Read Processing Unit (Example of Registration Unit)
55 Second extraction unit 59 Second determination unit (an example of determination means)
60 storage unit (an example of storage means)
61 Terminal authentication management DB
62 Terminal management DB
63 Destination list management DB
64 Request management DB
65 Administrator DB
80 Destination Registration System 81 First Communication Unit (Example of Receiving Unit)
82 First Authentication Unit 84 Storage / Read Processing Unit 85 First Extraction Unit 87 First Determination Unit

JP 2006-074453 A

Claims (7)

A transmission management system for managing destination candidates of a predetermined transmission terminal,
Association associated with administrator identification information for identifying an administrator who manages a predetermined transmission terminal, predetermined terminal identification information for identifying the predetermined transmission terminal, and attribute information indicating the attribute of the administrator Storage means for storing information;
Receiving means for receiving specific terminal identification information for identifying a transmission terminal as a destination candidate of the predetermined transmission terminal, and first manager identification information for identifying a first manager;
When the specific terminal identification information and the first administrator identification information received by the receiving means are not associated in the related information, the related information is associated with the first administrator identification information. Determining means for determining whether the first attribute information is the same as the second attribute information associated with the specific terminal identification information in the related information;
A registering unit for registering the specific terminal identification information as a destination candidate of the predetermined transmission terminal when the determining unit determines that the first attribute information and the second attribute information are the same; ,
A transmission management system comprising: The determination unit determines whether the specific terminal identification information and the first administrator identification information received by the reception unit are associated in the related information;
When the determination means determines that the information is not associated, the first attribute information associated with the first administrator identification information in the related information and the specific terminal identification information in the related information 2. The transmission management system according to claim 1, wherein it is determined whether the second attribute information associated with the same is the same. When the determination unit determines that the specific terminal identification information and the first administrator identification information received by the reception unit are not associated in the related information, the specific terminal identification information is Determining whether there is the second administrator information associated in the related information;
The determination means includes first attribute information associated with the first administrator identification information in the related information, and second attribute information associated with the specific terminal identification information in the related information; The transmission management system according to claim 2, wherein it is determined whether or not they are the same.   The related information includes first related information associated with the administrator identification information and the attribute information, and second related information associated with the administrator identification information and the predetermined terminal identification information. The transmission management system according to any one of claims 1 to 3.   The attribute information includes at least one of affiliation information indicating affiliation in the administrator's organization, position information indicating position in the administrator's organization, and authority information indicating authority in the administrator's organization. The transmission management system according to any one of claims 1 to 4, wherein the transmission management system is characterized in that: A management method executed by a transmission management system that manages destination candidates of a predetermined transmission terminal,
The transmission management system includes administrator identification information for identifying an administrator who manages a predetermined transmission terminal, predetermined terminal identification information for identifying the predetermined transmission terminal, and an attribute indicating the attribute of the administrator Storage means for storing related information associated with the information;
The transmission management system includes:
Receiving step of receiving specific terminal identification information for identifying a transmission terminal as a destination candidate of the predetermined transmission terminal, and first administrator identification information for identifying the first administrator;
If the specific terminal identification information and the first administrator identification information received by the receiving step are not associated in the related information, the related information is associated with the first administrator identification information. A determination step of determining whether the first attribute information is the same as the second attribute information associated with the specific terminal identification information in the related information;
A registration step of registering the specific terminal identification information as a destination candidate of the predetermined transmission terminal when the determination step determines that the first attribute information and the second attribute information are the same; ,
The management method characterized by performing.   A program for causing a computer to execute the method according to claim 6.

Images