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

Abstract

To provide a transmission management system, a management method, and a program that, even when the transmission management system manages relevant information corresponding to a destination list, can delete a desired destination candidate from the relevant information.SOLUTION: A manager terminal 20a under management of a manager A transmits, to a transmission management system 40, a deletion request for deleting a transmission terminal 10ca not under the management from destination lists (destination list management DBs) of transmission terminals under the management (10aa, 10ab) (ST31). The transmission management system 40 then performs batch deletion from the destination lists (destination list management DBs) (ST32), and transmits deletion completion notice to the transmission terminals (10aa, 10ab, 10ca) (ST33).SELECTED DRAWING: Figure 15

Description

  The present invention relates to the invention of managing destination candidates of a predetermined transmission terminal.

  2. Description of the Related Art In recent years, transmission systems for conducting video conferences and the like via communication networks such as the Internet have become widespread along with requests to reduce business trip expenses and business trip time. In such a transmission system, when a call is started between a plurality of transmission terminals, image data and audio data are transmitted and received, and a video conference can be realized.

  Also, in order to make it easy for the user to select a desired destination terminal from among the call destination candidates, the destination terminal can be displayed to the user by displaying the destination list on the side of the start terminal that requests the start of the call. It can also be selected (see Patent Document 1). Further, when a new destination candidate is registered in the destination list, the management server inquires of the transmission terminal as a new destination candidate whether it may be registered as a destination candidate or not, If the registration is approved on the transmitting terminal side, the destination candidate is newly registered (see Patent Document 2).

  On the other hand, in the case of a portable telephone, it is well known that the user of the portable telephone can delete the destination candidate from the destination list registered in his / her portable telephone.

  However, in the invention described in Patent Document 2, the start terminal does not manage the destination list by itself, and a management server (transmission management system) connected to the start terminal via the communication network manages the destination list. There is. In such a case, Patent Document 2 does not disclose a method of deleting a destination candidate from the destination list.

  The invention according to claim 1 is a transmission management system for managing a destination candidate of a predetermined transmission terminal, wherein a start terminal identification for identifying a start terminal which is a transmission terminal requesting a start of communication among the transmission terminals. Storage means for storing related information in which information and destination candidate identification information for identifying the destination candidate of the start terminal are associated, and destination candidate identification information associated with specific start terminal identification information Receiving means for receiving a deletion request for deleting specific destination candidate identification information, and a destination to which the specific starting terminal identification information is associated in the related information based on the deletion request received by the receiving means It is a transmission management system characterized by having a deletion means which deletes said specific addressee candidate identification information among candidate identification information.

  As described above, according to the present invention, even when related information corresponding to a destination list is managed on the transmission management system side, a desired destination candidate can be deleted from the related information. Play.

