JP6750664B2 - 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.

2. Description of the Related Art In recent years, a transmission system for conducting a video conference via a communication network such as the Internet has become widespread in response to a request for reducing travel expenses and travel time. In such a transmission system, when a call is started between a plurality of transmission terminals, image data and audio data are transmitted and received, and a video conference can be realized.

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

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

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

The invention according to claim 1 is a management system for managing destination candidates used when communication is started between two or more communication terminals, wherein the first identification information is transmitted from the first communication terminal. When logging in to the management system based on, transmits a first destination list including destination candidates corresponding to second identification information different from the first identification information to the first communication terminal, When logging in to the management system based on the second identification information transmitted from the second communication terminal, the second destination list including the destination candidates corresponding to the first identification information is set to the second destination list. The first transmitting means for transmitting to the communication terminal, and the administrator terminal including the first communication terminal in the administrator terminal logged in to the management system based on the third identification information corresponding to the administrator. The second transmission means for transmitting the list of the communication terminals managed by the user and the input accepted from the administrator terminal specify and designate the destination candidate corresponding to the second identification information as the destination candidate to be deleted . if the list or al before Symbol first communication terminal for deletion of a destination candidate is selected, based on the request for deleting the destination candidate received from the administrator terminal, the second from the first destination list While deleting the destination candidate corresponding to the identification information, the first identification information is selected from the second destination list associated with the second identification information corresponding to the deletion-requested destination candidate. And a deleting unit that deletes the destination candidate corresponding to.
Further, the invention according to claim 9 is from an administrator terminal that manages two or more communication terminals, and a management system that manages destination candidates used when communication is started between the two or more communication terminals. And a second identification different from the first identification information when the management system logs in to the management system based on the first identification information transmitted from the first communication terminal. A case where a first destination list including destination candidates corresponding to information is transmitted to the first communication terminal and the management system is logged in based on the second identification information transmitted from the second communication terminal. Based on the first transmission means for transmitting the second destination list including the destination candidates corresponding to the first identification information to the second communication terminal, and the third identification information corresponding to the administrator. A second transmitting means for transmitting a list of communication terminals managed by the manager, including the first communication terminal, to an administrator terminal logged in to the management system. Is a display control means for displaying the list, and a destination candidate corresponding to the second identification information is designated as a destination candidate to be deleted, and the first communication from the list is targeted for deletion of the designated destination candidate. When a terminal is selected, a third transmission means for transmitting a deletion request of the destination candidate to the management system, and the management system further based on the deletion request accepted from the administrator terminal. While deleting the destination candidate corresponding to the second identification information from the first destination list, the second candidate associated with the second identification information corresponding to the destination candidate requested to be deleted And a deleting unit that deletes the destination candidate corresponding to the first identification information from the destination list.

As described above, according to the present invention, even when the destination list is managed on the management system side, the destination list of a plurality of communication terminals is desired in response to a request from the administrator who manages the communication terminals. The effect is that the destination candidate of can be deleted.

FIG. 1 is a schematic diagram of a transmission system according to a first embodiment of the present invention. FIG. 2 is a conceptual diagram showing a transmission/reception state of image data, sound data, and various management information in the transmission system. FIG. 3 is a conceptual diagram illustrating the image quality of image data. FIG. 4 is an external view of the transmission terminal. FIG. 5 is a hardware configuration diagram of the transmission terminal. FIG. 6 is a hardware configuration diagram of 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 that form the transmission management system. FIG. 8 is a conceptual diagram of the terminal authentication management DB. FIG. 9 is a conceptual diagram of the terminal management DB. FIG. 10 is a conceptual diagram of the destination list management DB. FIG. 11 is a conceptual diagram of the request management DB. FIG. 12 is a conceptual diagram of the administrator DB. FIG. 13 is a conceptual diagram showing an example of destination candidate registration processing. FIG. 14 is a conceptual diagram showing an example of destination candidate registration processing. FIG. 15 is a conceptual diagram showing an example of destination candidate deletion processing. FIG. 16 is a flowchart showing a management method by the transmission management system. FIG. 17 is a conceptual 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 the confirmation screen for deleting the management terminal. FIG. 22 is a conceptual diagram of the destination candidate registration screen. FIG. 23 is a conceptual diagram of the destination candidate deletion screen. FIG. 24 is a conceptual diagram of the destination candidate deletion screen. FIG. 25 is a flowchart showing the process of registering and deleting the management terminal. FIG. 26 is a flowchart showing the processing of registration and deletion of destination candidates. FIG. 27 is a conceptual diagram of the administrator DB according to the second embodiment.

Embodiments of the present invention will be described below with reference to the drawings.

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

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

Further, the transmission system 1 includes a communication system for mutually transmitting information, emotions, etc. between a plurality of terminals. This communication system is a system for mutually transmitting information, feelings, and the like between a plurality of communication terminals (corresponding to "transmission terminals") via a communication management system (corresponding to "transmission management system" of this embodiment). As an example, a television (video) conference system or the like can be given.

