JP6958686B2 - Management system, management method, program, system and method - Google Patents

Description

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

In recent years, in response to a request to reduce business trip expenses and business trip time, a transmission system for conducting a video conference or the like via a communication network such as the Internet has become widespread. 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.

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

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

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

The invention according to claim 1, first and destination list associated with the first identification information, the second destination list associated with the second identification information management, the first destination list The second identification information, which is a destination candidate for communication using the first identification information, is included in the second destination list, and the destination for communication using the second identification information is included in the second destination list. The destination list management means including the first identification information as a candidate and the terminal authenticated based on the identification information of the administrator registered as the administrator information are included in the first destination list. The second from the first destination list based on the receiving means for receiving the request for deleting the destination candidate corresponding to the second identification information and the request for deleting the destination candidate received by the receiving means. while deleting the destination candidate corresponding to the identification information, from the second destination list, characterized by having a a deleting means for deleting the destination candidate corresponding to the first identification information.

According to the present invention described above, an effect that even when managing the destination list in the management system side can be deleted desired destination candidates from the destination list.

FIG. 1 is a schematic view 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 a transmission system. FIG. 3 is a conceptual diagram illustrating the image quality of the 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 the terminal management system and the destination registration system constituting 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 requirements management DB. FIG. 12 is a conceptual diagram of the administrator DB. FIG. 13 is a conceptual diagram showing an example of the destination candidate registration process. FIG. 14 is a conceptual diagram showing an example of the destination candidate registration process. FIG. 15 is a conceptual diagram showing an example of a destination candidate deletion process. FIG. 16 is a flowchart showing a management method by the transmission management system. FIG. 17 is a conceptual diagram of the 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 confirmation screen for deleting the management terminal. 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 conceptual diagram of a destination candidate deletion screen. FIG. 25 is a flowchart showing the process of registering and deleting the management terminal. FIG. 26 is a flowchart showing a process of registering and deleting destination candidates. FIG. 27 is a conceptual diagram of the administrator DB according to the second embodiment.

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

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

<Overall configuration of the embodiment>
FIG. 1 is a schematic view 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 a transmission system. FIG. 3 is a conceptual diagram illustrating the image quality of the image data.

Further, the transmission system 1 includes a communication system for mutually transmitting 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 terminal") via a communication management system (corresponding to "transmission management system" of this embodiment). An example is a television (video) conferencing 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, ...), And a plurality of managements. It is constructed by a personal terminal (20a, 20b, 20c, 20d), a plurality of relay devices (30a, 30b, 30c, 30d), a transmission management system 40, a program providing system 90, and a maintenance system 100. Further, 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 perform transmission by transmitting and receiving image data and sound data as an example of content data. As another example of the content data, text data can be mentioned. Further, the content data may include at least one of image data, sound data, and text data.

In the following, any transmission terminal among the plurality of transmission terminals (10aa, 10ab, ...) Is referred to as "transmission terminal 10", and any display among the plurality of displays (120aa, 120ab, ...) Is referred to as "display 120". , And any of the plurality of relay devices (30a, 30b, 30c, 30d) is represented by "relay device 30".

Further, the transmission terminal 10 which is a request source for 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". Further, the transmission terminal 10 that makes a request for registering the other party's transmission terminal 10 in its own destination list is referred to as a "request source terminal", and the other party's transmission terminal 10 in this case is referred to as a "request destination terminal". ..

Further, as shown in FIG. 2, in the transmission system 1, there is 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. Established. Further, between the start terminal and the destination terminal, four types of data, 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 a session sed for image / sound data. It should be noted that the relay device 30 does not necessarily have to be established between the start terminal and the destination terminal, and the image / sound data session sed may be directly established between the start terminal and the destination terminal.

Here, the image resolution of the image data handled in the present embodiment will be described. As shown in FIG. 3A, a low-resolution image consisting of 160 pixels in the horizontal direction and 120 pixels in the vertical direction and serving as a base image, and as shown in FIG. 3B, the horizontal direction is There is a medium-resolution image consisting of 320 pixels and 240 pixels in the vertical direction, and a high-resolution image consisting of 640 pixels in the horizontal direction and 480 pixels in the vertical direction as shown in FIG. 3C. Of these, when passing through a narrow band path, low-quality image data consisting of only low-resolution image data serving as a base image is relayed. When the band is relatively wide, low-resolution image data as a base image and medium-quality image data including medium-resolution image data are relayed. When the band is very wide, high-quality image data including low-resolution image data, medium-resolution image data, and high-resolution image data, which is the base image quality, 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 the destination list, and the like, and the communication status of the relay device 30. The image of the image data may be a moving image or a still image, and may be both a moving image and a still image.

The plurality of routers (70a, 70b, 70c, 70d, 70ab, 70cd) select the optimum route for image data and sound data. In the following, any 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 described later, and stores a transmission terminal program for realizing various functions in the transmission terminal 10 (or making the transmission terminal 10 function as various means). , The transmission terminal program can be transmitted to the transmission terminal 10. Further, the HD204 of the program providing system 90 also stores a program for the relay device for realizing various functions in the relay device 30 (or making the relay device 30 function as various means), and the relay device 30 stores the program for the relay device. A program for a relay device can be transmitted.