FIG. 1 is a schematic view of a transmission system according to a first embodiment of the present invention. FIG. 2 is a conceptual diagram showing the state of transmission and reception of image data, sound data, and various management information in the transmission system. FIG. 3 is a conceptual diagram for explaining 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 a relay device, a terminal management system, a destination registration system, a program providing system, and a maintenance system. FIG. 7 is a functional block diagram of a terminal management system and a destination registration system constituting the transmission management system. FIG. 8 is a conceptual view of a terminal authentication management DB. FIG. 9 is a conceptual view of a terminal management DB. FIG. 10 is a conceptual diagram of the destination list management DB. FIG. 11 is a conceptual view of a request management DB. FIG. 12 is a conceptual view of a manager DB. FIG. 13 is a conceptual diagram showing an example of destination candidate registration processing. FIG. 14 is a conceptual diagram showing an example of destination candidate registration processing. FIG. 15 is a conceptual diagram showing an example of destination candidate deletion processing. FIG. 16 is a flowchart showing a management method by the transmission management system. FIG. 17 is a conceptual view of an authentication screen. FIG. 18 is a schematic view of the manager registration screen. FIG. 19 is a conceptual view of a management terminal list screen. FIG. 20 is a conceptual diagram of a management terminal registration screen. FIG. 21 is a conceptual diagram of a management terminal deletion confirmation screen. FIG. 22 is a conceptual diagram of the destination candidate registration screen. FIG. 23 is a conceptual diagram of the destination candidate deletion screen. FIG. 24 is a conceptual diagram of the destination candidate deletion screen. FIG. 25 is a flowchart showing processing of registration and deletion of a management terminal. FIG. 26 is a flowchart showing processing of registration and deletion of a destination candidate. FIG. 27 is a conceptual diagram of a manager DB according to the second embodiment.

  Hereinafter, embodiments of the present invention will be described using 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 view of a transmission system according to a first embodiment of the present invention. FIG. 2 is a conceptual diagram showing the state of transmission and reception of image data, sound data, and various management information in the transmission system. FIG. 3 is a conceptual diagram for explaining the image quality of image data.

  The transmission system 1 further includes a communication system for mutually transmitting information, emotions, etc. among 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 this embodiment). An example is a television (video) conference system or the like.

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

  The plurality of transmission terminals 10 transmit and receive image data and sound data as an example of content data. Note that text data can be given as another example of content data. Also, the content data may include at least one of image data, sound data, and text data.

  Hereinafter, an arbitrary transmission terminal among the plurality of transmission terminals (10aa, 10ab,...) Will be referred to as “transmission terminal 10”, and an arbitrary display among the plurality of displays (120aa, 120ab,. Among the plurality of relay devices (30a, 30b, 30c, and 30d), any relay device is represented as "the relay device 30".

  Further, the transmission terminal 10 which is a request source requesting the start of a video conference or the like is represented as a "start terminal", and the transmission terminal 10 as a destination (relay destination) which is a request destination is represented as a "destination terminal". Furthermore, the transmission terminal 10 that makes a request for registering the transmission terminal 10 of the other party in its own destination list is represented as a "request source terminal", and the transmission terminal 10 of the other party in this case is represented as a "request destination terminal" .

  Further, as shown in FIG. 2, in the transmission system 1, a management information session sei for transmitting and receiving various management information between the start terminal and the destination terminal via the terminal management system 50 is provided. Is established. Also, between the start terminal and the destination terminal, four pieces of data of high resolution image data, medium resolution image data, low resolution image data, and sound data are transmitted and received via the relay device 30. Four sessions are established. Here, these four sessions are collectively shown as image / sound data session sed. Note that the start terminal and the destination terminal do not necessarily have to go 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 of the image data handled in the present embodiment will be described. As shown in FIG. 3A, the low resolution image, which is 160 pixels wide and 120 pixels high and is a base image, and as shown in FIG. 3B, is horizontal As shown in FIG. 3C, there are a medium resolution image consisting of 320 pixels and 240 vertical pixels, and a high resolution image consisting of 640 horizontal pixels and 480 vertical pixels. Among these, when passing through a narrow band path, low-quality image data consisting only of low-resolution image data to be a base image is relayed. When the bandwidth is relatively wide, low-resolution image data to be a base image and medium-quality image data consisting of medium-resolution image data are relayed. Further, when the bandwidth is very wide, high-quality image data consisting of low-resolution image data serving as a base image, medium-resolution image data, and high-resolution image data is relayed.

  The relay device 30 shown in FIG. 1 relays content data between 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 a destination list, etc., and communication status etc. of the relay device 30. The image of the image data may be a moving image or a still image, or may be both a moving image and a still image.

  A plurality of routers (70a, 70b, 70c, 70d, 70ab, 70cd) perform selection of an optimal path of image data and sound data. In the following, any of the routers (70a, 70b, 70c, 70d, 70ab, 70cd) is represented as "router 70".

  The program providing system 90 includes an HD (Hard Disk) 204 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, a transmission management program for causing the terminal management system 50 to realize various functions (or to cause the terminal management system 50 to function as various means) is also stored in the HD 204 of the program providing system 90, and the terminal management system At 50, a transmission management program can be sent. 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). At 80, a destination registration program can be sent. 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 maintaining, managing, or maintaining 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 Japan, and the transmission terminal 10, the relay apparatus 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 a communication network 2 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 is performed remotely via the above. In addition, the maintenance system 100 does not go through the communication network 2, but the model number and the serial number 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. Perform maintenance such as sales destination, maintenance inspection, or management of failure history.

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

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

  The terminal management system 50, the destination registration system 80, and the program providing system 90 are communicably connected to the transmission terminal 10 and the relay device 30 via the Internet 2i. The terminal management system 50, the destination registration system 80, and the program providing system 90 may be installed in the area A or the area B, or may be installed in areas 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 portions where wireless communication such as WiFi (Wireless Fidelity) or Bluetooth (registered trademark) is performed as well as 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 generally IP addresses in simple IPv4 are shown. For example, the IP address of the transmission terminal 10aa is "1.2.1.3". Also, although IPv6 may be used instead of IPv4, in order to simplify the description, IPv4 will be used.

  In addition, each transmission terminal 10 is not only a call between a plurality of establishments, a call between different rooms in the same establishment, a call in the same room, and an outside and an indoor or an outside and an outside. 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 (vertical direction) orthogonal to the X-axis and Y-axis directions 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 wall surface 1110 of the housing 1100 is provided with a suction surface (not shown) formed by a plurality of suction holes, and the rear 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 the cooling fan incorporated in the housing 1100, the outside air at the rear of the terminal 10 can be taken in via the air intake surface (not shown) and exhausted to the rear of the terminal 10 via the exhaust surface 1121. A sound collecting hole 1131 is formed on the right side wall surface 1130 of the housing 1100, and a sound such as sound, noise, and the like 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) which will be described later, a power switch 109 which will be described later, and an alarm lamp 119 which will be described later. A sound emitting surface 1151 formed by a plurality of sound output holes for passing therethrough is formed. Further, on the side of the left side wall surface 1140 of the housing 1100, a housing portion 1160 as a concave portion for housing the arm 1200 and the camera housing 1300 is formed. The right wall surface 1130 of the housing 1100 is provided with a plurality of connection ports (1132 a to 1132 c) for electrically connecting a cable 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 a cable 120 c for the display 120 to an external device connection I / F 118 described later.

  In the following, the "operation button 108" is used to indicate any of the operation buttons (108a to 108e), and "if any connection port of the connection ports (1132a to 1132c) is indicated. Description will be made using the connection port 1132 ".

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

  The camera housing 1300 is provided with a built-in camera 112 described later, and can image a user, a document, a room, and the like. Further, 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 the torque hinge 1310, and the camera housing 1300 is at a pan angle θ2 of ± 180 ° with the state shown in FIG. In the range of ± 45 degrees, and in the range of the tilt angle θ3, it is configured to be rotatable in the vertical and horizontal directions.

  The relay apparatus 30, the terminal management system 50, the destination registration system 80, the program providing system 90, and the maintenance system 100 are the same as the appearance of a general server computer, and thus the description of the appearance is omitted.

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

  In addition, the transmission terminal 10 has a built-in camera 112 that captures an object and obtains image data according to control of the CPU 101, an imaging device I / F 113 that controls driving of the camera 112, and a built-in microphone 114 that inputs sound. A built-in speaker 115 for outputting sound, a sound input / output I / F 116 for processing input / output of a sound signal between the microphone 114 and the speaker 115 under the control of the CPU 101, an image data on the external display 120 under the control of the CPU 101 4, an external device connection I / F 118 attached to the connection port 1021g shown in FIG. 4 for connecting various external devices, and an alarm lamp 119 notifying an abnormality in various functions of the transmission terminal 10. And for electrically connecting the above-mentioned 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 of a liquid crystal or an organic EL that displays an image of a subject, an operation icon, and the like. The display 120 is also connected to the display I / F 117 by a cable 120c. The cable 120c may be a cable for an analog RGB (VGA) signal or a cable for a component video, or a cable for HDMI (High-Definition Multimedia Interface) or DVI (Digital Video Interactive) signals. It may be a cable of

  The camera 112 includes a lens and a solid-state imaging device that converts light into electric charge to digitize an image (image) of a subject, and as a solid-state imaging device, a complementary metal oxide semiconductor (CMOS) or a charge coupled device (CCD) Etc. are used.

  An external device 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 prior to the built-in camera 112 according to the control of the CPU 101. Similarly, when an external microphone is connected or an external speaker is connected, the external microphone or the external speaker 115 is given priority over the built-in microphone 114 or the built-in speaker 115 according to the control of the CPU 101. External speakers drive.

  The camera 112, the microphone 114, and the speaker 115 do not necessarily have to be built-in, and only an external camera, an external microphone, and an external speaker may be connected. Also, the recording medium 106 is configured to be attachable to and detachable from the terminal 10. Further, as long as the nonvolatile memory performs reading or writing of data according to the control of the CPU 101, not only the flash memory 104 but also EEPROM (Electrically Erasable and Programmable ROM) or the like may be used.

  Furthermore, the program for the transmission terminal may be recorded and distributed in a computer readable recording medium such as the recording medium 106 in the form of an installable or executable file. 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 a relay device, a terminal management system, a destination registration system, a program providing system, and a maintenance system. The terminal management system 50 includes a CPU 201 for controlling the overall operation of the terminal management system 50, a ROM 202 storing programs used to drive the CPU 201 such as IPL, a RAM 203 used as a work area for the CPU 201, and various programs for terminal management. HD 204 for storing data, HDD (Hard Disk Drive) 205 for controlling reading and writing of various data to HD 204 according to control of CPU 201, and media for controlling reading and writing (storage) of data to recording media 206 such as flash memory. A drive 207, a display 208 for displaying various information such as a cursor, a menu, a window, characters, or an image, a network I / F 209 for transmitting data using the communication network 2, characters 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 an object to be processed, moving a cursor, etc. CD as an example of a removable recording medium -A CD-ROM drive 214 that controls reading and writing of various data 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-described components. Is equipped.

  The terminal management program may be a file in an installable format or an executable format, and may be distributed by being recorded in a computer readable storage medium such as the storage medium 206 or the CD-ROM 213. . The terminal management program may be stored not in the HD 204 but in the ROM 202.

  Further, since the relay device 30 has the same hardware configuration as that of the terminal management system 50, the description thereof will be omitted. However, the relay device program for controlling the relay device 30 is recorded in the HD 204. Also in this case, the program for the relay device may be recorded and distributed in a computer readable recording medium such as the recording medium 206 and the CD-ROM 213 in the form of an installable or executable file. Good. Furthermore, 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, the description thereof will be omitted. However, in the HD 204, a destination registration program for controlling the destination registration system 80 is recorded. Also in this case, the destination registration program is recorded and distributed in a computer readable recording medium such as the recording medium 206 or the CD-ROM 213 in the form of an installable or executable file. Good. The destination registration program may be stored not in the HD 204 but in the ROM 202.

  Further, 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 will be 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 for program provision is a file of an installable format or an executable format, and may be recorded and distributed in a computer readable recording medium such as the recording medium 206 or the CD-ROM 213. Good. Further, the program for the program providing system may be stored in the ROM 202 instead of the HD 204. The same applies to the maintenance system 100 and the maintenance program.

  In addition, as another example of the removable recording medium, it is configured to be provided by being recorded on a computer-readable recording medium such as a compact disc recordable (CD-R), a digital versatile disc (DVD), and a Blu-ray disc. You may