First, the transmission system 1 shown in FIG. 1 has 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 the individual terminals (20a, 20b, 20c, 20d), the plurality of relay devices (30a, 30b, 30c, 30d), the transmission management system 40, the program providing system 90, and the maintenance system 100. 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. Note that text data is another example of the content data. The content data may include at least one of image data, sound data, and text data.

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

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

Further, as shown in FIG. 2, in the transmission system 1, a management information session sei for transmitting and receiving various management information is transmitted between the start terminal and the destination terminal via the terminal management system 50. Established. Further, between the start terminal and the destination terminal, for transmitting and receiving each of four data of high resolution image data, medium resolution image data, low resolution image data, and sound data via the relay device 30. Four sessions are established. Here, these four sessions are collectively shown as an image/sound data session sed. Note that the start terminal and the destination terminal do not necessarily have to go through the relay device 30, 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 this embodiment will be described. As shown in FIG. 3( a ), a low-resolution image that is a base image and has 160 pixels in the horizontal direction and 120 pixels in the vertical direction, and a horizontal image as shown in FIG. 3( b ). There are a medium resolution image having 320 pixels and 240 pixels in the vertical direction and a high resolution image having 640 pixels in the horizontal direction and 480 pixels in the vertical direction as shown in FIG. Of these, when passing through a narrow band path, low-quality image data consisting only of low-resolution image data that is a base image is relayed. When the band is relatively wide, medium resolution image data including low resolution image data serving as a base image and medium resolution image data is relayed. Further, when the band is very wide, high-quality image data including low-resolution image data, medium-image resolution image data, and high-resolution image data, which are base image quality, is relayed.

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

The plurality of routers (70a, 70b, 70c, 70d, 70ab, 70cd) select an optimum path for image data and sound data. In the following, any router among the routers (70a, 70b, 70c, 70d, 70ab, 70cd) is referred to as "router 70".

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

Further, the HD 204 of the program providing system 90 also stores a transmission management program for causing the terminal management system 50 to realize various functions (or causing the terminal management system 50 to function as various means). The transmission management program can be transmitted to the server 50. The HD 204 of the program providing system 90 also stores a destination registration program for causing the destination registration system 80 to realize various functions (or causing the destination registration system 80 to function as various means). The destination registration program can be transmitted to the destination 80. The terminal management program and the destination registration program are handled together 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 uses the communication network 2 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 provision system 90 is performed remotely via. Further, the maintenance system 100 does not go through the communication network 2, but the model number and the manufacturing number in at least one of the transmission terminal 10, the relay device 30, the terminal management system 50, the destination registration system 80, and the program providing system 90. , Maintenance such as sales destination, maintenance inspection, management of failure history, etc.

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

On the other hand, the transmission terminals (10ca, 10cb, 10cc,... ), the relay device 30c, and the router 70c are communicatively connected by a LAN 2c. The transmission terminals (10da, 10db, 10dc,... ), the relay device 30d, and the router 70d are communicably connected by a LAN 2d. The LAN 2c and the LAN 2d 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, LAN 2c is built in the development part, and LAN 2d is built in the development part 2. Area A and area B are communicably connected from the routers (70ab, 70cd) via the Internet 2i.

The terminal management system 50, the destination registration system 80, and the program providing system 90 are communicatively 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 areas.

In the present embodiment, the communication network 2 of the present embodiment is constructed by the LAN 2a, LAN 2b, dedicated line 2ab, Internet 2i, dedicated line 2cd, LAN 2c, and LAN 2d. The communication network 2 may include not only wired communication but also wireless communication such as WiFi (Wireless Fidelity) and Bluetooth (registered trademark).

In addition, in FIG. 1, the four sets of numbers shown below each transmission terminal 10, each relay device 30, the terminal management system 50, each router 70, the destination registration system 80, and the 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”. Although IPv6 may be used instead of IPv4, IPv4 will be used for the sake of simplicity.

In addition, each transmission terminal 10 is not limited to a call between a plurality of business establishments, a call between different rooms within the same business establishment, a call within the same room, a call between outdoors and indoors, or a call between 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 will be the Y-axis direction, and the direction orthogonal to the X-axis direction and the Y-axis direction (vertical direction) will be 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. An exhaust surface 1121 is provided. Thereby, by driving the cooling fan built in the housing 1100, 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 collection hole 1131 is formed on the right wall surface 1130 of the housing 1100, and sounds such as sounds, objects, and noises can be collected by a built-in microphone 114 described later.

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

In the following, the "operation button 108" is used to indicate any operation button among the operation buttons (108a to 108e), and the "operation button 108" is used to indicate any connection port among the connection ports (1132a to 1132c). The connection port 1132" will be used for description.

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

The camera housing 1300 is provided with a built-in camera 112, which will be described later, and can capture images of users, documents, rooms, and the like. A torque hinge 1310 is formed on 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 makes a pan angle θ2 of ±180 degrees with respect to the arm 1200 when the state shown in FIG. 4 is 0 degree. And a tilt angle .theta.3 of .+-.45 degrees are rotatable in the vertical and horizontal directions.

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

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

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

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

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

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

The camera 112, the microphone 114, and the speaker 115 do not necessarily have to be built in, and may have a configuration in which only an external camera, an external microphone, and an external speaker can be connected. Further, the recording medium 106 is configured to be removable 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 in a computer-readable recording medium such as the recording medium 106 and distributed. The transmission terminal program may be stored in the ROM 102 instead of the flash memory 104.