Further, the HD204 of the program providing system 90 also stores a transmission management program for realizing various functions in the terminal management system 50 (or making the terminal management system 50 function as various means), and the terminal management system A transmission management program can be transmitted to the 50. Further, the HD204 of the program providing system 90 also stores a destination registration program for realizing various functions in the destination registration system 80 (or making the destination registration system 80 function as various means), and the destination registration system A destination registration program can be transmitted to 80. The terminal management program and the destination registration program are collectively treated 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 device 30, the terminal management system 50, the destination registration system 80, or the program providing system 90 is installed overseas, the maintenance system 100 is the communication network 2. Remotely perform 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. Further, the maintenance system 100 has a model number and a serial 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 going through the communication network 2. , Sales destination, maintenance and inspection, or maintenance such as failure history management.

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

On the other hand, the transmission terminal (10ca, 10cc, 10cc, ...), The relay device 30c, and the router 70c are communicably connected by LAN2c. The transmission terminal (10da, 10db, 10dc, ...), The relay device 30d, and the router 70d are communicably connected by LAN2d. Further, LAN2c and LAN2d are communicably connected by a dedicated line 2cd including a router 70cd, and are constructed in a predetermined area B. For example, area B is an office in Osaka, LAN2c is built in the development part, and LAN2d is built in the development part 2. Area A and area B are connected to each other from routers (70ab, 70cd) so as to be able to communicate with each other via the Internet 2i.

Further, 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 an area other than these.

In the present embodiment, the communication network 2 of the present embodiment is constructed by the LAN2a, LAN2b, the leased line 2ab, the Internet 2i, the leased line 2cd, the LAN2c, and the LAN2d. The communication network 2 may have a place where wireless communication such as WiFi (Wireless Fidelity) or Bluetooth (registered trademark) is performed as well as wired communication.

Further, 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". Further, IPv6 may be used instead of IPv4, but for the sake of brevity, the description will be made using IPv4.

In addition, each transmission terminal 10 is not only a call between a plurality of business establishments and a call between different rooms in the same business establishment, but also a call within the same room and a call between outdoors and indoors or outdoors and outdoors. May be used in. When each transmission terminal 10 is used outdoors, wireless communication such as a mobile phone communication network is performed.

<Hardware configuration of the 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 directions 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. Of these, the front side wall surface 1110 of the housing 1100 is provided with an intake surface (not shown) formed by a plurality of intake holes, and the rear side wall surface 1120 of the housing 1100 is formed with a plurality of exhaust holes. The exhaust surface 1121 is provided. As a result, by driving the cooling fan built in the housing 1100, the outside air behind the terminal 10 can be taken in through the intake surface (not shown) and exhausted to the rear of the terminal 10 through the exhaust surface 1121. A sound collecting hole 1131 is formed in the right wall surface 1130 of the housing 1100, and sounds such as sound, noise, and noise can be collected by a built-in microphone 114 described later.

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

In the following, "operation button 108" is used to indicate an arbitrary operation button among the operation buttons (108a to 108e), and "operation button 108" is used to indicate an arbitrary connection port among the connection ports (1132a to 1132c). This will be described with reference to 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 rotatable in the vertical direction within a range of a tilt angle θ1 of 135 degrees with respect to the housing 1100. 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, which will be described later, and can image users, documents, rooms, 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 has a pan angle θ2 of ± 180 degrees with respect to the arm 1200, with the state shown in FIG. 4 as 0 degrees. It is configured to be rotatable in the vertical and horizontal directions within the range of ± 45 degrees and the tilt angle θ3.

Since the relay device 30, the terminal management system 50, the destination registration system 80, the program providing system 90, and the maintenance system 100 each have the same appearance as a general server computer, the description of the appearance will be 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 the CPU 101 such as the CPU (Central Processing Unit) 101 and the IPL (Initial Program Loader) that control the operation of the entire transmission terminal 10. ROM (Read Only Memory) 102 for 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 programs, image data, and sound data, 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, media drive 107 that controls reading or writing (storage) of data to the recording medium 106 such as the flash memory, transmission. An operation button 108 operated when selecting a destination of the terminal 10, a power switch 109 for switching the power ON / OFF of the transmission terminal 10, and a network I / for data transmission using the communication network 2. It includes F (Interface) 111.

Further, the transmission terminal 10 includes a built-in camera 112 that captures a subject and obtains image data under the control of the CPU 101, an image pickup element I / F 113 that controls the drive of the camera 112, and a built-in microphone 114 that inputs sound. Image data on the external display 120 under the control of the built-in speaker 115 that outputs sound, the sound input / output I / F 116 that processes the input and output of sound signals between the microphone 114 and the speaker 115 under the control of the CPU 101, and the CPU 101. Display I / F 117 for transmitting data, external device connection I / F 118 for connecting various external devices attached to the connection port 1021 g shown in FIG. 4, and alarm lamp 119 for notifying an abnormality of various functions of the transmission terminal 10. A bus line 110 such as an address bus or a data bus for electrically connecting each of the above components is provided as shown in FIG.

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

The camera 112 includes a lens and a solid-state image sensor that converts light into electric charges to digitize an image (video) of the subject. As the solid-state image sensor, CMOS (Complementary Metal Oxide Semiconductor) or CCD (Charge Coupled Device) 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 according to the control of the CPU 101. Similarly, when an external microphone is connected or an external speaker is connected, the external microphone and the external speaker are given priority over the built-in microphone 114 and the built-in speaker 115 according to the control of the CPU 101. The external speaker is driven.