<Functional Configuration of Embodiment>
The functional configurations of the terminal management system 50 and the destination registration system 80 will be particularly described below with reference to FIGS. 7 to 12. FIG. 7 is a functional block diagram of a terminal management system and a 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 view of the terminal authentication management DB 61. As shown in FIG. In the terminal authentication management DB 61, each piece of information indicating a terminal ID and a password is managed as related information associated with each other. The terminal ID is identification information for identifying the transmission terminal 10. The terminal ID (an example of the terminal identification information) may be identification information stored in advance in the transmission terminal 10, or may be identification information input by the user of the transmission terminal 10 to 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 records of the terminal authentication management DB 61 may have columns (fields) other than the above.

  FIG. 9 is a conceptual view of the terminal management DB 62. As shown in FIG. In the terminal management DB 62, each piece of information indicating the terminal ID, the name, the operation status, the reception date and time, and the IP address of the terminal is managed as related information associated with each other. The terminal ID is identification information for identifying the transmission terminal 10. The name is the name of the transmission terminal 10. However, it may be the name of the user of the transmission terminal 10 or the name of the department. The operating state is the latest operating state of the transmission terminal 10. The reception date is the date 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. The record of the terminal management DB 62 may have columns other than the above.

  FIG. 10 is a conceptual view of the destination list management DB 63. As shown in FIG. In the destination list management DB 63, the terminal ID of the start terminal and the terminal ID of a destination candidate that can be a destination terminal are managed as related information associated with each other. The records of the destination list management DB 63 may have columns other than the above.

  FIG. 11 is a conceptual view 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. The records of the request management DB 64 may have columns other than the above.

  FIG. 12 is a conceptual view of the administrator DB 65. In the manager DB 65, a manager ID, a password, a terminal ID of a management terminal, a manager's e-mail address, and attribute information of the manager are associated and managed as related information. As the related information, at least a manager ID, a terminal ID of a management terminal, and attribute information of the manager may be associated.

  Among these, the administrator ID is identification information for identifying the administrator 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 the administrator's email address. The attribute information is department information indicating the department to which the manager belongs in an organization such as a company, post information indicating the post, and authority information indicating the authority and the like. The attribute information may be any one of these pieces of information (belonging information, post information, authority information), or may be information combining at least two or more of these pieces of information. . The records of the administrator DB 65 may have columns other than the above.

  Further, in the present 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 its own 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 a management terminal of the manager B. 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 administrator D uses the administrator terminal 20d and, as his own management terminal, manages a plurality of transmission terminals (10da, 10db,...) Connected to the LAN 2d.

  Referring back to FIG. 7, the second communication unit 51 communicates with the transmission terminal 10 or another system 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 (the transmission management system 40) in order to start communication with another transmission terminal 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 judging whether or not the search key matches the information in the terminal authentication management DB 61.

  The terminal management unit 56 manages the operation 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 of 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 "operating status" is changed from offline to online (transmittable), and the "reception date" and the "IP address" are updated.

  The second extraction unit 55 searches the destination list management DB 63 using, for example, 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 made the login request. Read terminal ID. Further, 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 of the extracted terminal IDs. The read terminal ID and the operation 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 display 120 of the transmission terminal 10 which made the request displays the destination list in which the destination candidate is indicated, and the user of the transmission terminal 10 designates the desired destination from the destination list to thereby transmit the transmission terminal 10. It is possible to establish a session sed between them, and communication between the transmission terminals 10 can be realized.

  The establishment of the session sed between the transmission terminals 10 may be performed via the transmission management system 40 or may be directly exchanged without the intervention. Also, the transmission terminal 10 can exchange content data by the session sed.

  Further, 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 the terminal ID of the transmission terminal 10 having made a login request is a candidate terminal. The terminal ID of the start terminal can also be extracted from the record registered as the ID. Thereby, the second extraction unit 55 extracts the corresponding operation state by searching the terminal management DB 62 using the terminal ID of the start terminal registering the transmission terminal 10 that has made the login request as the destination candidate as a search key. Can.

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

  The destination list management unit 57 adds, changes, and deletes records of the destination list management DB 63. For example, the destination list management unit 57 extracts a record of the destination list management DB 63 in which the terminal ID of the request source terminal managed by 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 terminal ID of the destination candidate in the extracted record.

  The storage / read processing unit 54 performs processing for storing data in the storage unit 60. In addition, the storage / read processing unit 54 performs a process of 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 it is not associated by the first determination, another administrator ID (second administrator ID) in which the terminal ID is associated in the related information is Determine whether there is (second determination). Furthermore, when the second determination unit 59 determines that there is a second administrator ID according to the second determination, the attribute information associated with the first administrator ID in the related information (first attribute It is judged (the third judgment) whether the information) and the attribute information (second attribute information) associated with the second administrator ID in the related information are the same.