FIG. 6 is a hardware configuration diagram of 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 overall operation of the terminal management system 50, a ROM 202 that stores a program used to drive the CPU 201 such as an IPL, a RAM 203 that is used as a work area of the CPU 201, and a variety of terminal management programs. A HD 204 that stores data, an HDD (Hard Disk Drive) 205 that controls reading or writing of various types of data according to the control of the CPU 201, a medium that controls reading or writing (storing) of data to a recording medium 206 such as a flash memory. Drive 207, cursor 208, display for displaying various information such as menus, windows, characters, images, network I/F 209 for data transmission using communication network 2, input of characters, numerical values, various instructions A keyboard 211 having a plurality of keys for the purpose, a mouse 212 for selecting and executing various instructions, selecting a processing target, moving a cursor, and a CD-ROM (Compact Disc Read Only) as an example of a removable recording medium. A memory (ROM) 213 is provided with a CD-ROM drive 214 for controlling the reading or writing of various data, and a bus line 210 such as an address bus or a data bus for electrically connecting the above-mentioned components.

The terminal management program is a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 for distribution. .. 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 HD 204 stores a relay device program for controlling the relay device 30. Also in this case, the relay device program is a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 for distribution. Good. 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, its explanation is omitted. However, in the HD 204, a destination registration program for controlling the destination registration system 80 is recorded. Also in this case, the destination registration program is a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 for distribution. Good. 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, in the HD 204, a program providing program for controlling the program providing system 90 is recorded. Also in this case, the program providing program is a file in an installable format or an executable format, and may be recorded in a computer-readable recording medium such as the recording medium 206 or the CD-ROM 213 for distribution. Good. 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 removable recording medium, it is configured to be provided by being recorded on a computer-readable recording medium such as a CD-R (Compact Disc Recordable), a DVD (Digital Versatile Disk), and a Blu-ray disc. You may.

<Functional configuration of the embodiment>
In particular, the functional configurations of the terminal management system 50 and the destination registration system 80 will be described below with reference to FIGS. 7 to 12. 7. FIG. 7 is a functional block diagram of the terminal management system and the destination registration system that form 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/readout 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 piece of information indicating the terminal ID and the password is managed as related information associated with each other. This terminal ID is identification information for identifying the transmission terminal 10. The terminal ID (an example of terminal identification information) may be identification information stored in advance in the transmission terminal 10 or may be identification information input by the user of the transmission terminal 10 to the transmission terminal 10. Good. The password is a password for the transmission terminal 10 to log in to the transmission management system 40 with the terminal ID. The record of the terminal authentication management DB 61 may have columns (fields) other than the above.

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

FIG. 10 is a conceptual diagram of the destination list management DB 63. In the destination list management DB 63, the terminal ID of the start terminal and the terminal ID of the destination candidate that can be the destination terminal are managed as associated 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 request management DB 64. In the request management DB, the terminal ID of the request source terminal and the terminal ID of the request destination terminal are managed as associated information associated with each other. The terminal ID of the request source terminal is identification information for identifying the transmission terminal 10 that has requested the registration of the destination candidate. The terminal ID of the request destination terminal is identification information for the transmission terminal 10 identified by the request source terminal ID to identify the transmission terminal 10 requesting to be registered as a destination candidate. The record of the request management DB 64 may have columns 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 email 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.

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 email address is the email address of the administrator. The attribute information is affiliation information indicating a department to which an administrator belongs in an organization such as a company, post information indicating a post, and authority information indicating authority. The attribute information may be any one of these pieces of information (affiliation information, post information, authority information), or may be information that is a combination of at least two of these pieces of information. .. The record of the administrator DB 65 may have columns other than the above.

Further, in the present embodiment, in FIG. 1, the administrator A uses the administrator terminal 20a and manages a plurality of transmission terminals (10aa, 10ab,...) Connected to the LAN 2a as its own management terminal. doing. The administrator B uses the administrator terminal 20b and manages a plurality of transmission terminals (10ba, 10bb,...) Connected to the LAN 2b as its own management terminal. The administrator C uses the administrator terminal 20c and manages a plurality of transmission terminals (10ca, 10cb,...) Connected to the LAN 2c as its own management terminal. The administrator D uses the administrator terminal 20d and manages a plurality of transmission terminals (10da, 10db,...) Connected to the LAN 2d as its 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 performs authentication when the transmission terminal 10 logs in to the terminal management system 50 (transmission management system 40) in order to start communication with 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 a search key, and stores the terminal authentication management DB 61 in the storage unit 60. Search for. The second authentication unit 52 authenticates whether or not to permit login to the terminal management system 50 by determining whether or not the search key matches the information in the terminal authentication management DB 61.

The terminal management unit 56 manages the operating state of the transmission terminal 10 that has requested the login to the transmission management system 40. The terminal management unit 56 updates the record in the terminal management DB 62 corresponding to the terminal ID of the transmission terminal 10 that has requested the login to the transmission management system 40. Specifically, if the login is successful, the "operating state" is changed from offline to online (transmission possible), and the "reception date and time" and "IP address" are updated.

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

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