The camera 112, the microphone 114, and the speaker 115 do not necessarily have to be built in, and may be configured so that only the external camera, the external microphone, and the external speaker can be connected. Further, the recording medium 106 has a structure that can be attached to and detached from the terminal 10. Further, as long as it is a non-volatile memory that reads or writes data under 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 a file in an installable format or an executable format, and may be recorded and distributed on a computer-readable recording medium such as the recording medium 106. Further, 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 that controls the operation of the entire 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 of the CPU 201, a terminal management program, and the like. A medium that controls reading or writing (storage) of data to a recording medium 206 such as an HDD (Hard Disk Drive) 205 or a flash memory that controls reading or writing of various data to HD204 according to the control of HD204 or CPU201 that stores data. Input of drive 207, display 208 for displaying various information such as cursors, menus, windows, characters, or images, network I / F 209 for data transmission using communication network 2, characters, numerical values, various instructions, etc. A keyboard 211 equipped with multiple keys for, a mouse 212 for selecting and executing various instructions, selecting a processing target, moving a cursor, etc., and a CD-ROM (Compact Disc Read Only) as an example of a removable recording medium. It includes a CD-ROM drive 214 that controls reading or writing of various data to the Memory) 213, and a bus line 210 such as an address bus or a data bus for electrically connecting each of the above components.

The terminal management program may be a file in an installable format or an 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. .. Further, 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 will be omitted. However, the HD204 records a program for the relay device for controlling the relay device 30. In this case as well, the program for the relay device may be a file in an installable format or an 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. Further, the relay device program may be stored in the ROM 202 instead of the HD 204.

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

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 HD204. In this case as well, the program providing program is a file in an installable format or an executable format, and can be recorded and distributed on 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.

As another example of the detachable recording medium, it is configured to be recorded and provided on a computer-readable recording medium such as a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), or a Blu-ray disc. You may.

<Functional configuration of the embodiment>
Hereinafter, the functional configurations of the terminal management system 50 and the destination registration system 80 will be described with reference to FIGS. 7 to 12. FIG. 7 is a functional block diagram of the terminal management system and the destination registration system constituting 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 / reading 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, each information indicating the terminal ID and the password is managed as related related information. 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 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 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 information indicating the terminal ID, the name, the operating state, the reception date and time, and the IP address of the terminal is managed as related related information. This 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, the name of the department, or the like. The operating state is the latest operating state of the transmission terminal 10. The reception date and time is the date and time when the login request to the transmission management system 40 is received from the transmission terminal 10. 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 diagram of the destination list management DB 63. In the destination list management DB 63, the terminal ID of the starting terminal and the terminal ID of the destination candidate that can be the destination terminal are managed as related information associated with each other. The record of the destination list management DB 63 may have columns other than the above.

FIG. 11 is a conceptual diagram of the requirements 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 requesting terminal is identification information for identifying the transmission terminal 10 that has requested the 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 destination candidate registration target. The record of the request management DB 64 may have a column other than the above.

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

Of 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 e-mail address is the e-mail address of the administrator. The attribute information is affiliation information indicating the department to which the manager belongs in an organization such as a company, position information indicating a position, authority information indicating authority, and the like. The attribute information may be any one of these pieces of information (affiliation information, job title information, authority information), or may be a combination of at least two or more of each of these pieces of information. .. The record of the administrator DB65 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 his / her own management terminal. doing. The administrator B uses the administrator terminal 20b and manages a plurality of transmission terminals (10ba, 10bb, ...) Connected to the LAN 2b as his own management terminal. The administrator C uses the administrator terminal 20c and manages a plurality of transmission terminals (10ca, 10cc, ...) Connected to the LAN 2c as his own management terminal. The administrator D uses the administrator terminal 20d and manages a plurality of transmission terminals (10da, 10db, ...) Connected to the LAN 2d as his own 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 authenticates when the transmission terminal 10 logs in to the terminal management system 50 (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 uses the terminal authentication management DB 61 of the storage unit 60 as a search key. Search for. The second authentication unit 52 authenticates whether or not to allow login to the terminal management system 50 by determining whether or not the search key and the information in the terminal authentication management DB 61 match.

The terminal management unit 56 manages the operating state of the transmission terminal 10 that has requested login 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 requested login to the transmission management system 40. Specifically, when the login is successful, the "operating state" is changed from offline to online (transmission is possible), and the "reception date and time" 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 requested login 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 login. Read the 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 out the operating state of the transmission terminal 10 for each extracted terminal ID. The read terminal ID and operating state are transmitted to the transmission terminal 10 that has requested login to the transmission management system 40 via the second communication unit 51. By this process, a destination list showing destination candidates is displayed on the display 120 of the requested transmission terminal 10, and the user of the transmission terminal 10 specifies a desired destination from the destination list, whereby the transmission terminal 10 is displayed. It is possible to establish a session seed between the transmission terminals 10 and realize communication between the transmission terminals 10.

The session sed between the transmission terminals 10 may be established via the transmission management system 40 or may be directly exchanged without the transmission management system 40. In addition, the transmission terminal 10 can exchange content data by session sed.

Further, 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 uses the terminal ID of the transmission terminal 10 requested to log in as a destination candidate terminal. The terminal ID of the starting terminal can also be extracted from the record registered as the ID. As a result, 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 has requested login as a destination candidate as a search key. Can be done.

The requirements management unit 58 adds, changes, and deletes records in the requirements 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 of the destination list management DB 63 in which the terminal ID of the request source terminal managed by the request management DB 64 and the terminal ID of the start terminal in the destination list management DB 63 match. 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 / reading processing unit 54 performs a process of storing data in the storage unit 60. Further, the storage / reading processing unit 54 performs a process of reading the 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 with each other in the related information (first determination). Further, when the second determination unit 59 determines that the terminal ID is not associated by the first determination, another administrator ID (second administrator ID) to which this terminal ID is associated in the related information is used. Judge if there is (second judgment). Further, when the second determination unit 59 determines that there is a second administrator ID by the second determination, the attribute information (first attribute) associated with the first administrator ID in the related information. It is determined whether the information) and the attribute information (second attribute information) associated with the second administrator ID in the related information are the same (third determination).