(Functional configuration of destination registration system)
Subsequently, 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. Furthermore, 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. , I omit the explanation. Although the destination registration system 80 does not have a storage unit, the storage and readout processing unit 84 and the first extraction unit 85 can access the storage unit 60 of the terminal management system 50 through the communication network 2 as follows. The same function as 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 in to the destination registration system 80 (transmission management system 40) in order to add or delete a destination candidate. That is, the request for addition or deletion of the destination candidate can be made not only from the transmission terminal 10 but also from the administrator terminal 20.

  In addition, 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 a search key, and uses the terminal authentication management DB 61 of the storage unit 60 (or administrator DB 65). Search for). The first authentication unit 82 permits login to the destination registration system 80 (transmission management system 40) by determining whether the search key matches the information of the terminal authentication management DB 61 (or the administrator DB 65). Perform authentication of whether or not.

  The screen creation unit 86 includes an authentication screen (see FIG. 17), a manager 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) Create etc. The screen creation unit 86 creates a screen according to, for example, HTML (Hyper Text Markup Language).

  Subsequently, with reference to FIGS. 13 to 15, a plurality of patterns will be described as to the registration process of the destination candidate managed in the destination list.

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

  First, the transmission terminal 10aa transmits to the transmission management system 40 a registration request for a destination candidate indicating that the transmission terminal 10da is required to be registered as a destination candidate for the transmission terminal 10aa (ST11). Next, the transmission management system 40 transmits, to the transmission terminal 10da, an approval request indicating that the approval for registration as a destination candidate of the transmission terminal 10aa is requested (ST12). On the other hand, 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 the response indicating approval, the transmission terminal 10da is registered in the destination list management DB 63 as a destination candidate for the transmission terminal 10aa, and that the registration of the destination is completed in the transmission terminal 10aa and the transmission terminal 10da. Is sent (ST14).