The second extraction unit 55 also searches the destination list management DB 63 using the terminal ID of the transmission terminal 10 that has made a login request to the transmission management system 40 as a search key, and uses the terminal ID of the transmission terminal 10 that has made a login request 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 extracting unit 55 extracts the corresponding operating state by searching the terminal management DB 62 by using the terminal ID of the start terminal that has registered the login request of the transmission terminal 10 as a destination candidate as a search key. You can

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

The destination list management unit 57 adds, changes, and deletes records in the destination list management DB 63. For example, the destination list management unit 57 extracts a record in the destination list management DB 63 in which the terminal ID of the request source terminal managed in the request management DB 64 and the terminal ID of the starting 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/readout processing unit 54 performs a process of storing data in the storage unit 60. Further, the storage/readout processing unit 54 performs processing for reading out 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 in the related information (first determination). When the second determination unit 59 determines that the terminal ID is not associated by the first determination, another administrator ID (second administrator ID) associated with this terminal ID in the related information is It is determined whether there is any (second determination). Further, when the second judgment unit 59 judges that the second manager ID exists by the second judgment, the attribute information (first attribute) associated with the first manager ID in the related information is obtained. Information) and the attribute information (second attribute information) associated with the second administrator ID in the related information are determined to be the same (third determination).

(Functional configuration of destination registration system)
Next, the destination registration system 80 will be described. The destination registration system 80 includes a first communication unit 81, a first authentication unit 82, and a display control unit 83 according to the hardware configuration and the terminal management program shown in FIG. Furthermore, the display control unit 83 includes a storage/readout 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/readout processing unit 84, and the first extraction unit 85 have the same functions as the second communication unit 51, the storage/readout processing unit 54, and the second extraction unit 55, respectively. , Description is omitted. Although the destination registration system 80 does not include a storage unit, by accessing the storage unit 60 of the terminal management system 50 via the communication network 2, the storage/read processing unit 84 and the first extraction unit 85 The same functions as the storage/read processing unit 54 and the second extraction unit 55 can be realized.

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

In addition, the first authentication unit 82 uses the terminal ID (or administrator ID) and password included in the login information received by the first communication unit 81 as a search key, and uses the terminal authentication management DB 61 (or administrator DB 65) of the storage unit 60. ) Is searched. The first authentication unit 82 permits the login to the destination registration system 80 (transmission management system 40) by determining whether the search key matches the information in the terminal authentication management DB 61 (or the administrator DB 65). 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. 22) and the like. The screen creation unit 86 creates a screen by, for example, HTML (HyperText Markup Language).

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

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

First, the transmission terminal 10aa transmits to the transmission management system 40 a destination candidate registration request indicating that the transmission terminal 10da is requested to be registered as a destination candidate of the transmission terminal 10aa (ST11). Next, the transmission management system 40 transmits, to the transmission terminal 10da, an approval request indicating that the transmission terminal 10da requests approval 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 receiving a response indicating approval, the transmission management system 40 registers the transmission terminal 10da in the destination list management DB 63 as a destination candidate in the transmission terminal 10aa, and notifies the transmission terminal 10aa and the transmission terminal 10da that the destination registration is completed. A registration completion notification indicating is transmitted (ST14).

(Second pattern)
The second pattern is shown in FIG. 14, in which the user of the transmission terminal 10aa (the first user aa) transmits the same organization (for example, the same “department”) as a destination candidate to its own destination list. The registration processing when registering the terminal 10ab is shown. Note that FIG. 14 is a conceptual diagram showing an example of the destination candidate registration processing.

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

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

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

First, the administrator terminal 20a issues a destination candidate deletion request indicating that the destination candidates for the transmission terminal 10ca are collectively deleted from the destination lists of the transmission terminal 10aa and the transmission terminal 10ab. (ST31). Next, the transmission management system 40 collectively deletes the destination candidates as the transmission terminal 10ca from the destination lists of the transmission terminal 10aa and the transmission terminal 10ab (ST32). At this time, the destination candidates for 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 request deletion of destination candidates, respectively, the administrator A Deletes them in a lump and sends a notification of deletion completion indicating that the deletion of the destination is completed to each transmission terminal (10aa, 10ab, 10ca) (ST33).