(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 terminal management program shown in FIG. Further, the display control unit 83 includes a storage / reading processing unit 84, a first extraction unit 85, a screen creation unit 86, and a first determination unit 87.

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

The first authentication unit 82 authenticates 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 destination candidates. That is, the request for adding or deleting the destination candidate 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 uses the terminal authentication management DB 61 (or administrator DB 65) of the storage unit 60 as a search key. ) Is searched. 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 the information of the terminal authentication management DB 61 (or the administrator DB 65) match. Authenticate 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. 20). 22) etc. are created. The screen creation unit 86 creates a screen by, for example, HTML (HyperText Markup Language).

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

(First pattern)
The first pattern is shown in FIG. 13, when a user of the transmission terminal 10aa wants to register a transmission terminal 10da of a different organization (for example, a different “business establishment”) as a destination candidate in his / her destination list. Indicates the registration process. Note that FIG. 13 is a conceptual diagram showing an example of the destination candidate registration process.

First, the transmission terminal 10aa transmits a destination candidate registration request indicating that the transmission terminal 10da is requested to be registered as the destination candidate of the transmission terminal 10aa to the transmission management system 40 (ST11). Next, the transmission management system 40 transmits an approval request indicating that the transmission terminal 10da is requested to be approved for registration as a destination candidate of the transmission terminal 10aa (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 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 the above is transmitted (ST14).

(Second pattern)
The second pattern is shown in FIG. 14, in which 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. The registration process when the terminal 10ab is desired to be registered is shown. Note that FIG. 14 is a conceptual diagram showing an example of the destination candidate registration process.

First, the transmission terminal 10aa transmits a destination candidate registration request indicating that the transmission terminal 10ab is requested to be registered as the destination candidate of the transmission terminal 10aa to the transmission management system 40 (ST21). Next, the transmission management system 40 is a management terminal of the administrator A (a transmission terminal under the control of the administrator A) in which the transmission terminal 10aa, which is the request source terminal, and the transmission terminal 10ab, which is the request destination terminal, are the same. (ST22). As a result, 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 approval from the transmission terminal 10ab as in ST12 above. 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).

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. Further, when the administrator A requests the registration of the destination candidate, it is also possible to collectively request the registration request of the destination candidate of the plurality of transmission terminals 10.

(Third pattern)
The third pattern is shown in FIG. 15, in which the administrator (administrator A) of the transmission terminal 10aa and the transmission terminal 10ab is from each destination list of the transmission terminal 10aa and the transmission terminal 10ab under his / her control. The deletion process when it is desired to collectively delete the destination candidates as the transmission terminal 10ca under the control of another administrator (administrator C) is shown. Note that FIG. 15 is a conceptual diagram showing an example of the destination candidate deletion process.

First, the administrator terminal 20a sends a request for deleting the destination candidate indicating that the destination candidate as the transmission terminal 10ca is requested to be collectively deleted from each destination list of the transmission terminal 10aa and the transmission terminal 10ab in the transmission management system 40. (ST31). Next, the transmission management system 40 collectively deletes the destination candidates as the transmission terminal 10ca from the destination list of the transmission terminal 10aa and the transmission terminal 10ab (ST32). At this time, the destination candidates as the transmission terminal 10aa and the transmission terminal 10ab are collectively deleted from the destination list of the transmission terminal 10ca. As a result, 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 each request to delete the destination candidate, the administrator A Deletes all at once, and sends a deletion completion notification indicating that the deletion of the destination is completed to each transmission terminal (10aa, 10ab, 10ca) (ST33).

<Operation or processing of the embodiment>
Subsequently, the operation or processing of the present embodiment will be described with reference to FIGS. 16 to 27. 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 is accepted by the administrator ID from the administrator terminal 20 operated by the administrator via the communication network 2 (step S101). If the login request is accepted by the administrator ID (step S101, Yes), the process proceeds to step S102. When the login request is not accepted by the administrator ID (the login request is accepted by the terminal ID by the user) (steps S101 and No), the login process by the terminal ID is performed (step S199). The transmission terminal 10 can only register the destination candidates in its own destination list, but the administrator can register the destination candidates in all the destination lists of the management terminal (transmission terminal 10 under management). Can be done.

FIG. 17 is a conceptual diagram of the 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 me.

Each screen data of FIGS. 17 to 25 is held by the screen creation unit 86 itself. The screen data of FIGS. 17 to 25 is stored in the storage unit 60, and the storage / reading processing unit 84 reads each screen data from the storage unit 60 by a command of the screen creation unit 86. May be good.