(Second pattern)
The second pattern is shown in FIG. 14 and shows that the user of the transmission terminal 10aa (first user aa) transmits the same organization (for example, the same "department") as a destination candidate in its own destination list. It shows a registration process when it is desired to register the terminal 10ab. FIG. 14 is a conceptual diagram showing an example of destination candidate registration processing.

  First, the transmission terminal 10aa transmits to the transmission management system 40 a registration request for a destination candidate indicating that the transmission terminal 10ab is required to be registered as a destination candidate for the transmission terminal 10aa (ST21). Next, the transmission management system 40 is a management terminal of the same administrator A (a transmission terminal under the management of the administrator A) that has the same transmission terminal 10aa as the request source terminal and the transmission terminal 10ab as the request destination terminal. It is determined (ST22). As a result, when the transmission terminal 10aa and the transmission terminal 10ab are the same management terminal of the manager A, the transmission management system 40 transmits the transmission terminal without making an approval request to the transmission terminal 10ab as in the above-mentioned ST12. 10ab is registered in the destination list management DB 63 as a destination candidate for the transmission terminal 10aa, and a transmission completion notification indicating that the registration of the destination is completed is transmitted to the transmission terminal 10aa and the transmission terminal 10ab (ST23).

  The registration request of the destination candidate indicated in ST21 may be made by the administrator A from the administrator terminal 20a to the transmission management system 40. In addition, when the manager A makes a registration request of destination candidates, it is also possible to collectively request the registration requests of destination candidates of a plurality of transmission terminals 10 collectively.

(Third pattern)
The third pattern is shown in FIG. 15, and from the respective destination lists of the transmission terminal 10aa and the transmission terminal 10ab, the administrators (administrator A) of the transmission terminal 10aa and the transmission terminal 10ab are under the control of itself It shows a deletion process when it is desired to collectively delete a destination candidate as the transmission terminal 10 ca under the control of another administrator (administrator C). FIG. 15 is a conceptual diagram showing an example of destination candidate deletion processing.

  First, the administrator terminal 20a sends a deletion request for a destination candidate indicating that the administrator terminal 20a requests that the destination candidate as the transmission terminal 10ca be collectively deleted from each destination list of the transmission terminal 10aa and the transmission terminal 10ab. It sends to (ST31). Next, the transmission management system 40 collectively deletes destination candidates as the transmission terminal 10 ca from the destination lists of the transmission terminal 10 aa and the transmission terminal 10 ab (ST 32). At this time, destination candidates as the transmission terminal 10aa and the transmission terminal 10ab are collectively deleted from the destination list of the transmission terminal 10ca. Thus, even if the user of the transmission terminal 10aa (first user aa) and the user of the transmission terminal 10ab (second user ab) do not request deletion of the destination candidate, respectively, the administrator A Collectively delete, and transmit a notification of deletion completion indicating that the deletion of the destination is completed to each of the transmission terminals (10aa, 10ab, 10ca) (ST33).