<Operation or Processing of Embodiment>
Next, the operation or processing of this 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 or not the login request is accepted by the administrator ID from the administrator terminal 20 operated by the administrator via the communication network 2 (step S101). When 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 user by the terminal ID) (step S101, 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 registers the destination candidates in all the destination lists of the management terminal (the transmission terminal 10 under the control). You can

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 the authentication screen shown in FIG. 17, for example, on the administrator terminal 20 operated by the administrator via the first communication unit 81. Let

Each screen data in FIGS. 17 to 25 is held by the screen creation unit 86 itself. The screen data shown in FIGS. 17 to 25 is stored in the storage unit 60, and the storage/read processing unit 84 reads the screen data from the storage unit 60 according to an instruction from the screen creation unit 86. 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 the password. It is determined whether the person is registered in the DB 65 (step S102). Then, when the administrator information is registered in the administrator DB 65 (step S102, No), the first authentication unit 82 permits the login (step S104). On the other hand, if the administrator information is not registered in the administrator DB 65 (step S102, Yes), the screen creating unit 86 displays the information 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 on the registration screen in the administrator DB 65, the user logs in to the destination registration system 80 (step S103). An example of the case where the administrator information is not registered in the administrator DB 65 is, for example, the case where the administrator is used for the first time using the initial setting password.

FIG. 18 is a conceptual diagram of the administrator registration screen. In step S103, the administrator registration screen of FIG. 18, for example, 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 starting terminal in the destination list management DB 63 (the same as the terminal ID in the terminal management DB 62), and the terminal ID of the destination candidate.

In order for the screen creation unit 86 to create the management terminal list screen shown in FIG. 19, specifically, the first extraction unit 85 manages the administrator ID received by the destination registration system 80 as a search key. The person DB 65 is searched to acquire the terminal ID of the administrator terminal associated with the administrator ID. As a result, the transmission terminal 10 managed by a specific manager can be specified. Further, the first extracting unit 85 searches for the terminal ID of the starting terminal in the destination list management DB 63 using the acquired terminal IDs as search keys, and acquires the terminal IDs of the destination candidates associated with each terminal ID. The first extraction unit 85 also 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. In this way, the screen creation unit 86 can create the management terminal list screen based on the information acquired by the first extraction unit 85.

On the management terminal list screen, 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 a terminal ID are displayed for each terminal ID. Further, a check box CA for collectively selecting all terminal IDs is displayed. In addition, a “logout” button for logging out is also displayed on the management terminal list screen. Each check box or each button is selected by being pressed by the administrator.

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

Next, the screen creation unit 86 determines whether the "register destination candidate" button or the "delete destination candidate" button has been selected on the administrator terminal 20 side (step S108). When the "destination candidate registration" button or the "destination candidate deletion" button is selected (step S108, Yes), the process (registration and deletion of destination candidates) described below is performed (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 by the administrator is completed depending on whether the “logout” button has been 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). When the "logout" button is not selected (No in step S110), the process returns to step S106.

(Process 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. FIG. 20 is a conceptual diagram of the management terminal registration screen. FIG. 21 is a conceptual diagram of the 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 judgment unit 87 judges whether the administrator selects the “management terminal registration” button or the “management terminal deletion” button on the management terminal list screen shown in FIG. It is determined whether the management terminal is registered (step S201). When the “registration of management terminal” button is selected (Yes at step S201), the screen creation unit 86 notifies the administrator terminal 20 via the first communication unit 81 as shown in FIG. Send the data of the management terminal registration screen.

On the other hand, the administrator terminal 20 displays the management terminal registration screen as shown in FIG. On this management terminal registration screen, a plurality of "registered terminal ID" input fields are displayed for the administrator to newly input the terminal ID of the transmission terminal 10 that the administrator desires to register as his or her own management terminal. Then, when the administrator inputs the terminal ID of the transmission terminal 10 in the “registration terminal ID” input field and presses the “registration” button, the administrator terminal 20 displays the terminal input in the “registration terminal ID” input field. A registration request including the ID and the administrator ID of the entered administrator is transmitted to the destination registration system 80. Thereby, the first communication unit 81 of the destination registration system 80 receives the registration request. Then, the storage/read processing unit 84 stores the registered terminal ID in the administrator DB 65 of the terminal management system 50 in the column of the terminal ID in the record including the administrator ID used for the login processing in step S101. The terminal ID input as is added (step S202).

On the other hand, if the management terminal is not registered (step S201, No), the first determination unit 87 determines whether the transmission terminal 10 is deleted (step S203). If the management terminal is deleted (step S203, Yes), the screen creation unit 86 checks (selects) the check boxes (CA, C1 to CN) in FIG. 19 via the first communication unit 81. By transmitting a deletion request including the ID and the administrator ID of the entered administrator to the terminal management system 50, the storage/read processing unit 54 of the terminal management system 50 manages the administrator ID used for the login processing. The terminal ID requested to be deleted is deleted from the record of the administrator DB 65 that has been made (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 management terminal deletion confirmation screen shown in FIG. 21 via the first communication unit 81. FIG. 21 is a confirmation screen for deleting the management terminal. In this case, if the administrator presses the "OK" button, the process of step S204 is executed, and if the "Cancel" button is pressed, the process of step S204 is not executed.

Note that FIG. 20 illustrates an example in which the administrator inputs the terminal ID, but the present invention is not limited to this. 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 a path).

(Process of registration and deletion of destination candidates)
Next, processing of registration and deletion of destination candidates 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 destination candidate deletion screens. FIG. 26 is a flowchart showing the processing of registration and deletion of destination candidates. Here, an example of (Pattern 3) shown in FIG. 15 will be described.

First, the first determination unit 87 receives a request from the administrator terminal 20a by the administrator A by accepting a request source terminal that desires registration or deletion of a request 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 request source terminal on the management terminal list screen shown in FIG. 19 and presses the “destination candidate registration” button, The request source terminal desiring 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 “destination candidate deletion” button, The request source terminal desiring to be deleted is specified.

Next, the first determination unit 87 determines whether or not the operation such as the pressing received from the administrator terminal 20a is the operation indicating the registration of the destination candidate (step S302). For example, the first determination unit 87 determines whether or not the “register destination candidate” 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 an operation indicating registration of a destination candidate (step S302, Yes), the display control unit 83 causes the management terminal 20a to display the destination candidate registration screen as shown in FIG. 22 via the first communication unit 81. Data is transmitted and the destination candidate registration screen is displayed on the management terminal 20a (step S303).

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

Next, returning to FIG. 26, the administrator A inputs a desired terminal ID into the “registration terminal ID” input field of the destination candidate registration screen shown in FIG. 22, and presses the “registration” button. Thus, the designation of the transmission terminal 10 requested to be registered as a destination candidate is accepted (step S304), and the terminal ID of the transmission terminal 10 requested to be registered is transmitted from the destination registration system 80 to the terminal management system 50. More specifically, the first communication unit 81 of the destination registration system 80 transmits a destination candidate registration request to the second communication unit 51 of the terminal management system 50. In this registration request, the terminal ID of the request source terminal (request source terminal specified in step S301) requesting registration of the destination candidate and the request destination terminal requested to be registered as the destination candidate (input on the screen of FIG. 22). The terminal ID of the request destination terminal (identified by the terminal ID) and the administrator ID during login are included. Further, when the check box of approval omission in each registration terminal ID on the destination candidate registration screen shown in FIG. 22 is checked, the registration request requests the request destination terminal to omit the approval request for registration. The 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. It is determined (step S305). Specifically, when the received registration request includes the approval request omission request information, the second judgment unit 59 sends the request destination terminal whose check box is shown in FIG. Judges that the approval request is not necessary, and judges that the approval request is necessary for the request destination terminal whose 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 to refer to the terminal ID of the request destination terminal requested to be registered as the destination candidate (specific terminal). It is determined whether the ID) and the manager ID (first manager ID) are associated with each other (step S306). Then, if they are associated (step S306, YES), it is determined that the approval process is not necessary, and the process proceeds to step S307. If they are not associated (step S306, NO), the process proceeds to step S308 for further determination.

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

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

That is, if it is selected in step S305 that the approval is not omitted, the request management unit 58 of the terminal management system 50 creates a new association of the request source terminal ID and the request destination terminal ID included in the received registration request. The record is additionally stored in the request management DB 64. Then, the second extraction unit 55 of the terminal management system 50 extracts the corresponding 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 (transmittable), etc.), 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). When the second communication unit 51 receives the approval response (Yes in step S311), the process proceeds to step S307. In step S307, the destination list management unit 57 registers the terminal ID of the request destination terminal as a destination candidate in the destination list management DB 63 as the destination candidate when the request source terminal becomes the start terminal, and the request destination terminal becomes the start terminal. In this case, the terminal ID of the request source 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. Note that in step S307, the request source terminal and the request destination terminal may not be registered as destination candidates with each other, and the terminal ID of the request destination terminal may only be registered with the destination candidate of the request source terminal.