Returning to FIG. 16, when it is determined in step S101 that the login request is made with the administrator ID (step S101, Yes), the first authentication unit 82 manages the administrator information such as the administrator ID and password. It is determined whether or not the person is registered in the person DB65 (step S102). Then, when the administrator information is registered in the administrator DB 65 (step S102, No), 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 placed on 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). 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 used for the first time by using the initial setting password.

FIG. 18 is a conceptual diagram of the 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.

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 manages the administrator ID received by the destination registration system 80 as a search key. The person DB65 is searched, and the terminal ID of the administrator terminal associated with the administrator ID is acquired. Thereby, the transmission terminal 10 managed by a specific administrator can be specified. Further, 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. Based on the information acquired by the first extraction unit 85 in this way, the screen creation unit 86 can create a management terminal list screen.

On the management terminal list screen, there is a "management terminal registration" button for newly registering the transmission terminal 10 as a management terminal, and a "management terminal deletion" for deleting the transmission terminal 10 already registered as a 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 candidates. Is displayed.

Further, on the management terminal list screen, check boxes (C1, C2, C3, CN) for selecting the terminal ID are displayed for each terminal ID. Further, a check box CA for selecting all terminal IDs at once is displayed. In addition, a "logout" button for logging out is also displayed on the management terminal list screen. Each check box and each button 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 is 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 (process of registering and deleting the management terminal) is executed (step S107). On the other hand, if neither the "register management terminal" button nor the "delete management terminal" button is selected (steps 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 later-described (destination candidate registration / deletion process) is executed (step S109). On the other hand, if 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 the operation of the administrator is completed depending on whether the "log out" button is selected on the administrator terminal 20 side (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). If the "logout" button is not selected (step S110, No), the process returns to step S106.

(Processing of registration and deletion of management terminal)
Subsequently, the process of registering and deleting 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 the management terminal registration screen. FIG. 21 is a conceptual diagram of a confirmation screen for deleting the management terminal. FIG. 25 is a flowchart showing the process of registering and deleting the management terminal.

First, the first determination unit 87 determines whether to select the "management terminal registration" button or the "management terminal deletion" button by the administrator on the management terminal list screen shown in FIG. It is determined whether to register the management terminal (step S201). When the "management terminal registration" button is selected (step S201, Yes), the screen creation unit 86 refers to the administrator terminal 20 via the first communication unit 81 as shown in FIG. Send data on the management terminal registration screen.

On the other hand, on the administrator terminal 20, the management terminal registration screen as shown in FIG. 20 is displayed. On this management terminal registration screen, a plurality of "registered terminal ID" input fields for the administrator to input the terminal ID of the transmission terminal 10 that he / she wishes to newly 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 is the terminal entered in the "registered terminal ID" input field. A registration request including the ID and the administrator ID of the input administrator is transmitted to the destination registration system 80. As a result, the first communication unit 81 of the destination registration system 80 receives the registration request. Then, the storage / reading processing unit 84 sets 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. The terminal ID input as is added (step S202).

On the other hand, when the management terminal is not registered (step S201, No), the first determination unit 87 determines whether the transmission terminal 10 is deleted (step S203). In the case of deleting the management terminal (step S203, Yes), the screen creation unit 86 is a terminal in which the check boxes (CA, C1 to CN) are checked (selected) in FIG. 19 via the first communication unit 81. By transmitting the deletion request including the ID and the administrator ID of the input administrator to the terminal management system 50, the storage / reading processing unit 54 of the terminal management system 50 is managed by the administrator ID used for the login process. The terminal ID requested to be deleted is deleted from the record of the administrator DB65 (step S204). If the transmission terminal 10 is not deleted (step S203, No), the process ends. Further, in the process of step S203, the screen creation unit 86 causes the administrator terminal 20 to display the confirmation screen for deleting the management terminal shown in FIG. 21 via the first communication unit 81. FIG. 21 is a confirmation screen for deleting the management terminal. 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.

Note that FIG. 20 has described an example in which the administrator inputs the terminal ID, but the present invention is not limited to this, and for example, a file in which the terminal ID is described is specified (necessary for the screen creation unit 86 to refer to the file). The terminal ID may be input by specifying the path, etc.).

(Processing of registration and deletion of destination candidates)
Subsequently, the process of registering and deleting the destination candidate will be described with reference to FIGS. 22 to 24 and 26. Note that 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 a process of registering and deleting destination candidates. Here, an example of (Pattern 3) shown in FIG. 15 will be described.

First, the first determination unit 87 makes a request by receiving from the administrator terminal 20a by the administrator A a requesting source terminal that wishes to register or delete the requesting destination terminal among the management terminals under the control of the administrator A. The original terminal is specified (step S301). Specifically, when the administrator A checks the check box of the transmission terminal (terminal ID) to be the requesting terminal on the management terminal list screen shown in FIG. 19 and presses the "destination candidate registration" button, The requesting terminal that wants to register the destination candidate is specified. Further, when the administrator A checks the check box of the transmission terminal (terminal ID) to be the request source terminal on the management terminal list screen shown in FIG. 19 and presses the "Delete destination candidate" button, the destination candidate is selected. The requesting terminal that you want to delete is specified.