<Operation or Process of Embodiment>
Subsequently, the operation or processing of the present embodiment will be described using 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 a login request has been received from the administrator terminal 20 operated by the administrator via the communication network 2 based on the administrator ID (step S101). When the login request is received by the administrator ID (step S101, Yes), the process proceeds to step S102. If the login request has not been received by the administrator ID (the login request has been received by the user by the terminal ID) (step S101, No), login processing by the terminal ID is performed (step S199). Although the transmission terminal 10 can only register destination candidates in its own destination list, the administrator registers destination candidates in all destination lists of the management terminal (the transmission terminal 10 under management). Can.

  FIG. 17 is a conceptual view of an authentication screen of the transmission management system 40. As shown in FIG. 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 in FIGS. 17 to 25 is held by the screen generation unit 86 itself. Each screen data in FIGS. 17 to 25 is stored in storage unit 60, and storage / read processing unit 84 reads out each screen data from storage unit 60 according to an instruction from screen creation unit 86. It is also good.

  Referring back to FIG. 16, when it is determined in step S101 that a login request has been made by the administrator ID (Yes in step S101), the first authentication unit 82 manages administrator information such as administrator ID and password. It is judged whether it is registered in the person DB 65 (step S102). When the administrator information is registered in the administrator DB 65 (No in step S102), the first authentication unit 82 permits 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 the registration screen is displayed and the administrator information input to the registration screen is registered in the administrator DB 65, the destination registration system 80 is logged in (step S103). As an example of the case where the administrator information is not registered in the administrator DB 65, for example, there is a case where the administrator is the first person using an initial setting password.

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

  Referring back 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 data of the management terminal list screen to the administrator terminal 20. (Step S105). FIG. 19 is a conceptual view of a management terminal list screen. The 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, and the terminal ID of the starting terminal in the destination list management DB 63 (the same as the terminal ID in the terminal management DB 62) and the terminal ID of the destination candidate.

  In order for the screen creation unit 86 to create the management terminal list screen shown in FIG. 19, specifically, the first extraction unit 85 uses the administrator ID accepted by the destination registration system 80 as a search key. The person DB 65 is searched, and the terminal ID of the administrator terminal associated with the administrator ID is acquired. Thus, it is possible to specify the transmission terminal 10 managed by a specific administrator. Furthermore, the first extraction unit 85 searches for the terminal ID of the start terminal of 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. Further, 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. Thus, based on the information acquired by the first extraction unit 85, the screen creation unit 86 can create a management terminal list screen.

  In 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 a management terminal from the management terminal. Button, "destination candidate registration" button for newly registering the transmission terminal 10 as a destination candidate, and "destination candidate deletion" button for deleting the transmission terminal 10 already registered as a destination candidate from the destination candidate Is displayed.

  Further, on the management terminal list screen, check boxes (C1, C2, C3, CN) for selecting a terminal ID are displayed for each terminal ID. Furthermore, a check box CA for selecting all the terminal IDs collectively is displayed. In addition, on the management terminal list screen, a "logout" button for logging out is also displayed. Each check box and each button are 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 is selected on the administrator terminal 20 side (step S106). When the “management terminal registration” button or the “management terminal deletion” button is selected (Yes at step S106), the below-described (management terminal registration and deletion processing) is performed (step S107). On the other hand, when neither the “management terminal registration” button nor the “management terminal deletion” button is selected (step S106, No), 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 is 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 below-described (processing for destination candidate registration and deletion) is performed (step S109). On the other hand, when neither the “destination candidate registration” button nor the “destination candidate deletion” button is selected (step S108, No), the process proceeds to step S110.

  Next, the screen creation unit 86 determines whether or not the operation of the administrator ends based on whether the “logout” button is selected on the side of the administrator terminal 20 (step S110). When the “logout” button is selected (Yes at step S110), the destination registration system 40 logs out to the administrator terminal 20 (step S111). If the "logout" button is not selected (step S110, No), the process returns to step S106.

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

  First, the first determination unit 87 determines whether the administrator selects the “register management terminal” button or selects the “delete management terminal” button on the management terminal list screen shown in FIG. It is determined whether to register a management terminal (step S201). When the “management terminal registration” button is selected (step S201, Yes), the screen generation unit 86 is shown in FIG. 20 with respect to the administrator terminal 20 via the first communication unit 81. The data of the management terminal registration screen is sent.

  On the other hand, on the administrator terminal 20, a management terminal registration screen as shown in FIG. 20 is displayed. On the management terminal registration screen, a plurality of "registered terminal ID" input fields for displaying the terminal ID of the transmission terminal 10 that the administrator desires to register as his / her own management terminal are displayed. Then, when the administrator inputs the terminal ID of the transmission terminal 10 in the "registered terminal ID" input field and presses the "register" button, the administrator terminal 20 receives the terminal input in the "registered terminal ID" input field. A registration request including the ID and the administrator ID of the entered administrator is transmitted 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 / readout processing unit 84 sets the registration terminal ID in the terminal ID column in the record in which the administrator ID used in the login process of step S101 is included in the administrator DB 65 of the terminal management system 50. The terminal ID input as is added (step S202).

  On the other hand, when the registration of the management terminal is not performed (No in step S201), the first determination unit 87 determines whether the deletion of the transmission terminal 10 is performed (step S203). If the management terminal has been deleted (Yes at step S203), the screen generation unit 86 is a terminal checked (selected) in the check boxes (CA, C1 to CN) in FIG. 19 via the first communication unit 81. By transmitting a deletion request including the ID and the entered administrator ID to the terminal management system 50, the storage / readout processing unit 54 of the terminal management system 50 manages the administrator ID used in the login process. The terminal ID for which the deletion request has been made is deleted from the record of the administrator DB 65 (step S204). If it is not the deletion of the transmission terminal 10 (step S203, No), the process ends. Further, at the time of the process of step S203, the screen generation 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 confirmation screen of management terminal deletion. In this case, when the administrator presses the "OK" button, the process of step S204 is performed. When the "cancel" button is pressed, the process of step S204 is not performed.

  Although FIG. 20 illustrates an example in which the administrator inputs the terminal ID, the present invention is not limited thereto. For example, a file in which the terminal ID is described is designated (the screen generation unit 86 needs to refer to the file The terminal ID may be input by specifying a path or the like.

(Processing of registration and deletion of destination candidates)
Subsequently, processing of registration and deletion of destination candidates will be described with reference to FIGS. 22 to 24 and 26. FIG. FIG. 22 is a conceptual diagram of the destination candidate registration screen. 23 and 24 are conceptual diagrams of the destination candidate deletion screen. FIG. 26 is a flowchart showing processing of registration and deletion of a destination candidate. Here, an example of (pattern 3) shown in FIG. 15 will be described.

  First, the first determination unit 87 is a request from the administrator terminal 20a by the administrator A by receiving a request source terminal that wishes to register or delete the request destination terminal among the management terminals under the management of the administrator A. The original terminal is identified (step S301). Specifically, when the manager A checks the check box of the transmission terminal (terminal ID) that he wants to be the 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 identified. Also, if the manager A checks the check box of the transmission terminal (terminal ID) that he wants to be the request source terminal on the management terminal list screen shown in FIG. 19 and presses the “delete destination candidate” button, A request source terminal that wants to be deleted is identified.

  Next, the first determination unit 87 determines whether the 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 the “destination candidate registration” button on the management terminal list screen illustrated in FIG. 19 is pressed. If the operation is not an operation indicating registration of a destination candidate (No at step S302), the process proceeds to step S313. If the operation indicates registration of a destination candidate (Yes at Step S302), the display control unit 83 displays a destination candidate registration screen as illustrated in FIG. 22 on the management terminal 20a via the first communication unit 81. The above data is transmitted, and the destination candidate registration screen is displayed on the management terminal 20a (step S303).

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

  Next, returning to FIG. 26, the desired terminal ID is input by the administrator A in the “registered terminal ID” input field of the destination candidate registration screen shown in FIG. 22, and the “register” button is pressed. Thus, 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 (step S304). More specifically, the first communication unit 81 of the destination registration system 80 transmits a registration request of a destination candidate 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 (displayed on the screen of FIG. 22) The terminal ID of the request destination terminal indicated by the terminal ID and the administrator ID during login are included. When the check box of approval omission in each registration terminal ID of the destination candidate registration screen shown in FIG. 22 is checked, the request request terminal is requested to omit the approval request of registration for the registration request. It includes an approval request omission request information indicating that.

  Next, the second determination unit 59 of the terminal management system 50 determines whether 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. It judges (step S305). Specifically, if the received request for registration contains approval request omission request information, the second judging unit 59 sends the request destination terminal checked in the check box shown in FIG. Determines that the approval request is not necessary, and determines that the approval request is necessary for the request destination terminal whose check box is not checked.

  Then, when the check box in FIG. 22 is not checked, the second determination unit 59 refers to the administrator DB 65 to find the terminal ID of the request destination terminal requested to be registered as the destination candidate (a specific terminal It is determined whether the ID) and the administrator ID (first administrator ID) are associated (step S306). Then, if it is associated (step S306, YES), it is determined that the approval process is not necessary, 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 performs registration by determining whether there is another administrator ID (second administrator ID) associated with the specific terminal ID in the administrator DB 65. It is determined whether the destination candidate to be selected is also managed by another administrator. Then, when there is another administrator ID that is associated (YES in step S308), the second determination unit 59 further causes the first administrator ID to be associated with the first administrator ID in the administrator DB 65. It is determined whether the second attribute information associated with the second attribute information of the second administrator ID is the same as the second attribute information (step S309). Then, if the first attribute information and the second attribute information are the same (step S309, YES), the process proceeds to step S307. Further, if there is no other associated administrator ID in step S308 (NO in step S308) and if the first attribute information and the second attribute information are not the same in step S309 (step S309). , NO), it progresses to step S310.

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

  That is, when it is selected that the approval is not omitted in step S305, the request management unit 58 of the terminal management system 50 newly associates the request source terminal ID and the request destination terminal ID included in the received registration request. The record is additionally stored in the request management DB 64. Then, the second extraction unit 55 of the terminal management system 50 extracts the corresponding operation status 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. Then, when the operating state is communicable (for example, online (transmittable)), the second communication unit 51 transmits an approval request for destination registration 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 so as to be communicable.

  Next, after step S310, the second determination unit 59 of the transmission management system 40 determines whether an acknowledgment response has been received from the request destination terminal that has received the acknowledgment request (step S311). Then, when the second communication unit 51 receives the acknowledgment response (Yes at Step S311), the process proceeds 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. The terminal ID of the request source terminal is registered as a destination candidate in the case of (step S307). That is, the request source terminal and the request destination terminal are mutually registered as destination candidates. In step S307, the request source terminal and the request destination terminal may not be registered as destination candidates each other, and only the terminal ID of the request destination terminal may be registered as the destination candidate of the request source terminal.

  When the registration is completed, the second communication unit 51 transmits a notification of registration completion to the request source terminal and the request destination terminal (step S312). When the above processing is completed, the request management unit 58 of the terminal management system 50 deletes the record for which registration has been completed from the request management DB 64. In the case where omission of approval is not requested in step S305 (NO), a new record is not added to the request management DB 64 for the combination of the terminal ID of the request source terminal and the terminal ID of the request destination terminal. There is no need to delete it.

  Note that even if NO at step S305, step S306 may be executed. 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 further, whether or not the response indicates approval.

  Subsequently, a process of deleting a destination candidate will be described.

  If NO in step S302, the first determination unit 87 determines whether the operation indicates deletion of a destination candidate (step S313). Specifically, when the “delete destination candidate” button in the management terminal list screen of FIG. 19 is pressed, the first determination unit 87 requests the first communication unit 81 to delete the destination candidate from the administrator terminal 20. It is determined whether or not it has been received. In this case, the destination candidate of the transmission terminal 10 checked in the check box (CA, C1 to CN) of the management terminal list screen is to be deleted.

  Then, if the operation is not an operation indicating deletion of the destination candidate (No in step S313), the process illustrated in FIG. 26 ends. If the operation is an operation indicating deletion of the destination candidate (Yes in step S313), the screen generation unit 86 is shown in FIG. 23 or 24 to the administrator terminal 20 via the first communication unit 81. A destination candidate deletion screen is displayed, and the first determination unit 87 specifies a destination candidate to be deleted based on the terminal ID selected and input by the administrator (step S314). 23 and 24 are conceptual diagrams of the destination candidate deletion screen.

  Here, step S314 will be described in more detail using FIG. 23 and FIG. On the destination candidate deletion screen shown in FIG. 23 and FIG. 24, a radio button selected in the case of “delete all destination candidates” and a “delete specified destination candidate” radio button are displayed. In addition, on the destination candidate deletion screen, a plurality of “deleted terminal ID” input fields for inputting the terminal ID of the destination candidate that the administrator wants to delete, and a “delete” button pressed when executing deletion A "cancel" button to be pressed when canceling deletion is displayed.

  In FIG. 23, the administrator indicates that the "Delete specified destination candidate" radio button is pressed, and the terminal ID "01ca" of the destination candidate is input in the "Deleted terminal ID" input field. . On the other hand, FIG. 24 shows a state in which the “delete all destination candidates” radio button is pressed. In the case shown in FIG. 24, since the deletion target is all the destination candidates, hatching is displayed in the “deleted terminal ID” input field, and the administrator can not input the terminal ID.

  Here, the third pattern shown in FIG. 15 will be described. That is, after the administrator A checks the check box CA on the management terminal list screen shown in FIG. 19 and presses the “delete destination candidate” button, the “specified destination candidate shown in FIG. 23 is further displayed. The case where the user deletes the "Delete" radio button and inputs the terminal ID "01ca" in the "Deleted terminal ID" input field and finally presses the "Delete" button will be described below.

  In this case, in the destination list management DB 63, since the start terminal having the terminal ID "01ca" as the destination candidate is the start terminal indicated by the terminal ID "01aa" and the terminal ID "01ab", the administrator A has a terminal ID This means that the request source terminal (10aa, 10ab) indicated by "01aa" and terminal ID "01ab" is selected. Also, the administrator terminal 20a requests deletion of the destination candidate indicated by the terminal ID "01ca" from the destination candidate of each starting terminal indicated by the terminal ID "01aa" and the terminal ID "01ab" by the administrator A. It will be Thereby, the first communication unit 81 receives the deletion request of the destination candidate from the administrator terminal 20, and the first determination unit 87 is indicated by the terminal ID "01aa" and the terminal ID "01ab" as the start terminal. The transmission terminals (10aa, 10ab) are identified, and the transmission terminal 10ca indicated by the terminal ID "01ca" is identified as a destination candidate to be deleted.

  Next, based on the deletion request received by the second communication unit 51 via the first communication unit 81, the storage / readout processing unit 84 determines that the terminal ID of the start terminal in the destination list management DB 63 is “01aa” and In each record of "01ab", the terminal ID "01ca" is deleted from the terminal ID of the destination candidate (step S315). Thereby, the second communication unit 51 transmits a notification of deletion completion indicating that the deletion of the destination is completed to the request source terminal (transmission terminals (10aa, 10ab) and the request destination terminal (transmission terminal 10ca) (see FIG. Step S316).

  In step S315, the terminal IDs "01aa" and "01ab" may be deleted from the terminal IDs of the destination candidate even in the record in which the terminal ID of the start terminal is "01ca".

<Main effects of the embodiment>
As described above, according to the present embodiment, even when the transmission management system 40 manages the destination list management DB 63, a desired destination candidate can be deleted from the destination list management DB 63. Play an effect.

  Furthermore, the terminal IDs of a plurality of or all of the destination candidates can be collectively deleted from the destination candidates of the plurality of or all of the starting terminals in the destination list management DB 63. As a result, the user of each start terminal (transmission terminal 10) can save the trouble of deleting the terminal IDs of a plurality of or all of the destination candidates.

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 described in the first embodiment will be described. 27 (a) and 27 (b) are conceptual diagrams of the manager DB according to the second embodiment. As shown in FIG. 27, the administrator DB 65 'of this embodiment is constructed by two tables. That is, as shown in FIG. 27A, 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. 27B, as the second table, a manager ID and a terminal ID are associated and managed. Thus, the information shown in FIG. 27A and FIG. 27B corresponds to the “related information” shown in the first embodiment. The manager ID, the password, the terminal ID, the manager e-mail address, and the attribute information have the same contents as in the first embodiment, and thus the description thereof will be omitted.

  Also 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 process of step S306 and the process of step S308 may be omitted.

  The transmission management system 40 can be applied to any system as long as it is a communication system in which the transmission terminals 10 can communicate with each other. For example, the present invention can be applied to a television (video) conference system, an audio conference system, an audio telephone system (including a mobile phone system), a text chat system, or a whiteboard sharing system. The transmission terminal 10 may be a dedicated terminal of the communication system described above or a dedicated terminal of a game, or may be a general-purpose terminal such as a personal computer, a smartphone, a mobile phone terminal, or a tablet terminal. 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)