Then, when the registration is completed, the second communication unit 51 transmits a notification of registration completion to the request source terminal and the request destination terminal (step S312). When the above processing is completed, the request management unit 58 of the terminal management system 50 deletes the registered record from the request management DB 64. If no omission of approval is 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.

In addition, even if it is 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 to the approval request for registering the destination candidate, and further, whether or not the response indicates approval.

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

In the case of NO in step S302, the first determination unit 87 determines whether or not the operation is an operation indicating deletion of a destination candidate (step S313). Specifically, when the “destination candidate deletion” button on the management terminal list screen of FIG. 19 is pressed, the first determination unit 87 causes the first communication unit 81 to request the deletion of the destination candidate from the administrator terminal 20. Is received. In this case, the destination candidates of the transmission terminal 10 whose check boxes (CA, C1 to CN) on the management terminal list screen are checked are targets for deletion.

Then, when the operation does not indicate the deletion of the destination candidate (step S313, No), the processing illustrated in FIG. 26 ends. In the case of an operation indicating the deletion of the destination candidate (step S313, Yes), the screen creating unit 86 causes the administrator terminal 20 to display the screen as illustrated in FIG. 23 or FIG. 24 via the first communication unit 81. A destination candidate deletion screen is displayed, and the first determination unit 87 specifies 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. In the destination candidate deletion screens shown in FIGS. 23 and 24, a radio button selected when “delete all destination candidates” and a “delete specified destination candidate” radio button are displayed. Further, on the destination candidate deletion screen, a plurality of “deleted terminal ID” input fields for the administrator to input the terminal ID of the destination candidate to be deleted, a “delete” button that is pressed when executing deletion, and The "Cancel" button that is pressed to cancel the deletion is displayed.

FIG. 23 shows a state in which the administrator has pressed the “Delete specified destination candidate” radio button and entered the terminal candidate terminal ID “01ca” in the “deleted terminal ID” input field. .. On the other hand, FIG. 24 shows a state where the “delete all destination candidates” radio button is pressed. In the case shown in FIG. 24, since the deletion targets are all the destination candidates, the “deleted terminal ID” input field is shaded and the administrator cannot enter the terminal ID.