Next, the first determination unit 87 determines whether or not the operation such as pressing received from the administrator terminal 20a is an operation indicating registration of the 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 shown in FIG. 19 has been pressed. If the operation does not indicate the registration of the destination candidate (step S302, No), the process proceeds to step S313. In the case of the operation indicating the registration of the destination candidate (step S302, Yes), the display control unit 83 uses the first communication unit 81 to display the destination candidate registration screen as shown in FIG. 22 on the management terminal 20a. 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 newly desired to be registered as the destination candidate are displayed on the destination candidate registration screen. .. Further, for each registered terminal ID, as shown in ST12 of FIG. 13, approval for asking the requesting terminal whether the requesting terminal may be registered as a destination candidate in the destination list of the requesting terminal. A check box is displayed as an item for selecting whether or not to omit the request.

Next, returning to FIG. 26, the administrator A inputs the desired terminal ID in the “registered terminal ID” input field of the destination candidate registration screen shown in FIG. 22, and the “register” button is pressed. As a result, the designation of the transmission terminal 10 for which registration is requested as a destination candidate is accepted (step S304), and the terminal ID of the transmission terminal 10 for which registration is requested 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 the registration of the destination candidate and the request destination terminal (the screen of FIG. 22) for which registration is requested as the destination candidate are input. The terminal ID of the request destination terminal indicated by the terminal ID and the logged-in administrator ID are included. Further, when the check box for omitting approval in each registered terminal ID on the destination candidate registration screen shown in FIG. 22 is checked, the registration request is requested to omit the registration approval request to the requesting terminal. 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 the 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. Determine (step S305). Specifically, when the received registration request includes the approval request omission request information, the second determination unit 59 refers to the request destination terminal in which the check box shown in FIG. 22 is checked. Determines that an approval request is not required, and determines that an approval request is required for the request destination terminal for which the above check box is not checked.

Then, when the check box is not checked in FIG. 22, the second determination unit 59 refers to the administrator DB 65, and by referring to the administrator DB 65, the terminal ID (specific terminal) of the request destination terminal requested to be registered as a destination candidate. 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), the process of approval is not required, and the process proceeds to step S307. If it is not associated (step S306, NO), the process proceeds to step S308 for further determination.