54 storage / read processing unit 59 determination unit 60 storage unit (an example of storage means)
61 Terminal authentication management DB
62 Terminal Management DB
63 Destination list management DB (an example of storage means)
64 Requirements Management DB
65 Administrator DB
80 Destination Registration System 81 First Communication Unit (An Example of Reception Means)
84 Memory / read processing unit (an example of deletion means)
87 Judgment Department

JP, 2006-074453, A JP, 2013-085208, A

Claims (10)

A transmission management system for managing destination candidates of a predetermined transmission terminal, comprising:
Related information in which start terminal identification information for identifying a start terminal that is a transmission terminal that requests start of communication among the transmission terminals is associated with destination candidate identification information for identifying a destination candidate of the start terminal Storage means for storing
Receiving means for receiving a deletion request to delete specific destination candidate identification information from among the destination candidate identification information associated with the specific start terminal identification information;
Deletion means for deleting the specific destination candidate identification information among the destination candidate identification information in which the specific start terminal identification information is associated in the related information based on the deletion request received by the receiving means;
A transmission management system characterized by having. The transmission management system according to claim 1,
A transmission management system comprising: transmission means for transmitting a deletion completion notification indicating that the deletion has been completed, to a destination candidate indicated by destination candidate identification information deleted by the deletion means.   The transmission management system according to claim 2, wherein the transmission means transmits the deletion completion notification to a start terminal indicated by the specific start terminal identification information.   In the case where the deletion request indicates that specific destination candidate identification information associated with a plurality of specific start terminal identification information is to be deleted, the deletion means identifies the plurality of specific start terminal identifications in the related information. The transmission management system according to any one of claims 1 to 3, wherein each specific destination candidate identification information associated with the information is deleted.   When the deletion request indicates that the specific destination candidate identification information associated with all the start terminal identification information is to be deleted, the deletion means is associated with the all the start terminal identification information in the related information. The transmission management system according to any one of claims 1 to 3, wherein each specific destination candidate identification information is deleted.   In the case where the deletion request indicates that a plurality of specific destination candidate identification information of destination candidates associated with the specific start terminal identification information is to be deleted, the deletion means may use the specific information in the related information. The transmission management system according to any one of claims 1 to 5, wherein the plurality of specific destination candidate identification information associated with the start terminal identification information is deleted.   In the case where the deletion request indicates that all destination candidate identification information of destination candidates associated with the specific start terminal identification information is to be deleted, the deletion means may specify the specific start terminal in the related information. The transmission management system according to any one of claims 1 to 5, wherein all the destination candidate identification information associated with the identification information is deleted.   The transmission management system according to any one of claims 4 to 7, wherein said deletion means collectively deletes. A management method executed by a transmission management system that manages destination candidates of a predetermined transmission terminal.
The transmission management system includes: start terminal identification information for identifying a start terminal that is a transmission terminal that requests start of communication among the transmission terminals; destination candidate identification information for identifying a destination candidate of the start terminal; Has storage means for storing related information associated with the
The transmission management system
A receiving step of receiving a deletion request to delete specific destination candidate identification information among the destination candidate identification information associated with the specific start terminal identification information;
A deletion step of deleting the specific destination candidate identification information among destination candidate identification information in which the specific start terminal identification information is associated in the related information, based on the deletion request received in the receiving step;
Management method characterized by performing.   The program for making a computer perform the method of Claim 9.