Here, the third pattern shown in FIG. 15 will be described. That is, the administrator A checks the check box CA on the management terminal list screen shown in FIG. 19 and presses the “destination candidate deletion” button, and then the “specified destination candidate” shown in FIG. A case will be described below in which the "Delete" radio button is pressed, the terminal ID "01ca" is input in the "Deleted terminal ID" input field, and the "Delete" button is finally pressed.

In this case, in the destination list management DB 63, the starting terminal having the terminal ID “01ca” as the destination candidate is the starting terminal indicated by the terminal ID “01aa” and the terminal ID “01ab”, so the administrator A This means that the request source terminals (10aa, 10ab) indicated by "01aa" and the terminal ID "01ab" have been selected. In addition, the administrator terminal 20a requests the deletion of the destination candidate indicated by the terminal ID “01ca” from the destination candidates of the respective start terminals indicated by the terminal ID “01aa” and the terminal ID “01ab” by the administrator A. It will be. Thereby, the first communication unit 81 receives the 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 terminals. The transmission terminals (10aa, 10ab) are specified, and the transmission terminal 10ca indicated by the terminal ID “01ca” is specified as the destination candidate to be deleted.

Next, the storage/read processing unit 84 determines that the terminal ID of the start terminal in the destination list management DB 63 is “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 IDs of the destination candidates (step S315). As a result, the second communication unit 51 transmits a deletion completion notification indicating that the deletion of the destination has been completed to the request source terminal (transmission terminal (10aa, 10ab)) and the request destination terminal (transmission terminal 10ca) ( Step S316).

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

<Main effects of the embodiment>
As described above, according to the present embodiment, it is possible to delete a desired destination candidate from the destination list management DB 63 even when the destination list management DB 63 is managed on the transmission management system 40 side. Produce an effect.

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

[Second Embodiment]
Then, the 2nd Embodiment of this Embodiment is described using FIG. Here, another example of the administrator DB 65 shown in the first embodiment will be described. 27A and 27B are conceptual diagrams of the administrator DB according to the second embodiment. As shown in FIG. 27, the administrator DB 65' of this embodiment is constructed by two tables. That is, as shown in FIG. 27A, the administrator ID, password, administrator email address, and attribute information are associated and managed as the first table. Further, as shown in FIG. 27B, the administrator ID and the terminal ID are associated and managed as the second table. As described above, the information shown in FIGS. 27A and 27B corresponds to the “related information” shown in the first embodiment. Note that the administrator ID, password, terminal ID, administrator email address, and attribute information have the same contents as in the first embodiment, so a description thereof will be omitted.

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

[Other Embodiments]
In the above embodiment, at least one of the processes of step S306 and 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 video (video) conference system, a sound conference system, a sound telephone system (including a mobile phone system), a text chat system, a whiteboard sharing system, or the like. 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 information processing devices including the functional blocks illustrated in FIG. 7, and may be dedicated server devices or general-purpose terminal devices.

1 transmission system 10 transmission terminal 20 administrator terminal 40 transmission management system 50 terminal management system 51 second communication unit (an example of receiving means)
54 storage/readout 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 Request management DB
65 Administrator DB
80 Address Registration System 81 First Communication Unit (Example of Receiving Unit)
84 storage/reading processing unit (an example of a deleting unit)
87 Judgment section

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

Claims (10)