Next, in step S308, the second determination unit 59 registers 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 candidates to be made are also managed by other administrators. Then, when there is another administrator ID associated with the administrator ID (step S308, YES), the second determination unit 59 is the first administrator ID associated with the first administrator ID in the administrator DB 65. It is determined whether the attribute information of the above and the second attribute information associated with the second administrator ID are the same (step S309). Then, when the first attribute information and the second attribute information are the same (step S309, YES), the process proceeds to step S307. Further, in step S308, when there is no other administrator ID associated (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 for which registration is requested as a destination candidate. More specifically, for example, it can be realized by the following processing.

That is, when it is selected in step S305 that the approval is not omitted, the request management unit 58 of the terminal management system 50 associates the request source terminal ID included in the received registration request with the request destination terminal ID. 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 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. Then, when the operating state is communicable (for example, online (transmissible)), the second communication unit 51 transmits a destination registration approval request to the communicable transmission terminal 10. An approval request is transmitted to the transmission terminal 10 whose operating state is incommunicable (for example, offline) when the operating state is updated to be communicable.

Next, after step S310, the second determination unit 59 of the transmission management system 40 determines whether or not an approval response has been received from the request destination terminal that has received the approval request (step S311). Then, when the second communication unit 51 receives the approval response, the process proceeds to step S307 (step S311, Yes). 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 becomes the start terminal in the destination list management DB 63, and the request destination terminal becomes the start terminal. In this case, the terminal ID of the requesting terminal is registered as a destination candidate (step S307). That is, the request source terminal and the request destination terminal are registered as destination candidates with each other. 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.

Then, 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 (step S312). 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. If 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 to delete it.

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

Next, the process of deleting the destination candidate will be described.

If NO in step S302, the first determination unit 87 determines whether or not the operation indicates deletion of the destination candidate (step S313). Specifically, when the "Delete destination candidate" button on the management terminal list screen of FIG. 19 is pressed, the first determination unit 87 requests that the first communication unit 81 delete the destination candidate from the administrator terminal 20. Is received or not. In this case, the destination candidates of the transmission terminal 10 checked in the check boxes (CA, C1 to CN) on the management terminal list screen are to be deleted.

If the operation does not indicate the deletion of the destination candidate (step S313, No), the process shown in FIG. 26 ends. In the case of the operation indicating the deletion of the destination candidate (step S313, Yes), the screen creation unit 86 is as shown in FIG. 23 or FIG. 24 on the administrator terminal 20 via the first communication unit 81. The destination candidate deletion screen is displayed, and the first determination unit 87 identifies the 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 with reference to FIGS. 23 and 24. On the destination candidate deletion screens shown in FIGS. 23 and 24, a radio button selected when "delete all destination candidates" and a radio button "delete a designated destination candidate" are displayed. In addition, on the destination candidate deletion screen, a plurality of "delete terminal ID" input fields for the administrator to input the terminal ID of the destination candidate to be deleted, a "delete" button pressed when executing the deletion, and a "delete" button The "Cancel" button that is pressed to cancel the deletion is displayed.

In FIG. 23, the state in which the “Delete designated destination candidate” radio button is pressed by the administrator and the destination candidate terminal ID “01ca” is input in the “Delete terminal ID” input field is shown. .. 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, the shaded area is displayed in the "deleted terminal ID" input field, and the administrator cannot 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 "designated destination candidate" shown in FIG. 23 is further displayed. The case where the "Delete" radio button is pressed, the terminal ID "01ca" is input in the "Delete terminal ID" input field, and the "Delete" button is pressed at the end will be described below.

In this case, in the destination list management DB 63, the start terminal whose destination ID is the terminal ID "01ca" is the start terminal indicated by the terminal ID "01aa" and the terminal ID "01ab", so that the administrator A has the terminal ID. It means that the requesting terminal (10aa, 10ab) indicated by "01aa" and the terminal ID "01ab" is selected. In addition, the administrator A requests the administrator terminal 20a to delete the destination candidate indicated by the terminal ID "01ca" from the destination candidates of each start terminal indicated by the terminal ID "01aa" and the terminal ID "01ab". It means that. As a result, the first communication unit 81 receives the destination candidate deletion request 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 terminal (10aa, 10ab) is specified, and the transmission terminal 10ca indicated by the terminal ID "01ca" is specified as a destination candidate to be deleted.

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

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

<Main effects of the embodiment>
As described above, according to the present embodiment, even when the destination list management DB 63 is managed on the transmission management system 40 side, a desired destination candidate can be deleted from the destination list management DB 63. It works.

Further, the terminal IDs of the plurality of or all the destination candidates can be collectively deleted from the destination candidates of the plurality of or all the start terminals in the destination list management DB 63. This has the effect that the user of each start terminal (transmission terminal 10) can save the trouble of deleting the terminal IDs of a plurality or all of the destination candidates.

[Second Embodiment]
Subsequently, the second embodiment of the present embodiment will be described with reference to FIG. 27. Here, another example of the administrator DB65 shown in the first embodiment will be described. 27 (a) and 27 (b) are conceptual diagrams of the administrator DB according to the second embodiment. As shown in FIG. 27, the administrator DB65'of this embodiment is constructed by two tables. That is, as shown in FIG. 27A, the administrator ID, password, administrator email address, and attribute information are managed in association with each other as the first table. Further, as shown in FIG. 27B, the administrator ID and the terminal ID are managed in association with each other as the second table. As described above, the information shown in FIGS. 27 (a) and 27 (b) corresponds to the "related information" shown in the first embodiment. Since the administrator ID, password, terminal ID, administrator e-mail address, and attribute information have the same contents as those in the first embodiment, their description will be omitted.

In this case as well, the same effect as that of the first embodiment is 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.

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, it can be applied to a television (video) conferencing system, a sound conferencing system, a sound telephone system (including a mobile phone system), a text chat system, a whiteboard sharing system, and the like. Further, the transmission terminal 10 may be a dedicated terminal for the communication system or a dedicated terminal for a game described above, 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 device provided with the functional blocks illustrated in FIG. 7, and may be a dedicated server device or a general-purpose terminal device.

1 Transmission system 10 Transmission terminal 20 Administrator terminal 40 Transmission management system 50 Terminal management system 51 Second communication unit (example of receiving means)
54 Storage / reading processing unit 59 Judgment 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 (example of receiving means)
84 Storage / reading processing unit (example of deletion means)
87 Judgment Department

Japanese Unexamined Patent Publication No. 2006-0744553 Japanese Unexamined Patent Publication No. 2013-085208

Claims (18)

A first destination list associated with the first identification information and a second destination list associated with the second identification information are managed, and the first identification information is stored in the first destination list. The second identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list, and the first identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list. Destination list management means including information,
Receive a request to delete the destination candidate corresponding to the second identification information included in the first destination list from the terminal authenticated based on the identification information of the administrator registered as the administrator information. Receiving means to
Based on the request to delete the destination candidate received by the receiving means, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the second destination list is deleted from the second destination list. A deletion means for deleting the destination candidate corresponding to the identification information of 1 and
A management system characterized by having. The first identification information is included in the plurality of identification information associated as managed with the identification information of said different administrators the first identification information and second identification information,
Claim 1 is characterized in that the request for deleting the destination candidate is a request for which the first identification information among the plurality of identification information is designated by the administrator as a target for deleting the destination candidate. The management system described in. The management system according to claim 2, further comprising a transmission means for transmitting a list of the plurality of identification information to the terminal that has logged in to the management system based on the identification information of the administrator. The transmission means completes the deletion indicating that the deletion has been completed for the destination candidate corresponding to the first identification information and the destination candidate corresponding to the second identification information deleted by the deletion means. The management system according to claim 3, wherein a notification is transmitted. In the request for deleting the destination candidate, when a plurality of specific destination candidates including the destination candidate corresponding to the second identification information are designated as the destination candidates to be deleted from the first destination list, the deletion is performed. means, based on the request to delete the destination candidate, from the first list of destinations, while deleting the plurality of specific destination candidate, associated with each identification information corresponding to said plurality of specific destination candidate The management system according to any one of claims 1 to 4, wherein a destination candidate corresponding to the identification information associated with the specific destination list is deleted from each destination list. The deletion means is associated with the administrator's identification information as a management target based on a request for deleting the specific identification information among a plurality of identification information associated with the administrator's identification information as a management target. The management system according to any one of claims 2 to 4, wherein the specific identification information is deleted from a plurality of identification information. The second identification information included in the first destination list and the first identification information included in the second destination list are approved by the second user in response to the approval request from the first user. The present invention according to any one of claims 1 to 6, wherein the information is the information of the destination candidate registered in each of the first destination list and the second destination list when the response is received. Management system. The first destination list is displayed on the first transmission terminal that requests login to the management system using the first identification information, and by accepting the designation of destination candidates included in the first destination list. The management system according to any one of claims 1 to 7, wherein the list is for establishing a session for transmitting or receiving content data with the specified destination candidate. The first identification information is input by the user to the identification information stored in the first transmission terminal requested to log in to the management system using the first identification information or to the first transmission terminal. The second identification information is the identification information stored in the second transmission terminal that is requested to log in to the management system using the second identification information, or the second transmission terminal. The management system according to any one of claims 1 to 8, characterized in that the identification information is input by the user. Claim 1 is characterized in that the communication between two or more transmission terminals started by using the destination candidate is communication by content data including at least one of image data, sound data, and text data. The management system according to any one of 9 to 9. The first identification information is used when the first user logs in to the management system, and the second identification information is used when the second user logs in to the management system. The management system according to any one of claims 1 to 10 . The management system according to any one of claims 1 to 11, wherein the terminal is an administrator terminal operated by an administrator registered in the administrator information . It is a management method executed by the management system.
The management system
The first and the destination list associated with the first identification information, the second destination list associated with the second identification information management, the first destination list, the first identification information The second identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list, and the first identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list. Has a destination list management means that includes information
Receive a request to delete the destination candidate corresponding to the second identification information included in the first destination list from the terminal authenticated based on the identification information of the administrator registered as the administrator information. Receive step and
Based on the request to delete the destination candidate received by the reception step, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the second destination list is deleted from the second destination list. A deletion step for deleting the destination candidate corresponding to the identification information of 1 and
A management method characterized by executing. A first destination list associated with the first identification information and a second destination list associated with the second identification information are managed, and the first identification information is displayed in the first destination list. The second identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list, and the first identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list. For a management system that has a destination list management means that includes information,
Receive a request to delete the destination candidate corresponding to the second identification information included in the first destination list from the terminal authenticated based on the identification information of the administrator registered as the administrator information. Receive step and
Based on the request to delete the destination candidate received by the reception step, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the second destination list is deleted from the second destination list. A program characterized by executing a deletion step of deleting a destination candidate corresponding to the identification information of 1. It is a system consisting of an administrator terminal operated by an administrator and a management system that manages a destination list including destination candidates.
The management system
A first destination list associated with the first identification information used when the first user logs in to the management system, and a second destination list used when the second user logs in to the management system . The second destination list associated with the identification information of the above is managed, and the first destination list includes the second identification information which is a destination candidate for communication using the first identification information. The second destination list includes a destination list management means including the first identification information which is a destination candidate for communicating using the second identification information.
The administrator terminal is
It has a transmission means for transmitting a request for deleting a predetermined destination candidate specified by the administrator to the management system.
The management system further
Based on the request to delete the predetermined destination candidate, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the first identification is deleted from the second destination list. A system characterized by having a deletion means for deleting destination candidates corresponding to information. It is a method executed by a system consisting of an administrator terminal operated by an administrator and a management system that manages a destination list including destination candidates.
The administrator terminal executes a transmission step of transmitting a request for deleting a predetermined destination candidate specified by the administrator to the management system.
A first destination list associated with the first identification information used when the first user logs in to the management system, and a second destination list used when the second user logs in to the management system . The second destination list associated with the identification information of the above is managed, and the first destination list includes the second identification information which is a destination candidate for communication using the first identification information. In a management system having a destination list management means, the second destination list includes the first identification information which is a destination candidate for communication using the second identification information.
Based on the request to delete the predetermined destination candidate, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the first identification information is deleted from the second destination list. A method characterized by performing a delete step that deletes the destination candidate corresponding to. It is a system consisting of a terminal and a management system.
The management system
A first destination list associated with the first identification information and a second destination list associated with the second identification information are managed, and the first identification information is stored in the first destination list. The second identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list, and the first identification information, which is a destination candidate for communication using the second identification information, is included in the second destination list. Has a destination list management means that includes information
The terminal
When authenticated based on the identification information of the administrator registered as the administrator information, the request for deleting the destination candidate corresponding to the second identification information included in the first destination list is requested. Has a transmission means to transmit to the management system
The management system further
Based on the request for deleting the destination candidate transmitted by the transmission means, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the destination candidate corresponding to the second identification information is deleted from the second destination list. Deletion means for deleting the destination candidate corresponding to the first identification information
A system characterized by having . The terminal, the first destination list associated with the first identification information, and the second destination list associated with the second identification information are managed, and the first destination list includes the first destination list. The second identification information, which is a destination candidate for communication using the identification information, is included in the second destination list, and the second destination list, which is a destination candidate for communication using the second identification information, is included in the second destination list. A method executed by a system including a management system having a destination list management means including the identification information of 1.
In the terminal
When authenticated based on the identification information of the administrator registered as the administrator information, the request for deleting the destination candidate corresponding to the second identification information included in the first destination list is requested. Send step to send to management system
And
In the management system
Based on the request to delete the destination candidate transmitted by the transmission step, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the destination candidate corresponding to the second identification information is deleted from the second destination list. Deletion step to delete the destination candidate corresponding to the first identification information
A method characterized by performing .

Images