A management system for managing destination candidates used when starting communication between two or more communication terminals,
When logging in to the management system based on the first identification information transmitted from the first communication terminal, a first candidate including a destination candidate corresponding to the second identification information different from the first identification information. It corresponds to the first identification information when the destination list is transmitted to the first communication terminal and the management system is logged in based on the second identification information transmitted from the second communication terminal. First transmitting means for transmitting a second destination list including destination candidates to the second communication terminal;
A second transmitting a list of communication terminals managed by the administrator including the first communication terminal to an administrator terminal logged in to the management system based on the third identification information corresponding to the administrator. Transmission means,
The input received from the administrator terminal, the destination candidate corresponding to the second identification information is designated as a destination candidate to be deleted, the list or al before Symbol first communication for deletion of the specified destination candidate When the terminal is selected , based on the request for deleting the destination candidate received from the administrator terminal , while deleting the destination candidate corresponding to the second identification information from the first destination list, the deletion request Deleting means for deleting the destination candidate corresponding to the first identification information from the second destination list associated with the second identification information corresponding to the destination candidate having
A management system comprising: The management system according to claim 1, wherein
The transmission means includes a destination candidate indicated by the first destination candidate identification information corresponding to the first identification information deleted by the deletion means, and a second destination corresponding to the second identification information. A management system, characterized in that a deletion completion notification indicating that the deletion is completed is transmitted to the destination candidate indicated by the candidate identification information. If a particular destination candidates that are associated with more specific identification information including a pre-Symbol first identification information is specified as a destination candidate to be deleted, the deletion unit, based on the deletion request received, the The management system according to claim 1, wherein each specific destination candidate associated with a plurality of specific identification information is deleted. The first destination list is displayed on the first communication terminal, and by accepting the designation of the destination candidate included in the first destination list, the designated destination candidate and the content data are transmitted or received. The management system according to claim 1, wherein the management system is a list for establishing a session. The first identification information transmitted from the first communication terminal is identification information stored in the first communication terminal or identification information input by a user to the first communication terminal. The second identification information transmitted from the second communication terminal is identification information stored in the second communication terminal or identification information input by the user to the second communication terminal. The management system according to any one of claims 1 to 4, wherein: The communication between two or more communication 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 items 1 to 5. A management method executed by a management system for managing destination candidates used when starting communication between two or more communication terminals,
When logging in to the management system based on the first identification information transmitted from the first communication terminal, a first candidate including a destination candidate corresponding to the second identification information different from the first identification information. It corresponds to the first identification information when the destination list is transmitted to the first communication terminal and the management system is logged in based on the second identification information transmitted from the second communication terminal. A first transmitting step of transmitting a second destination list including destination candidates to the second communication terminal;
A second transmitting a list of communication terminals managed by the administrator including the first communication terminal to an administrator terminal logged in to the management system based on the third identification information corresponding to the administrator. A send step,
The input received from the administrator terminal, the destination candidate corresponding to the second identification information is designated as a destination candidate to be deleted, the list or al before Symbol first communication for deletion of the specified destination candidate When the terminal is selected , based on the request for deleting the destination candidate received from the administrator terminal , while deleting the destination candidate corresponding to the second identification information from the first destination list, the deletion request A deletion step of deleting a destination candidate corresponding to the first identification information from the second destination list associated with the second identification information corresponding to the destination candidate having
A management method characterized by executing. On the computer,
Based on the first identification information transmitted from the first communication terminal, when the management system that manages a destination candidate used when starting communication between two or more communication terminals is logged in, A first destination list including destination candidates corresponding to second identification information different from the first identification information is transmitted to the first communication terminal, and the second identification transmitted from the second communication terminal is transmitted. A first transmission step of transmitting a second destination list including destination candidates corresponding to the first identification information to the second communication terminal when logging in to the management system based on information;
A second transmitting a list of communication terminals managed by the administrator including the first communication terminal to an administrator terminal logged in to the management system based on the third identification information corresponding to the administrator. A send step,
The input received from the administrator terminal, the destination candidate corresponding to the second identification information is designated as a destination candidate to be deleted, the list or al before Symbol first communication for deletion of the specified destination candidate When the terminal is selected , based on the request for deleting the destination candidate received from the administrator terminal , while deleting the destination candidate corresponding to the second identification information from the first destination list, the deletion request A deletion step of deleting a destination candidate corresponding to the first identification information from the second destination list associated with the second identification information corresponding to the destination candidate having
A program to execute. A system comprising an administrator terminal that manages two or more communication terminals, and a management system that manages destination candidates used when communication is started between the two or more communication terminals,
The management system is
When logging in to the management system based on the first identification information transmitted from the first communication terminal, a first candidate including a destination candidate corresponding to the second identification information different from the first identification information. It corresponds to the first identification information when the destination list is transmitted to the first communication terminal and the management system is logged in based on the second identification information transmitted from the second communication terminal. First transmitting means for transmitting a second destination list including destination candidates to the second communication terminal;
A second transmitting a list of communication terminals managed by the administrator including the first communication terminal to an administrator terminal logged in to the management system based on the third identification information corresponding to the administrator. Transmission means,
Have
The administrator terminal is
Display control means for displaying the list,
When the destination candidate corresponding to the second identification information is designated as the destination candidate to be deleted and the first communication terminal is selected from the list as the target of the designated destination candidate to be deleted , the destination candidate is deleted. Third transmitting means for transmitting a request to the management system,
Have
The management system further includes
Based on the deletion request received from the administrator terminal, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the first candidate corresponding to the deletion candidate for which the deletion request is made. Deleting means for deleting a destination candidate corresponding to the first identification information from the second destination list associated with the second identification information;
A system comprising: A method executed by a system comprising an administrator terminal that manages two or more communication terminals and a management system that manages destination candidates used when communication is started between the two or more communication terminals,
In the management system,
When logging in to the management system based on the first identification information transmitted from the first communication terminal, a first candidate including a destination candidate corresponding to the second identification information different from the first identification information. It corresponds to the first identification information when the destination list is transmitted to the first communication terminal and the management system is logged in based on the second identification information transmitted from the second communication terminal. A first transmitting step of transmitting a second destination list including destination candidates to the second communication terminal;
A second transmitting a list of communication terminals managed by the administrator including the first communication terminal to an administrator terminal logged in to the management system based on the third identification information corresponding to the administrator. A send step,
Run
In the administrator terminal,
A display control step of displaying the list,
When the destination candidate corresponding to the second identification information is designated as the destination candidate to be deleted and the first communication terminal is selected from the list as the target of the designated destination candidate to be deleted , the destination candidate is deleted. A third sending step of sending a request to the management system;
Run
In the management system,
Based on the deletion request received from the administrator terminal, the destination candidate corresponding to the second identification information is deleted from the first destination list, while the first candidate corresponding to the deletion request is deleted. A deletion step of deleting a destination candidate corresponding to the first identification information from the second destination list associated with the second identification information;
A method of performing.